Cisco MCS-7825-H3-IPC1 Service Guide - Page 245

Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages Cisco Unified Serviceability Alarms and CiscoLog Messages recognizable facilities: AAAA, SYS, ATM, BGP, CRYPTO, ETHERNET, FTPSERVER, CONFIG_I, IP, ISDN, RADIUS, SNMP, SYS, TCP, UBR7200, X25. A complete list of defined facilities is available in Cisco IOS documentation at http://. Outside of the Cisco IOS, there can be multiple applications on the same host originating log messages. Therefore, it is necessary that APPNAME field identify the specific application. Additional source identifiers are available in the HOST field as well as various standard TAGS field values (pname, pid, comp, etc). The APPNAME field must consist of at least two uppercase letters or digits and may include underscore characters. More precisely, the acceptable character set is limited to characters with the following ASCII decimal values: 48-57 (numbers), 65-90 (upper-case letters) and 95 (underscore). The length of the APPNAME field must not exceed 24 characters. Application names cannot conflict with other Cisco software applications and with Cisco IOS facilities. On the Solaris platform, it is recommended (not required) that the application name values used in the APPNAME field be consistent with those used for the application installation package name, only in upper case and without the CSCO prefix. For example, an application registering as "CSCObacc" on Solaris should use "BACC" as the value of the APPNAME field. Some applications may choose to specify a version as part of the APPNAME field. This is acceptable and may be useful in cases where the meaning of certain messages is redefined from one release to another. For example, an APPNAME value could be "BACC_2_5" for BACC version 2.5. The use the version within an application name is optional and may be introduced by applications in any release. SEVERITY Field The SEVERITY field is a numeric value from 0 to 7, providing eight different severities. The severities defined below match Cisco IOS severity levels. They are also standard syslog severities. It is important that messages use the correct severity. An error in a certain component may be severe as far as the component is concerned, but if the overall application handles it gracefully, then the severity may be lower for the application as a whole. Table 6-2 lists guidelines that should be followed in determining the severity of a message. Table 6-2 Name and Severity Level and Descriptions in Error Messages Name/ Severity Level Emergency (0) Description System or service is unusable. Examples: • Service repeatedly fails to startup • System ran out of disk space while disk space is essential for this system to operate Alert (1) • Application requires root privileges to run but does not have them Action must be taken immediately. Examples: • Application is about to run out of licenses • Application is about to run out of disk space • Too many unauthorized access attempts detected • Denial of service attack is detected OL-22523-01 Cisco Unified Communications Manager Managed Services Guide 6-11