System Error Messages for 11.2 P

This chapter lists and describes the system error messages for Cisco IOS Release 11.2 P, up to and including 11.2(14)P. 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.

This chapter only lists error messages for Cisco IOS Release 11.2 P that are not documented in the Cisco IOS Release 11.2 System Error Messages manual. For additional system error messages, refer to the System Error Messages manual.

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 1 lists the system facilities codes.

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

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.

**Table 1: Facility Codes**
Code	Facility
AAAA	TACACS+ Authentication, Authorization, and Accounting security
AIP	ATM Interface Processor
ALIGN	Memory optimization in Reduced Instruction-Set Computer (RISC) processor
AMDP2_FE	Presidio Ethernet & Laguna Fast Ethernet
APPN	Advanced Peer-to-Peer Networking
ARAP	Apple Remote Access Protocol
ASPP	Asynchronous Security Protocol
AT	AppleTalk
ATM	Asynchronous Transfer Mode
BAP	PPP Bandwidth Allocation Protocol (BAP)
BGP	Border Gateway Protocol
BRI	Integrated Services Digital Network (ISDN) Basic Rate Interface
BRIMUX	AS5200 BRIMUX board
BSC	Binary Synchronous Communications mode
BSTUN	Block serial tunneling
C1600	Cisco 1600 platform
C3600	Cisco 3600 platform
C5RSP	Cisco Catalyst 5000 platform
CBUS	ciscoBus controller
CDM	Cable Data Modem subsystem
CI	75xx platform chassis interface
CIP facility	Channel Interface Processor
CIRRUS_PM	Slow speed async/sync port module
CLEAR	Clear facility
CLNS	OSI Connectionless Network Service
CLS	Cisco Link Services
CLSDR	Cisco Link Services Driver
COMP	Point-to-point compression
CONTROLLER	Controller
CPAD	Compression service adapter
CPM	Combo Port Module device driver
CRYPTO	Encryption
CSC2	CSC2/CSC3 CPU cards
CSM	CSM integrated modem
CT3	Channelized T3 port adapter
DBUS	Data bus
DIALER	Dial-on-demand routing
DLC	Data-link control
DLSw	Data-link switching
DMA	Direct memory access
DNET	DECnet
DRP	Director Response Protocol
DSPU	Downstream physical unit
DSX1	Channelized E1 (Europe) and T1(US) telephony standard
DUAL	Enhanced Interior Gateway Routing Protocol
DVMRP	Distance Vector Multicast Routing Protocol
EGP	Exterior Gateway Protocol
ENT_API	Entity MIB API
ENV	Environmental monitor card
ESWITCH	Ethernet switched port adapter
ETHERNET	Ethernet for the C1000 series
FDDI	Fiber Distributed Data Interface
FLASH	Flash nonvolatile memory
FR	Frame Relay
FTC_TRUNK	Cisco 3801 platform
FW	Inspection subsystem
GRIP	Xerox Network Systems (XNS) Routing Protocol
HD	HD64570 serial controller
HOOD	LAN controller 100VG-AnyLAN interface
HMM_ASYNC	Hex modem network module asynchronous driver
HP100VG	100VG-AnyLAN PA driver
HUB	Cisco Ethernet hub
IBM2692	IBM Token Ring chip set
IDMGR	ID-Manager
IFS	IOS File System
IGRP	Interior Gateway Routing Protocol
ILACC	ILACC driver
INTERFACE_API	Binary API for the interface descriptor block
IP	Internet Protocol
IPC	Interprocess Communication
IPFAST	IP fast switching
IPRT	Internet Protocol routing
IPX	Internetwork Packet Exchange Protocol
IP-SNMP	Simple Network Management Protocol specific to IP
ISDN	Integrated Services Digital Network
LANCE	Local Area Network Controller Ethernet
LANE	LAN Emulation
LANMGR	IBM LAN Network Manager
LAPB	X.25 Link Access Procedure, Balanced
LAT	DEC Local Area Transport
LEX	LAN extension
LINEPROTO	Line Protocol
LINK	Data link
LLC2	Logical Link Control type 2
LNMC	LAN network manager
LPD	Line printer daemon
MAILBOX	ChipCom mailbox support
MBRI	Multi-BRI port module
MCI	Multiport Communications Interface
MICA	Modem ISDN Channel Aggregation modem
MK5	MK5025 serial controller
MMODEM	Integrated modem network module
MODEM	Modem management
MPA68360	VIP Multi-channel Port Adapter
MROUTE	Multicast route
MUESLIX	Mx serial application-specific integrated circuit (ASIC)
NIC100	NIC100 driver
NIM	Network interface module
OSPF	Open Shortest Path First
PA	Port adapter
PAD	X.25 packet assembler/disassembler
PARSER	Parser
PIM	Protocol-independent multicast
PPP	Point-to-Point Protocol
QA	Queue and accumulator
QLLC	Qualified Logical Link Control
QUICC	MC68360 Quad Integrated Communications Controller
RADIUS	Remote Access Dial-In User Service (RADIUS) facility
RADIX	Radix facility
RCMD	Remote commands
RIP	IP Routing Information Protocol
RSP	Route Switch Processor
RSRB	Remote source-route bridging
S4T68360	Four port synchronous serial adapter based on the 68360 processor
SCHED	Scheduler
SDLC	Synchronous Data Link Control
SDLLC	SDLC/Logical Link Control type 2 (LLC2) translation
SEC	IP security
SERVICE_MODULE	Service Module
SLIP	Serial Line Internet Protocol
SMRP	Simple Multicast Routing Protocol
SNAPSHOT	Snapshot dial-on-demand routing
SNMP	Simple Network Management Protocol
SNMP_MGR	SNMP Proxy
SSE	Silicon switching engine
STANDBY	Hot Standby Router Protocol (HSRP)
STUN	Serial tunneling
SUBSYS	Software subsystems
SWITCH	Switch interface
SYS	Operating system
SYSMGT	System management
TAC	Terminal Access Controller Protocol Access Control System
TBRIDGE	Transparent bridging
TCP	Transmission Control Protocol
TMQ	Inbound terminal port queuing
TN	Telnet
TN3270	TN3270 protocol
TR	Token Ring
TUN	Tunnel
UCODE	Microcode
UNIX	UNIX
UTIL	Utility
VINES	Banyan VINES
VIP	Versatile Interface Processor
VPN	Virtual Private Dialup Network
X25	X.25

**Table 2: 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 3: Representation of Variable Fields in Error Messages**
Representation	Type of Information
[atalk_address]	AppleTalk address
[atalk_net]	AppleTalk network, either 600 or 600-601
[char]	Single character
[chars]	Character string
[dec]	Decimal number
[enet]	Ethernet address (for example, 0000.FEED.00C0)
[hex]	Hexadecimal number
[inet]	Internet address (for example, 12.128.2.16)
[int]	Integer number
[node]	Address or node name
[sci_notation]	Scientific notation
[t-line]	Terminal line number in octal (or decimal if the decimal-TTY service is enabled)
[v-name]	VINES name; or number (hex or decimal)

