-
Cisco IOS Release 12.0 System Message Guide
-
About the Cisco IOS Software Documentation
-
System Error Messages Overview
-
AAAA through APPN
-
ARAP through C1600
-
C2600 through CT3
-
DBCONN through FILESYS
-
FPGA through IPC_RSP_CBUS
-
IPFAST through LPD
-
M32X through NHRP
-
NIC100 through RTT
-
S4T68360 through SWITCH
-
SYS through TI1570
-
TIB through XCPA
-
CMCC-ADAPTER through CMCC-IPC_DRVR
-
CMCC-LOADER through CMCC-XCPA
-
System Failure Error Messages
-
Table Of Contents
DBCONN Error Messages
Database Connection error messages
Error Message%DBCONN-3-APPCVERB : Unexpected APPC error: opcode [hex], primary code [hex], secondary code %08lx
Explanation An unexpected APPC error occurred. Database Connection (DBConn) uses APPC API calls to APPN to communicate with the remote database server. Opcode identifies the APPC API call that received the error. Primary and secondary return codes are returned by the APPC API.
Recommended Action This usually indicates a problem in the SNA network. Try the dbconn ping command to test connectivity to the remote database server. If the DBConn ping fails, check the status of the APPN link to the remote database server with the show appn link command. If the link is active, try stopping and starting the link. If the problem persists, contact your SNA network administrator for help in troubleshooting. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If possible, also provide the output of the debug dbconn appc command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message%DBCONN-3-APPNNOTSTARTED : APPN is not started -- unable to connect to remote database.
Explanation A client connected to a Database Connection (DBConn) server, but DBConn was unable to connect out to the remote database because APPN is not started. DBConn uses APPN to connect to the remote database server. You must start APPN before DBConn clients attempt to connect.
Recommended Action Start APPN, and retry the client connection.
Error Message%DBCONN-3-APPNSTOPPED : APPN was stopped -- existing connections have been closed.
Explanation APPN was stopped while Database Connection (DBConn) connections were open. Stopping APPN caused all open APPN connections to the remote database server to be lost. As a result, all client connections were disconnected. You should not stop APPN while there are open DBConn connections.
Recommended Action Restart APPN. Disconnected clients must be reconnected.
Error Message%DBCONN-3-BADLICENSEKEY : Bad license key configured for Database Connection.
Explanation The license key configured with the dbconn license configuration command is not valid.
Recommended Action Check that the license key was entered correctly in the dbconn license command. Refer to the Database Connection feature documentation for information on how to obtain a valid license key.
Error Message%DBCONN-3-BADMODE : Unknown mode '[chars]' configured for server [chars]
Explanation The mode configured for the Database Connection server was rejected by the remote database server.
Recommended Action Contact your SNA network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server.
Error Message%DBCONN-3-BADRLU : Bad remote LU '[chars]' configured for server [chars]
Explanation The remote LU configured for the Database Connection server is incorrect.
Recommended Action Contact your SNA network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Be sure to check that the SNA network name is correct as well as the LU name.
Error Message%DBCONN-3-BADTPNAME : Bad TP name configured for server [chars]
Explanation The TP name configured for the Database Connection (DBConn) server is not recognized by the remote database server.
Recommended Action Configure a TP name that is available on the remote database server. Most DB2 systems will accept the DRDA default TP name of
\x076DB, except for SQL/DS. Contact your SNA network administrator or your DB2 administrator to determine the TP name used by your DB2. To use the DRDA default, do not explicitly configure a TP name for your DBConn server.Error Message%DBCONN-3-DRDASYNTAX : DRDA protocol error from server [chars], SYNERRCD x'[hex]'
Explanation An unexpected DRDA protocol error occurred between Database Connection (DBConn) and the remote database server.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information. If possible, also provide the output of the debug dbconn drda command, and an SNA line trace between the router and the remote database server, for the period during which this message appeared.
Error Message%DBCONN-5-IDLETIMEOUT : Client [int] connected to server [chars] has timed out after %TE
Explanation The client was idle for too long, and the idle timeout configured for the Database Connection server expired.
Recommended Action This is an informational message only. No action is required.
Error Message%DBCONN-5-SECFAIL : APPC security failed, client [int] using userid '[chars]' for server [chars]
Explanation The user ID and/or password passed in by the client were rejected by the remote database server.
Recommended Action This is an informational message only. No action is required.
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.
DCU Error Messages
ATM access concentrator PCI port adapter error messages
Error Message%DCU-3-DCU_RESET : [chars]: DCU keep-alive failure, card reset
Explanation The port adapter has stopped processing keepalives.
Recommended Action The system should recover. No action is required.
Error Message%DCU-1-NODCUPORTS : The maximum number of DCU ports ([dec]) is exceeded
Explanation The system detected too many DCU ports.
Recommended Action Check the configuration.
Error Message%DCU-1-NOMEMORY : No memory available for [chars] [dec]
Explanation Memory exhaustion has occurred.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
DEC21140 Error Messages
DEC21140 Fast Ethernet controller error messages
Error Message%DEC21140-5-COLL : [chars] excessive collisions
Explanation A Fast Ethernet packet was dropped because too many attempts to transmit it were stopped by collisions. This can be caused by a Fast Ethernet segment that is full to capacity or by other equipment on the LAN malfunctioning.
Recommended Action No action is required.
Error Message%DEC21140-1-DISCOVER : Only found [dec] interfaces on bay [dec], shutting down bay
Explanation The number of interfaces found was not what was expected, indicating a possible hardware failure.
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%DEC21140-3-ERRINT : [chars] csr0=[hex], csr5=[hex]
Explanation The Fast Ethernet controller has signaled an error condition on the specified port.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-1-INITFAIL : [chars] timed out, csr5=[hex]
Explanation The Fast Ethernet port initialization failed. This can be caused by a disconnected cable or a failure to detect the media in use.
Recommended Action Check the cabling. Try initializing the port again. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-5-JABBER : [chars] transmit timed out
Explanation The transmitter for the port adapter's Fast Ethernet port timed out and caused the transmission of a packet to fail.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-5-LATECOLL : [chars] transmit error
Explanation Late collisions are collisions that occur after transmitting the preamble. The packet will be retransmitted but this could indicate that another device is failing to detect when the network is in use.
Recommended Action If this recurs, check for malfunctions in other devices on the Fast Ethernet.
Error Message%DEC21140-5-LOSTCARR : [chars] cable/transceiver problem?
Explanation The Fast Ethernet port lost its carrier while transmitting, meaning that it is no longer receiving signals from the LAN. This can be caused by a disconnected Fast Ethernet cable or a transceiver failure.
Recommended Action Check your Fast Ethernet wiring and port adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-5-NOCARR : [chars] cable/connector problem?
Explanation The Fast Ethernet port did not find a carrier when preparing to transmit a packet, meaning that it is no longer receiving signals from the LAN. This can be caused by disconnected Fast Ethernet cables or a transceiver failure.
Recommended Action Check your Fast Ethernet wiring and port adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-2-NOISL : Interface [chars] does not support ISL
Explanation ISL is not supported on the specified interface's hardware.
Recommended Action No action is required.
Error Message%DEC21140-3-NOTDEC21140 : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The Fast Ethernet driver failed to initialize.
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%DEC21140-3-OWNERR : [chars] packet buffer, pak=0x[hex]
Explanation This message indicates an internal software inconsistency.
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%DEC21140-3-RXFIFO : [chars] overflow error
Explanation The Fast Ethernet receiver was unable to deliver received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data. This problem could be caused by excessive system load.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-3-UNDERFLO : [chars] transmit error
Explanation The Fast Ethernet transmitter was ready to go before a packet was in the buffer. This problem could be caused by excessive system load.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DEC21140-5-WATCHDOG : Enormous packet received on [chars]
Explanation A packet received via Fast Ethernet was dropped because of its excessive size.
Recommended Action If necessary, adjust the MTU of the interface. Otherwise, no action is required.
DIALER Error Messages
Dial-on-demand routing (DDR) error messages
Error Message%DIALER-6-BIND : Interface [chars] bound to profile [chars]
Explanation This message indicates that a dialer interface has been bound to a dialer profile.
Recommended Action This is a status message only. No action is required.
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.)
Error Message%DIALER-2-NULLPTR : Unexpected null pointer in [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. 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%DIALER-6-UNBIND : Interface [chars] unbound from profile [chars]
Explanation This message indicates that a dialer interface has been unbound to a dialer profile.
Recommended Action This is a status message only. No action is required.
DIALSHELF Error Messages
Dial shelf error messages on a router shelf
Error Message%DIALSHELF-3-EVENT : Unknown event [dec] for slot [dec]
Explanation The software generated an unknown event for the specified slot. This is a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DIALSHELF-3-INVALIDMSG : [chars] ([dec])
Explanation The router shelf received an invalid message from the DSC in the dial shelf. This is a software error or compatibility issue. Check the software versions on the router shelf and the DSC.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DIALSHELF-3-MSG : Unknown message type [dec] from DSC
Explanation The router shelf received an unknown message from the DSC in the dial shelf. This is a software error or compatibility issue. Check the software versions on the router shelf and the DSC.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DIALSHELF-3-SLOTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected an invalid state change for the specified slot. This is a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DIALSHELF-2-TIMEOUT : [chars] slot [dec] after [dec] secs in state '[chars]'
Explanation The specified dial shelf slot timed out as per the message. Either a software or a hardware component failed.
Recommended Action Try removing and reinserting the card. If that does not help, try a different card. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DIALSHELF-2-UNDEFCARD : Card type [dec] in slot [dec]
Explanation The software does not have a driver for the card in the specified slot.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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-IDMGR : [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, call your Cisco technical support representative and provide the representative with the gathered information.
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.
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.
DRIP Error Messages
Duplicate Ring Protocol error messages
Error Message%DRIP-6-DRIP_CONFLICT : DRIP conflict with CRF [dec]
Explanation A DRIP conflict occurred. The virtual ring or pseudo ring's CRF is being re-used in the network.
Recommended Action Ensure that the CRF vlanid of the virtual ring and the pseudo ring is unique in the network.
Error Message%DRIP-3-DRIPFAIL : DRIP: Assertion failed: [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, call your Cisco technical support representative and provide the representative with the gathered information.
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.
DRVGRP Error Message
Interface driver operational error message
Error Message%DRVGRP-3-CMD : Interface ([chars]): [chars] (cause :[int])
Explanation Interface driver initialization errors occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DSCCLOCK Error Messages
Dial shelf controller clock notification messages
Error Message%DSCCLOCK-3-FAIL : The System Primary Clock is down. Moving to HOLDOVER state and waiting to see if it comes up
Explanation This message is generated whenever the current primary clock goes bad. The TDM clock circuit goes into HOLDOVER mode and a holdover timer is started to see if the bad clock turns good within the holdover time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-NOMEMORY : Failed to allocate memory for the DSC clocks
Explanation The clock switching software failed to allocate memory while adding a clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-5-SWITCH1 : Clock moving to NORMAL from FREERUN, selected clock is on slot [dec] port [dec] line [dec]
Explanation The primary TDM clock, which has been running off the local oscillator of DSC in FREERUN mode, switched to the line clock coming in via the specified trunk.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH2 : Clock moving to FREERUN from HOLDOVER
Explanation The current primary TDM clock was deleted. Therefore the system primary switched to the DSC local oscillator, which is the current highest priority good clock. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH3 : Clock moving to NORMAL from HOLDOVER, selected clock is on slot [dec] port [dec] line [dec]
Explanation The current primary TDM clock was deleted. Therefore the system primary switched to the clock coming in via the trunk specified by the slot/port, which is the current highest priority good clock. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH4 : Switching to the user configured clock on slot [dec] port [dec] line [dec]
Explanation The TDM primary clock is switching from the default clock to the user configured clock coming in via a trunk. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH5 : Switching to the clock on slot [dec] port [dec] line [dec]
Explanation The TDM primary clock is switching to the clock coming in via the trunk specified, most likely after the router-shelf and feature boards reload. The phase of the output TDM clock is forced to align with the input reference during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH6 : Switching to the clock on slot [dec] port [dec] line [dec] as the current primary has gone bad
Explanation The TDM primary clock switched to a backup clock coming in via the specified trunk since the current primary clock has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH7 : Moving to NORMAL mode from HOLDOVER mode, clock is slot [dec] port [dec] line [dec]
Explanation The TDM primary clock that is in HOLDOVER mode and whose source was a trunk port, switched to the same trunk port and moved to NORMAL mode with a phase alignment between the input source clock and output TDM reference clock. Most likely the router-shelf and the feature boards have reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH8 : Moving to NORMAL mode from HOLDOVER mode without phase correction, clock is slot [dec] port [dec] line [dec]
Explanation The source trunk port of the TDM primary clock which had failed has turned good again before the holdover timer expiry. Therefore, the primary moved from HOLDOVER to NORMAL state without phase correction between input trunk reference and the output TDM clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-SWITCH_ERROR1 : Failed to select any clock as the system clock. Remaining in HOLDOVER mode
Explanation The clock selection algorithm failed to select any clock as the TDM primary clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCCLOCK-3-UP : The System Primary Clock is up. Moving to NORMAL state from HOLDOVER
Explanation The TDM primary clock that had failed has turned good within the holdover time. Therefore, the TDM primary clock switched to the NORMAL mode from the HOLDOVER mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DSC_ENV Error Messages
Cisco AS5800 environment monitor error messages
Error Message%DSC_ENV-1-CRITICAL : Slot [dec], [chars] [int] [chars]
Explanation The card environmental parameters specified are outside the normal range of operation.
Recommended Action Check blowers and the ambient room temperature.
Error Message%DSC_ENV-0-SHUTDOWN : Slot [dec], [chars] [int] [chars]
Explanation The card environmental parameters specified are outside the normal range of operation.
Recommended Action Check blowers and the ambient room temperature.
Error Message%DSC_ENV-2-WARNING : Slot [dec], [chars] [int] [chars]
Explanation The card environmental parameters specified are outside the normal range of operation.
Recommended Action Check blowers and the ambient room temperature.
DSCEXTCLK Error Messages
Dial shelf controller clock error messages
Error Message%DSCEXTCLK-5-SWITCH1 : Clock moving to NORMAL from FREERUN, selected clock is external clock on DSC
Explanation The primary TDM clock, which has been running off the local oscillator of DSC in FREERUN mode, switched to the external network reference clock being fed from the DSC front panel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCEXTCLK-3-SWITCH3 : Clock moving to NORMAL from HOLDOVER, selected clock is external clock on DSC
Explanation The current primary TDM clock was deleted. Therefore, the system primary switched to the clock coming in via the external network reference clock on the DSC front panel, which is the current highest priority good clock. Phase continuity is maintained during the switchover
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCEXTCLK-3-SWITCH4 : Switching to the user configured external clock on DSC
Explanation The TDM primary clock is switching from the default clock to the user configured clock coming in via the DSC front panel clock feed. Phase continuity is maintained during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCEXTCLK-3-SWITCH5 : Switching to the external clock on DSC
Explanation The TDM primary clock is switching to the clock coming in via the DSC front panel, most likely after the router-shelf and hence feature boards reload. The phase of the output TDM clock is forced to align with the input reference during the switchover.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCEXTCLK-3-SWITCH6 : Switching to the external clock on DSC as the current primary has gone bad
Explanation The TDM primary clock switched to a backup clock coming in via the DSC front panel external clock feed since the current primary clock failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCEXTCLK-3-SWITCH7 : Moving to NORMAL mode from HOLDOVER mode, selected external clock on DSC
Explanation The TDM primary clock, which is in HOLDOVER mode and whose source was the DSC front panel clock, switched to the same clock and moved to the NORMAL mode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DSCEXTCLK-3-SWITCH8 : Moving to NORMAL mode from HOLDOVER mode without phase correction, selected external clock on DSC
Explanation The DSC front panel clock, which is the source of the current TDM primary clock and which had failed, turned good again before the holdover timer expiry. Therefore, the primary moved from HOLDOVER to NORMAL state without phase correction between input reference and the output TDM clock.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DSI Error Messages
Cisco AS5800 dial shelf interconnect board error messages
Error Message%DSI-3-AGENTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected an invalid state change for the specified slot's mbus agent. This is a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DSI-3-AGENTSTSCHNG : From [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected an mbus agent state change for the specified slot.
Recommended Action This is an informational message only. No action is required.
Error Message%DSI-2-BADPORT : Out of range PCI port [dec]
Explanation The software specified an out-of-range port on the dial shelf interconnect board. This is a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DSI-3-EVENT : Unknown event [dec] for slot [dec]
Explanation The software generated an unknown event for the specified slot. This is a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DSI-3-SLOTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected an invalid state change for the specified slot. This is a software error.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%DSI-3-SLOTSTSCHNG : From [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected a state change for the specified slot.
Recommended Action This is an informational message only. No action is required.
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