System Error Messages

This section lists and describes Cisco Internetwork Operating System (Cisco IOS) Release 11.2 F system error messages. The system software sends these error 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, while others may help diagnose problems with communications lines, internal hardware, or the system software.

How to Read System Error Messages

The messages are organized according to the particular system facility that produces the messages. The facility sections appear in alphabetical order, and within each facility section, messages are listed alphabetically by mnemonic. Each error message is followed by an explanation and a recommended action.

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

%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text

FACILITY is a code consisting of two or more uppercase letters that indicates the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. Table 58 lists the system facilities codes.

SUBFACILITY is a code relevant only to Channel Interface Processor (CIP) error messages. There are currently no CIP error messages in this chapter.

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 59 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 60 lists the representations of variable fields and the type of information in them.

Table 58: Facility Codes

Code	Facility
BRI	Integrated Services Digital Network (ISDN) Basic Rate Interface
BSTUN	Block serial tunneling
CBUS	ciscoBus controller
OIR	Online insertion and removal
QLLC	Qualified Logical Link Control
RSP	Route switch processor
SNMP	Simple Network Management Protocol
SYS	Operating System
TCP	Transmission Control Protocol

Table 59: Error Message Severity Levels

Level	Description
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

Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default logs messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the appropriate Cisco IOS configuration guides and command reference publications.

Table 60: Representation of Variable Fields in Error Messages

Representation	Type of Information
[chars]	Character string
[dec]	Decimal number
[enet]	Ethernet address (for example, 0000.FRED.00C00)
[hex]	Hexadecimal number
[t-line]	Terminal line number in octal (or decimal, if the decimal-TTY service is enabled)

Error Messages

This section lists error messages alphabetically by facility, severity, and mnemonic.

Error Message
%BAP-4-NOSTATE: [char] [char] [char] in illegal state [dec]

Explanation An internal software error occurred.

Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)

Error Message
%BAP-4-WAVL: Failed to initialise AVL tree, BAP not started

Explanation BAP will not be operational and will not be negotiated.

Error Message
%BRI-4-NOSWITCH: Inifail

Explanation ISDN leased line requires an ISDN switch type configuration.

Recommended Action Choose and configure a BRI switch type; if unsure, choose any switch.

Error Message
%BTSUN-3-IFNOTSETUP: Could not setup interface for protocol [chars]

Explanation BSTUN was unable to start the interface for handling the specified protocol traffic.

Recommended Action If this message appears while you are configuring BSTUN, check for other system errors, such as no available memory in the router, or the interface shutting down. If no obvious problem can be detected, record all the displayed values and any other BSTUN error messages, and contact your technical support representative.

Error Message
%BTSUN-3-NOPEER: No peer configured to route frame with destination address [chars] bstun group [dec]

Explanation A BSTUN route has not been configured for the frame with a destination address.

Recommended Action If this message appears while you are debugging BSTUN, it indicates that no specific BSTUN route has been configured for the frames being received with the device address listed in the packet debug trace. You may choose to configure a BSTUN route or ignore this message.

Error Message
%CBUS-3-CATRBADLOVE1: Interface [chars], SRB_COMPLETE lovenote received with unknown command [hex]

Explanation The system received a message from the Token Ring interface but does not recognize the message.

Recommended Action Copy the exact the text of the error message and contact your technical support representative.

Error Message
%CBUS-3-CTRACHECK: Interface [chars], Adapter Check Error [hex] [hex] [hex] [hex]

Explanation The Token Ring monitor firmware detected a fatal error on the interface card.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRACHECK: Unit [dec], Adapter Check Error [hex] [hex] [hex] [hex]

Explanation The Token Ring monitor firmware detected a fatal error on the interface card.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CBUS-3-CTRBADLOVE1_DUMP: Dump of MEMB follows\n-SRB_ADDR: [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]

Explanation The system is printing codes related to a previous lovenote error message.

Recommended Action Copy the exact text of the error message and contact your technical support representative.

Error Message
%CBUS-3-CTRCMDFAILED: Interface [chars], CTR Command [chars] Failed, [chars] [hex]

Explanation A command from the system to the Token Ring interface failed to complete.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CBUS-3-CTRCMDFAILED: Unit [dec], CTR Command [hex] Failed, [chars] [hex]

Explanation A command from the system to the Token Ring interface failed to complete.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRCMDFAILED2: Unit [dec], CTR Command [hex] Failed, Code [hex]

Explanation A hardware or software error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CBUS-3-CTRINIT: Interface [chars], CTR Initialization Failed - [chars]

Explanation The Token Ring interface failed one of its internal self-tests.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRINIT: Unit [dec], CTR Initialization Failed - [chars]

Explanation The Token Ring interface failed its internal self-tests.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRMDFAILED2: Interface [chars], CTR Command [chars] Failed, Code [hex]

Explanation A command from the system to the Token Ring interface failed to complete.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CBUS-3-CTRRAMTEST: Interface [chars] RAM Addressing Test Failed - [chars]