Error Messages

This section lists error messages alphabetically by facility and mnemonic.

Error Message
%AAAA-3-BADARG: [atalk_address]talk_address]AA: bad argument ([hex])

Explanation NVGEN was attempted on a non-existent AAA command.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%AAAA-3-BADLIST: [atalk_address]talk_address]AA: bad [chars] list [dec]

Explanation One of the AAA methods does not seem to have a list associated with it.

Error Message
%AAAA-3-BADSTATE: [atalk_address]talk_address]AA: Bad state for [chars] list name ([dec])

Explanation An AAA method list is neither default nor named.

Error Message
%AAAA-3-DROPACCT: accounting record dropped: [chars]-[chars] [chars] [chars]

Explanation An attempt to send an accounting record to a server failed.

Recommended Action Check that the server (TACACS+ or RADIUS) is operational. Next, check the NAS is configured properly. Finally, check that the NAS can communicate with the server.

Error Message
%AAAA-3-INVALIDLIST: [atalk_address]talk_address]AA: invalid [chars] list [dec]

Explanation One of the AAA methods lists has inconsistent settings.

Error Message
%AAAA-3-LOSTTIMER: Lost periodic accounting timer for user [chars]. Restarting timer...

Explanation Somehow, the periodic timer associated with this ustruct has been lost.

Recommended Action Re-allocate and restart a timer.

Error Message
%AAAA-3-MKTIMERFAIL: Failed to create periodic accounting timer for user [chars]. This user may not generate periodic accounting records

Explanation Failed to malloc a timer struct for periodic accounting.

Recommended Action Free up some memory and have the user re-authenticate.

Error Message
%AAAA-3-NOFREELISTS: [atalk_address]talk_address]AA: No free [chars] lists for [chars]

Explanation You have reached the maximum number of possible authentication lists for this method.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%AAAA-3-PERIODICFORKFAIL: Failed to start periodic accounting process. Periodic accounting records may not be sent

Explanation Failed to create the periodic accounting process.

Recommended Action Free up some memory.

Error Message
%AAAA-3-PERNOTIMER: AAA/ACCT/TIMER: Periodic update but no timer

Explanation An attempt was made to free a timer, and the method is PERIODIC, but no timer seems to exist.

Error Message
%AAAA-3-TIMERNOPER: AAA/ACCT/TIMER: No periodic update but timer set

Explanation An attempt was made to free a timer, but the update method is not PERIODIC, so no timer should exist.

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]

Explanation Ethernet/Fast Ethernet is seeing multiple collisions. This 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/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 shutdown and no shutdown 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
%ARAP-0-DEFAULT: TTY [dec]

Explanation An internal software error occurred.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%ARAP-6-LRPHASERROR: TTY [dec]: Received LT in CONNECTION PHASE

Explanation The router received an invalid packet during ARA connection setup phase.

Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.

Error Message
%ARAP-6-MAXRESENDS: TTY [dec]

Explanation The router resent MNP4 packets the maximum number of times without receiving an acknowledgment.

Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.

Error Message
%ARAP-6-MNP4RCVDISC: TTY [dec]: MNP4 input disconnect

Explanation The router received a disconnect request from the remote Macintosh client.

Recommended Action No action is required.

Error Message
%ARAP-6-MNP4T401: TTY [dec]: T401 [dec] baud rate [dec]

Explanation The router received an MNP4 connection request. The MNP4 acknowledgment timer value is also indicated.

Recommended Action No action is required.

Error Message
%ARAP-2-NOLOG: TTY [dec]: Could not malloc log

Explanation Memory not available for internal MNP4 logging.

Error Message
%ARAP-0-NOTNULLRESEND: TTY [dec]

Explanation An internal software error occurred.

Error Message
%ARAP-0-NULLRESEND: TTY [dec]

Explanation An internal software error occurred.

Recommended Action Report this error to your technical support representative.

Error Message
%ARAP-6-RCVGIANT: TTY [dec]: Rcv giant. dropping frame

Explanation The router received an oversized MNP4 frame.

Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.

Error Message
%ARAP-6-RCVNOPAK: TTY [dec]: Receive getbuffer failure. dropping frame

Explanation No buffer exists for an incoming packet.

Recommended Action Examine buffer usage statistics. Possibly more memory is required.

Error Message
%ARAP-3-REMOTEERROR: TTY [dec]: arap input error

Explanation ARAP connection was terminated without a known cause.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

Error Message
%ARAP-6-RESENDSLOW: TTY [dec]

Explanation The router repeated resending of MNP4 packets as the Macintosh client failed to acknowledge previously resent packets.

Recommended Action If this error message persists for several ARAP connections, report it to your technical support representative.

Error Message
%ARAP-6-TIMERERROR: TTY [dec]: MNP4 timeout error

Explanation The router is dropping the connection after doing maximum resends.

Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.

Error Message
%ARAP-0-VSERROR: TTY [dec]: VS queued error

Explanation An internal software error occurred.

Error Message
%ARAP-0-WAITBADMSG: TTY [dec]: arg msg bad [hex]

Explanation The router received an invalid packet during ARAP MNP4 connection setup phase.

Recommended Action Check for excessive line noise. Check the ARAP client software configuration for possible problems.

Error Message
%ARAP-6-XTICKLE: TTY [dec]: exited user [chars]: Other side stopped answering ARAP tickles (mnp4 pak resent [dec] mnp4 pak sent [dec] last [dec] now [dec])

Explanation The router disconnected as the remote Macintosh client stopped sending ARAP tickle or data packets.

Recommended Action To determine the cause of the disconnection, correlate the receipt of this message with the user problem reports.

Error Message
%BGP-3-ADDROUTE: Unable to add route for [inet] 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 on the console or in the system log, and report it to your Cisco technical support representative.

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

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

Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

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

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 on the console or in the system log, and report it to your Cisco technical support representative.

Error Message
%BGP-2-INSUFMEM: Insufficient memory for [chars] entry

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
%BGP-3-MAXPATHS: Too many parallel paths for [inet], maximum is [dec]

Explanation The number of parallel paths exceeds the configured limit.

Recommended Action Increase the number of parallel paths allowed.

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

Explanation The software does not recognize an interface, but your router is functional.

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-ACFAIL: System detected Redundant Power System AC FAIL condition

Explanation The Redundant Power System experienced an AC failure.

Recommended Action One of the AC inputs has failed on the Redundant Power Supply. The "AC Input" LED on the front of the Redundant Power Supply will identify which AC input has failed. Ensure that the AC circuit in your building is operational, verify that the power cord is plugged into the Redundant Power Supply, and ensure that the AC power switch on the Redundant Power Supply is on.

Error Message
%C3600-3-ACOK: Redundant Power System AC condition is now normal

Explanation The Redundant Power System AC is normal.

Recommended Action This is an informational message only. No action is required.

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
%C3600-3-DCFAIL: System detected Redundant Power System DC FAIL condition

Explanation The Redundant Power System experienced a DC failure.

