Table Of Contents
DBUS Error Messages
Data bus error messages
Error Message%DBUS-3-BADCTRLRTYPE : Invalid controller type [dec] in slot [dec]
Explanation An interface processor responded with an unknown or illegal controller type when queried. This should not happen unless the running software does not support the interface processor in question, or the interface processor fails.
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%DBUS-3-BADEEPROM : Invalid EEPROM data found for card in slot [dec], card disabled
Explanation The ID EEPROM on the indicated card is not programmed correctly.
Recommended Action Call your Cisco technical support representative for a replacement.
Error Message%DBUS-3-BADHSACONF : Down rev RSP EPROM found HSA system, upgrade EPROM, or remove one RSP
Explanation A software or hardware 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%DBUS-3-CXBUSERR : Slot [dec], CBus Error
Explanation A processor reported a bus error. The processor will be reset and not used until the next on-line insertion and removal (OIR) event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. 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%DBUS-3-DAUGHTER_STATS : Slot [dec] control 0x[hex], status 0x[hex]
Explanation A processor reported an error. This message is sent out in conjunction with other error messages to provide additional information.
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%DBUS-3-DBUSINTERR : Slot [dec], Internal Error
Explanation A processor reported an internal error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. 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%DBUS-3-NOMAGIC : No magic number found in RP1 EEPROM
Explanation The structure containing the system MAC address needed by the OIR facility cannot be found in the RP EEPROM. The RP must be returned for reprogramming.
Recommended Action Return the RP for reprogramming and call your Cisco technical support representative for assistance.
Error Message%DBUS-3-NORESP : bad or no response, slot [int]
Explanation A board in the slot identified in the error message failed to respond.
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%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%DBUS-3-SLOTCOMP : Slot [dec], dbus error, slot (0x[hex]) and complement (0x[hex]) do not match
Explanation A processor reported a mismatch between the contents of the slot register and its complement. This condition indicates a hardware failure in the diagnostic bus controller on that processor or on the diagnostic bus. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
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%DBUS-3-SW_NOTRDY : DBUS software not ready after [chars], elapsed [int], status 0x[hex]
Explanation An interface processor failed to come online after being reset. A software or hardware 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%DBUS-2-UNKNOWN : Slot [dec], unknown controller type 0x[hex], ignoring
Explanation A processor reported a controller type that is unknown to the system. The processor will not be used and must be repaired.
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%DBUS-3-WCSCTRLRERR : Slot [dec], WCS Controller Instruction Error
Explanation The writable control store (WCS) is the set of devices on each interface processor that contains the running microcode. It can be loaded either from the ROM on the interface processor or from the system by using the downloadable microcode facility. In this message, a processor reported a WCS controller instruction error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
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%DBUS-3-WCSERR : Slot [dec], WCS controller in error state (0x[hex]), resetting
Explanation The processor in the slot identified in the error message reported a writable control store (WCS) controller error. The processor will be reset and new microcode loaded. This error message appears only when microcode is downloaded.
Recommended Action Reset the processor and load new microcode. 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%DBUS-3-WCSFLOW : Slot [dec], flow cntrl error loading WCS, last data 0x[hex] pos [dec]
Explanation A processor indicated an error condition while downloading microcode. The status, cmd/data, and pos numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted and the ROM microcode is loaded.
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%DBUS-3-WCSLDERR : Slot [dec], error loading WCS, status 0x[hex] cmd/data 0x[hex] pos [dec]
Explanation A processor indicated an error condition while downloading microcode. The status, cmd/data, and pos numbers shown in the message reflect the error condition, the last byte of microcode loaded, and the position in the file, respectively. If this error appears, the microcode download is aborted and the ROM microcode is loaded.
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%DBUS-3-WCSPARERR : Slot [dec], WCS Controller Parity Error
Explanation A processor reported a WCS parity error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Replace the processor or download microcode. If this message recurs, call your Cisco technical support representative for assistance.
Error Message%DBUS-3-XILINX : ready wait timeout, slot [int]
Explanation The field-programmable gate arrays on an interface processor failed to load after being reset. This indicates a probable software or hardware problem.
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.
DIALER Error Message
Dial-on-demand routing (DDR) error message
Error Message%DIALER-2-NOSWIDB : No software interface associated with hw interface [chars]
Explanation An internal software error occurred.
Recommended Action Call your technical support representative and report the error message, the system version, and the router configuration. (Use the show version command to obtain the software version.)
DLC Error Messages
Data-link control error messages
Error Message%DLC-3-BADPARAM : Function [chars]: value [hex] passed in parameter [chars]
Explanation An internal software error occurred.
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%DLC-3-INVPCEP : Close Station, invalid P_CEP
Explanation An internal software error occurred.
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%DLC-2-NOMEMORY : no memory for [chars]
Explanation There was not enough free memory to complete the operation.
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%DLC-3-OPTNULL : Error, NULL parameter unexpected
Explanation An internal software error occurred.
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%DLC-3-WPUTERR : unknown port type [hex]
Explanation An internal software error occurred.
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.
DLSw Error Messages
Data-link switching error messages
Error Message%DLSWC-3-BADCLSI : [chars] primitive not valid for dlsw [chars] [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSICNF : [chars] Invalid confirm [chars] [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSIDATALEN : [chars] Bad data len = [dec] [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSIHDRLEN : [chars] Bad header len = 0x[hex] [chars]
Explanation A data-link switching system error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DLSWC-3-BADCLSIIDTYPE : [chars] Invalid ID type = 0x[hex] [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSIPRIMTYPE : [chars] Invalid primitive type = 0x[hex] [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSIRET : [chars] Invalid ret code (0x[hex]) [chars], [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADCLSISAP : [chars] Bad clsi SAP id = [hex] [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADDLCOP : dlsw_action, bad dlc event [dec], [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADPEEROP : bad peer op in peer_to_core [dec]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADSSPEVENT : dlsw_action, bad ssp event [dec], [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-BADSSPHDR : bad ssp hdr in proc ssp - [chars] = 0x[hex]
Explanation A Silicon Switch Processor (SSP) header received from the remote peer contains errors in one of the fields.
Recommended Action If the remote peer is a non-Cisco router, confirm that it supports the DLSw RFC 1795 standard.
Error Message%DLSWC-3-BADSSPOP : bad ssp op in proc ssp [dec]
Explanation A Silicon Switch Processor (SSP) frame with an invalid command was received from the remote peer.
Recommended Action If the remote peer is a non-Cisco router, confirm that it supports DLSw RFC 1795 standard.
Error Message%DLSWC-3-BADTIMEROP : dlsw_action, bad timer event [dec], [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-FAILASSERT : Assertion failed: [chars]
Explanation An internal software inconsistency occurred. The router continues to operate.
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%DLSWC-3-FORKFAIL : Can't fork : [chars] process
Explanation DLSw process cannot run.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory. If this message recurs, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Error Message%DLSWC-3-FSMACTION : [chars]
Explanation Indicates frames sent by DLSw on LAN or WAN side. This is good, expected behavior.
Recommended Action No action is required.
Error Message%DLSWC-3-FSMCALL : [chars] state [chars], event: [chars][chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-FSMERR : fsm error [chars] [chars] [chars] event: [chars][chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-FSMINTERR : fsm internal error - [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-FSMUNKERR : [chars] [dec]: [chars] [chars] event:[chars][chars] input: [dec] [dec] states: [dec] [dec]
Explanation A data-link switching system error occurred.
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%DLSWC-3-INVALIDSTATE : finite state machine in invalid state
Explanation A data-link switching system error occurred.
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%DLSWC-3-INVALIDTIMER : bad timer pop for [chars], new state [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-NODLSW : no dlsw, [chars]
Explanation A data-link switching system error occurred.
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%DLSWC-3-NOPARAM : dlsw_action, null param blk
Explanation A data-link switching system error occurred.
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%DLSWC-3-NOPEER : no peer, [chars]
Explanation A data-link switching system 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%DLSWC-3-RECVSSP : SSP OP = [dec]([chars]) [chars] from [chars]
Explanation A Silicon Switch Program (SSP) frame was received from the remote peer.
Recommended Action No action is required.
Error Message%DLSWC-3-SENDSSP : SSP OP = [dec]([chars]) [chars] to [chars] [chars]
Explanation A Silicon Switch Program (SSP) frame was sent to the remote peer.
Recommended Action No action is required.
Error Message%DLSWP-3-PBADVALUE : DLSw: [chars]: invalid [chars] [dec]
Explanation A bad parameter value was passed to function chars1 - invalid parameter chars2 with value. This error should not cause any network problems unless it happens repeatedly.
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%DLSWP-3-PCAPMISMATCH : DLSw: [chars]: [chars]
Explanation Priority keyword was used on one router but not on the other. The priority keyword is an option on the DLSw remote peer definition. If priority keyword is used on one router, it must be used on the other.
Recommended Action If you want to use prioritization, use it on both routers.
Error Message%DLSWP-3-PGENERAL : DLSw: [chars] [chars]
Explanation A general error condition was detected as described in the message text. This error should not cause any network problems unless it happens repeatedly.
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%DLSWP-3-PLFCHANGE : [chars] [dec]; [chars]
Explanation The largest frame size configured in the DLSw remote peer definition is being changed because the MTU size configured on the interface, used by DLSw, is less than the configured value of the largest frame on DLSw remote peer definition. The largest frame size is being changed to that configured on the interface.
Recommended Action If you want to use this largest frame size for DLSw, increase the MTU on the interface to a value larger than the configured largest frame size.
Error Message%DLSWP-3-PNOMEM : DLSw: No memory to [chars]
Explanation The router ran out of system memory for operation, as described in the message text. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your Cisco technical support representative about memory requirements for a specific image.
Error Message%DLSWP-3-PPASSIVE : DLSw: passive open failed from [int]([dec]) - [dec]
Explanation The system does not have enough main memory (RAM) for TCP to allocate the data structures required to accept an incoming TCP connection. Most likely, the router image requires more system memory (RAM) than the router contains.
Recommended Action Consult with your Cisco technical support representative about memory requirements for a specific image.
DMA Error Messages
Direct memory access error messages
Error Message%DMA-1-BADICBPTR : No icb assigned to port [dec], interface [dec]
Explanation An internal software error occurred.
Recommended Action If this error message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%DMA-1-BADJUMPSTART : DMA jumpstart failed, [dec]
Explanation This is an anomalous situation where the direct memory access (DMA) jumpstart mechanism failed to find the DMA to start.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DMA-1-BADLENGTH : Zero length memd packet in buffer header [hex]
Explanation VIP found that the memory device (MEMD) buffer header indicated a zero length transmit.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DMA-1-BADOWN : Own bit not set before end of packet reached
Explanation This message indicates that an unexpected own bit was found in a DMA entry.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
DNET Error Messages
DECnet error messages
Error Message%DNET-3-HEARSELF : Hello type [hex] for my address from [dec].[dec] via [chars]
Explanation The system is receiving its own DECnet packets. Either a serial line is looped back or another host with the same DECnet address is already present on the LAN.
Recommended Action Check the serial lines (if present) and the DECnet configuration.
Error Message%DNET-4-MAPCON : Map entry [dec].[dec] conflicts with adjacency to [dec].[dec]
Explanation Your DECnet configuration is incorrect. A host that is specified as nonlocal is present on your local network.
Recommended Action Correct the configuration. Call your technical support representative if you need assistance.
DRP Error Messages
Director Response Protocol error messages
Error Message%DRP-7-NOROUTE : no route for destination [int]
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%DRP-3-NOWRITE : unable to send response to [int]:[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%DRP-3-SUBNETTED : unable to determine metric for [int], [int] subnetted
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.
DSPU Error Messages
Downstream physical unit error messages
Error Message%DSPU-3-ActpuNegResponse : ACTPU Neg rsp received from PU [chars]
Explanation Remote PU rejected the router's request for an SSCP-PU session.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and correct it. If the problem persists, call your Cisco technical support representative for assistance.
Error Message%DSPU-3-CLSIBadAdptCorr : CLSI bad Adapter correlator, header= [chars]
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%DSPU-3-CLSIBadIdentifier : CLSI bad identifier, header= [chars]
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%DSPU-3-CLSIBadIdentifierType : CLSI bad identifier type, header= [chars]
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%DSPU-3-CLSIBadLength : CLSI bad length, header= [chars]
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%DSPU-3-CLSIBadPrimitiveCmd : CLSI bad primitive command, header= [chars]
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%DSPU-3-CLSIBadPrimitiveType : CLSI bad primitive type, header= [chars]
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%DSPU-3-CLSIBadReturnCode : CLSI bad return code: [dec], header= [chars]
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%DSPU-3-CLSIUnexpctActSapCnf : CLSI unexpected ActivateSapCnf, header= [chars]
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%DSPU-3-CLSIUnexpctDeactSapCnf : CLSI unexpected DeactivateSapCnf, header= [chars]
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%DSPU-3-CLSIUnexpctEnableCnf : CLSI unexpected EnableCnf, header= [chars]
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%DSPU-3-CLSIUnexpctIdStnInd : CLSI unexpected IdStnInd, header= [chars]
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%DSPU-3-DSPU_BufferCorrupted : DSPU could not free buffer - buffer corrupted
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%DSPU-3-LSConnInFailed : Connect in from remote address [chars] failed
Explanation Connection with remote station could not be established.
Recommended Action Verify configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connectIn from this remote station.
Error Message%DSPU-3-LSConnInFailedNoMem : Connect in from remote address [chars] failed; insufficient memory
Explanation Connection with the remote station could not be established because of insufficient memory in the router.
Recommended Action Correct low memory problem in the router. If the problem persists, call your technical support representative for assistance.
Error Message%DSPU-3-LSConnInFromHostFailed : Connect in from host [chars] with remote address [chars] failed
Explanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the router is configured to accept connection from this host.
Error Message%DSPU-3-LSConnInFromPuFailed : Connect in from pu [chars] with remote address [chars] failed
Explanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept connectIn from this remote PU.
Error Message%DSPU-3-LSConnOutToHostFailed : Connect out to host [chars] failed
Explanation Connection with the remote host could not be established.
Recommended Action Verify host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.
Error Message%DSPU-3-LSConnOutToPuFailed : Connect out to pu [chars] failed
Explanation Connection with the remote PU could not be established.
Recommended Action Verify PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.
Error Message%DSPU-3-LSInvalidMaxIFrame : Connection attempt failed from XID= [chars], Invalid MaxIFrame= [dec]
Explanation An invalid MaxIFrame value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link-station configuration at the remote station.
Error Message%DSPU-3-LSInvalidWindowSize : Connection attempt failed from XID= [chars], Invalid WindowSize= [dec]
Explanation An invalid WindowSize value in an exchange identification (XID) was received from the remote station; connection with remote station could not be established.
Recommended Action Correct link-station configuration at the remote station.
Error Message%DSPU-3-LSNoACTPUCapability : Connection attempt failed from XID= [chars], ACTPU not supported
Explanation The remote station did not request PU 2.0 activation; connection with remote station is terminated.
Recommended Action Correct link-station configuration parameters at the remote station to request a system services control point (SSCP)-PU session with the router.
Error Message%DSPU-3-LSXIDNegotiationError : XID Negotiation Error, bad byte= [dec], bad bit= [dec], sense data= [chars]
Explanation XID3 with an error indication was received from the remote station; connection with the remote station could not be established.
Recommended Action Determine, from the CV 22 byte or bit information, which field in the XID3 is rejected by the remote station, and correct the link-station configuration parameters at either the router or the remote station.
Error Message%DSPU-3-NotifyNegRsp : LU [dec] received a Notify Neg Resp from host [chars]
Explanation Remote host rejected the router's request to activate/deactivate an SSCP-LU session.
Recommended Action Verify host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and correct it. If the problem persists, call your technical support representative for assistance.
Error Message%DSPU-3-SnaBadData : Bad SNA data received from PU [chars], data= [chars]
Explanation Unrecognized SNA data was received from the remote PU.
Recommended Action Correct the problem at the remote PU. If the problem persists, call your Cisco technical support representative for assistance.
Error Message%DSPU-3-UnknownXid : XID Format not supported, XID= [chars]
Explanation Unsupported XID received from the remote station; connection with remote station could not be established.
Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are XID Format 0 and XID Format 3.
DSX1 Error Messages
Channelized E1 (Europe) and T1 (US) DSX-1 telephony standard error messages
Error Message%DSX1-1-M32_INPUT_CONGEST : Munich 32 channel input queue is congested
Explanation Cannot allocate receive buffers since 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 and/or increase the number of input queues.
Error Message%DSX1-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.
DUAL Error Messages
Enhanced Interior Gateway Protocol error messages
Error Message%DUAL-3-ANCHORCOUNT : Anchor count negative
Explanation A software or hardware error occurred.
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%DUAL-3-BADCOUNT : Route [chars], [dec] successors, [dec] rdbs
Explanation A hardware or software error occurred.
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%DUAL-6-EVENT : [chars], [chars]
Explanation A hardware or software error occurred.
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%DUAL-3-INTERNAL : [chars] [dec]: Internal Error
Explanation A software or hardware error occurred.
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%DUAL-3-LINKSEXIST : Interface [chars] going down and [dec] links exist
Explanation An interface is going down or is being removed from routing through IGRP, but not all links (neighbors) have been removed from the topology table.
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%DUAL-3-LINKSTILLUP : Link [dec] [chars] still exists on [chars]
Explanation A hardware or software error occurred.
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%DUAL-3-MULTIFLOW : Flow control error, [chars], on [chars]
Explanation A hardware or software error occurred.
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%DUAL-5-NBRCHANGE : [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]
Explanation A neighbor went up or down.
Recommended Action No action is required.
Error Message%DUAL-3-NOBUFFER : No buffers available for [int] byte packet
Explanation The DUAL software was unable to allocate a packet buffer. The system may be out of memory.
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%DUAL-3-NOHANDLE : Handle [dec] is not allocated in pool
Explanation A hardware or software error occurred.
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%DUAL-3-NOMATCH : Nexthop and infosource don't match. N = [chars], I = [chars]
Explanation A hardware or software error occurred.
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%DUAL-3-NOSOCKET : Unable to open socket for AS [dec]
Explanation A hardware or software error occurred.
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%DUAL-3-PEERSEXIST : [dec] peers exist on IIDB [chars]
Explanation A software or hardware error occurred.
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%DUAL-3-PROBESEQ : Bad probe sequence [dec] from [chars], expecting [dec]
Explanation A software or hardware error occurred.
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%DUAL-3-RDBLEFT : Lingering DRDB deleting IIDB, dest [chars], nexthop [chars] ([chars]), origin [chars]
Explanation A software or hardware error occurred.
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%DUAL-3-REFCOUNT : Negative refcount in pakdesc [hex]
Explanation A software or hardware error occurred.
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%DUAL-3-SIA : Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up
Explanation A hardware or software error occurred.
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%DUAL-3-SIANOHANDLE : Stuck-in-active and [dec] unallocated handle(s) in reply-status table ([hex]). Cleaning up
Explanation A hardware or software error occurred.
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%DUAL-3-UNKTIMER : Unknown timer type [dec] expiration
Explanation A hardware or software error occurred.
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.
DVMRP Error Messages
Distance Vector Multicast Routing Protocol (DVMRP) error messages
Error Message%DVMRP-1-BADMASK : Bad mask [int] received from [int], Report ignored
Explanation A software or hardware 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%DVMRP-1-ROUTEHOG : Receiving [dec] routes from [int] ([chars]) in the last [chars]
Explanation A software or hardware 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.
EGP Error Messages
Exterior Gateway Protocol error messages
Error Message%EGP-3-NOPDB : No pdb for [int]
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%EGP-3-TOOBIG : Insufficient ([dec]) buffering for update message
Explanation An EGP update message was too large to fit into a single buffer.
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.
ENT_API Error Messages
Entity MIB API error messages
Error Message%ENT_API-4-NOALIAS : [chars] entity not found when adding an alias with physical index = [int] and logical index = [int] to the Entity MIB
Explanation An attempt to add an alias entry to the Entity MIB was made. The logical or physical entity with the specified index does not exist, and so the alias entry creation failed.
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. Using your network management system (NMS) tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-3-NOCREAT : EntityApiProcess not created - Entity MIB will not be initialized
Explanation Attempt to start EntityApiProcess failed when the entity subsystem was initialized. The Entity MIB will not be populated.
Recommended Action The Entity MIB API process was not created, possibly because of a lack of memory. If you want to use the Entity MIB API, reconfigure the box so that less memory is used by other features, or add more memory to the system. Reload the box after reconfiguring.
Error Message%ENT_API-4-NOENT : Trying to add or delete an unknown entity to the Entity MIB
Explanation An attempt to add/delete an unknown entity to the Entity MIB was made. The request could not be processed.
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. Using your network management system (NMS) tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-4-NOLPMAP : [chars] entity not found when adding an LPMapping entry with logical index = [int] and physical index = [int] to the Entity MIB
Explanation An attempt to add an LPMapping entry to the Entity MIB was made. The logical or physical entity with the specified index does not exist, and so the LPMapping entry creation failed.
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. Using your network management system (NMS) tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-4-NOPARENT : Parent physical entity [int] did not exist when trying to add child physical entity [int]
Explanation An attempt to add a physical entity failed, because its parent physical entity did not exist in the entPhysicalTable of the Entity MIB.
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. Using your network management system (NMS) tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-4-NOPORT : Physical entity does not have a Port PhysicalClass when adding an alias with physical index = [int] and logical index = [int] to the Entity MIB
Explanation An attempt to add an alias entry to the Entity MIB was made. The physical entity with the specified index does not have an entPhysicalClass of 10(Port class) and so the alias entry creation failed. See RFC2037 for the definition of the PhysicalClass textual-convention and the aliasMappingEntry object.
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. Using your network management system (NMS) tool, also provide the content of the Entity MIB table.
ENV Error Messages
Environmental monitor card error messages
Error Message%ENV-2-FLOW : Air flow appears marginal
Explanation A temperature reading indicates poor air flow.
Recommended Action Attempt to resolve the air flow problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENV-1-SHUTDOWN : Environmental Monitor initiated shutdown
Explanation One of the environmental measurements reached SHUTDOWN status. The system is about to shut down the processor to prevent damage to the hardware.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENV-2-TEMP : Ambient temperature measured [chars]. Shutdown at [chars]
Explanation The ENV card indicates the temperature it measured and the temperature at which it shuts down.
Recommended Action Attempt to resolve the temperature problem. If the problem is not resolved, call your technical support representative for assistance.
Error Message%ENV-2-VOLTAGE : [chars] testpoint measured [chars]. shutdown margin is [chars]
Explanation The ENV card indicates the voltage it is measuring (for example, +5, +12, -5, -12), the amount of voltage that it measured, and the voltage at which the processor will shut down the system.
Recommended Action Attempt to resolve the voltage problem. If the problem is not resolved, call your technical support representative for assistance.
ETHERNET Error Messages
C1000 series Ethernet error messages
Error Message%ETHERNET-1-NOMEMORY : msgtxt_nomemory
Explanation Insufficient memory exists to allocate the necessary memory pools.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%ETHERNET-1-TXERR : [chars]: Fatal transmit error. Restarting...
Explanation A fatal transmit error occurred on the Ethernet line, causing the line to be restarted.
Recommended Action If this message recurs, call your technical support representative for assistance.
FDDI Error Messages
Fiber Distributed Data Interface error messages
Error Message%FDDI-3-BADSLOT : Unit [dec], Slot [dec] does not exist
Explanation The main processor detects an invalid slot location for one of the network interface cards. This should never happen.
Recommended Action Call your technical support representative about obtaining a replacement card.
Error Message%FDDI-3-FDDIFAIL : Interface [chars], [chars], [chars] = [hex]
Explanation The FDDI interface failed.
Recommended Action Save the output of the error message and call your technical support representative for assistance.
Error Message%FDDI-3-FDDIFAIL2 : Interface [chars], [chars], [chars] = [hex], [chars] = [hex]
Explanation The FDDI interface failed. This is the second line of the preceding FDDIFAIL message. This line contains debug information.
Recommended Action Save the output of the error message and call your technical support representative for assistance.
Error Message%FDDI-3-NOCAM : Unit [dec], No CAM exists for this interface
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%FDDI-1-NOMEMORY : msgtxt_nomemory
Explanation The FDDI Management Information Base/Station Management (MIB/SMT) processing functions could not initialize because of insufficient memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
FLASH Error Messages
Flash nonvolatile memory error messages
Error Message%FLASH-3-ACCESSATTRIBONRP : [chars]
Explanation The route processor cannot access the Flash memory card's attribute memory. The Flash memory card should continue to operate normally.
Recommended Action If there is still a problem with the Flash memory card, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%FLASH-3-ERASEFAIL : flash_erasefail_msg
Explanation The system was unable to erase a Flash memory device.
Recommended Action Try to erase again. If that fails, call your technical support representative for assistance.
Error Message%FLASH-3-WRITEFAIL : flash_writefail_msg
Explanation The write operation to Flash memory failed.
Recommended Action Try erasing the device and trying the write again. If that fails, call your technical support representative for assistance.
FR Error Messages
Frame Relay error messages
Error Message%FR-5-DLCICHANGE : Interface [chars] - DLCI [dec] state changed to [chars]
Explanation The state of the Frame Relay PVC specified by the data-link connection identifier (DLCI) changed.
Recommended Action This is a notification message only. No action is required.
Error Message%FR-3-INCORRECT_INT : Incorrect output (sub)interface, broadcast packet dropped!
Explanation Output (sub)interface specified in packet is incorrect; 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.
FTC_TRUNK Error Message
Cisco 3801 platform error message
Error Message%FTC_TRUNK-1-NOMEMORY : msgtxt_nomemory
Explanation The MC68360/QUICC CPU was unable to access the memory it needs to carry out its functions. Here 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.
GRIP Error Messages
Xerox Network Systems (XNS) Routing Protocol error messages
Error Message%GRIP-3-BADPATHS : Invalid number of paths ([dec]) for [dec]
Explanation An internal inconsistency was detected in the XNS routing table structure.
Recommended Action Note the parameters associated with this message and call your technical support representative for assistance.
Error Message%GRIP-2-BADROUTE : Error [chars] route - null table
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.
HD Error Messages
HD64570 serial controller error messages
Error Message%HD-1-BADLOOPCABLE : Loopback not supported for a 4T DTE/X.21, port [dec] in slot [dec]
Explanation Loopback mode is not allowed when using an X.21 DTE cable on a Quad serial NIM port.
Recommended Action Do not enable loopback, or use a different cable type.
Error Message%HD-1-BADPORTADAPTER : 4T Port Adapter fault on port [dec] in slot [dec]
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%HD-1-BADRING : msgtxt_badringsize
Explanation An internal software error occurred.
Recommended Action If message recurs, call your technical support representative for assistance.
Error Message%HD-5-LINEFLAP : Unit [dec] excessive modem control changes
Explanation Too many modem control interrupts have been received. The port was disabled to prevent excessive use of the CPU.
Recommended Action Check the cable on the serial port.
HOOD Error Messages
LAN controller 100VG-AnyLA interface error messages
Error Message%HOOD-3-BADUNIT : msgtxt_badunit
Explanation An internal software error occurred.
Recommended Action If the message recurs, call your technical support representative for assistance.
Error Message%HOOD-5-CABLEERR : Unit [dec], HP100VG, cable error. Training failed
Explanation A 100VG cable or hub is faulty.
Recommended Action If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.
Error Message%HOOD-5-COLL : Unit [dec], excessive collisions
Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the router.
Error Message%HOOD-5-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Error Message%HOOD-5-NOCABLE : Unit [dec], HP100VG, no tone detected. Check cable, hub
Explanation A 100VG cable is faulty.
Recommended Action If the message recurs, and either the cable or hub appears to be good, repair or replace the router module.
HP100VG Error Messages
100VF-AnyLAN PA driver error messages
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 An 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 detected.
Recommended Action Ensure that 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 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 login to the hub.
Recommended Action Take action based on the following error messages.
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 with the network.
Recommended Action Check the configuration of the hub for Frame Format, Promiscuous, and Repeater bit to indicate proper configuration.
Error Message%HP100VG-5-LOSTCARR : HP100VG([dec]/[dec]), lost carrier
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 An 100VG cable is faulty.
Recommended Action Repair or replace the cable. If either 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 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 100VG PCI device.
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-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.
HUB Error Messages
Cisco Ethernet hub error messages
Error Message%HUB-1-BADHUB : Invalid hub type [dec] and number [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%HUB-1-BADUNIT : Bad port number [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%HUB-1-NOMEMORY : msgtxt_nomemory
Explanation The system detected that there is not enough memory for the hub initialization.
Recommended Action If conditions warrant, upgrade to a larger memory configuration.
Error Message%HUB-1-READERR : Read op [dec] not allowed
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%HUB-1-WRITEERR : Write op [dec] not allowed
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IBM2692 Error Messages
Error messages which refer to an IBM Token Ring chip set
Error Message%IBM2692-1-DISCOVER : IBM2692, Only found [dec] interfaces on bay [dec], shutting down bay
Explanation One of the interface controller devices on the module did not initialize properly.
Recommended Action Power down, reinsert the network module, and reboot. If the message recurs, call your technical support representative for assistance.
Error Message%IBM2692-1-NOPCIMEMORY : IBM2692 ([dec]/[dec]), PCI memory unavailable
Explanation The router or access server could not allocate memory for the descriptors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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.
IFS Error Messages
IOS File System error messages
Error Message%IFS-4-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.
IGRP Error Message
Interior Gateway Routing Protocol error message
Error Message%IGRP-3-NOSOCKET : Unable to open socket for AS [dec]
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.
ILACC Error Messages
ILACC driver error messages
Error Message%ILACC-4-BABBLE : Unit [dec], babble error, csr0 = 0x[hex]
Explanation An Ethernet interface is malfunctioning.
Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.
Error Message%ILACC-3-BADUNIT : msgtxt_badunit
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%ILACC-5-COLL : Unit [dec], excessive collisions. TDR=[dec]
Explanation An Ethernet cable is broken or unterminated, or the transceiver is unplugged. The time delay reflectometer (TDR) counter is an internal ILACC counter that counts the time (in ticks of 100 ns each) from the start of a transmission to the occurrence of a collision. Because a transmission travels about 35 feet per tick, this value is useful to determine the approximate distance to a cable fault.
Recommended Action If the transceiver appears to be properly terminated, repair or replace the Ethernet interface card.
Error Message%ILACC-1-INITFAIL : msgtxt_initfail
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%ILACC-5-LATECOLL : Unit [dec], late collision error
Explanation An Ethernet transceiver is malfunctioning, the Ethernet is overloaded, or the Ethernet cable is too long.
Recommended Action Repair or replace the controller.
Error Message%ILACC-5-LOSTCARR : Unit [dec], lost carrier. Transceiver problem?
Explanation An Ethernet transceiver is unplugged or faulty.
Recommended Action Repair or replace the controller.
Error Message%ILACC-1-MEMERR : msgtxt_memoryerror
Explanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%ILACC-3-OWNERR : msgtxt_ownerror
Explanation An Ethernet interface is malfunctioning, or an internal software error occurred.
Recommended Action Repair or replace the controller.
Error Message%ILACC-3-SPURIDON : Unit [dec], spurious IDON interrupt, csr[dec]=0x[hex]
Explanation An Ethernet interface generated a spurious Initialization Done interrupt.
Recommended Action Repair or replace the controller.
Error Message%ILACC-3-UNDERFLO : Unit [dec], underflow error
Explanation The Ethernet hardware is requesting data faster than the system can supply it. This condition might indicate that the system is at the limit of its performance.
Recommended Action A small number of underflows might not be a cause for concern. You can monitor underflows with the show interface command. Reducing the load on the router or installing a higher-performance router should alleviate this problem.
INTERFACE_API Error Messages
Error messages for the binary API for the interface descriptor block
Error Message%INTERFACE_API-4-BADPAKINPUT : pak-if_input is not initialized
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%INTERFACE_API-4-BADPAKOUTPUT : pak-if_output is not initialized
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%INTERFACE_API-4-BADSWIDB : [chars] may not be referencing the correct swidb
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.
IP Error Messages
Internet Protocol error messages
Error Message%IP-3-BADIPALIGN : Invalid alignment in packet for IP. [chars]=[hex]
Explanation The packet data structure is misaligned. This condition may result in a small amount of overhead in processing IP traffic.
Recommended Action Enter a show hardware command and report the output, along with this error message, to your technical support representative.
Error Message%IP-3-BADSROUTE : Improper source route. Length [dec] Ptr [dec]
Explanation A hardware or software error occurred.
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%IP-4-CLASS : Bad IP address and mask [inet] in class_resolve()
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%IP-3-DESTHOST : src=[int], dst=[int], NULL desthost
Explanation An internal software error occurred.
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%IP-4-DUPADDR : Duplicate address [int] on [chars], sourced by [sci_notation]
Explanation Another system is using your IP address.
Recommended Action Change the IP address of one of the two systems.
Error Message%IP-3-LOOPPAK : Looping packet detected and dropped - src=[int], dst=[int], hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] in=[chars], nexthop=[int], out=[chars]options=[chars]
Explanation A software error occurred.
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%IP-5-WEBINST_COMP : Selected IP address [int]
Explanation A hardware or software error occurred.
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%IP-5-WEBINST_KILL : Terminating DNS process
Explanation A hardware or software error occurred.
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%IP-5-WEBINST_RESP : Sending DNS response to [int] (request was for [int])
Explanation A hardware or software error occurred.
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%IP-5-WEBINST_START : Attempting web install from host [int]
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%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.
IPC Error Messages
Interprocess Communication error messages
Error Message%IPC-2-CANT_SEND : Cannot send IPC message: [chars]
Explanation An error occurred in the IPC slave-discovery mechanism. It might result in a malfunction in the operation of the IPC.
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%IPC-4-CONSISTENCY : Message failed consistency check: [chars]
Explanation An internal inconsistency was found in some IPC data structures.
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%IPC-3-DELETED : Attempt to delete an IPC message (0x[hex]) a second time
Explanation An internal inconsistency was found in some IPC data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status and show ipc queue commands 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 ipc status and show ipc queue output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-3-GIANT : Request for giant IPC packet denied. Request size = [dec]
Explanation Someone requested a message that was too large for the IPC system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-LOCK : Lock done a deleted element
Explanation An internal inconsistency was found in some IPC data structures.
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%IPC-3-NOBUFF : The [chars] IPC message header cache has emptied
Explanation The given IPC message header cache has emptied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-NODELFUNC : Delayed init function not available
Explanation The IPC application cannot be initialized because its initialization function does not appear in the IPC initialization function list.
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%IPC-2-NODISPATCH : Message for [dec].[dec] has no receive queue or dispatch routine
Explanation The IPC user failed to provide any means of handling the received message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc ports 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 ipc ports output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-2-NOMEM : No memory available for [chars]
Explanation The IPC protocol subsystem could not obtain the memory it needed.
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%IPC-2-ONINT : Called from interrupt level: [chars]
Explanation The IPC user attempted a prohibited call into IPC while IPC was running on the interrupt stack.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show ipc status 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 ipc status output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%IPC-5-SLAVELOG : VIP-[chars]
Explanation The Cisco IOS software, running on a Versatile Interface Processor (VIP) card, generated this message. The error message has been passed up to the Route Processor (RP) or Route Switch Processor (RSP) for display. This message appears only if the user has configured the service slavelog command.
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%IPC-2-UNLOCK : Unlock done on already unlocked element
Explanation An internal inconsistency was found in some IPC data structures.
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%IPC_RSP_CBUS-3-CARDERR : [chars]
Explanation An IPC card has registered itself to the IPC master twice. The card malfunctioned and its IPC is not active.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-INVNUM : [chars] ([dec])
Explanation The IPC application tried to send a message that was larger than IPC could handle. The message was not transmitted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-MSGERR : [chars] ([dec])
Explanation The slave IPC cannot register with master. It cannot exchange messages with the master.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOBUF : [chars]
Explanation The IPC ran out of memory device (MEMD) buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-NOHWQ : Hardware queue for card at slot [dec] not found
Explanation IPC messages cannot be transmitted because of a missing hardware queue. The messages were discarded, and subsequent messages will not be transmitted to that card.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%IPC_RSP_CBUS-3-SEATERR : [chars] ([dec])
Explanation The ID associated with an IPC card is either missing, duplicated, or cannot be created.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IPFAST Error Messages
IP fast-switching error messages
Error Message%IPFAST-2-BADIF : No support available for interface [chars] (programming error)
Explanation A programming 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%IPFAST-3-INTLEV : Cache update request at interrupt level: [int]([chars])-[int]([chars])
Explanation A programming error occurred.
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%IPFAST-3-INVALIDADDR : Invalid cache destination [int]/[dec]
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%IPFAST-6-INVALIDATE : Cache invalidation occurring for [chars]
Explanation The system is invalidating all cache entries for a given interface.
Recommended Action No action is required.
Error Message%IPFAST-6-INVALREQ : Cache invalidation request for [chars]
Explanation The system is invalidating all cache requests for a given interface.
Recommended Action No action is required.
Error Message%IPFAST-4-RADIXDELETE : Error trying to delete prefix entry for [int]/[dec] (expected [hex], got [hex])
Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your Cisco technical support representative.
Error Message%IPFAST-2-RADIXINIT : Error initializing IP fast cache structures
Explanation A programming 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%IPFAST-4-RADIXINSERT : Error trying to insert prefix entry for [int]/[dec] (expected [hex], got [hex])
Explanation Problems related to the IP route cache triggered this debugging message.
Recommended Action The router should correct for this error. If the router cannot forward packets properly or is experiencing other problems, copy the error message exactly as it appears and report it to your Cisco technical support representative.
IPRT Error Messages
Internet Protocol routing error messages
Error Message%IPRT-3-BADCOMLIST : Community list check with bad list [dec]
Explanation A user specified an invalid BGP community list number.
Recommended Action Check the system configuration to ensure that the specified community list falls within the valid range.
Error Message%IPRT-2-COMPRESS : Bad route_compress() call, sdb= [hex]
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%IPRT-3-NOMEMORY : No memory available for [chars]
Explanation The requested operation failed because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%IPRT-3-PATHIDX : Bad path index of [dec] for [int], [dec] max
Explanation A software error occurred.
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%IPRT-3-TOOMANYNETS : Too many networks in [chars] [dec] (limit [dec])
Explanation Too many network subcommands have been entered for this routing protocol.
Recommended Action No action is required.
IPX Error Messages
Internetwork Packet Exchange error messages
Error Message%IPX-3-BADCOUNT : Bad IPX server count. [chars] [dec], [chars] [dec]
Explanation The internal SAP service count does not match the number of services currently present and displayed by the show ipx servers command.
Recommended Action If this message recurs, report the problem to your technical support representative, along with the output of the show px servers command taken before the message appeared and again after the message appeared.
Error Message%IPX-3-BADIGRPSAP : Cannot send incremental SAP update to peer on [chars]. Increasing output-sap-delay may help
Explanation An incremental SAP update could not be sent, because this might cause the SAP tables between peers to become out of synch.
Recommended Action Increase the output SAP delay on the listed interface to reduce buffer usage. If, after changing the delay, the message remains, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%IPX-3-BADIGRPSAPTYPE : Unsupported SAP type for EIGRP being [chars] - type [hex]
Explanation There are two types of service access points (SAPs)—general queries and general responses. This message is sent when you receive or attempt to send a SAP with a type code that is not a general query or a general response. It is also sent when you receive a general query not addressed to the broadcast address.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. If possible, also provide the output of the debug ipx sap activity and debug ipx sap event commands for the period during which this message appeared.
Error Message%IPX-3-BADPATHS : Invalid number of paths ([dec]) for [hex]
Explanation An internal inconsistency was detected in the IPX routing table structure.
Recommended Action Copy and save this message. If possible, clear the IPX routing table by issuing the clear ipx route command. (This will result in lost connectivity until the routing table is rebuilt.) If the message recurs, copy and save the message, along with the output from the show ipx route, and call your technical support representative for assistance.
Error Message%IPX-6-NOVACCESSLOG : [chars] [chars] [chars] [chars] [hex].[sci_notation] [chars] [hex].[sci_notation] [dec] pkt[chars]
Explanation If IPX access violation logging is enabled, these messages are displayed when an access list logging event has occurred.
Recommended Action Verify that the host system is permitted or denied, as defined in the access list.
Error Message%IPX-3-TOOMANYNETS : Too many networks
Explanation The limit of connected IPX networks has been reached. Additional IPX interfaces cannot be configured.
Recommended Action Do not configure IPX on additional interfaces. Remove IPX configuration commands from inactive interfaces.
IP_SNMP Error Messages
Simple Network Management Protocol specific to IP error messages
Error Message%IP_SNMP-4-NOTRAPIP : SNMP trap source [chars] has no ip address
Explanation The user entered an snmp-server trap-source command. The interface requested for use as the source address has no address associated with it. The SNMP trap is being sent anyway, but without the source address that the user intended.
Recommended Action There are two possible solutions. Either enter a no snmp-server trap-source command to disable the request for a specific source IP address, or add an IP address to the interface referenced in the snmp-server trap-source configuration command.
Error Message%IP_SNMP-3-SOCKET : can't open UDP socket
Explanation The SNMP server was unable to open a port for receiving or transmitting SNMP requests. This usually happens when the SNMP server is started using the snmp-server community configuration command on a router or communication server with an interface that has no IP address configured. Another possible cause is low memory.
Recommended Action Configure at least one interface with an IP address or specify the no snmp-server command to remove the SNMP server process. Call your technical support representative if the problems persist or if it becomes necessary to add memory.
ISDN Error Messages
Integrated Services Digital Network (ISDN) error messages
Error Message%ISDN-6-CONNECT : Interface [chars] is now connected to [chars] [chars]
Explanation This is an informational message sent when a call is connected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call.
Recommended Action No action is required.
Error Message%ISDN-6-DISCONNECT : Interface [chars] disconnected from [chars] [chars], call lasted [int] seconds
Explanation This is an informational message sent when a call is disconnected. The message displays the remote name and number, which it receives from the Point-to-Point Protocol (PPP) authentication or from where the dialer placed the call. It also shows how long the call lasted.
Recommended Action 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.
LANCE Error Messages
Local area network controller Ethernet interface error messages
Error Message%LANCE-4-BABBLE : Unit [dec], babble error, csr0 = 0x[hex]
Explanation An Ethernet interface is malfunctioning.
Recommended Action Determine whether the malfunction stems from a software or hardware error by turning off all fast switching. Error messages showing that the packet is too large for the link indicate a software error at a high level. Copy the error message exactly as it appears, and report it to your technical support representative. Receiving no error messages indicates a hardware error. Repair or replace the controller.
Error Message%LANCE-3-BADCABLE : msgtxt_badcable
Explanation Ethernet cable is not connected.
Recommended Action Check Ethernet cable connection.
Error Message%LANCE-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%LANCE-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 LANCE 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%LANCE-1-INITFAIL : msgtxt_initfail
Explanation The hardware failed to initialize correctly.
Recommended Action Repair or replace the controller.
Error Message%LANCE-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%LANCE-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%LANCE-1-MEMERR : msgtxt_memoryerror
Explanation An Ethernet interface detected a hardware problem.
Recommended Action Repair or replace the controller.
Error Message%LANCE-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%LANCE-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%LANCE-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.
LANE Error Messages
LAN emulation error messages
Error Message%LANE-3-BADILMI : Unexpected ILMI event [dec]
Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-BADNAME : ELAN name must be 1-32 characters long
Explanation An emulation LAN (ELAN) name was entered in a command that is longer than 32 characters. The LANE standard v1.0 requires a name that is 32 characters or less in length.
Recommended Action Re-enter a shorter name.
Error Message%LANE-3-BADTYPE : LAN Emulation supports only Ethernet type
Explanation The user specified a Token-Ring-emulated LAN, which is not currently supported.
Recommended Action Specify an Ethernet-emulated LAN. Future software releases will support Token Ring ELANs.
Error Message%LANE-3-LANE_SIG_ERR : [chars]
Explanation An internal error occurred while system routines were handling ATM signaling messages for LANE.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_BADAD : [chars] LEC unable to compute ATM address
Explanation The client cannot obtain an ATM address from the given configuration, or auto-assignment failed to get an ATM prefix from the switch.
Recommended Action If you expect the switch to assign the prefix to the router, check that the Interim Local Management Interface (ILMI) is functional and the switch has a prefix configured. Otherwise, confirm that the client has an address in the nonvolatile RAM (NVRAM) configuration.
Error Message%LANE-3-LEC_CFG : [chars] CFG_REQ failed, [chars] (LECS returned [dec])
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_CONTROL_MSG : Received bad control message on interface [chars]
Explanation The client received a control message over one of its control virtual channel connections (VCCs) that failed the header check.
Recommended Action This message indicates a noninteroperable LANE configuration server, LANE server, or LANE client implementation on the emulated LAN.
Error Message%LANE-3-LEC_ERR : [chars]
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-6-LEC_INFO : [chars]
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_JOIN : [chars] JOIN failed, [chars] (LES returned [dec])
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_LISTEN : [chars] listen failed on [chars]
Explanation The client failed an attempt to listen on a particular ATM address.
Recommended Action Reconfigure the client ATM address. It is conflicting with another component on the ATM Interface Processor (AIP) for the same ATM address.
Error Message%LANE-3-LEC_REGISTER : [chars] REGISTER failed, [chars] (LES returned [dec])
Explanation A software or hardware error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LEC_SIGNAL : Unexpected SigAPI event [dec]
Explanation ATM signaling sent the client an unexpected message type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LECS_ERROR : [chars]
Explanation An internal consistency error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-4-LECS_WARNING : [chars]
Explanation The LANE Configuration Server address could not be registered with or de-registered from the switch, using Interim Local Management Interface (ILMI). The following are possible causes. The switch prefix is not available. The address is not acceptable to the switch (the prefix does not conform). The interface over which this operation should take place is down. The ILMI subsystem on the router is not completely initialized.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%LANE-3-LSV_ADDR : [chars] elan [chars] unable to register LES/BUS ATM addr
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%LANE-3-LSV_BADAD : [chars] elan [chars] unable to compute [chars] ATM address
Explanation Software was unable to compute an ATM address based on the ATM address template given. The characters in [chars] will be either BUS (broadcast-and-unknown), server, or config server in the actual error message.
Recommended Action Enter a correct ATM address template for the LANE component (BUS, server, or config server) named in the error message.
Error Message%LANE-3-LSV_CRASH : [chars] elan [chars] unrecoverable error [chars]
Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_DUPATM : [chars] elan [chars] client [dec] duplicate ATM address registration [chars]
Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated an ATM address already registered to another LANE client.
Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same ATM address.
Error Message%LANE-3-LSV_DUPID : [chars] elan [chars] duplicate LECID [dec]
Explanation An attempt was made to define two different server-direct PVCs both on the same subinterface (same LANE server) and both for the same client (LECID).
Recommended Action Delete one of the lane pvc commands that has this duplicated LECID.
Error Message%LANE-3-LSV_DUPMAC : [chars] elan [chars] client [dec] duplicate MAC address registration [sci_notation]
Explanation An attempt was made by the specified LANE client to register a MAC address and ATM address pair that duplicated a MAC address already registered to another LANE client.
Recommended Action Use the show lane server command to list the registered addresses in the LANE server reporting the error. Correct one of the two LANE clients that is trying in error to use the same MAC address.
Error Message%LANE-4-LSV_LECID : [chars] elan [chars] LECIDs exhausted
Explanation The LANE server specified has 65,279 clients. No more can be added.
Recommended Action Change the configurations to avoid trying to have more than 65,279 LANE clients on this server.
Error Message%LANE-3-LSV_MCAST : [chars] elan [chars] unable to create [chars] MC group
Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-LSV_NOREG : [chars] elan [chars] client [dec] unable to register MAC address [sci_notation]
Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-NAMECHG : A LANE Client is already running here using another elan name
Explanation Both the LANE client and the LANE server/BUS may have an emulated LAN name specified in the configuration via the lane server-bus and lane client commands. If both specify the emulated LAN name, then the name cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with another emulated LAN name. Finally, re-enter the deleted command with the new emulated LAN name.
Error Message%LANE-3-NEWPREF : [chars] elan [chars] ATM address prefix [chars]
Explanation Entering a new ATM address template for some LANE component caused the specified LANE server or bus to drop all clients and restart.
Recommended Action This is an informational message only. No action is required.
Error Message%LANE-3-NOILMI : ILMI service registration failed
Explanation The Interim Local Management Interface (ILMI) feature is not included in the software image running on the router.
Recommended Action Reload router with software that includes the ILMI feature.
Error Message%LANE-3-NOINT : [chars] still destroying old sub-interface
Explanation An attempt was made to create a new subinterface while a previous version of the subinterface was still being destroyed.
Recommended Action Wait a minute and try again. If failure still occurs, try shutting down the main interface. Rebooting may be required to recover in extreme cases.
Error Message%LANE-3-NOREGILMI : [chars] [chars] cannot register [ATM address] with ILMI
Explanation An attempt to register the given ATM address with the ATM switch failed. This failure can occur because the ATM switch is down or misconfigured. The registration will be retried.
Recommended Action If the situation persists after a number of attempts, and the switch is up, the configuration of the switch and router should be examined. A likely cause is that the ATM address being registered is not compatible with the parameters configured in the switch. Correct the configuration.
Error Message%LANE-3-NOVCD : VCDs exhausted
Explanation When trying to create PVC 0/17, the router ran out of PVC resources.
Recommended Action The number of PVCs can be increased with the atm maxvc command.
Error Message%LANE-3-REGSTATE : ILMI event in state [dec]
Explanation An internal error occurred.
Recommended Action This error should not occur. Download the system error log, then call your technical support representative and provide the log, the error message, and the router configuration.
Error Message%LANE-3-TYPECHG : A LANE Client is already running here using another elan type
Explanation Both the LANE client and the LANE Server/BUS may have an ELAN type specified in the configuration via the lane server-bus and lane client commands as either Ethernet or Token Ring. If both are configured, specify the type; the type cannot be changed by re-entering just one of the commands.
Recommended Action Use the no lane server-bus command to delete the server-bus or the no lane client command to delete the client. Then, the other of the two commands can be re-entered with a new type. Finally, re-enter the deleted command with the new type.
Error Message%LANE-5-UPDOWN : [chars] [chars] [chars]: [chars] changed state to [chars]
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.
LANMGR Error Messages
IBM LAN Network Manager error messages
Error Message%LANMGR-4-BADRNGNUM : Ring number mismatch on [chars], shutting down the interface
Explanation The router detected a conflict in assigned ring numbers for the specified Token Ring. The Ring Parameter Server (RPS) function was shut down to prevent potentially incorrect information from being sourced onto the ring.
Recommended Action Check all bridges connected to this Token Ring and ensure that they are using the same assigned ring number.
Error Message%LANMGR-4-BADUPCALL : Unexpected call ([chars]) from LLC2 for Bridge [hex]-[hex]-[hex]
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%LANMGR-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%LANMGR-4-NORING : No ring info for [chars]
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%LANMGR-4-OLDTRAMON : Cannot run RPS on [chars], Old TRAMON code
Explanation The software on this interface cannot support the functions required for LAN Network Manager.
Recommended Action Call your Cisco technical support representative about a firmware upgrade for this interface card.
LAPB Error Messages
X.25 Link Access Procedure, Balanced error messages
Error Message%LAPB-4-CTRLBAD : Interface [chars], Invalid control field
Explanation A received Frame Reject (FRMR) reported a frame with an invalid control code.
Recommended Action Check the serial line and the devices attached to the line.
Error Message%LAPB-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] [char] VR [dec], Reason [hex]
Explanation A Frame Reject (FRMR) frame was received, indicating that a protocol violation was detected. The Reason field will be interpreted by generating INFOBAD, CTRLBAD, N1TOOBIG, or INVNR messages immediately after this message; refer to the explanations for these messages for more information.
Recommended Action The protocol will recover by resetting the service. This will disrupt any network service on top of LAPB (for example, X.25 virtual circuits will be cleared). Follow the recommended action for any error message following the FRMR reports. If service becomes unacceptable, check the serial line and its attached devices.
Error Message%LAPB-4-INFOBAD : Interface [chars], Info field not permitted
Explanation A received Frame Reject (FRMR) frame reported that an information field was present in a frame where no information field is allowed.
Recommended Action Check the serial line and the device attached to the line.
Error Message%LAPB-4-INVNR : Interface [chars], Invalid NR value
Explanation A received Frame Reject (FRMR) reported a frame with an invalid N(R) value.
Recommended Action Verify that the equipment attached to the serial line is configured with the same K value (maximum number of outstanding I frames).
Error Message%LAPB-4-N1TOOBIG : Interface [chars], N1 too large
Explanation A received Frame Reject (FRMR) reported an information frame that was too long.
Recommended Action Verify that the equipment attached to the serial line is configured with the same N1 value. N1 is in bits and includes the entire frame plus 16 bits of CRC. However, some equipment may require configuration in octets, the omission of the two CRC octets, or the omission of the three octets of LAPB control information.
Error Message%LAPB-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation There was insufficient memory for the LAPB protocol engine to send a message.
Recommended Action This message is acceptable if it occurs infrequently, because the LAPB protocol is designed to handle loss of frames. Frequent occurrences can cause disruption of service. The system can be configured to ease memory demands or, if conditions warrant, the system can be upgraded to a larger memory configuration.
Error Message%LAPB-3-NOINPIDB : Input idb not set
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
Error Message%LAPB-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error occurred.
Recommended Action If either of these messages recur, call your technical support representative for assistance.
LAT Error Messages
DEC Local Area Transport error messages
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, contact your technical support representative.
Error Message%LAT-3-BUFFULL : Tty[t-line], data buffer full with count [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
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, contact your technical support representative.
Error Message%LAT-3-NULLIDB : Null IDB pointer with destination [sci_notation]
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%LAT-3-QBSPACED : Queue block at [hex] not found for HI connection
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
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, contact your technical support representative.
LEX Error Messages
LAN extension error messages
Error Message%LEX-3-NOTSENT : Serial line down, [chars] : [chars] not sent
Explanation The serial line went down, and the specified command was not sent to the LAN Extender.
Recommended Action Determine why the serial line went down. For example, was the cable was pulled, or the LAN Extender powered off? The command will automatically be re-sent once the serial interface is operational.
Error Message%LEX-3-RCMDNAK : [chars] : [chars] could not be processed by LAN Extender
Explanation The LAN Extender could not process the command from the host router. Possible causes are as follows. The LAN Extender ran out of memory. The message from the host router is malformed. A request to write Flash memory occurred while the LAN Extender was busy writing Flash memory for a previous request. The size of a file to be downloaded is greater than the amount of Flash memory available.
Recommended Action If the command was copy tftp lex unit-number or copy flash lex unit-number, ensure that the correct file (a FLEX image file) is specified. Only a single copy request can be handled at one time. If the problem was caused by a temporary out-of-memory condition on the LAN Extender, re-enter the command.
Error Message%LEX-3-RCMDREJ : [chars] : [chars] could not be processed by LAN Extender
Explanation The LAN Extender did not recognize the code for the specified remote command. This might occur if the user is running old LAN Extender software with newer host router software that has support for new LEX remote commands.
Recommended Action Update the LAN Extender software.
Error Message%LEX-3-TIMEOUT : Retry count exceeded for [chars] : [chars]
Explanation The host router re-sent the given message as many times as specified in the lex retry-count command configuration variable, without receiving an acknowledgment from the LAN Extender. At this point, the host router gives up trying to send this particular remote command message.
Recommended Action Use the LEDs on the LAN Extender to determine if it is operational. Confirm that the lex timeout configuration command is set appropriately for the speed of the link.
LINEPROTO Error Message
Line Protocol error message
Error Message%LINEPROTO-5-UPDOWN : Line protocol on Interface [chars], changed state to [chars]
Explanation The data-link level line protocol changed state.
Recommended Action No action is required.
LINK Error Messages
Data link error messages
Error Message%LINK-3-BADENCAP : Interface [chars], Bad encapsulation code ([dec])
Explanation The lower-level software was unable to write a MAC header for a datagram. A probable cause is configuration 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%LINK-3-BADMACREG : Interface [chars], non-existent MACADDR registry for link [dec]
Explanation An attempt to map a network level address to a MAC level address failed.
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%LINK-2-BADVCALL : Interface [chars], undefined entry point
Explanation An internal software error occurred. The high-level system code tried to use an unimplemented entry point with the virtual interface descriptor block (IDB) driver.
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%LINK-6-BERTSTATUS : Interface [chars], [chars]
Explanation BERT is completed for this interface.
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%LINK-3-BOGUSENCAP : msgtxt_badencap
Explanation A serial interface has been configured with an unknown encapsulation.
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%LINK-5-BOOTP : [chars] address [int], resolved by [int]
Explanation An interface's IP address was successfully learned dynamically through BootP. The first address is the learned IP address. The second IP address is the IP address of the BootP server that provided the information.
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%LINK-4-BRIDGECONFLICT : Interface [chars], encapsulated BPDU recvd from [sci_notation]
Explanation An FCIT running in nonencapsulating transparent mode detected an FDDI bridge running in encapsulation mode on the same fiber. This is an unstable situation and should be corrected. The incoming interface is displayed, along with the FDDI MAC address in standard form.
Recommended Action Upgrade the errant interface to full-transparent mode. Copy the error message exactly as it appears, and report it to your Cisco technical support representative.
Error Message%LINK-5-CHANGED : Interface [chars], changed state to [chars]
Explanation The interface hardware changed state.
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%LINK-3-COMPREG : Interface [chars], non-existent (de)compression registry. Packet dropped
Explanation A software or hardware error occurred.
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%LINK-4-FDDISTAT : Interface [chars], FDDI state [chars] detected
Explanation A state change occurred on the FDDI ring.
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%LINK-2-LINEST : No linestate vector for [chars]
Explanation An internal software inconsistency occurred.
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%LINK-5-LOOPSTATUS : Interface [chars], [chars]
Explanation The interface entered or exited loopback.
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%LINK-4-NOMAC : A random default MAC address of [sci_notation] has been chosen. Ensure that this address is unique, or specify MAC addresses for commands (such as 'novell routing') that allow the use of this address as a default.
Explanation An addressing inconsistency occurred.
Recommended Action Ensure that this address is unique, or specify MAC addresses for commands such as novell routing that allow the use of this address as a default.
Error Message%LINK-2-NOSOURCE : Source idb not set
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%LINK-5-RARP : [chars] address [int], resolved by [int]
Explanation The Reverse Address Resolution Protocol (RARP) resolved an IP 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%LINK-5-REMLOOP : Interface [chars], remote loop [chars] [chars]
Explanation The interface entered or exited a remote loopback.
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%LINK-5-SLARP : [chars] address [int], resolved by [int]
Explanation The Serial Line Address Resolution Protocol (SLARP) resolved an IP 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%LINK-4-TOOBIG : Interface [chars], Output packet size of [dec] bytes too big
Explanation An internal software error occurred.
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%LINK-3-TOOSMALL : Interface [chars] - packet was less than minimum allowed
Explanation An output packet was detected that was smaller than the minimum allowable datagram size. An error in another driver or an error in the system software probably triggered this error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%LINK-3-UPDOWN : Interface [chars], changed state to [chars]
Explanation The interface hardware went either up or down.
Recommended Action If the state change was unexpected, confirm the configuration settings for the interface.
LLC2 Error Message
Logical Link Control, type 2 error message
Error Message%LLC-2-UNEXPECT : LLC2: [chars] UNEXPECTED EVENT
Explanation An internal software error was found. A software component is trying to use LLC2 structures that do not exist.
Recommended Action Record the configuration and any information that would be useful in re-creating the error and call your technical support representative.
LNMC Error Messages
LAN network manager system error messages
Error Message%LNMC-3-BADCLSI : [chars] primitive not valid for lnm [chars] [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSICNF : [chars] Invalid confirm [chars] [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSIDATALEN : [chars] Bad data len = [dec] [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSIHDRLEN : [chars] Bad header len = 0x[hex] [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSIIDTYPE : [chars] Invalid ID type = 0x[hex] [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSIIND : [chars] Invalid indication [chars], [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSIPRIMTYPE : [chars] Invalid primitive type = 0x[hex] [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSIRET : [chars] Invalid ret code (0x[hex]) [chars], [chars]
Explanation A LAN network manager system error occurred.
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%LNMC-3-BADCLSISAP : [chars] Bad clsi SAP id = [hex] [chars]
Explanation A LAN network manager system error occurred.
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.
LPD Error Message
Line printer daemon error message
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.