Explanation The Token Ring interface failed its memory diagnostic tests.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRRESET: Interface [chars] failed to initialize

Explanation The Token Ring interface failed to insert into the Token Ring. The interface is placed into a "reset" state and will not automatically try to re-insert.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRRESET: Unit [dec], Error [hex] [chars] - cbus_token_reset

Explanation The Token Ring interface failed to complete a command that is part of the reset sequence.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRUCHECK: Interface [chars], Microcode Check Error

Explanation The Token Ring interface microcode detected an unrecoverable error.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-CTRUCHECK: Unit [dec], Microcode Check Error

Explanation The CTR microcode detected an unrecoverable error.

Recommended Action Issue a clear interface command. If this message recurs, contact your technical support representative.

Error Message
%CBUS-3-RESETNXI: Reset of removed interface [hex] [chars]

Explanation An interface received a packet with bad VC encapsulation. This message can indicate a software or hardware problem.

Recommended Action Copy the debugging information exactly as it appears and report it to your technical support representative.

Error Message
%CBUS-4-CTRBADLOVE2: Interface [chars], Unexpected SRB_COMPLETE lovenote, command=[hex], result=[hex]

Explanation The system received an unsolicited message from the Token Ring interface. The system ignored the message and continued normal processing.

Recommended Action If the message recurs repeatedly, copy the exact text of the error message and contact your technical support representative.

Error Message
%ILACC-1-INITFAIL: msgtxt_initfail

Explanation The hardware failed to initialize correctly.

Recommended Action Repair or replace the controller.

Error Message
%ILACC-1-MEMERR: msgtxt_memoryerror

Explanation An Ethernet interface detected a hardware problem.

Recommended Action Repair or replace the controller.

Error Message
%ILACC-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

Recommended Action If message recurs, contact your technical support representative.

Error Message
%ILACC-3-OWNERR: MSG_TRACEBACK | MSG_PROCESS, msgtxt_ownerror

Explanation An Ethernet interface is malfunctioning, or an internal software error occurred.

Recommended Action Repair or replace the controller.

Error Message
%ILACC-3-SPURIDON: Unit [dec], spurious IDON interrupt, csr[dec]=[hex]

Explanation An Ethernet interface generated a spurious Initialization Done interrupt.

Recommended Action Repair or replace the controller.

Error Message
%ILACC-3-UNDERFLO: Unit [dec], underflow error

Explanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.

Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.

Error Message
%ILACC-4-BABBLE: Unit [dec], babble error, csr0=[hex]

Explanation An Ethernet interface is malfunctioning.

Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fastswitching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.

Error Message
%ILACC-5-COLL: Unit [dec], excessive collisions

Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal ILACC counter that counts the time (in "ticks" of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.

Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.

Error Message
%ILACC-5-LATECOLL: Unit [dec], late collision error

Explanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.

Recommended Action Repair or replace the controller.

Error Message
%ILACC-5-LOSTCARR: Unit [dec], lost carrier. Transceiver problem?

Explanation An Ethernet transceiver is unplugged or faulty.

Recommended Action Repair or replace the controller.

Error Message
%NIC100-1-INITFAIL: msgtxt_initfail

Explanation The hardware failed to initialize correctly.

Recommended Action Repair or replace the controller.

Error Message
%NIC100-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

Recommended Action If message recurs, contact your technical support representative.

Error Message
%OIR-3-SEATED: Insert/removal failed (slot [dec]), check card seating

Explanation The OIR facility detected an incorrectly seated card in slot [dec], causing the insertion or removal of this card to fail.

Recommended Action Reseat the card in the indicated slot.

Error Message
%RSP-2-QADIAG: QA Diagnostic [chars] error at 08 hex

Explanation An error occurred while accessing RSP internal hardware.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%RSP-3-BADHUFHDR: [chars], address [hex]

Explanation A software or hardware error occurred.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%SNMP-3-CPUHOG: Processing of [chars] of [chars]

Explanation SNMP took too much time processing a request.

Recommended Action If feasible, use the debug snmp packet command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative.

Error Message
%SYS-6-MEMDUMP: [hex]: [hex] [hex] [hex] [hex]

Explanation This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block.

Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.

Error Message
%TCP-2-BADQUEUE: Multiple entry for packet [hex]

Explanation An internal software error occurred.

Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.

Error Message
%TCP-2-BADREFCNT: Tty[t-line]: Bad refcnt for packet 0x[hex] during retransmit, [char]: [dec] to [char]: [dec], state [dec]

Explanation An internal software error occurred.

Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.

Error Message
%TCP-2-HALFCLOSE: Tty[t-line], tcp_putbyte() write disabled

Explanation TCP received a packet from the user application after the connection has already been half-closed.

Recommended Action Determine which TCP application is still sending after the half-closed connection.

Error Message
%TCP-6-INTERCEPT: [char], count ([dec]/[dec]) 1 min [dec]

Explanation The TCP Intercept code has changed state.

Recommended Action This message is for informational purposes only, but may indicate a security problem.

Table of Contents