Cisco IOS XR System Error Message Reference Guide, Release 3.8
Downloads: This chapterpdf (PDF - 344.0 KB) The complete bookPDF (PDF - 45.06 MB) | Feedback

System Error Messages Overview

Table Of Contents

System Error Messages Overview

Obtaining Technical Assistance

How This Manual Is Organized

How to Read System Messages

Message Traceback Reports

System Error Messages Overview

This publication lists and describes Cisco IOS XR system error messages. The system software sends these messages to the console (and, optionally, to a logging server on another system) during operation. Not all system error messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software.

This manual also includes messages that appear when the system crashes.

Obtaining Technical Assistance

When the recommended action of an error message advises that you contact Cisco technical support, open a case with the Cisco Technical Assistance Center (TAC). Please see the section "Contacting TAC by Using the Cisco TAC Website" in the preface of "About Cisco IOS XR Software."

How This Manual Is Organized

The individual chapters provide descriptions of system messages related to Cisco IOS XR software. The messages are organized according to the particular system category that produces the messages. The category sections appear in alphabetical order, and within each category section, messages are listed alphabetically by group code. Each message is followed by an explanation and a recommended action.

For alphabetizing purposes, lowercase and uppercase letters are treated the same.

How to Read System Messages

System messages begin with a percent sign (%) and are structured as follows.


CATEGORY is a code consisting of two or more uppercase letters that indicate the category to which the message refers. Table 1 lists the system category codes for the Cisco CRS-1 and Cisco XR 12000 Series Router.

GROUP is a code consisting of two or more uppercase letters that indicate the group to which the message refers. A group can be a hardware device, a protocol, or a module of the system software.

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 2 lists the severity levels.

MNEMONIC is a code that uniquely identifies the error 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 3 lists the representations of variable fields and the type of information in them.

The following is a sample system error message:

%ACL-IP_ACL_PARSE-2-ALLOC Unable to allocate memory for [chars] 

Table 1 Category Codes

Description of Category


All Access Control List (ACL) related messages.


All Application infrastructure related messages.


All Diagnostic related messages.


All Fabric (HW and SW both) related messages.


All CEF and FIB related messages.


All High Availability (HA) related messages.


All Installation related messages.


All Internet Protocol (IP) related messages.


All Layer 1 (L1) related messages.


All Layer 2 (L2) related messages, for instance ethernet drivers, PoS, SONET, PLIMS, and so forth.


All Layer 3 (L3) related messages.


All License related messages.


All Media related messages, including disk, nvram, flash, and so forth.


All Managament Plane and Managability related messages, for instance, config, cli, sml, pm, and so forth.


All Operating System (OS) and OS infrastructure related messages.


All Packet Infrastructure related messages, such as ifmgr, tunnels, bundlemgr, pakman, and so forth.


All Platform related commands, for instance, shelf magr, chassis, env ctrl, and so forth.


All Quality of Service (QoS) related messages.


All routing related messages, such as MPLS, OSPF, BGP, Multicast, MRIB, RIB, and so forth.


All security related messages, such as AAA, IPSec and related protocols, and so forth.


All service related messages, such as RSPP, and SD.


All Simple Network Management Protocol (SNMP) related messages, such as BGP MIB, CONFIG MIB, SNMP agent. MIB location does not matter.


All system database related messages.

Table 2 Error Message Severity Levels 


0 - emergency

System unusable

1 - alert

Immediate action needed

2 - critical

Critical condition

3 - error

Error condition

4 - warning

Warning condition

5 - notification

Normal but significant condition

6 - informational

Informational message only

7 - debugging

Appears during debugging only

Message severity levels correspond to the keywords assigned by the logging console and logging monitor global configuration commands that define where and at what level these messages appear. In general, the default is to log messages from level 0 (emergencies) to level 7 (debugging). However, the default level varies by platform. For more information, see the system configuration chapter and descriptions of the logging console and logging monitor commands in the appropriate Cisco IOS configuration guide and command reference publications.

Table 3 Representation of Variable Fields in Messages 

Type of Information


AppleTalk address


AppleTalk network, either 600 or 600-601


Single character


Character string


Decimal number


Ethernet address (for example, 0000.FEED.00C0)


Hexadecimal number


Internet address (for example,




IP version 6 (IPv6) address


Address or node name




Scientific notation


Terminal line number in octal (or decimal if the decimal-TTY service is enabled)


VINES name; or number (hex or decimal)

Message Traceback Reports

Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.

The following sample message includes traceback information:

-Process= "Exec", level= 0, pid= 17 
-Traceback= 1A82 1AB4 6378 A072 1054 1860