Web Gateway 7.1.5 Product Guide - McAfee

List of incident IDs
Appendix: Configuration lists
List of incident IDs
The following table provides a list of the incident IDs that can be used in web security rules on the
appliance.
The incident IDs are grouped in numerical ranges as follows:
1–199: Incidents related to the appliance system
200–299: Core subsystem incidents
300–399: Update module incidents
500–599: Log File Manager incidents
600–699: sysconfd daemon incidents
700–799: Proxy module incidents
800–899: Virus and malware filtering incidents
900-999: Authentication incidents
1000–1099: URL filtering incidents
1600–1699: SSL certification incidents
3000–3200: Central management incidents
For more information on how to use incident IDs and other incident properties, see Error handling using
incidents.
For individual incident properties, see List of properties.
Table A-4 List of incident IDs
Incident ID Description Origin number and name Severity
5 A rule that uses an incident property has been executed. 1 System 7
20 RAID monitoring reports critical status or failure of one 1 Health monitor 4 (or 3 for
or more hard disks.
hard-disk
failure)
21 S.M.A.R.T health check reports an error on a HDD hard
disk.
1 Health monitor 4
22 File system usage exceeds a configured limit. 1 Health monitor 4
23 Memory usage exceeds a configured limit. 1 Health monitor 4
24 System load exceeds a configured limit. 1 Health monitor 4
200 The license expiration date has been checked. 2 Core 6
201 The appliance has successfully completed all FIPS 140-2
self-tests.
2 Core 6
301 Download of update files was stopped because there is
not enough disk space.
3 Updater 3
302 Download of product x failed for node y in central
management.
3 Updater 3
303 The update module reports that update of product x
failed on node y in central management.
3 Updater 3
304 The update module received a report from an update
server that status of product x is up-to-date.
3 Updater 3
305 The update module could not connect to an update
server.
3 Updater 3
501 The Log File Manager failed to push log files. 5 Log File Manager 3
601 Data packages involved in a yum update require an
restart of the appliance to become effective.
6 mwg-update 4
666 A FIPS 140-2 self-test failed on node y in central
management. The node is running in non-FIPS mode.
1 FIPS 0
McAfee Web Gateway 7.1.5 Product Guide 327