Cisco IE 3010 Switch System Message Guide, Cisco IOS Release 12.2(53)EZ
Bias-Free Language
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.
- Updated:
- March 21, 2015
Chapter: System Message Overview
System Message Overview
This guide describes the Cisco IE 3010 switch-specific system messages. During operation, the system software sends these messages to the console (and, optionally, to a logging server on another system). Not all system messages mean problems with your system. Some messages are informational, while others can help diagnose problems with communications lines, internal hardware, or the system software.
Note 
For information about system messages that are not Cisco IE 3010 platform-specific, see the Cisco IOS Software System Messages for Cisco IOS Release 12.2S.
•Error Message Traceback Reports
How to Read System Messages
System log messages can contain up to 80 characters and a percent sign (%), which follows the optional sequence number or time-stamp information, if configured. Messages appear in this format:
seq no:timestamp: %facility-severity-MNEMONIC:description
By default, a switch sends the output from system messages to a logging process.
Each system message begins with a percent sign (%) and is structured as follows:
%FACILITY-SEVERITY-MNEMONIC: Message-text
•FACILITY is two or more uppercase letters that show 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 Cisco IE 3000 switch-specific facility codes.
These messages are described in Chapter 2, "Message and Recovery Procedures," in alphabetical order by facility code, with the most severe (lowest number) errors described first.
•SEVERITY 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.
•MNEMONIC is a code that uniquely identifies the message.
•Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 1-3 lists the variable fields in messages.
Error Message Traceback Reports
Some messages describe internal errors and contain traceback information. Include this information when you report a problem to your technical support representative.
This message example includes traceback information:
-Process= "Exec", level= 0, pid= 17
-Traceback= 1A82 1AB4 6378 A072 1054 1860
Some system messages ask you to copy the error messages and take further action. These online tools also provide more information about system error messages.
Output Interpreter
The Output Interpreter provides additional information and suggested resolutions based on the output of many CLI commands, such as the show tech-support privileged EXEC command.
https://www.cisco.com/pcgi-bin/Support/OutputInterpreter/home.pl
Bug Toolkit
The Bug Toolkit provides information on open and closed caveats and allows you to search for all known bugs in a specific Cisco IOS Release.
http://tools.cisco.com/Support/BugToolKit/
Contacting TAC
If you cannot determine the nature of the error, see the "Obtaining Documentation and Submitting a Service Request" section on page vii for further information.
Feedback