Cisco MCS-7825-H3-IPC1 Service Manual page 247

Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Table 6-2
Name/
Severity Level
Informational (6)
Debug (7)
If an application uses a default severity level to determine which messages should be logged, then it is
recommended that this level be set at 5 (notice). This ensures that all messages of severity 5 or higher
are logged by default.
MSGNAME Field
The MSGNAME field of the HEADER uniquely identifies the message within the context of a given
APPNAME. A fixed severity and logical meaning is associated with a specific MSGNAME within a
specific APPNAME. In other words, the same message name cannot appear with different severity or a
completely different logical meaning for the same APPNAME value even if the message is originated
by a different process.
Message names are only unique within a given application (a given APPNAME value) unless the
message is one of the standard messages. Thus, applications interpreting CiscoLog messages should be
careful not to assume that a message with a given name has the same meaning for all applications that
may use this message name. Indeed, if the message is not one of the standard messages, it may have a
different severity and meaning in a different application.
The MSGNAME field must consist of at least two characters. Acceptable characters are limited to the
following ASCII decimal values: 48-57 (numbers), 65-90 (upper-case letters) and 95 (underscore).
While IOS allows lower-case letters as well, the vast majority of IOS messages use only the upper-case
letters. In order to be consistent with established conventions we opted to restrict the character set to
upper-case letters, numbers and underscore characters.
OL-22523-01
Name and Severity Level and Descriptions in Error Messages (continued)
Description
Informational messages are distinguished from notification in that they
provide information for internal flows of the application or per-request
information instead of system-wide notifications. Informational messages
are used for troubleshooting by users who are familiar with the basic flows
of the application. Examples:
• Request received
• Request was parsed successfully
• Request being processed
Response sent back
•
Acknowledgement received
•
Detailed audit information
•
Debugging messages are similar to informational messages, but provide
more detail and require the user to have better knowledge of system internal
processing. These messages are typically reserved for very advanced users
or Cisco technical support. Examples:
• Complete details for a request packet
• Internal state machine state changes
Internal profiling statistics
•
Internal events
•
Cisco Unified Communications Manager Managed Services Guide
Cisco Unified Serviceability Alarms and CiscoLog Messages
6-13