Recommended Action One of the DC outputs has failed on the Redundant Power Supply. The "DC Status" LED on the front of the Redundant Power Supply will identify which DC output has failed. When there is a DC failure, you must replace the Redundant Power Supply.

Error Message
%C3600-3-DCOK: Redundant Power System DC condition is now normal

Explanation The Redundant Power System DC is normal.

Recommended Action This is an informational message only. No action is required.

Error Message
%C3600-3-MULTFAIL: There is more than one failure with the Redundant Power System; please resolve problems immediately

Explanation The Redundant Power System experienced multiple failures. This is a critical condition.

Recommended Action There are multiple failures on the Redundant Power Supply. Examine the LEDs on the front of the Redundant Power Supply to find out which failures have occurred.

Error Message
%C3600-3-NVERASEFAIL: Failed to erase config due to internal error

Explanation The password protection feature failed to erase the configuration because of an internal error.

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

Error Message
%C3600-3-OVERTEMP_OK: System temperature is now normal

Explanation The system is operating at a normal temperature.

Recommended Action The system previously detected an over-temperature condition, which has now cleared. This is most likely because of a high ambient temperature where the router is located.

Error Message
%C3600-3-RPSOK: Redundant Power System is now normal

Explanation The Redundant Power System is operating normally.

Recommended Action This is an informational message only. No action is required.

Error Message
%C3600-3-THERMAL: System detected Redundant Power System THERMAL FAIL condition

Explanation The Redundant Power System experienced either a fan failure or an over-temperature condition.

Recommended Action Look at the "FAN" and "TEMP" LEDs on the front of the Redundant Power Supply. If the "FAN" LED is amber, one of the fans has failed and you should replace the Redundant Power Supply. If the "TEMP" LED is amber, the ambient temperature is too high.

Error Message
%C3600-3-THERMOK: Redundant Power System THERMAL condition is now normal

Explanation The Redundant Power System THERMAL is now normal.

Recommended Action The Redundant Power Supply previously detected an over-temperature condition, which has now cleared. This is most likely because of a high ambient temperature where the Redundant Power Supply is located. A Redundant Power System thermal failure can also be caused by a fan failure in the Redundant Power Supply.

Error Message
%C5RSP-6-BRIDGE_AFU: vlan [dec] could/could not be configured for bridging

Explanation A virtual LAN (VLAN) could not be reset with the proper bridging information.

Recommended Action To remedy the problem, configure the VLAN with or without bridging.

Error Message
%C5RSP-3-C5_BADIPC: bad message received from the NMP

Explanation An unsolicited in-band IPC message was received by the router from the Network Management Processor (NMP).

Recommended Action No action is required.

Error Message
%C5RSP-3-C5_MACADRFAIL: can't get C5 Line Card Mac Addr

Explanation An attempt by the RSP to query the C5IP for VLAN 0 IP address failed.

Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problems persist, contact Cisco for replacement.

Error Message
%C5RSP-3-C5_NMPMACADRFAIL: can't get NMP Mac Addr

Explanation An attempt by the RSP to query the C5IP for VLAN 0 MAC address failed.

Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problems persist, contact Cisco for replacement.

Error Message
%C5RSP-3-C5_SAGE0FAIL: Length error occurred on dma channel 0

Explanation A hardware error has occurred on DMA channel 0.

Recommended Action Report this error to your technical support representative.

Error Message
%C5RSP-3-C5_SAGE1FAIL: Length error occurred on dma channel 1

Explanation A hardware error has occurred on DMA channel 1.

Recommended Action Report this error to your technical support representative.

Error Message
%C5RSP-3-C5IP_SLOTFAIL: can't get Catalyst 5000 Slot number of router

Explanation An attempt by the RSP to query the C5IP for the lot it is plugged into has failed.

Recommended Action To remedy the problem, reset the router from the Network Management Processor's (NMP) console. If the problem persists, contact Cisco for replacement.

Error Message
%C5RSP-3-CANT_CREATE_VLAN: vlan [dec] cannot be created. media not supported

Explanation An attempt to create a virtual LAN (VLAN) of a media that is not supported has failed.

Recommended Action To remedy the problem, configure the VLAN with a different media type.

Error Message
%C5RSP-3-INVALID_LOVE_LETTER: Invalid loveletter type, [dec], sent by c5ip

Explanation Cisco IOS software is receiving bogus messages from the C5IP.

Recommended Action No action is required. If problems persists, contact your Cisco technical support representative.

Error Message
%C5RSP-3-MAXVLAN_EXCEEDED: can't configure more than 256 VLANS

Explanation The VLAN router product can configure a maximum of 256 virtual LANs.

Recommended Action To remedy the problem, delete unused VLANs before configuring new ones.

Error Message
%C5RSP-3-NMP_DELETE_VLAN: having problems deleting vlan [dec] on the NMP

Explanation An in-band IPC message to the Network Management Processor (NMP) from the router to delete a virtual LAN (VLAN) has failed.

Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP via the front-panel LED, and check the state of the NMP. Reset the router.

Error Message
%C5RSP-3-NMP_INIT_FAIL: can't talk to NMP during initialization

Explanation An in-band IPC router initialization message to the Network Management Processor (NMP) has failed.

Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP on the front-panel LED, and check the state of the NMP. Reset the router.

Error Message
%C5RSP-3-NMP_PROG_FAIL: NMP won't allow vlan [dec] configuration

Explanation An in-band IPC message from the router to the Network Management Processor (NMP) to create a virtual LAN (VLAN) has failed.

Recommended Action To remedy the problem, check the state of VLAN 0, check the state of the C5IP on the front-panel LED, and check the state of the NMP. Reset the router.

Error Message
%C5RSP-6-NOSWIDB: vlan [dec] missing IDB

Explanation Internal data structure of the virtual LAN (VLAN) is missing.

Recommended Action Contact your Cisco technical support representative.

Error Message
%C5RSP-3-UNKNOWN_NMP_PROG: unknown timer for NMP programming

Explanation An unknown timer event has expired.

Recommended Action No action is required.

Error Message
%C5RSP-6-VLAN_INFO_MISSING: vlan [dec] info errant. something very wrong

Explanation Internal information about the virtual LAN (VLAN) is missing.

Recommended Action Contact your Cisco technical support representative.

Error Message
%CBUS-3-ADDRFILTR: Interface [chars], address filter [chars] command failed, code [hex]

Explanation The specified address filter command sent to the specified interface failed with the displayed error code.

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]

Explanation An interface received a packet with bad VC encapsulation. This indicates either a software or hardware problem.

Error Message
%CBUS-3-CATMCFG: Interface [chars], Cannot config interface, CBus ATM MEM 0x[hex], status [dec]

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
%CBUS-3-CATMREJCMD: [chars] [chars] command failed (error code 0x[hex])

Explanation The ciscoBus ATM microcode rejected a command sent by the Route Processor (RP). The error code is the status value returned by the command.

Error Message
%CBUS-3-CATMRSET: Interface [chars], Error ([hex]) [chars] - aip_reset()

