The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the Cisco IOS system message structure and error message traceback report.
This chapter contains the following sections:
•Error Message Traceback Reports
The message includes the following information:
•Facility code
•Severity level
•Mnemonic code
•Description field
System error messages are structured as follows:
FACILITY-SEVERITY-MNEMONIC: Message-text
The facility code consists of at least two uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 1-1 lists the system facility codes.
The severity level is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 1-2 lists the message severity levels.
The MNEMONIC code uniquely identifies the error message. All mnemonics are all uppercase character strings.
Message text is a text string that describes the error condition. The text string may contain detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because variable fields change from message to message, they are represented here by short strings that are enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 1-3 lists the variable fields in messages.
|
|
---|---|
[dec] |
Decimal |
[chars] or [char] |
Character string |
[hex] |
Hexadecimal integer |
[num] |
Number |
The following is an example of a system error message:
Error Message LINK-2-BADVCALL: Interface [chars], undefined entry point
Some error messages also indicate the card and slot reporting the error. These error messages are structured as follows:
CARD-SEVERITY-MSG:SLOT FACILITY-SEVERITY-MNEMONIC:
Message-text
•CARD is a code that describes the type of card reporting the error.
•MSG is a mnemonic indicating that this is a message. It is always shown as MSG.
•SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a number (for example, SLOT5).
Some messages describe internal errors and contain traceback information, which provides the stack trace of the function calls that resulted in the message. This trace helps the engineers track down the problem that is indicated in the message. You should include this information when you report a problem to your technical support representative.
The traceback report includes the following sample information:
-Process= "Exec", level= 0, pid= 17
-Traceback= 1A82 1AB4 6378 A072 1054 1860
The numbers that are printed in the message indicate which lines of code caused the message to occur.