How to Read System Error Messages

System Error Messages

This section lists and describes the system error messages for Cisco IOS Release 11.2 F. 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 115 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 116 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 117 lists the representations of variable fields and the type of information in them.

Table 115: Facility Codes
Code Facility

AMDP2_FE

Presidio Ethernet & Laguna Fast Ethernet

BAP

PPP Bandwidth Allocation Protocol (BAP)

BGP

Border Gateway Protocol

BRI

Integrated Services Digital Network (ISDN) Basic Rate Interface

BRIMUX

AS5200 BRIMUX board

BSTUN

Block serial tunneling

C1600

Cisco 1600 platform

C3600

Cisco 3600 platform

CBUS

ciscoBus controller

CI

75xx platform chassis interface

CIRRUS_PM

Slow speed async/sync port module

CLNS

OSI Connectionless Network Services

CPAD

Compression service adapter

CPM

C3600 combination port module

CT3

Channelized T3 port adapter

DBUS

Data bus

DLSWP

Data-link switching peer

HOOD

LAN controller 100VG-AnyLAN interface

IBM2692

IBM Token Ring chip set

ILACC

ILACC driver

INTERFACE_API

Binary API for the interface descriptor block

IPFAST

IP fast switching

IPX

Internetwork Packet Exchange Protocol

ISDN

Integrated Services Digital Network

LANE

LAN Emulation

LANMGR

IBM LAN Network Manager

LINK

Data link

MBRI

Multi-BRI port module

MUESLIX

Mx serial ASIC

NIC100

NIC100 driver

OIR

Online insertion and removal

OSPF

Open Shortest Path First

QLLC

Qualified Logical Link Control

QUICC

MC68360 Quad Integrated Communications Controller

RSP

Route Switch Processor

SCHED

Scheduler

SDLC

Synchronous Data Link Control

SNMP

Simple Network Management Protocol

STUN

Serial tunneling

SWITCH

Switch interface

SYS

Operating system

TCP

Transmission Control Protocol

Table 115: **Facility Codes**
Code	Facility
AMDP2_FE	Presidio Ethernet & Laguna Fast Ethernet
BAP	PPP Bandwidth Allocation Protocol (BAP)
BGP	Border Gateway Protocol
BRI	Integrated Services Digital Network (ISDN) Basic Rate Interface
BRIMUX	AS5200 BRIMUX board
BSTUN	Block serial tunneling
C1600	Cisco 1600 platform
C3600	Cisco 3600 platform
CBUS	ciscoBus controller
CI	75xx platform chassis interface
CIRRUS_PM	Slow speed async/sync port module
CLNS	OSI Connectionless Network Services
CPAD	Compression service adapter
CPM	C3600 combination port module
CT3	Channelized T3 port adapter
DBUS	Data bus
DLSWP	Data-link switching peer
HOOD	LAN controller 100VG-AnyLAN interface
IBM2692	IBM Token Ring chip set
ILACC	ILACC driver
INTERFACE_API	Binary API for the interface descriptor block
IPFAST	IP fast switching
IPX	Internetwork Packet Exchange Protocol
ISDN	Integrated Services Digital Network
LANE	LAN Emulation
LANMGR	IBM LAN Network Manager
LINK	Data link
MBRI	Multi-BRI port module
MUESLIX	Mx serial ASIC
NIC100	NIC100 driver
OIR	Online insertion and removal
OSPF	Open Shortest Path First
QLLC	Qualified Logical Link Control
QUICC	MC68360 Quad Integrated Communications Controller
RSP	Route Switch Processor
SCHED	Scheduler
SDLC	Synchronous Data Link Control
SNMP	Simple Network Management Protocol
STUN	Serial tunneling
SWITCH	Switch interface
SYS	Operating system
TCP	Transmission Control Protocol

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

Table 116: 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.

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

Table 117: 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

[inet]

Internet address

[int]

Integer number

[sci_notation]

Scientific notation