Explanation A software error occurred.

Error Message
%CBUS-3-CATMRSETU: Unit [dec], Error ([hex]) [chars] - cbus_atm_reset()

Explanation A software error occurred.

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]

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

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.

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 love note error message.

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 the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco 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.

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.

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 the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

Error Message
%CBUS-5-FDDICMD: '[chars]' is not supported on [chars]

Explanation This command is not supported on this FDDI interface.

Recommended Action No action is required.

Error Message
%CBUS-2-IPAUTO: [chars] [hex] - disabling autonomous

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-SERRSET: Interface [chars], Error ([hex]) [chars] - serial_reset()

Explanation A software error occurred.

Error Message
%CDM-3-CONFIG: Interface [chars] must be ACIP to run cable application

Explanation The named interface is not an ATM Cable Interface Processor (ACIP) interface.

Recommended Action An ACIP is required to run the cable data modem (CDM) application. Check that an ACIP is installed in the system.

Error Message
%CDM-3-INIT: ACIP required to run this Cisco IOS image

Explanation No ATM Cable Interface Processor (ACIP) is installed in the system.

Recommended Action An ACIP is required to run the cable data modem (CDM) application. Install ACIP.

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 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 Ensure that sufficient memory is 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 into which it is being plugged.

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]

Explanation An internal error occurred in the Intermediate System-to-Intermediate System (ISIS) 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.

Error Message
%CLS-3-CLSMSG: [chars]

Explanation A software error was detected while manipulating CLSIMsg objects.

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

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