[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 and mnemonic.

Error Message
%AMDP2_FE-4-BABBLE: AMDP2/FE([dec]/[dec]), Babble error

Explanation The transmitter has been on the channel longer than the time taken to transmit the largest frame.

Recommended Action The system should recover. No action is required.

Error Message
%AMDP2_FE-5-COLL: AMDP2/FE([dec]/[dec]), Excessive collisions, TDR=[dec], TRC=[dec]., MSGDEF_LIMIT_SLOW

Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This problem may occur under heavy loads.

Recommended Action The system should recover. No action is required.

Error Message
%AMDP2_FE-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bay

Explanation The software could not identify the interface card.

Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.

Error Message
%AMDP2_FE-1-INITFAIL: AMDP2/FE([dec]/[dec]), Init failed, CSR[dec]=0x[hex]

Explanation The software failed to initialize or restart an Ethernet/Fast Ethernet interface.

Recommended Action Clear the interface. If the message recurs, call your technical support representative for assistance.

Error Message
%AMDP2_FE-5-LATECOLL: AMDP2/FE([dec]/[dec]), Late collision

Explanation Late collisions occurred on the Ethernet/Fast Ethernet interface.

Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. For regular Ethernet, the system should recover. No action is required.

Error Message
%AMDP2_FE-5-LOSTCARR: AMDP2/FE([dec]/[dec]), Lost carrier. Transceiver problem?

Explanation The cable and/or transceiver is not connected.

Recommended Action Connect the cable and/or transceiver.

Error Message
%AMDP2_FE-1-MEMERR: AMDP2/FE([dec]/[dec]), Memory error, CSR[dec]=0x[hex]

Explanation The interface could not access system resources for a long time. This problem may occur under very heavy loads.

Recommended Action The system should recover. No action is required. If the message recurs, call your technical support representative for assistance.

Error Message
%AMDP2_FE-2-NOISL: Interface [chars] does not support ISL

Explanation The interface cannot be configured as an ISL trunk.

Recommended Action Check the configuration.

Error Message
%AMDP2_FE-1-NOMII: AMDFE([dec]/[dec]), MII Interface transceiver not connected

Explanation The MII transceiver was disconnected while the MII port was selected.

Recommended Action Connect the transceiver and enter the shut and no shut commands for the interface in the configuration menu.

Error Message
%AMDP2_FE-3-NOTAMDP2: Device reported [hex]

Explanation The software could not recognize the interface chips.

Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, call your technical support representative for assistance.

Error Message
%AMDP2_FE-3-OVERFLO: AMDP2/FE([dec]/[dec]), Receive overflow

Explanation While receiving a frame, the controller chip's local buffer transmitted insufficient data because data could not be transferred to DRAM fast enough to keep pace with its input rate. Normally, such a problem is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required.

Error Message
%AMDP2_FE-3-OWNERR: AMDP2/FE([dec]/[dec]), Buffer ownership error, pak=0x[hex]

Explanation The software detected an error in descriptor ownership.

Recommended Action Try a later version of the software. If the message recurs, call your technical support representative for assistance.

Error Message
%AMDP2_FE-3-SPURIDON: AMDP2/FE([dec]/[dec]), Spurious IDON interrupt, CSR[dec]=0x[hex]

Explanation An illegal condition indicating initialization done has occurred.

Recommended Action Clear the interface. If this message recurs, call your technical support representative for assistance.

Error Message
%AMDP2_FE-3-UNDERFLO: AMDP2/FE([dec]/[dec]), Transmit underflow

Explanation While transmitting a frame, the controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required.

Error Message
%BAP-4-NOSTATE: [chars] [chars] [chars] in illegal state [int]

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 initialize AVL tree, BAP not started

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

Error Message
%BGP-3-ADDROUTE: Unable to add route for [int] to radix trie

Explanation An addition to the radix trie could not be completed because of an error.

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

Error Message
%BGP-3-DELPATH: Attempted to delete path from an empty net for [int], MSGDEF_LIMIT_SLOW

Explanation A BGP path could not be deleted because of an error.

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

Error Message
%BGP-3-DELROUTE: Unable to remove route for [int] from radix trie, MSGDEF_LIMIT_SLOW

Explanation A deletion from the radix trie could not be completed because of an error.

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

Error Message
%BGP-3-MAXPATHS: Too many parallel paths for [int], maximum is [dec], MSGDEF_LIMIT_SLOW

Explanation The number of parallel paths exceeds the configured limit.

Recommended Action Increase the number of parallel paths allowed.

Error Message
%BRI-4-NOSWITCH: msgtxt_initfail

Explanation ISDN leased line requires an ISDN switch type configured.

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

Error Message
%BRIMUX-3-BADBRIMUX: Slot [dec] [chars]

Explanation A BRIMUX firmware problem may be present.

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

Error Message
%BRIMUX-1-BADCODE: Software error: [chars]

Explanation An internal software error occurred.

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

Error Message
%BRIMUX-3-BADDLACK: Slot [dec] BRIC, failed to acknowledge download data block [dec]

Explanation A BRIMUX firmware problem may be present.

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

Error Message
%BRIMUX-3-BADDPM: Slot [dec] DPM, test failed at offset 0x[hex], expect 0x[hex], read 0x[hex]

Explanation A BRIMUX board hardware problem may be present.

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

Error Message
%BRIMUX-3-CHANUPDOWN: B[dec] of BRI[dec] on slot [dec] BRIC, changed state to [chars]

Explanation A B-channel on the BRIMUX board changed state.

Recommended Action No action is required.

Error Message
%BRIMUX-4-HEARTBEAT: Slot [dec] BRIC, lost heartbeat for [dec] seconds

Explanation A BRIMUX board hardware or firmware problem may be present.

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

Error Message
%BRIMUX-3-PORTUPDOWN: BRI[dec] on slot [dec] BRIC, changed state to [chars]

Explanation A port on the BRIMUX board changed state.

Recommended Action No action is required.

Error Message
%BRIMUX-3-UPDOWN: Slot [dec] BRIC, changed state to [chars]

Explanation A BRIMUX board changed state.

Recommended Action No action is required.

Error Message
%BSTUN-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
%BSTUN-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
%C1600-4-BADINTFC: Interface [dec], (0-1 Onboard interfaces 2=WIC) Invalid interface (Unknown, Uninitialized or Bad Cookie value read)

Explanation Your router is functional; however, there is an interface that the software does not recognize.

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

Error Message
%C1600-4-INTFCNOFLH: Unable to load images or communicate over interface

Explanation The operation might have failed because of a transient network problem.

Recommended Action Retry the operation. If the problem persists, call your technical support representative for assistance.

Error Message
%C3600-3-BADNV: Detected invalid NVRAM size: [dec] bytes

Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM may be bad.

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

Error Message
%CBUS-3-BADVC: [chars] [dec]/[dec] got bad VC packet [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex], 1 * ONEMIN

Explanation An interface received a packet with bad VC encapsulation. This message indicates either 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-3-CMDDROPPED: Cmd dropped, CCB 0x[hex], slot [dec], cmd code [dec]

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
%CBUS-3-CT3DSX3ERR: ([chars])Illegal dsx3 value - unit is [dec], 1 * ONEMIN

Explanation Internal data structure is corrupted, which causes the love letter to drop.

Recommended Action Copy the error message exactly as it appears, and report it to 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-CTRBADLOVE1: Interface [chars], SRB_COMPLETE lovenote received with unknown command (0x[hex])

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

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-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 for assistance.

Error Message
%CBUS-4-CTRBADLOVE2: Interface [chars], Unexpected SRB_COMPLETE lovenote, command=0x[hex], result=0x[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 this message recurs, copy the error message exactly as it appears, and report it to your technical support representative.

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

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

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

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

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

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-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, call your technical support representative for assistance.

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

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

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, call your technical support representative for assistance.

Error Message
%CBUS-3-SERRSET: Interface [chars], Error ([hex]) [chars] - serial_reset()

Explanation A software error occurred.

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

Error Message
%CI-4-COND: Restarting with [int] recent soft power shutdowns (or system just powered-on)

Explanation A soft shutdown occurs when the router powers itself down due to a detected over temperature condition. When the temperature goes up past the board shutdown trip point, the cards are shutdown but the power supplies, fans, and CI continue to run.

When the system cools past the restart trip point, the system will restart. To keep the up/down cycle from repeating indefinitely, the system counts the number of times this restart happens. If the counter reaches zero, the system undergoes a hard shutdown, which requires a power cycle to recover. The soft shutdown counter is reset to its maximum value after the system has been up for six hours.

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

Error Message
%CIRRUS_PM-3-BADLOOPCABLE: Loopback not supported for DTE/X.21 port [dec] in slot [dec]

Explanation The DTE/X.21 cable does not support loopback.

Recommended Action Use the proper cable for loopback testing.

Error Message
%CIRRUS_PM-3-DISCOVER: CIRRUS PM at slot [dec]: PCI discovery failed

Explanation The software failed to initialize the network module.

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

Error Message
%CIRRUS_PM-2-NOBUFPOOL_ASYNC: Unable to create buffer pool for async mode interface

Explanation There is not enough memory for a per channel control block of the CD2430 asynchronous driver.

Recommended Action Make sure there is sufficient memory available in the router. If the message recurs, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CIRRUS_PM-3-NOTCD2430: Device reported [hex]

Explanation The network module hardware reports that a non-low-speed port module was detected.

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

Error Message
%CIRRUS_PM-3-UNKNOWNPLATFORM: Unknown Platform type to support CD2430 interfaces

Explanation The network module is not compatible with the current platform that it is being plugged into.

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

Error Message
%CLNS-3-BADIFNUM: ISIS: Bad if number, pdb [hex], idb [hex], if [hex], MSGDEF_LIMIT_MEDIUM

Explanation An internal error occurred in the Intermediate System-to-Intermediate System (IS-IS) or NetWare Link Services Protocol (NLSP). An inconsistency was detected in an internal data structure related to tracking protocol/interface state, possibly related to enable/disable of the protocol on an interface.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. If possible, include a current configuration and any IS-IS and/or NLSP related configuration commands recently issued.

Error Message
%CPAD-1-ERROR: [chars]: [chars]

Explanation An error occurred in the application using the CSA.

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

Error Message
%CPAD-1-INITFAIL: bay [dec]: [chars]

Explanation The CSA driver failed to initialize at the specified point.

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

Error Message
%CPAD-1-NOMEMORY: bay [dec]: out of memory: could not allocate [chars]

Explanation The CSA driver, in its initialization phase, could not allocate memory for the specified data structure.

Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%CPAD-1-PLXINIT: bay [dec] Invalid vendor/device id [dec]

Explanation The CSA driver, in its initialization phase, encountered a communication failure with the CSA in the specified bay.

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

Error Message
%CPAD-6-SHUTDOWN: [chars] shutting down

Explanation The specified CSA is shutting down. It may have been physically removed.

Recommended Action This is an informational message only. It occurs in normal operation.

Error Message
%CPAD-6-STARTUP: [chars] starting up

Explanation The specified CSA has initialized successfully.

Recommended Action This is an informational message only. It occurs in normal operation.

Error Message
%CPM-3-DISCOVER: CPM at slot [dec]: PCI discovery failed count = [dec]

Explanation One of the interface controller devices on the module did not initialize properly.

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

Error Message
%CPM-3-INCORRECT_ID: CPM at slot [dec]: PCI device not supported

Explanation An interface controller device did not report the correct PCI device ID.

Recommended Action Power down, reinsert the port module, and reboot. If the message recurs, call your technical support representative for assistance.

Error Message
%CT3-3-BADMSG: Received unexpected mailbox message (id = [dec])

Explanation Unexpected message from CT3 firmware.

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

Error Message
%CT3-1-CONFIGURE: CT3: Fail to configure [dec] interfaces on bay [dec], shutting down bay

Explanation The CT3 hardware failed. Some components on the board failed to initialize.

Recommended Action Replace the CT3 port adapter.

Error Message
%CT3-2-CT3FWCRASHED: CT3 F/W crashed: [hex] - VIP reset

Explanation CT3 firmware does not update the software watchdog.

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

Error Message
%CT3-3-CT3NOACC: [chars] - Accumulator is not available

Explanation An invalid TX accumulator is detected.

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

Error Message
%CT3-1-DISCOVER: CT3: only found [dec] interfaces on bay [dec], shutting down bay

Explanation The CT3 hardware failed. Some components on the board failed to initialize.

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

Error Message
%CT3-1-DWNLDFL: PA down load failed.

Explanation Failed to download firmware into the CT3 port adapter.

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

Error Message
%CT3-3-ERROR: [chars]

Explanation General error information.

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

Error Message
%CT3-1-INITFAIL: Bay [dec]: Init failed at [chars]

Explanation CT3 firmware initialization failure.

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

Error Message
%CT3-1-INITFAILP: [chars]: Init failed at [chars]

Explanation CT3 initialization failure.

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

Error Message
%CT3-3-LOVEFAIL: [chars]: failed to send [chars] love letter

Explanation A love letter was not sent to RSP.

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

Error Message
%CT3-3-MBOXRECV: Bay [dec]: fail receiving mbox reply [dec]

Explanation A message was not received from CT3 firmware.

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

Error Message
%CT3-3-MBOXRECVP: Bay [dec]: fail receiving mbox reply [dec] for port [dec]

Explanation A message to configure the port was not received from CT3 firmware.

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

Error Message
%CT3-3-MBOXSEND: Bay [dec]: fail sending mbox msg [dec]

Explanation A message was not sent to CT3 firmware.

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

Error Message
%CT3-3-MBOXSENDP: Bay [dec]: fail sending mbox msg [dec] for port [dec]

Explanation A port-related message was not sent from CT3 firmware.

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

Error Message
%CT3-3-NOTMXT: Device is not MX - Device reported [hex]

Explanation Failed to detect the HDLC controller on the CT3.

Recommended Action Replace the CT3 port adaptor.

Error Message
%CT3-3-NOTPLX: Device is not PLX 9060 - Device reported [hex]

Explanation The PLX 9060 was not detected on the CT3.

Recommended Action Replace the CT3 port adaptor.

Error Message
%CT3-1-NOTREADY: Not ready for download.

Explanation An error was detected on the communication path between VIP and CT3.

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

Error Message
%CT3-2-NOVC: [chars]: packet received for non-exist VC [dec]

Explanation The virtual channel encapsulation is corrupted.

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

Error Message
%CT3-3-OWNERR: CT3 serial ([dec]), Buffer ownership error, pak=0x[hex].

Explanation A software or hardware error occurred. The CT3 driver detected that the transmit ring is in an inconsistent and unrecoverable state.

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

Error Message
%CT3-1-RESTARTFAIL: [chars]: Start failed at [chars]

Explanation The restart failed to reset the interface.

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

Error Message
%CT3-1-STARTFAIL: [chars]: Start failed at [chars]

Explanation The restart failed to enable the interface.

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

Error Message
%CT3-1-STOPFAIL: [chars]: Stop failed at [chars]

Explanation The shutdown failed to disable the interface.

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

Error Message
%CT3-3-TOOSMALL: MSG_TRACEBACK | MSG_PROCESS, [char] - packet was less than two bytes

Explanation An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.

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

Error Message
%DBUS-3-NOSUPPORT: No driver support in this image for [chars] in slot [dec] (card type [dec]) - disabled

Explanation The Cisco IOS image does not have driver support code for the specified interface processor.

Recommended Action Remove the unsupported interface processor card, or reload the router with a Cisco IOS image that has driver support code for that interface processor card.

Error Message
%DLSWP-3-PLFCHANGE: [chars] [dec]; [chars]

Explanation The largest frame size configured in the DLSW remote peer definition is being changed because the MTU size configured on the interface, used by DLSW, is less than the configured value of the largest frame on DLSW remote peer definition. The largest frame size is being changed to that configured on the interface.

Recommended Action If you wish to use this largest frame size for DLSW, increase the MTU on the interface to a value larger than the configured largest frame size.

Error Message
%HOOD-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

Recommended Action If the message recurs, call your technical support representative for assistance.

Error Message
%HOOD-5-CABLEERR: Unit [dec], HP100VG, cable error. Training failed

Explanation A 100VG cable or hub is faulty.

Recommended Action If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.

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

Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged.

Recommended Action If the transceiver appears to be properly terminated, repair or replace the router.

Error Message
%HOOD-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
%HOOD-5-NOCABLE: Unit [dec], HP100VG, no tone detected. Check cable, hub

Explanation A 100VG cable is faulty.

Recommended Action If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.

Error Message
%IBM2692-1-DISCOVER: IBM2692, Only found [dec] interfaces on bay [dec], shutting down bay

Explanation One of the interface controller devices on the module did not initialize properly.

Recommended Action Power down, reinsert the network module, and reboot. If the message recurs, call your technical support representative for assistance.

Error Message
%IBM2692-1-SRBQ_OVERFLOW: IBM2692 ([dec]/[dec]), SRB queue overflow

Explanation The maximum number of commands that can be queued to the Token Ring port has been exceeded. Normally, such a problem is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required.

Error Message
%IFS-3-FILEMAX: Failed to open [chars], maximum open files [dec])

Explanation An internal software error occurred.

Recommended Action If this messages recurs, contact your technical support representative.

Error Message
%IFS-3-FSDUP: Failed to add [chars], filesystem prefix exists

Explanation An internal software error occurred.

Recommended Action If this messages recurs, contact your technical support representative.

Error Message
%IFS-3-FSMAX: Failed to add [chars], maximum filesystems [dec]

Explanation An internal software error occurred.

Recommended Action If this messages recurs, contact your technical support representative.

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

Explanation An Ethernet interface is malfunctioning.

Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. 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-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

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

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

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-1-INITFAIL: msgtxt_initfail

Explanation The hardware failed to initialize correctly.

Recommended Action Repair or replace the controller.

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
%ILACC-1-MEMERR: msgtxt_memoryerror

Explanation An Ethernet interface detected a hardware problem.

Recommended Action Repair or replace the controller.

Error Message
%ILACC-3-OWNERR: 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]=0x[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
%INTERFACE_API-4-BADPAKINPUT: pak-if_input is not initialized

Explanation An internal software error occurred.

Recommended Action If this message recurs, call your technical support representative for assistance.

Error Message
%INTERFACE_API-4-BADPAKOUTPUT: pak-if_output is not initialized

Explanation An internal software error occurred.

Recommended Action If this message recurs, call your technical support representative for assistance.

Error Message
%INTERFACE_API-4-BADSWIDB: [chars] may not be referencing the correct swidb

Explanation An internal software error occurred.

Recommended Action If this message recurs, call your technical support representative for assistance.

Error Message
%IPFAST-6-INVALIDADDR: Invalid cache destination [int]/[dec], ONESEC

Explanation The system attempted to add a cache entry for an invalid address.

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

Error Message
%IPX-6-NOVACCESSLOG: [chars] [chars] [chars] [chars] [hex].[sci_notation] [chars] [hex].[sci_notation] [dec] pkt[chars]

Explanation If IPX access violation logging is enabled, these messages are displayed when an access list logging event has occurred.

Recommended Action Verify that the host system is permitted or denied as defined in the access list.

Error Message
%IPX-3-TOOMANYNETS: Too many networks

Explanation The limit of connected IPX networks has been reached. Additional IPX interfaces cannot be configured.

Recommended Action Do not configure IPX on additional interfaces. Remove IPX configuration commands from inactive interfaces.

Error Message
%ISDN-4-INVALID_CALLEDNUMBER: Interface [chars], Ignoring call, LDN and Called Party Number mismatch

Explanation The incoming ISDN call is ignored because the Called Party Number does not match the LDN numbers configured in the router.

Recommended Action Correct the LDN in the router to match the Called Party Number delivered in the incoming setup message.

Error Message
%ISDN-4-INVALID_EID: Interface [chars], Ignoring call, EndPoint Identifier (EID) mismatch

Explanation The incoming ISDN call is ignored because the EID delivered in the incoming setup message cannot be matched.

Recommended Action If EID is delivered in the setup message, use the isdn debugs and show isdn status commands to determine the current EID values. You may need to contact the service provider.

Error Message
%ISDN-4-INVALID_SPID: Interface [chars], Spid[dec] was rejected

Explanation The SPID configured in the router has been rejected by the switch.

Recommended Action Determine the correct SPID, reenter the SPID and clear the BRI interface.

Error Message
%ISDN-1-NOMEMORY: msgtxt_nomemory

Explanation The requested operation could not be accomplished because of a low-memory condition.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message
%LANE-3-LEC_REGISTER: [chars] REGISTER failed, [chars] (LES returned [dec])

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
%LANE-3-NOREGILMI: [chars] [chars] cannot register %Cj with ILMI

Explanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.

Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router should be examined. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration.

Error Message
%LANMGR-4-BADUPCALL: Unexpected call ([chars]) from LLC2 for Bridge [hex]-[hex]-[hex]

Explanation An internal software error occurred.

Recommended Action If this message recurs, call your technical support representative for assistance.

Error Message
%LANMGR-2-NOMEMORY: No memory available: [chars]

Explanation The requested operation failed because of a low-memory condition.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message
%LINK-5-LOOPSTATUS: Interface [chars], [chars]

Explanation The interface entered or exited loopback.

Recommended Action Notification message only. No action is required.

Error Message
%MBRI-1-INITFAIL: Initialization of MBRI interface failed on bay [dec], shutting down bay

Explanation The MBRI network module failed to complete initialization.

Recommended Action Make sure there is sufficient memory available in the router. If you continue to get this message, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%MBRI-3-NOTMBRI: Device reported [hex]

Explanation The network module hardware reports that a non-MBRI port module was detected.

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

Error Message
%MBRI-3-UNKNOWN_STATE: Unknown Layer1 State in unit [dec]

Explanation The MBRI driver detected an invalid Layer 1 condition.

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

Error Message
%MUESLIX-3-DISCOVER: Mx serial (bay [dec]): Interface found: [dec]

Explanation The Mx serial hardware failed. Some interfaces on the board failed to come up.

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

Error Message
%MUESLIX-1-DWNLDFL: Mx serial (bay [dec]): PA down load failed

Explanation The Mx serial hardware failed. It could not download its operational microcode.

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

Error Message
%MUESLIX-1-INITFAIL: Mx serial (bay [dec]), Init Failed at [chars]

Explanation The Mx serial port adaptor failed to complete hardware initialization.

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

Error Message
%MUESLIX-3-NOTMUESLIX: Mx serial (bay [dec]): Device reported [hex]

Explanation The Mx serial hardware failed. A non-Mx serial device pointed at the Mx serial software.

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

Error Message
%MUESLIX-3-OWNERR: Mx serial ([dec]/[dec]), Buffer ownership error, pak=0x[hex]

Explanation A software or hardware error occurred. The Mx serial driver detected that the transmit ring is in an inconsistent and unrecoverable state.

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

Error Message
%MUESLIX-1-STARTFAIL: Mx serial, [chars] Start Failed at [chars]

Explanation A software or hardware error occurred. The Mx serial interface is not responding to commands used to initialize it.

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

Error Message
%MUESLIX-1-STOPFAIL: Mx serial, [chars] Stop Failed at [chars]

Explanation The Mx serial port adaptor failed to respond to a request to disable an interface.

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

Error Message
%MUESLIX-3-TOOSMALL: MSG_TRACEBACK | MSG_PROCESS, Mx serial, [char] - packet was less than two bytes

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

Error Message
%NIC100-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

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

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-OWNERR: msgtxt_ownerror

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

Recommended Action Repair or replace the controller.

Error Message
%OSPF-3-NOSELF: if [chars] if_state [dec]

Explanation An internal error occurred.

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

Error Message
%OSPF-4-RCVSELF: from [chars] src [int] dst [int] id [int] type [dec] if_state [dec]

Explanation OSPF receive packet originated by itself.

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

Error Message
%QLLC-3-BAD_XID: Sna configuration error for [sci_notation]: Lan device is PU2.1, X.25 device is PU2.0 (XID Format 1)

Explanation The IBM Gateway (3172) or front-end processor on the LAN is sending XID Format 3, which is used to communicate with PU2.1 devices. The X.25 device is a PU2.0 (3174) that is configured to send XID Format 1 messages. This situation is very rare. A likely cause is that the revision levels on the IBM equipment are incompatible.

Recommended Action Check the revision levels on the external equipment, and upgrade them if necessary.

Error Message
%QUICC-1-BADHDXFSM: Quicc([dec]/[dec]), Unexpected HDX state [dec], event [dec]

Explanation A bad event was detected in the state machine for half-duplex transmission/reception.

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

Error Message
%QUICC-1-CTSLOST: QUICC([dec]/[dec]), Clear to Send Lost

Explanation The Clear To Send (CTS) input signal on a data terminal equipment (DTE) serial interface became inactive while transmitting a frame. This problem is a result of a communication line failure or cable disconnection.

Recommended Action Check the serial interface cable and/or communication equipment, such as the channel service unit/data service unit (CSU/DSU).

Error Message
%QUICC-1-INITFAIL: QUICC([dec]/[dec]), SCC[dec] init failed

Explanation The software failed to initialize or restart a 1T serial card.

Recommended Action Clear the serial interface. If the message recurs, call your technical support representative for assistance.

Error Message
%QUICC-1-LINEFLAP: Quicc([dec]/[dec]), Excessive modem control changes

Explanation The system received too many modem control signal interrupts. Modem control signals are hardware handshake signals between data terminal equipment (DTE) and data communications equipment (DCE). The signals include either a data carrier detect (DCD) or a data set ready (DSR), or both DCD and DSR.

Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected or has come loose and is picking up noise. If the cable appears to be connected correctly, check the equipment connected to the cable.

Error Message
%QUICC-1-NOMEMORY: msgtxt_nomemory

Explanation The MC68360/QUICC CPU was unable to access the memory it needs to carry out its functions. The following are possible causes:

The network is large, requiring a lot of memory for routing tables, and so forth.
The router configuration has many features enabled, each of which require a certain amount of memory.
A software error (memory leak) exists.

Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.

Error Message
%QUICC-3-OWNERR: QUICC([dec]/[dec]), Buffer ownership error, pak=0x[hex]

Explanation An internal software error occurred.

Recommended Action Call your technical support representative to obtain a software upgrade.

Error Message
%QUICC-1-TOOBIG: Quicc([dec]/[dec]), packet too big

Explanation A packet greater than the assigned MTU of this serial interface was queued up for transmission.

Recommended Action The system should recover. No action is required. If the message recurs, it may indicate an error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%QUICC-1-TOOSMALL: Quicc([dec]/[dec]), packet was less than 2 bytes

Explanation A small packet (less than 2 bytes) was queued up for transmission. The interface cannot handle such small packets for transmission.

Recommended Action The system should recover. No action is required. If the message recurs, it may indicate a hardware error related to data traffic patterns. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%QUICC-3-UCODE_REV_UNKN: Unknown microcode revision number: [dec]

Explanation The MC68360/QUICC CPU was running an unexpected version of microcode. This problem could be possible if a new version of the QUICC chip was released or if a very old version was used in the manufacturing process. This message could also occur if a new version of microcode was released to fix any bugs.

Recommended Action A decrease in performance might occur for any asynchronous interfaces running PPP. Call your technical support representative if this is an issue.

Error Message
%QUICC-1-UNDERFLO: QUICC([dec]/[dec]), Transmit underflow

Explanation While transmitting a frame, the serial controller chip's local buffer received insufficient data because data could not be transferred to the chip fast enough to keep pace with its output rate. Normally, such a problem is temporary, depending on transient peak loads within the system.

Recommended Action The system should recover. No action is required.

Error Message
%QUICC-1-UNEXPECTED_INTERRUPT: Quicc([dec]), Unexpected modem-signal interrupt

Explanation The software did not expect to see a modem control signal change on this type of WIC card interface.

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

Error Message
%QUICC-3-UNKNOWN_SCCS: Quicc, Incorrect SCC number

Explanation An internal software error occurred.

Recommended Action Call your technical support representative to obtain a software upgrade.

Error Message
%QUICC-1-UNKNOWN_WIC: Quicc([dec]), wic card has an unknown id of [hex]

Explanation The software does not recognize the type of WIC card plugged into the port module.

Recommended Action Check the part number on the WIC card to verify that it is supported in the Cisco IOS release operational on the router or contact your technical support representative.

Error Message
%QUICC-1-UNSUPPORTED_CONFIG: Slot [dec] has an unsupported combination of ISDN WAN interface cards

Explanation It is not possible to support this type of BRI card in slot 1 along with another BRI card in slot 0.

Recommended Action Remove one of the BRI cards from either slot.

Error Message
%QUICC-1-WRONG_SLOT: Quicc([dec]), BRI card in wrong slot(1)

Explanation The BRI card is not supported in WIC slot 0.

Recommended Action Power down, move the BRI card to the other WIC slot on the port module and reboot.

Error Message
%RSP-3-ACCERROR: [chars] acc [hex] had bad value [dec]

Explanation An incorrect value has been written on an accumulator.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. A microcode reload can correct the error condition as a workaround.

Error Message
%SCHED-3-CORRUPT: Scheduler '[chars]' corrupted by process [chars] (expected [hex], found [hex])

Explanation The scheduler has determined that its data structures were corrupted during the execution of the current process. This corruption is the result of either the actions of the process (multiple errors reported against the same process) or an interrupt driver (multiple errors reported against different processes).

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

Error Message
%SCHED-2-SEMUNLOCK: [chars] attempted to unlock semaphore owned by [chars]., 30*ONESEC

Explanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not owned by the process attempting to unlock it.

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

Error Message
%SCHED-2-SETHIGHORCRIT: Attempt to set [chars] priority on process [dec] ([chars])

Explanation Each process executes at a specified priority level. Higher-priority processes must use the new scheduler primitives, while lower-priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified priority too high for a process using old scheduler primitives.

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

Error Message
%SDLC-2-NOMEMORY: No memory available: [chars]

Explanation The requested operation failed because of a low-memory condition.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message
%SNMP-3-BADOID: Attempt to generate an invalid object identifier

Explanation A valid object identifier must contain at least two subidentifiers. An attempt was made to generate an object identifier whose size was less than two.

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

Error Message
%SNMP-3-BADVALUE: Maximum number of index supported is 8

Explanation An SNMP trap contains some number of MIB objects, and the size of the instance identifier for these objects is restricted. This message indicates that an attempt was made to generate an SNMP trap containing a MIB object whose size exceeded this limit.

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

Error Message
%SNMP-3-CPUHOG: Processing [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
%SNMP-4-TRAPDROP: [chars]

Explanation An attempt was made to generate an SNMP trap, but the trap could not be sent because of the reason given in this message. Most likely, this message means that the SNMP traps process is not running.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Use the show process command to determine whether the SNMP traps process is running. If it is not running, reload the system. If, after reloading, the SNMP traps process is still not running, there may not be enough memory for it to run.

Error Message
%SNMP-3-TRAPINTR: Attempt to generate SNMP trap from interrupt level

Explanation During the processing of an interrupt, the code attempted to generate an SNMP trap. This is not allowed.

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

Error Message
%STUN-2-NOMEMORY: No memory available: [chars]

Explanation The requested operation failed because of a low-memory condition.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message
%SWITCH-1-NOMEMORY: msgtxt_nomemory

Explanation The CPU was unable to access the memory it needs to carry out its functions. The following are possible causes:

The network is large, requiring a lot of memory for routing tables, and so forth.
The router configuration has many features enabled, each of which require a certain amount of memory.
A software error (memory leak) exists.

Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.

Error Message
%SYS-3-BADFREEMAGIC: Corrupt free block at [hex] (magic [hex])

Explanation A block of memory at the indicated location is corrupt.

Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.

Error Message
%SYS-2-CFORKBADFUNCT: Can't create process with start address = [hex]

Explanation An internal software error occurred.

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

Error Message
%SYS-2-CHUNKLOCK: Attempted to lock unlockable chunk data, chunk [hex] data [hex]., 10 * ONESEC

Explanation A software error occurred.

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

Error Message
%SYS-5-CONFIG: Configured from [chars] by [chars] [chars]

Explanation The router's configuration was changed.

Recommended Action This is a notification message only. No action is required.

Error Message
%SYS-2-GETBUFFFAIL: [chars] buffer allocation ([dec] bytes) failed from [hex], MSGDEF_LIMIT_SLOW

Explanation An operation could not be accomplished because of a low-memory condition. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router's memory.

Recommended Action If this message recurs, copy it exactly as it appears and report it 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 messages.

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, [chars]:[dec] to [chars]:[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 a user application after the connection was already half closed.

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

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

Explanation The TCP Intercept code has changed state.

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

Error Message
%TCP-3-NOTFOUND: Connection info for ([int]:[dec]) = ([int]:[dec]) not found.

Explanation The TCP Intercept code was searching its database for information for a particular connection, but this information was not found.

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

Table of Contents