Explanation An error occurred in the application using the compression service adapter (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 compression service adapter (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 compression service adapter (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 compression service adapter (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 compression service adapter (CSA) is shutting down. It may have been physically removed.

Recommended Action This is an informational message only and occurs in normal operation. No action is required.

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

Explanation The specified compression service adapter (CSA) has initialized successfully.

Recommended Action This is an informational message only and occurs in normal operation. No action is required.

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 protocol control information (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
%CRYPTO-0-AUDITFAIL: Encryption audit check found the wrong level of encryption in this image

Explanation The audit check that verifies encryption entitlement within Cisco IOS images either found encryption in a non-encryption image or the wrong strength within a Cisco IOS encryption image. Using the encryption image may violate U.S. Export Laws and Regulations.

Recommended Action Contact Cisco to obtain a replacement Cisco IOS image.

Error Message
%CRYPTO-4-AUDITWARN: Encryption audit check could not be performed

Explanation The audit check that verifies encryption entitlement within Cisco IOS images could not be performed because of an incomplete system configuration.

Recommended Action Manually verify that this Cisco IOS image is entitled to contain encryption.

Error Message
%CSM-1-CSM_BAD_EVENT: [chars]: [dec]/[dec] received invalid event [dec]

Explanation An invalid operation was detected by the router.

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

Error Message
%CSM-1-CSM_MODEM_BAD: Modem [dec]/[dec] has been marked as bad by the router software.

Explanation The modem is no longer usable because of a runtime error.

Recommended Action The modem may become operational following a reset of the router. If not, copy the error message exactly as it appears and contact your technical support representative.

Error Message
%CSM-1-HWIDB: [chars]: hwidb is NULL

Explanation An invalid operation was detected by the router.

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

Error Message
%CSM-1-INITSYS: [chars]

Explanation The modem signaling module failed initialization.

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

Error Message
%CSM-1-NODCHAN: Signaling channel not available

Explanation Modem calls cannot be processed.

Recommended Action Verify that the PRI network module is compatible with the modem network module. If not, copy the error message exactly as it appears and contact your technical support representative.

Error Message
%CSM-1-QUEUE_ERROR: An error was encountered in enqueuing a disconnect for modem [dec]/[dec]

Explanation The modem may no longer be usable if the amount of memory available in the router is not sufficient.

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

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

Explanation Unexpected message was 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-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 This is a 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 This message indicates a 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 This message indicates a 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 the 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 This message indicates a failure to detect the HDLC controller on the CT3.

Recommended Action Replace the CT3 port adapter.

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 adapter.

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
%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
%DLSWC-3-IDMGR: [chars]

Explanation A data-link switching system error occurred.

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

Explanation The largest frame size configured in the DLSW remote peer definition is being changed. This change occurred 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 then the configured largest frame size.

Error Message
%DSX1-1-M32_INPUT_CONGEST: Munich 32 channel input queue is congested

Explanation The router can't allocate receive buffers because the input queue is at its maximum. This indicates data is coming faster than the receiver can handle.

Recommended Action Reduce data going into this channel, or increase the number of input queue.

Error Message
%ESWITCH-1-DEC21140: ESWITCH([dec]) Failed to initialize DEC21140, shutting down bay

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
%ESWITCH-1-EALE: ESWITCH([dec]) Failed to initialize EALE

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-MULTICASTADD: ESWITCH([dec]), Cannot add multicast [sci_notation]

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-5-NOBRIDGEGROUP: ESWITCH([dec]), Bridge-group must be configured

Explanation A configuration error occurred.

Recommended Action Configure a bridge group on the interface.

Error Message
%ESWITCH-5-NOMOREVLANS: ESWITCH([dec]), Only [dec] Bridge-Groups(vLANS) are supported

Explanation A configuration error occurred.

Recommended Action Only configure the allowed number of bridge groups on the Ethernet switch port adapter.

Error Message
%ESWITCH-1-NOTPLX: ESWITCH([dec]) Device is not PLX 9060SD, Device reported [hex]

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-PCIINIT: ESWITCH([dec]) Failed to initialize PCI devices, shutting down bay

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-TSWITCH: ESWITCH([dec]) Failed to initialize TSWITCH

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-TSWITCHEALE: ESWITCH([dec]) Failed to initialize TSWITCH/EALE, shutting down bay

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
%ESWITCH-1-UNICASTADD: ESWITCH([dec]), Cannot add unicast [sci_notation]

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-UNICASTDEL: ESWITCH([dec]), Cannot remove unicast [sci_notation]

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-UNICASTDELP: ESWITCH([dec]), Cannot flush unicasts from port [dec]

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-UNICASTDELPV: ESWITCH([dec]), Cannot flush unicasts from vLAN [dec] on uplink

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-UNICASTDELV: ESWITCH([dec]), Cannot flush unicasts from vLAN [dec]

Explanation A hardware error occurred.

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

Error Message
%ESWITCH-1-UNICASTLOCK: ESWITCH([dec]), Cannot lock unicast [sci_notation]

Explanation A hardware error occurred.

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

Error Message
%FR-4-DLCIDELETE: Interface [chars] - DLCI [dec] - PVC use count [dec]

Explanation An attempt was made to remove PVC DLCI while it was still being used.

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

Error Message
%FR-3-INCORRECT_INT: Incorrect output (sub)interface, broadcast packet dropped!

Explanation Output interface or subinterface specified in a packet is incorrect, and the broadcast packet is dropped.

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

Error Message
%FR-3-NULL_INT: Null output interface. Broadcast packet dropped!

Explanation Output interface is NULL, broadcast packet is dropped.

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

Error Message
%FW-4-ALERT_OFF: [chars], count ([dec]/[dec]) current 1-min rate: [dec]

Explanation The number of half open connections (or the connection rate) has gone below the low threshold.

Recommended Action This is an informational message only. No action is required.

Error Message
%FW-4-ALERT_ON: [chars], count ([dec]/[dec]) current 1-min rate: [dec]

Explanation The high threshold of the number of half open connections (or connection rate) has been exceeded.

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

Error Message
%FW-2-BLOCK_HOST: Blocking new TCP connections to host [int] for [dec] minute[chars] (half-open count [dec] exceeded).

Explanation New TCP connection attempts to the specified host are denied because the per-host maximum limit of half-open TCP connections has been exceeded.

Recommended Action This message may indicate a SYN flood attack attempt to the specified host. The configuration specifies that the IP traffic to the host is to be blocked.

Error Message
%FW-3-FTP_NON_MATCHING_IP_ADDR: Non-matching address [int] used in [chars] -- FTP client [int] FTP server [int]

Explanation The CBAC code detected a non-matching IP address in the PORT command or in a response to a PASV command. The connection is reset.

Recommended Action This message may indicate an attempt to gain access to unauthorized hosts.

Error Message
%FW-3-FTP_PRIV_PORT: Privileged port [dec] used in [chars] -- FTP client [int] FTP server [int]

Explanation The CBAC code detected a privileged port number in the PORT command or in a response to a PASV command. Only 1023 ports are supported. The connection is reset.

Recommended Action This message may indicate an attempt to gain access to privileged ports.

Error Message
%FW-3-FTP_SESSION_NOT_AUTHENTICATED: Command issued before the session is authenticated -- FTP client [int] FTP server [int]

Explanation The CBAC code encountered a PORT command or PASV response before the session is authenticated. The command or the response was not processed. (The data channel was not opened).

Recommended Action This message may indicate an illegal attempt to access the server.

Error Message
%FW-4-HOST_TCP_ALERT_ON: Max tcp half-open connections ([dec]) exceeded for host [int]

Explanation The per-host maximum limit of half-open TCP connections has been exceeded.

Recommended Action This message is for informational purposes only, but may indicate a SYN flood attack attempt to the host.

Error Message
%FW-4-HTTP_JAVA_BLOCK: JAVA applet is blocked from ([int]:[dec]) to ([int]:[dec])

Explanation The Inspect code detected a JAVA applet entering into a secured area and the JAVA applet was denied.

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

Error Message
%FW-3-NOTFOUND: Session context for ([int]:[dec]) =([int]:[dec]) not found

Explanation The CBAC code was searching its database for information for a particular inspection session, 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.

Error Message
%FW-6-SESS_AUDIT_TRAIL: [chars] session initiator ([int]:[dec]) sent [int] bytes -- responder ([int]:[dec]) sent [int] bytes

Explanation This message is an audit trail of a session and lists the address or port information and the number of bytes sent.

Recommended Action This message is for informational purposes only and can be used to collect the basic accounting information for the inspected sessions.

Error Message
%FW-3-SMTP_INVALID_COMMAND: Invalid SMTP command from initiator ([int]:[dec])

Explanation The CBAC code detected an invalid SMTP command.

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

Error Message
%FW-4-UNBLOCK_HOST: New TCP connections to host [int] no longer blocked

Explanation New TCP connection attempts to the specified host are no longer blocked.

Recommended Action This message is for informational purposes only, but may indicate a SYN flood attack was attempted to the host.

Error Message
%HMM_ASYNC-3-CARD_FAILED_DOWNLOAD: Unable to download firmware image to digital modem card in slot [dec]

Explanation The processor on the digital modem card failed to initialize.

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

Error Message
%HMM_ASYNC-3-MODEM_FAILED_DIAGS: Digital modem [dec]/[dec] on Simm [dec] failed power on diagnostics

Explanation The digital modem did not pass the power diagnostics. It will not be used.

Recommended Action If the remaining SIMMs pass diagnostics, remove or replace the problem SIMM before continuing. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%HMM_ASYNC-3-MODEM_STOPPED_PROCESSING_MAIL: HMM Modem [dec]/[dec] failed to accept a new command

Explanation The modem did not accept a new command. This problem may be a transient failure or the modem may remain unusable until the system is reset.

Recommended Action You may try to reset the modem by issuing the clear modem slot/port command. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%HMM_ASYNC-3-NOMEMORY: No memory for [chars] of unit [dec]

Explanation The router does not have enough memory to perform the function.

Recommended Action Consider adding more shared memory. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%HMM_ASYNC-4-NO_MODEMS_PRESENT: HMM Digital Modem Card [dec] contains no active modems

Explanation There are no modems installed on the network module.

Recommended Action Make sure the network module contains properly installed MICA-6DM SIMMs.

Error Message
%HMM_ASYNC-3-NORAWRXPOOL: Unable to create pool for [dec] raw Rx mode buffers

Explanation The router does not have enough I/O memory for buffers.

Error Message
%HMM_ASYNC-3-NORAWTXPOOL: Unable to create pool [dec] raw Tx mode buffers

Explanation The router does not have enough I/O memory for buffers.

Error Message
%HMM_ASYNC-3-NOTTYCREATE: Unable to create TTY structure for line [dec]

Explanation Unable to create TTY line control block for the specified line. This may be caused by not having enough memory in the router.

Error Message
%HMM_ASYNC-3-SIMM_FAILED_DOWNLOAD: Unable to download modem firmware image to Simm [dec] in slot [dec]

Explanation Modem firmware failed to load onto the SIMM.

Recommended Action If firmware successfully loaded onto remaining SIMMs, remove or replace the problem SIMM before continuing. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%HMM_ASYNC-3-SIMM_RUNTIME_ERROR: Simm [dec] in slot [dec] has halted due to a Runtime Error

Explanation The portware running on the SIMM was halted because of a runtime error. The six modems contained on the SIMM have been marked "bad" and are not usable until the system is reloaded.

Recommended Action Copy the error message exactly as it appears, along with the output from the show modem and show modem log commands, and report it to your technical support representative.

Error Message
%HMM_ASYNC-3-TDM_SYNTHESIS_ERROR: HMM Digital Modem Card [dec] experienced a TDM Synthesis Error.

Explanation The digital modem card failed to send or receive PCM data in time to avoid data loss. This may cause the modems to speed shift, retrain, or hangup.

Recommended Action Verify that the DS1 interfaces share a common clock source. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%HMM_ASYNC-3-UNKNOWN_MESSAGE: Received unknown message 0x[hex] at mail offset [dec] from modem [dec]/[dec]

Explanation An unidentified message was received from the modem. This is symptomatic of running an incompatible version of modem firmware.

Error Message
%HMM_ASYNC-3-UNKNOWNPLATFORM: Unknown Platform type to support HMM Network Module

Explanation The network module is not compatible with the current platform that it is plugged in to.

Error Message
%HOOD-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

Recommended Action If either 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 either 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 either message recurs, and either the cable or hub appears to be good, repair or replace the router module.

Error Message
%HP100VG-1-ACCESS: HP100VG([dec]/[dec]), Access to network is not allowed

Explanation Access to the network is denied because of incompatible configuration.

Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.

Error Message
%HP100VG-5-CABLEERR: HP100VG([dec]/[dec]), cable error, training failed

Explanation A 100VG cable or hub is faulty.

Recommended Action Repair or replace the cable or hub. If the cable or hub appears to be good, repair or replace the VG PA interface module.

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

Explanation No VG interface was detected.

Recommended Action Ensure that the 100VG PA is properly seated in the slot. Otherwise, repair or replace the 100VG PA interface module.

Error Message
%HP100VG-1-DUPMAC: HP100VG([dec]/[dec]), A duplicate MAC address has been detected

Explanation Two VG devices on the same LAN segment have the same MAC address.

Recommended Action Check the router configuration to ensure that no duplicate MAC address is configured.

Error Message
%HP100VG-1-FAIL: HP100VG([dec]/[dec]), Training Fail - unable to login to the hub

Explanation Unable to log in to the hub.

Recommended Action Take action based on the error messages that appear after this error message.

Error Message
%HP100VG-1-LANCNF: HP100VG([dec]/[dec]), Router configuration is not compatible with the network

Explanation Configuration of the router module is not compatible to the network.

Recommended Action Check the configuration of the hub for the Frame Format, Promiscuous, and Repeater bits to indicate proper configuration.

Error Message
%HP100VG-5-LOSTCARR: HP100VG([dec]/[dec]), lost carrier, MSGDEF_LIMIT_SLOW

Explanation The VG controller detects a link to the hub is down because of a cable, hub, or VG controller problem.

Recommended Action Repair or replace the cable or hub. If either the cable or hub appears to be good, repair or replace the VG PA interface module.

Error Message
%HP100VG-5-NOCABLE: HP100VG([dec]/[dec]), no tone detected, check cable, hub

Explanation A 100VG cable is faulty.

Recommended Action Repair or replace the cable. If the cable appears to be good, repair or replace the VG PA interface module.

Error Message
%HP100VG-3-NOCAM: HP100VG([dec]/[dec]), No Hardware CAM device found

Explanation Could not find a hardware CAM on the PA module.

Recommended Action Repair or replace the 100VG PA interface module.

Error Message
%HP100VG-3-NOTHP100VG: Device reported [hex]

Explanation Could not find a 100VG PCI device.

Recommended Action Make sure 100VG PA is properly seated in the slot. Otherwise, repair or replace the 100VG PA interface module.

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

Explanation A software or hardware error occurred. The HP100VG driver detected that the buffer 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
%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 the router, reinsert the network module and reboot the router. 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
%IDMGR-3-INTERRUPT: [chars]

Explanation An id_get was attempted at the interrupt level.

Error Message
%IDMGR-3-INVALID_ID: bad id in [chars]

Explanation An ID Manager error occurred.

Error Message
%IDMGR-3-MALLOC_FAILURE: [chars]

Explanation A malloc failure occurred in the ID Manager.

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

Explanation An internal software error occurred.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

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

Explanation An internal software error occurred.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

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

Explanation An internal software error occurred.

Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco 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 is caused by 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
%IP-4-ZERO_ADDR: Zero MAC address for [int] in ARP cache

Explanation An entry in the ARP cache has a NULL MAC address.

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 on the console or in the system log, and report it to your Cisco technical support representative.

Error Message
%IPX-6-NOVACCESSLOG: [dec] [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-6-CHAN_UNAVAILABLE: Interface [chars] Requested Channel [dec] is not available

Explanation The requested channel is not available.

Recommended Action This is an informational message only. No action is required.

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 service profile identifier (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-6-LAYER2DOWN: Layer 2 for Interface [chars], TEI [int] changed to down

Explanation This is an informational message. It is sent when an ISDN Layer 2 logical link is down. It also shows the terminal endpoint identifier (TEI) associated with this logical link.

Recommended Action No action is required.

Error Message
%ISDN-6-LAYER2UP: Layer 2 for Interface [chars], TEI [int] changed to up

Explanation This is an informational message. It is sent when an ISDN Layer 2 logical link is up. It also shows the terminal endpoint identifier (TEI) associated with this logical link.

Recommended Action No action is required.

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
%LANCE-3-BADCABLE: msgtxt_badcable

Explanation Ethernet cable is not connected.

Recommended Action Check Ethernet cable connection.

Error Message
%LANE-3-LANE_SIG_INV_SDU: invalid SDU received in SETUP Call from: ATM NSAP - %Ch received forward SDU size is [dec] received backward SDU size is [dec] SDU size on the interface [chars] is [dec] Call Rejected

Explanation The incoming SDU size did not match the SDU size of the client.

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 when 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
%LAT-3-BADDATA: Tty[t-line], Data pointer does not correspond to current packet

Explanation An internal software error occurred.

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

Error Message
%LAT-3-BUFFULL: Tty[t-line], data buffer full with count [dec]

Explanation An internal software error occurred.

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

Error Message
%LAT-3-NOSYNC: Tty[t-line], Output data ptrs out of sync with byte count

Explanation An internal software error occurred.

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

Error Message
%LAT-3-REUSE: Tty[t-line], Attempt to re-use slot array, empty = [dec], fill = [dec]

Explanation An internal software error occurred.

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

Error Message
%LINK-6-BERTSTATUS: Interface [chars], [chars]

Explanation The bit error rate test (BERT) is completed for this interface.

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

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

Explanation The interface entered or exited loopback.

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

Error Message
%LPD-3-MANYLF: Line [t-line], packet has too many newlines to convert

Explanation An internal buffer did not have enough room to add all the necessary carriage returns to a packet of LPD data destined for a printer configured with a newline-convert command. This message is unlikely to occur with a file containing valid data.

Recommended Action Check the file being printed to see whether it contains valid, printable data.

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 Ensure that 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
%MICA-3-BOARD_DL_FAIL: Slot [dec] Boardware download failed because of [chars], all modems are marked bad

Explanation A MICA modem failed to download its on-board software (boardware). This was probably caused by a communication error between the router and the MICA hardware.

Recommended Action Try powercycling the router. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message
%MICA-1-BRDCRASHED: Slot [dec] Mica Board Crashed, Going to Recover

Explanation A MICA board has crashed. The router will automatically restart and reload.

Error Message
%MIF68840-5-NOTSUPPORTED: '[chars]' is not supported on [chars]

Explanation This command is not supported on this FDDI interface.

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

Error Message
%MMODEM-3-HWFAIL: Cannot determine hardware version for integrated modem Network Module in slot [dec]

Explanation The integrated modem network module hardware may be bad.

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

Error Message
%MMODEM-3-IMAGEBAD: Integrated modem image file [chars] cannot be loaded

Explanation The integrated modem override file does not contain a valid image.

Recommended Action The integrated modem network module will be loaded with the default software images. Copy the error message exactly as it appears, and report it to your technical support representative.

Error Message
%MMODEM-3-IMAGEHWINCOMPATMAX: Integrated modem image file [chars] cannot be loaded because it requires a minimum integrated modem network module hardware version between [hex] and [hex], inclusive

Explanation The integrated modem override file is not compatible with the integrated modem hardware version.

Recommended Action The integrated modem network module will be loaded with the default software images. This override file can only be used with specified network module hardware versions.

Error Message
%MMODEM-3-IMAGEHWINCOMPATNOMAX: Integrated modem image file [chars] cannot be loaded because it requires a minimum integrated modem network module hardware version of [hex].

Explanation The integrated modem override file is not compatible with the version of integrated modem hardware.

Recommended Action The integrated modem network module will be loaded with the default software image(s). This override file can only be used with specified network module hardware versions.

Error Message
%MMODEM-3-IMAGEIOSINCOMPATMAX: Integrated modem image file [chars] cannot be loaded because it requires an IOS version between [dec].[dec]([dec].[dec]) and [dec].[dec]([dec].[dec]), inclusive

Explanation The integrated modem override file is not compatible with the Cisco IOS software release running on this router.

Recommended Action The integrated modem network module will be loaded with the default software images. This override file can only be used with specified Cisco IOS releases.

Error Message
%MMODEM-3-IMAGEIOSINCOMPATNOMAX: Integrated modem image file [chars] cannot be loaded because it requires an IOS version of [dec].[dec]([dec].[dec]) or later

Explanation The integrated modem override file is not compatible with the Cisco IOS software release running on this router.

Recommended Action The integrated modem network module will be loaded with the default software images. If you wish to use this modem override image file, you must upgrade to the specified Cisco IOS release.

Error Message
%MMODEM-3-IMAGEWRONGTYPE: Integrated modem image file [chars] cannot be loaded

Explanation The integrated modem override file does not contain a valid firmware image.

Error Message
%MODEM-1-HWREV: The T1 or E1 network module in slot [dec] is incompatible with the digital modems installed in the router

Explanation This T1 or E1 network module cannot be used with digital modems.

Recommended Action Copy the error message exactly as it appears, and contact your technical support representative for upgrade information.

Error Message
%MODEM-5-NO_FLASH_FILE: Flash file [chars] not found for DSP download

Explanation You used the copy flash modem command to download Microcom modems but later erased the Flash memory.

Recommended Action This is an informational message saying DSP will be downloaded from bundled Cisco IOS software. No specific action is required. You might choose to copy the firmware image to Flash/bootFlash and copy to modems.

Error Message
%MPA68360-1-DWNLDCKSM: MPA68360: Download checksum error (sent = 0x[hex], received = 0x[hex]

Explanation The download of the internal firmware to the MPA68360 failed to checksum correctly. This usually indicates a hardware failure of the MPA6836.

Recommended Action Perform a power cycle. If the problem persists, the MPA68360 hardware may have a problem.

Error Message
%MPA68360-1-DWNLDFL: MPA68360 down load failed

Explanation Failed to download firmware into the PRI port adapter.

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

Error Message
%MPA68360-1-INITFAIL: MPA68360 slot [dec]: Init Failed at [chars]

Explanation The PRI port adapter 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
%MPA68360-3-MBXREAD: MPA68360: Stale msg in [chars] - mbx0:[hex] mbx1:[hex] mbx2:[hex]

Explanation The MPA68360 has not responded to a message within a specified time.

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

Error Message
%MPA68360-1-NOTCMPLT: MPA68360 download failed to complete.

Explanation The MPA68360 hardware has 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
%MPA68360-3-NOTMPA68360: MPA68360: Device reported [hex]

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

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

Error Message
%MPA68360-1-NOTREADY: NMPA6836: Not ready for download

Explanation An error occurred on the communication path between DRIVER and MPA68360.

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

Error Message
%MPA68360-3-PANIC: MPA68360: Exception [dec], trace [dec]

Explanation The MPA68360 firmware detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.

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

Error Message
%MPA68360-1-STARTFAIL: MPA68360 [chars]: Channel enable failed

Explanation A software or hardware error occurred. The MPA68360 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
%MPA68360-1-STOPFAIL: MPA68360 [chars]: Channel disable failed

Explanation The PRI port adapter 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-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-HALT: Mx serial: [chars] TPU halted: cause 0x[hex] status 0x[hex] shadow ptr 0x[hex]

Explanation The Mx serial port adaptor driver failed to synchronize with the firmware on the port adapter.

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 adapter 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 adapter 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
%NIC100-3-BADUNIT: msgtxt_badunit

Explanation An internal software error occurred.

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

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-5-ADJCHG: Process [dec], Nbr [int] on [chars] from [chars] to [chars], [chars]

Explanation An OSPF neighbor has changed state. The message describes the change and the reason for it. This message appears only if log-adjacency-changes command is configured for the OSPF process.

Recommended Action This message is for information only. No action is required.

Error Message
%OSPF-3-DBEXIST: area [chars] lsid [int] mask [int] adv [int] type [dec]

Explanation OSPF has a problem locating the LSA, which could lead to a memory leak.

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 An OSPF receive packet originated by itself.

Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.

Error Message
%OSPF-3-RDB_NO_LSA: lsid [int] adv [int] type [dec] gateway [int] metric [dec] network [int] mask [int] protocol [hex] attr [hex] net-metric [dec]

Explanation OSPF found an inconsistency between its database and IP routing table.

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

Error Message
%OSPF-6-ZERO_BANDWIDTH: interface [chars] has zero bandwidth)

Explanation The interface reported its bandwidth as zero.

Recommended Action This message is for information only. No action is required.

Error Message
%PAD-3-GETLINE: Tty[t-line], bad return code [dec] from x3_getline()

Explanation An internal software error occurred.

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

Error Message
%PAD-2-PUTSETUP: Tty[t-line], buffer already setup

Explanation An internal software error occurred.

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

Error Message
%PARSER-4-INVLDLINE: Invalid line in NV generation: [t-line]

Explanation The parser failed an internal software check.

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

Error Message
%QA-3-DIAG: NULL

Explanation This is a diagnostic message.

Recommended Action This message appears after a QA error, and contains diagnostic information regarding that error. Copy the original QA error message and all the following QA diagnostic error messages exactly as they appear. Also copy the output of the show version and show controllers cbus commands. Contact 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 is a very rare situation. 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 or 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 stems from 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 Software failed to initialize/restart a 1T serial card.

Recommended Action Clear the serial interface. If 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 a DCD and a 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-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 problem recurs, it indicates an error that might be 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 for transmission. The interface cannot handle such small packets for transmission.

Recommended Action The system should recover. No action is required. If the problem recurs, it indicates a hardware error that might be 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 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 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-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 see if it is supported in the Cisco IOS release that is running 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 the router, move the BRI card to the other WIC slot on the port module, and reboot the router.

Error Message
%QUICC_ETHER-5-HBEAT: Unit [dec], heartbeat check failure

Explanation The Ethernet cable might be too long, or there could be too many repeaters such that the delay from one end to the other is too long. The Ethernet cable might be overloaded with too many users.

Recommended Action Verify that your Ethernet cable is the correct length and that you do not have too many repeaters in use. If these are not the problem, try removing hosts from the Ethernet segment to reduce the load.

Error Message
%QUICC_SERIAL-5-LOSTCARR: Unit [dec], carrier detect signal lost during message reception

Explanation The RS-232C Carrier Detect (DCD) signal was de-asserted during message reception. The DCE equipment is responsible for asserting this signal.

Recommended Action Check the serial interface cable. The error can occur if the cable is disconnected.

Error Message
%RADIUS-3-ALLDEADSERVER: No active radius servers found

Explanation All RADIUS servers were found to be unresponsive.

Recommended Action Check the network connectivity to the RADIUS servers, and check that the servers are running.

Error Message
%RADIUS-3-FORKFAIL: Failed to fork process for [chars]

Explanation The system may have run out of memory. However, other explanations are possible.

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

Error Message
%RADIUS-3-IDENTFAIL: Save of unique accounting ident aborted. Configuration has been modified

Explanation Because the configuration has been modified, the unique accounting IDENT cannot be saved to NVRAM.

Recommended Action Save the configuration and try again. If the error persists, call your technical support representative for assistance.

Error Message
%RADIUS-6-IDENTSAVE: Saving config with new acct ident in nvram

Explanation Saving an accounting ident in NVRAM.

Recommended Action No action is required.

Error Message
%RADIUS-3-NOSERVERS: No Radius hosts configured

Explanation RADIUS is attempting to send a request, but there are no hosts configured that can receive the request.

Recommended Action Configure a host with the radius-server command.

Error Message
%RADIUS-6-SERVERALIVE: Radius server [int] is responding again (previously dead)

Explanation A RADIUS server, which previously was dead, has started responding again.

Recommended Action No action is required.

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
%RSP-2-BADCACHE: Possible cache overrun detected. datagram size 0x[hex] : sub interface mtu 0x[hex] bufhdr [hex]: [hex] [hex] [hex] [hex] Flushing Cache

Explanation Either a packet greater than the maximum possible MTU was processed, or an illegal buffer header data area was found.

Recommended Action Call your technical support representative for support.

Error Message
%RSP-4-HSA_MEM: size mismatch, master [int]MB, slave [int]MB

Explanation Memory size mismatch between a master and a slave RSP.

Recommended Action Configure both master and slave RSPs to have an equal amount of memory.

Error Message
%RSP-4-HSA_MINMEM: [int]MB required for HSA

Explanation HSA requires a minimum of 24 MB of memory.

Recommended Action Upgrade your system to meet minimum memory requirements for HSA.

Error Message
%RSP-3-IP_PANIC: Panic: [chars] [hex] [hex] [hex] [hex]

Explanation Firmware for the interface processor experienced a critical condition.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of show tech-support.

Error Message
%RSP-3-NOIDB: bad vc [int] on [chars]

Explanation A channelized interface driver received a packet on an unconfigured channel.

Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative, along with the output of show tech-support.

Error Message
%RSP-4-RSPDRAM: Insufficient DRAM to adequately run this IOS version. [dec]M is recommended

Explanation The quantity of RSP DRAM is below the recommended amount.

Recommended Action Add DRAM.

Error Message
%RSP-3-SLAVE_NVRAM_BUSY: Slave NVRAM is temporarily busy

Explanation Another process is temporarily locking the slave configuration.

Recommended Action Reissue the command that caused the error message. If the error message recurs, check for other EXECs by using the show users command. If you know that there are no other users locking the slave NVRAM, contact your technical support representative for assistance.

Error Message
%SCHED-3-INTSETWAKEUP: Invalid scheduler action ([chars]) at interrupt level

Explanation This message indicates that a process_set_wakeup_reasons was attempted from an interrupt handler.

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

Error Message
%SERVICE_MODULE-0-INITWICFAILURE: Unit [chars] - failed to download properly

Explanation The CSU/DSU driver detected a checksum error while downloading the WIC firmware.

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

Error Message
%SERVICE_MODULE-4-WICNOTREADY: Unit [chars] not ready for next command

Explanation The module was waiting for the current request to be processed before sending the next request. The current request has been in progress for more than 3 seconds.

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

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
%SWITCH-1-NOMEMORY: msgtxt_nomemory

Explanation The CPU was unable to access the memory it needs to carry out its functions. The following are some possible causes. The network is large, requiring a great deal of memory for routing tables, and so on. 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-2-BADPID: Bad pid [dec] for tty [t-line]

Explanation An internal software error occurred.

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

Error Message
%SYS-6-BOOT_MESSAGES: Messages above this line are from the boot loader

Explanation At least one informational or error message was printed by the boot loader.

Recommended Action If the system image was loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative.

Error Message
%SYS-2-CHUNKBADREFCOUNT: Bad refcount number in chunk header, chunk [hex] data [hex] refcount [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-4-CONFIG_NOLOCK: The configuration could not be locked

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
%TAC-3-XTACACL: [chars]: accesslist 0x[hex] out of range for [chars]

Explanation The TACACS facility created a message that contains an access list that is not a valid access list (out of bounds).

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

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.

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.

Error Message
%TCP-2-BADTCBREFCNT: Bad TCB refcount: TCB 0x[hex], refcnt [dec]

Explanation An internal software error occurred.

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

Error Message
%TCP-2-BUFFER: Tty[t-line], buffering bug

Explanation An internal software error occurred.

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

Error Message
%TCP-2-INVALIDTCB: Invalid TCB pointer: 0x[hex]

Explanation An invalid TCB is used.

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

Error Message
%TCP-2-PUTBYTE: Tty[t-line], tcp_putbyte() with blocking disabled

Explanation An internal software error occurred.

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

Error Message
%TCP-6-TOOBIG: Tty[t-line], too many bytes of options ([dec])

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
%TR-3-ADPCHK: Interface [chars], adapter check error (non-fatal)([hex] [hex] [hex] [hex])

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

Recommended Action Issue a clear interface command. If the message recurs, call your technical support representative for assistance.

Error Message
%TR-3-ADPCHKFATAL: Interface [chars], adapter check error (fatal) ([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 the message recurs, call your technical support representative for assistance. You may need to replace the interface card.

Error Message
%VIP-3-AFOVERFLOW: Ethernet address filter table full

Explanation VIP Ethernet-like interface uses an internal MAC address table to filter incoming packets. Once the table is full, additional address entries are rejected. Any incoming packet with destination address not in the table will be ignored.

Recommended Action The address table is consumed by various protocols (such as PIM or HSRP). If too many HSRP are configured for one interface, the entry could be exhausted. The suggested solution would be to distribute some of those HSRP entries to other Ethernet interface.

Table of Contents