-
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
S4T68360 Error Messages
S4T68360 error messages relate to the 4-port synchronous serial adapter based on the 68360 processor.
Error Message%S4T68360-1-DWNLDCKSM : Failed for bay [dec], sent = 0x[hex], received = 0x[hex]
Explanation The download of the internal firmware to the S4T failed to checksum correctly. This usually indicates a hardware failure of the S4T or the Versatile Interface Processor (VIP).
Recommended Action Perform a power cycle. If the problem persists, the S4T hardware may have a problem.
Error Message%S4T68360-1-DWNLDFAIL : Microcode to port adapter in bay [dec]
Explanation The S4T hardware has failed. It could not download its operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-INITFAIL : Bay [dec]: [chars]
Explanation The S4T port adapter failed to complete hardware initialization.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-3-MBXREAD : Bay [dec] stale msg [chars]- mbx0:%lx, mbx1:%lx, mbx2:%lx
Explanation The S4T has not responded to a message from the Versatile Interface Processor (VIP) within a specified time.
Recommended Action Perform a microcode reload of the VIP. If the problem persists, it indicates that the S4T or VIP hardware failed.
Error Message%S4T68360-1-NOTCMPLT : Microcode download to bay [dec] failed
Explanation The S4T port adapter hardware failed. It did not acknowledge the completion of the operational microcode download.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-NOTREADY : Bay [dec] for microcode download
Explanation The S4T port adapter hardware failed. The S4T port adapter would not begin to download the operational microcode.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-3-NOTS4T68360 : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The S4T hardware failed. A non-S4T device pointed at the software for the S4T.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-3-OWNERR : [chars] packet buffer, pak=0x[hex]
Explanation A software or hardware error occurred. The S4T driver detected that the transmit ring is an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-3-PANIC : Bay [dec], Exception [dec], trace [dec]
Explanation The S4T firmware detected an illegal or unexpected CPU exception or condition. This may be caused by a software error or by a hardware failure.
Recommended Action Perform a microcode reload of the Versatile Interface Processor (VIP). If the problem persists, it indicates that the S4T hardware failed.
Error Message%S4T68360-1-RESTART : Bay [dec] port adapter
Explanation The S4T port adapter hardware failed. The periodic check routine detected the failure and restarted it.
Recommended Action No action is required.
Error Message%S4T68360-5-RINGSIZE : [chars] TX packet dropped; particle count ([dec]) exceeds [dec]
Explanation The TX packet got dropped since the TX ring was full.
Recommended Action This is normal when the port adapter gets overdriven. No action is required.
Error Message%S4T68360-1-STARTFAIL : [chars] [chars]
Explanation A software or hardware error occurred. The S4T interface is not responding to commands used to initialize it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%S4T68360-1-STOPFAIL : [chars] [chars]
Explanation The S4T port adapter failed to respond to a request to disable an interface.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SCHED Error Messages
Scheduler error messages
Error Message%SCHED-2-ATTRCMD : Attempt to [chars] attribute [chars] on process [dec]
Explanation Each process has various public and private attributes associated with it. This message indicates that an attempt was made to set or get a private attribute belonging to another process.
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%SCHED-2-ATTRVALUE : Attempt to set bad [chars] value ([hex]) on process [dec]
Explanation Each process has various attributes associated with it. This message indicates that an attempt was made to set the specified attribute to an invalid value.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-CORRUPT : Scheduler '[chars]' corrupted by process [chars] (expected [hex], found [hex])
Explanation The scheduler has determined that its data structures were corrupted during the execution of the current process. This corruption is the result of either the actions of the process (multiple errors reported against the same process) or an interrupt driver (multiple errors reported against different processes).
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-EDISMSCRIT : Critical/high priority process [chars] may not dismiss
Explanation Each process executes at a specified priority level. Higher-priority processes must use the new scheduler primitives, while lower-priority processes can use primitives from either the new or old scheduler. This message indicates that a higher-priority process attempted to use an old scheduler primitive.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-INTSETWAKEUP : Invalid scheduler action ([chars]) at interrupt level
Explanation This message indicates that a process_set_wakeup_reasons was attempted from an interrupt handler.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SCHED-3-LOSTWAKEUP : Wakeup information for process [chars] lost (maj [hex], min [hex])
Explanation A process can register to be notified when various events occur in the router. This message indicates that an event for the specified process was lost and that the router might not be functioning correctly.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-MESSAGE : Key ([chars]) does not match key ([chars]) of process ([dec]) in process_send_message request
Explanation An attempt was made to send a message to a process. The key associated with that process did not match the key in the message. This usually means an incorrect process ID was used in the send message request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-NOATTR : Attempt to [chars] unknown process attribute [dec]
Explanation Each process has various attributes associated with it. This message indicates that an attempt was made to set or get a nonexistent process attribute.
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%SCHED-2-NOTWATCHTIMER : [chars] timer [hex] not being watched
Explanation A process can register to be notified when various events occur in the router. This message indicates that an attempt was made to deregister a timer expiration event that is not currently registered.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-PAGEZERO : Low memory modified by [chars] ([hex] = [hex])
Explanation In all Cisco products, the first 256 bytes of memory are unused and are off-limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically check this memory. This message appears only on older platforms and indicates that this off-limits memory area was modified.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-PRIORITY : Illegal priority ([dec]) specified for process [chars]
Explanation Each process executes at a specified priority level. Higher-priority processes must use the new scheduler primitives, while lower-priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified process to a priority level that is not allowed for the type of scheduler primitives used.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-QUEUENOTEMPTY : Attempt to delete non-empty watched queue [chars] (address [hex])
Explanation A process can register to be notified when various events occur in the router. This message indicates that an attempt was made to destroy a queue that still contained items. These items are lost and not returned to free memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-SEMNOTLOCKED : [chars] attempted to unlock an unlocked semaphore
Explanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not locked.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-SEMUNLOCK : [chars] attempted to unlock semaphore owned by [chars]
Explanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to unlock a semaphore that was not owned by the process attempting to unlock it.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-SETHIGHORCRIT : Attempt to set [chars] priority on process [dec] ([chars])
Explanation Each process executes at a specified priority level. Higher-priority processes must use the new scheduler primitives, while lower-priority processes can use primitives from either the new or old scheduler. This message indicates that an attempt was made to set the specified priority too high for a process using old scheduler primitives.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-STACKSIZE : Illegal stack size ([dec]) specified for process [chars]
Explanation Each process has its own stack space, which must be one of several predefined sizes. This message indicates that an attempt was made to specify an illegal stack size.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-STILLWATCHING : Process still watching [chars] [chars]
Explanation A process can register to be notified when various events occur in the router. This message indicates that a process destroyed a set of events without first individually removing each event in the set.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-STILLWATCHINGT : Process still watching [chars] timer [hex]
Explanation A process can register to be notified when various events occur in the router. This message indicates that a process destroyed a set of events without first individually removing each event in the set.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-STUCKMTMR : Sleep with expired managed timer [hex], time %#Ta (%TE ago)
Explanation A process can register to be notified when various events occur in the router. This message indicates that a registered timer is expired and its value is unchanged after the process has executed two successive times.
Recommended Action Upgrade to Cisco IOS Software version 12.0(5)WC10 or later. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCHED-3-STUCKTMR : Sleep with expired timer [hex], time %#Ta (%TE ago)
Explanation A process can register to be notified when various events occur in the router. This message indicates that a registered timer is expired and its value is unchanged after the process has executed two successive times.
Recommended Action Upgrade to Cisco IOS Software version 12.0(5)WC10 or later. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCHED-3-THRASHING : Process thrashing on watched [chars]
Explanation A process can register to be notified when various events occur in the router. This message indicates that the process relinquished the processor 50 consecutive times and there were still outstanding events to be processed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-UNEXPECTEDEVENT : Process received unknown event (maj [hex], min [hex])
Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received an event it did not know how to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-UNEXPECTEDMESSAGE : Unknown message [hex] received (ptr arg [hex], num arg [hex])
Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received a message from another process that it does not know how to handle.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-UNEXPECTEDQUEUE : Queue event for unknown queue (index [dec])
Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received a queuing event for an unknown queue.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-3-UNEXPECTEDTIMER : Unknown timer expiration, timer = [hex], type [dec]
Explanation A process can register to be notified when various events occur in the router. This message indicates that a process received a timer expiration event for an unknown timer.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SCHED-2-WATCH : Attempt to [chars] uninitialized watched [chars] (address [hex])
Explanation A processes can register to be notified when various events occur in the router. This message indicates that an attempt was made to register for an event without first creating the data structure for that event.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SDLC Error Messages
Synchronous Data Link Control error messages
Error Message%SDLC-4-BADFRAME : [chars], Received bad SDLC [chars]frame, address [hex], control [hex]
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%SDLC-3-CONFIGERR : [chars], addr [hex], Sent SNRM, received SNRM. Check link station roles
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%SDLC-4-CTRLBAD : Interface [chars], Invalid control field
Explanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message%SDLC-3-DLU_ERROR : [chars], DLU failed to close station [hex] before re-opening, [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%SDLC-4-DROPPED : Dropped SDLC packet from SDLC hold queue
Explanation An SDLC frame had to be dropped from the output hold queue, usually because of excessive congestion on the output link.
Recommended Action If this message occurs frequently, determine why your SDLC link is being overloaded with data and resolve the cause (typically by either increasing bandwidth to your SDLC line or reducing the load on your link).
Error Message%SDLC-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] [char] VR [dec], Reason [hex]
Explanation A Frame Reject (FRMR) frame was received. This can be caused by a noisy serial line, an overloaded SDLC device, or corrupted data.
Recommended Action If this message recurs, service the serial line and the devices attached to it.
Error Message%SDLC-2-ILLEGSTATE : [chars], illegal state for addr [hex], [chars]([dec])
Explanation An internal SDLC state violation was detected.
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%SDLC-4-INFOBAD : Interface [chars], Info field not permitted
Explanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message%SDLC-4-INVLDGRPCFG : Interface [chars], ignoring group-poll mismatch, UPOLL [hex]
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%SDLC-5-INVLDGRPPOLL : Interface [chars], not configured for group-poll frame, received [hex]
Explanation An unnumbered poll (UP) was received with the wrong group poll address.
Recommended Action Ensure that the group poll address configured on the router matches the one configured in the physical unit macro (GP3174=XX) in the Network Control Program (NCP) generate file.
Error Message%SDLC-4-INVNR : Interface [chars], Invalid NR value
Explanation A bad SDLC frame was received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to it.
Error Message%SDLC-4-N1TOOBIG : Interface [chars], N1 too large
Explanation An information frame was received from the other end of the SDLC link that was larger than allowed with the N1 parameter on this link.
Recommended Action Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame sent by the other end of the link.
Error Message%SDLC-3-NOINPIDB : Input idb not set
Explanation This is a software error. A frame was given to the SDLC handler to process, but the interface on which the frame arrived is not known.
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%SDLC-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SDLC-2-NOPOINTER : AW_SDLC_SEC with no sdllc_llc pointer
Explanation An error condition occurred during SDLLC initiation.
Recommended Action No action is required. The SDLLC session will restart without operator intervention.
Error Message%SDLC-4-NOUA : [chars], addr [hex] received command [hex] in response to SNRM, expected UA
Explanation The router received a frame other than a unnumbered acknowledgment (UA) in response to a set normal response mode (SNRM).
Recommended Action Check the end station to see if the SNA stack is up and running.
Error Message%SDLC-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error occurred in the router's SDLC processing system.
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, and report it to your Cisco technical support representative.
Error Message%SDLC-4-SDLC_ERR : SDLC_ERROR with no poll
Explanation A protocol error was detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This message indicates either poor line conditions or a faulty SDLC implementation.
Recommended Action If this message recurs, run traces on the SDLC line. Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SDLC-6-XID_DISPLAY : sa [sci_notation] da [sci_notation] ss [hex] ds [hex] [[hex][hex][hex][hex]]
Explanation This message supplies the information for the received and rejected XID.
Recommended Action See the "SDLC-4-XID_NOMATCH" error message.
Error Message%SDLC-6-XID_FORMAT : Unsupported XID format received, format [dec]
Explanation An inappropriate exchange identification (XID) format was received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to make sure they are supported.
Recommended Action See the "SDLC-4-XID_NOMATCH" error message.
Error Message%SDLC-4-XID_NOMATCH : [chars], XID mismatch for [hex]. CONNECTION REJECTED
Explanation An inbound exchange identification (XID) from a PU 2.0/PU 2.1 node was rejected. The targeted SDLC address is displayed. The XID information is displayed in a subsequent message "SDLC-6-XID_DISPLAY" or "SDLC-6-FORMAT."
Recommended Action This is a security feature. Additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
SDLLC Error Messages
Synchronous Data Link Control/Logical Link Control, type 2 translation error messages
Error Message%SDLLC-5-ACT_LINK : SDLLC: [chars] LINK address [hex] ACTIVATED: [chars]
Explanation An SDLLC media conversion session was activated.
Recommended Action No action is required.
Error Message%SDLLC-5-DACT_LINK : SDLLC: [chars] LINK address [hex] DEACTIVATED: [chars]
Explanation An SDLLC media conversion session was deactivated. If deactivation is a result of an error condition, this message will include a reason.
Recommended Action If the message does not include a description of an error, the deactivation was normal and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether session loss is related to LLC2 timers by issuing the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears, and report it to your technical support representative.
SEC Error Messages
IP security error messages
Error Message%SEC-6-IPACCESSLOGDP : list [chars] [chars] [chars] [int] [chars]- [int] ([dec]/[dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGNP : list [chars] [chars] [dec] [int] [chars]- [int], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGP : list [chars] [chars] [chars] [int]([dec]) [chars]- [int]([dec]), [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGRP : list [chars] [chars] [chars] [int] [chars]-> [int], [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-6-IPACCESSLOGS : list [chars] [chars] [int] [dec] packet[chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
Error Message%SEC-3-NOMAX : No default for NLESO defined
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%SEC-2-NOOPT : Box secured, no option on internal packet
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%SEC-2-NOTSEC : First opt in tcb not BASIC security
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%SEC-2-SECINS : Security opt in tcb not SECINSERT
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%SEC-4-TOOMANY : Box secured, too many options on internal packet
Explanation There is no room for all desired IP header options. The packet is discarded.
Recommended Action Configure for fewer IP header options.
SERVICE MODULE Error Messages
Service module error messages
Error Message%SERVICE_MODULE-4-ACCESSERROR : Unit [chars] reports register access error - [chars]
Explanation This message indicates that the T1 module supplied a bad register address. It might be because of having a new version of the module operating with an old Cisco IOS software image.
Recommended Action Update the Cisco IOS software image on the system. If this does not solve the problem, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-ALARMFAILURE : Unit [chars] - Could not access alarm status - disabling alarm processing
Explanation The system issued an alarm interrupt, but could not read the alarm status register from the module. This caused the system to disable alarm processing.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-BADTYPE : Unit [chars] - reports incompatible module type [dec] against router hw detect
Explanation A register read request returned an identity for a module that was not the same as the identity reported by the router hardware pinout.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-COMMANDFAILED : Unit [chars] not ready/responding after register [dec] access command issued
Explanation The system did not receive a ready signal within the allotted time after writing to the command register.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-0-INITFAILURE : Unit [chars] - failed to create data structures used for module-access
Explanation The CSU/DSU driver failed to allocate memory for its data structures. This is a catastrophic error. The system has crashed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-0-INITWICFAILURE : Unit [chars] - failed to download properly
Explanation The CSU/DSU driver detected a checksum error while downloading WIC firmware.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-INTERBYTETIMEOUT : Unit [chars] - timed out while [chars] byte [dec] of [dec] length register [dec]
Explanation The module took more than 2 seconds to respond between bytes.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-3-LOOPDOWNFAILED : Unit [chars] - WARNING - Loopdown of remote unit failed
Explanation A remote CSU is looping pings/test patterns back to the system. This error could be triggered if the user disabled loopbacks on the remote CSU after placing the remote CSU into remote loopback.
Recommended Action Execute a clear command on the remote CSU.
Error Message%SERVICE_MODULE-5-LOOPDOWNREMOTE : Unit [chars] - Remote loopback test cancelled
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 for assistance.
Error Message%SERVICE_MODULE-5-LOOPUPFAILED : Unit [chars] - Loopup of remote unit failed
Explanation This notification message indicates that the loopback on the remote unit failed. The failure may indicate that the network connection is broken, or that loopbacks are disabled at the other side.
Recommended Action Check that the router is connected to the network. Enable loopbacks on the remote unit. If the problem persists, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SERVICE_MODULE-5-LOOPUPREMOTE : Unit [chars] - Remote unit placed in loopback
Explanation This notification message indicates that the user executed a loopback command on the remote unit. The remote unit is now in loopback.
Recommended Action No action is required.
Error Message%SERVICE_MODULE-4-NOTREADY : Unit [chars] not ready for register access
Explanation The module was waiting for a ready status before executing a read/write request. The system reported a not ready status for 5 seconds. This caused the module to terminate the read/write request.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-OLDIMAGE : Unit [chars] - router image older than module version - access errors may be seen
Explanation The Cisco IOS software image does not recognize the PROM software version number on the module. The system displays this message if the PROM has been upgraded to a new version, but the Cisco IOS software image has not been upgraded.
Recommended Action Upgrade the Cisco IOS software image.
Error Message%SERVICE_MODULE-4-REPEATEDRESET : Unit [chars] - giving up after [dec] repeated resets couldn't bring module up again
Explanation The software issued several clear service-module requests to the module. The module did not respond to these requests.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-REQUESTOVERLOAD : Unit [chars] - module request overload - lock access timeout
Explanation The system employs a Cisco IOS scheduler semaphore object to ensure mutually exclusive access across software threads to the CSU/DSU. This message indicates that a thread had to wait for more than 5 seconds on this semaphore.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-5-RESET : Reset of Unit [chars] issued
Explanation This message indicates that the module was reset.
Recommended Action No action is required.
Error Message%SERVICE_MODULE-4-RESETFAILURE : Unit [chars] - failed to create reset process - non-default module configuration may be lost
Explanation To execute a reset, the Cisco IOS software must initiate a separate process. The Cisco IOS software did not have sufficient memory to create this separate process. The module came up in an initialized state with the default configuration. The user-defined configuration may have been lost.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-UNKNOWNALARM : Unit [chars] reports unknown network alarms - alarm status reg = [hex]
Explanation A recent version of the module operating with an old Cisco IOS software image did not recognize an alarm condition.
Recommended Action Update the Cisco IOS software image on the system. If this does not solve the problem, copy the error message exactly as it appears and report it to your technical support representative.
Error Message%SERVICE_MODULE-4-WICNOTREADY : Unit [chars] not ready for next command
Explanation The module was waiting for the current request to be processed before sending the next request. The current request has been in progress for more than 3 seconds.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SGBP Error Messages
Stack Group Bidding Protocol (SGBP) error messages
Error Message%SGBP-7-ACTIVE : Member [chars] State -> Active
Explanation This message is generated only when SGBP errors or events debugging is enabled. A link to another SGBP member has completed the interactions necessary to set it up and is now entering the active state.
Recommended Action No action is required.
Error Message%SGBP-5-ARRIVING : New peer event for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer joined the group.
Recommended Action No action is required.
Error Message%SGBP-1-AUTHFAILED : Member [chars] failed authentication
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that an attempted peer connection ended in authentication failure. A peer may be misconfigured the message could indicate an attempted security breach.
Recommended Action Check if the peer is correctly configured. If there is a chance your network is under attack, obtain knowledgeable assistance. 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%SGBP-7-AUTHOK : Member [chars] State -> AuthOK
Explanation This message is generated only when SGBP errors or events debugging is enabled. A message was received from another SGBP member, indicating that an authentication attempt to that member succeeded.
Recommended Action No action is required.
Error Message%SGBP-7-CANCEL : Local query #[dec]:[dec] for bundle [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-CHALLENGE : Send Hello Challenge to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. An authentication challenge was sent to a peer.
Recommended Action No action is required.
Error Message%SGBP-7-CHALLENGED : Rcv Hello Challenge message from member [chars] using [int]
Explanation This message is generated only when SGBP hellos debugging is enabled. An authentication challenge was received from a peer.
Recommended Action No action is required.
Error Message%SGBP-7-CLOSE : Closing pipe for member [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An interprocess communication link was closed.
Recommended Action No action is required.
Error Message%SGBP-1-DIFFERENT : Rcv [chars]'s addr [int] is different from the hello's addr [int]
Explanation The internally configured address for an SGBP member does not match the address of the host that tried to be authenticated as that member. The configuration is incorrect on either this system or the other member—they must agree.
Recommended Action Determine which configuration is in error and fix it.
Error Message%SGBP-7-DONE : Query #[dec] for bundle [chars], count [dec], master is [chars]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-DUPL : Duplicate local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-1-DUPLICATE : Rcv Duplicate bundle [chars] is found on member [chars]
Explanation This message is generated only when SGBP hellos or errors debugging is enabled. This indicates that a duplicate bundle was received from the same peer more than once. The duplicate was discarded.
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%SGBP-7-EQUAL : [dec] equal highest bids, randomly select bid# [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-HANGUP : I am a forward-only member, can't forward bundle [chars], hangup
Explanation This message is generated only when SGBP query, event and/or error debugging is enabled. It indicates that a routine change of role for the router in its SGBP interactions with its peers.
Recommended Action No action is required.
Error Message%SGBP-3-INVALID : MQ message with [chars]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid message was received and discarded.
Recommended Action This probably indicates an error in network media or a peer is generating erroneous packets.
Error Message%SGBP-3-INVALIDADDR : Stack group [chars] IP address [int]
Explanation The current configuration does not allow a local IP address to be configured using the sgbp member command. Local addresses are automatically removed from the SGBP group.
Recommended Action Do not configure the sgbp member command using a local IP address.
Error Message%SGBP-3-INVALIDB : [chars] for bundle '[chars]' -- [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.
Error Message%SGBP-3-INVFIELD : [chars] field type [hex] has [chars] [dec] (expected [dec])
Explanation An SGBP request from a peer contained invalid or corrupt data.
Recommended Action Check the peer equipment or network media for any problems.
Error Message%SGBP-7-KEEPALIVE : Sending Keepalive to [chars], retry=[dec]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that a keepalive message was sent to an SGBP member.
Recommended Action No action is required.
Error Message%SGBP-7-KEEPALIVE_TIMEOUT : Keepalive timeout on [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. It indicates that keepalive messages were not answered so the pipe to an SGBP member has been closed.
Recommended Action No action is required.
Error Message%SGBP-5-LEAVING : Member [chars] leaving group [chars]
Explanation This message is generated only when SGBP event debugging is enabled. An SGBP peer has left the group.
Recommended Action No action is required.
Error Message%SGBP-1-MISSCONF : Possible misconfigured member [chars] using [int]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. This indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address.
Recommended Action Find and correct the configuration error.
Error Message%SGBP-7-MQ : [chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec]
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP query has been received.
Recommended Action No action is required.
Error Message%SGBP-7-MQB : Bundle: [chars] State: [chars] OurBid: %03d
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action No action is required.
Error Message%SGBP-7-NEWL : Local query #[dec] for [chars], count [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-NEWP : Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec]
Explanation This message is generated only when SGBP query debugging is enabled. It provides information about queries in progress.
Recommended Action No action is required.
Error Message%SGBP-7-NORESP : Failed to respond to [chars] group [chars], may not have password
Explanation An authentication challenge was received but there was no information available to respond to it. This probably indicates a configuration error or a missing password.
Recommended Action Refer to the documentation in order to configure a username with the same name as the SGBP group.
Error Message%SGBP-7-PB : [int] State: [chars] Bid: %03d Retry: [dec]
Explanation This message is part of a list of debug states displayed at the request of the operator.
Recommended Action No action is required.
Error Message%SGBP-3-PEERERROR : Peer [int] [chars] during 'PB [chars]' state for bundle [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.
Error Message%SGBP-7-RCVD : MQ [chars] from [int] for query [dec]:[dec], bundle [chars], bid [dec]
Explanation This message is generated only when SGBP message debugging is enabled. An SGBP packet was received.
Recommended Action No action is required.
Error Message%SGBP-7-RCVINFO : Received Info Addr = [int] Reference = [hex]
Explanation This message is generated only when SGBP hellos debugging is enabled. Data was received by a listener process.
Recommended Action No action is required.
Error Message%SGBP-7-RESPONSE : Send Hello Response to [chars] group [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. A response to an authentication challenge was sent to a peer.
Recommended Action No action is required.
Error Message%SGBP-7-RESPONSED : Rcv Hello Response message from member [chars] using [int]
Explanation This message is generated only when SGBP hellos debugging is enabled. A response to an authentication challenge was received from a peer.
Recommended Action No action is required.
Error Message%SGBP-7-SENDAUTHOK : Send Hello Authentication OK to member [chars] using [int]
Explanation This message is generated only when SGBP hellos debugging is enabled. A message was sent or re-sent to another SGBP member, indicating that an authentication attempt from that member succeeded.
Recommended Action No action is required.
Error Message%SGBP-7-SENDINFO : Send Info Addr to [chars]
Explanation This message is generated only when SGBP hellos debugging is enabled. Data was sent by the listener process in response to received data.
Recommended Action No action is required.
Error Message%SGBP-7-SENT : MQ [chars] to [int] for query [dec]:[dec], bundle [chars], bid [dec], len [dec]
Explanation This message is generated only when SGBP message debugging is enabled. An SGBP packet was sent.
Recommended Action No action is required.
Error Message%SGBP-5-SHUTDOWN : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. A process involved in SGBP was terminated upon completion of its work.
Recommended Action No action is required.
Error Message%SGBP-5-STARTUP : [chars]
Explanation This message is generated only when SGBP event debugging is enabled. A process involved in SGBP was started.
Recommended Action No action is required.
Error Message%SGBP-3-TIMEOUT : Peer [int] bidding; state 'PB [chars]' deleted
Explanation This message is generated only when SGBP event debugging is enabled. It indicates that a peer timed out while closing a query. The connection has been dropped.
Recommended Action Check the peer equipment and network media for problems.
Error Message%SGBP-3-UNEXP : MQ [chars] from [int] for query [dec], bundle [chars], bid [dec], state [chars]
Explanation This message is generated only when SGBP error debugging is enabled. The SGBP connection has entered an unexpected state, possibly because of a software error.
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%SGBP-3-UNKNOWN : [int] not known
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP connection was attempted by a host that was not recognized as a peer. The connection was not accepted.
Recommended Action Depending on the network topology and firewall, SGBP connection attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. 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%SGBP-3-UNKNOWNEVENT : Event [hex] from peer at [int]
Explanation This message is generated only when SGBP error debugging is enabled. An invalid event occurred, which probably indicates an internal software error.
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%SGBP-1-UNKNOWNHELLO : Rcv Hello message from non-group member using [int]
Explanation This message is generated only when SGBP hellos or error debugging is enabled. An SGBP hello message was received from a host that is not a member of the SGBP group, and discarded.
Recommended Action This is a configuration error. Either that host should be listed in this router's configuration as a member (if that is actually true) or the other host is misconfigured to attempt to join this group.
Error Message%SGBP-3-UNKNOWNPEER : Event [hex] from peer at [int]
Explanation This message is generated only when SGBP error debugging is enabled. An SGBP event came from a network host that was not recognized as an SGBP peer. The event was discarded.
Recommended Action Check if a network media error corrupted the address, or if malfunctioning peer equipment generated corrupted packets. Depending on the network topology and firewall, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. 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.
SHELF Error Messages
Router shelf error messages
Error Message%SHELF-5-AUTH_FAILED : MD5 digest does not match, SDP packet received from, [int] rejected
Explanation An SDP hello packet was received from the shelf, which is not trusted.
Recommended Action Specify either the correct SDP password and/or destination on the shelf from which this message was received.
Error Message%SHELF-3-DISCOVER_SOCKET_OPEN : socket open failed
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.
Error Message%SHELF-6-HELLO_PROCESS_START : Shelf hello process has started
Explanation This is an informational message only. An internal system controller process was started.
Recommended Action Informational messages can be disabled by changing the logging level.
Error Message%SHELF-6-HELLO_PROCESS_STOP : Shelf hello process has been stopped
Explanation This is an informational message only. An internal system controller process completed its work.
Recommended Action Informational messages can be disabled by changing the logging level.
Error Message%SHELF-6-SYSCTLR_ESTABLISHED : Configured via system controller located at [int]
Explanation This is an informational message only. Configuration information was received from a system controller.
Recommended Action Informational messages can be disabled by changing the logging level.
SLIP Error Messages
Serial Line Internet Protocol error messages
Error Message%SLIP-2-BADQUOTE : Impossible quoted character [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%SLIP-2-BADSTATE : Impossible input state [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.
SLOTDUMP Error Message
Slot dump error message
Error Message%SLOTDUMP-3-CORE_DUMP_ERROR : Core dump error slot [dec]: [chars]
Explanation An error occurred during a core dump of the slot.
Recommended Action No action is required.
SMF Error Message
Software MAC Filter (SMF) error message
Error Message%SMF-4-INVALID_ACTION : failed to create SMF entry for [sci_notation] on [chars] with result [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, call your Cisco technical support representative and provide the representative with the gathered information.
SMRP Error Messages
Simple Multicast Routing Protocol error messages
Error Message%SMRP-2-ASSERTFAILED : SMRP assertion failed: [chars]
Explanation The software detected an inconsistency. This is considered a serious error. The router attempts to continue, but SMRP processing may be impaired.
Recommended Action Copy the error message exactly as it appears, noting any SMRP problems that you are experiencing, and report it to your technical support representative.
Error Message%SMRP-7-DEBUGMSG : SMRP Debug: [chars]
Explanation This message is generated by some debug commands to provide additional information about conditions in SMRP.
Recommended Action If you are experiencing problems in SMRP, these messages should be provided, along with any other information, in a report to your technical support representative.
Error Message%SMRP-5-NEIGHBORDOWN : [chars]: SMRP neighbor down - [chars]
Explanation A neighboring SMRP router is now down.
Recommended Action This is a notification message only. No action is required.
Error Message%SMRP-6-NEIGHBORUP : [chars]: SMRP neighbor up - [chars]
Explanation A neighboring SMRP router has appeared.
Recommended Action This is a notification message only. No action is required.
Error Message%SMRP-3-NOFDDICOMPAT : SMRP port [chars] disabled; pre-fdditalk not supported
Explanation SMRP cannot be started on an interface that is running pre-FDDITalk.
Recommended Action Use FDDITalk on the FDDI ring if possible.
Error Message%SMRP-5-PORTDOWN : [chars]: SMRP port down - [chars]
Explanation An SMRP port is down and is no longer operational.
Recommended Action This is a notification message only. No action is required.
Error Message%SMRP-6-PORTUP : [chars]: SMRP port up - [chars]
Explanation An SMRP port has come up.
Recommended Action This is a notification message only. No action is required.
SNAPSHOT Error Messages
Snapshot dial-on-demand routing error messages
Error Message%SNAPSHOT-2-BADSTATE : Bad state for Snapshot block [chars][[dec]], location [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%SNAPSHOT-2-TOOMANYDIALERS : Exceeded maximum dialer interfaces to watch. Ignoring [chars]
Explanation Snapshot is being used over more than 100 dial-on-demand routing (DDR) interfaces.
Recommended Action Do not use snapshot over more than 100 DDR interfaces.
SNMP Error Messages
Simple Network Management Protocol error messages
Error Message%SNMP-3-BADOID : Attempt to generate an invalid object identifier
Explanation A valid object identifier must contain at least two subidentifiers. An attempt was made to generate an object identifier whose size was less than two.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP-3-BADVALUE : Maximum number of index supported is 8
Explanation An SNMP trap contains some number of MIB objects, and the size of the instance identifier for these objects is restricted. This message indicates that an attempt was made to generate an SNMP trap containing a MIB object whose size exceeded this limit.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP-3-CPUHOG : Processing [chars] of [chars]
Explanation SNMP took too much time processing a request.
Recommended Action If feasible, use the debug snmp packet command to determine the contents of the SNMP request that is causing the message. Copy the error message exactly as it appears, and report it along with any debug output to your technical support representative.
Error Message%SNMP-4-TRAPDROP : [chars]
Explanation An attempt was made to generate an SNMP trap, but the trap could not be sent because of the reason given in this message. Most likely, this message means that the SNMP traps process is not running.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Use the show process command to determine whether the SNMP traps process is running. If it is not running, reload the system. If, after reloading, the SNMP traps process is still not running, there may not be enough memory for it to run.
Error Message%SNMP-3-TRAPINTR : Attempt to generate SNMP trap from interrupt level
Explanation During the processing of an interrupt, the code attempted to generate an SNMP trap. This is not allowed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SNMP_MGR Error Messages
Simple Network Management Protocol proxy error messages
Error Message%SNMP_MGR-3-BADAGETIMER : Unexpected age timer found on session [hex]
Explanation An internal timer was found running when it should not have been.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Disable the SNMP manager via the no snmp-server manager command. Then re-enable it via the snmp-server manager command. This should effectively reset all of the internal structures.
Error Message%SNMP_MGR-4-BADAUTHTYPE : Unsupported SNMP authorization type: [int]
Explanation An unknown SNMP authorization type was found. This may result in the inability of the SNMP manager functionality to correctly send and/or receive SNMP messages to or from a particular SNMP agent.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-BADINFORMTRANSPORT : Unknown inform transport type: [chars]
Explanation This SNMP inform destination uses an unknown transport type. Inform notifications cannot be sent to this destination.
Recommended Action Copy the error message and the output from the show tech-support command exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-BADOP : Unknown operation code [int]
Explanation An SNMP PDU delivered to the SNMP manager contains an unknown operation code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-BADPDUTYPE : Received unknown PDU type: [int]
Explanation The SNMP manager was delivered a PDU of an unknown type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-4-BADRESPONSESTATUS : Unknown response status code: [int]
Explanation The SNMP manager process received an internal response with an unknown status code.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-BADTRANSPORT : Unknown transport type: [int]
Explanation The SNMP manager was delivered a PDU from an unknown transport type.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-BADUSECOUNT : Corrupted use counter found on session [hex]
Explanation A cached SNMP session structure appears to have been corrupted.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Disable the SNMP manager via the no snmp-server manager command. Then re-enable it via the snmp-server manager command. This should effectively reset all of the internal structures.
Error Message%SNMP_MGR-4-EMPTYQUEUE : Input queue is empty
Explanation The SNMP manager process was notified that it needs to process its input queue. But, when the queue was examined, it was found to be empty.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-MISSINGHOST : Cannot locate information on SNMP informs host: [int]
Explanation A table entry for the mentioned SNMP informs destination cannot be found. As a result, inform notifications will not be sent to this destination.
Recommended Action Issue the show snmp host and show snmp commands. Copy the error message and output from the show commands exactly as they appear, and report it to your technical support representative. Deleting and re-adding the informs destination via the snmp-server host configuration command may clear the condition. Otherwise, reloading the system may be necessary.
Error Message%SNMP_MGR-4-NOCANCEL : Unable to cancel a previously sent inform request
Explanation The number of unacknowledged inform requests in-flight has reached the configured maximum limit. In order to make available resources for sending out a new inform request, one of these older inform requests must be cancelled. The algorithm used to choose the most appropriate inform to cancel has failed to choose any. The new inform that was to be sent will be dropped instead.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SNMP_MGR-3-NOPROC : Failed to create SNMP Manager process
Explanation The SNMP manager process was unable to initialize. This is most likely because of a lack of memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative. Use the show memory command to examine the amount of available memory. If free memory is low, you may need to reconfigure and/or reload the system.
Error Message%SNMP_MGR-4-NOTENABLED : SNMP Manager not enabled (requested by [chars])
Explanation A Cisco IOS application is attempting to make use of the SNMP manager's services. However, the SNMP manager functionality has not been enabled.
Recommended Action You may enable the SNMP manager services via the snmp-server manager configuration command. Otherwise, the Cisco IOS application that is requesting these services is given in the message. Disable or reconfigure this application so that it no longer tries to make SNMP manager requests.
Error Message%SNMP_MGR-3-RESPDROP : Insufficient memory to handle response to request id [int]
Explanation An SNMP response PDU was received, but not enough memory was available to cache the response and return it to the original requesting Cisco IOS application.
Recommended Action If this was only a transient problem, the original SNMP request will likely be resent, another SNMP response will be returned and delivered to the original requesting Cisco IOS application. If this message repeats, then you must free up some memory for the SNMP manager to function. Issue the show memory command to verify whether available memory is low. You may need to reconfigure and/or reload the system to free up some memory. Otherwise, you can disable the SNMP manager functionality via the no snmp-server manager command.
Error Message%SNMP_MGR-3-SESSIONINUSE : Attempt to destroy session [hex] that is still in use
Explanation An attempt was made to remove a cached SNMP session structure. However, it appears that the session is still in use, and, therefore, should not be removed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
SONET Error Messages
Synchronous Optical Network (SONET) error messages
Error Message%SONET-4-ALARM : [chars]: [chars] [chars]
Explanation The specified SONET alarm was declared or released.
Recommended Action Repair the source of the alarm.
Error Message%SONET-4-APSMM : APS mode mismatch - [chars]
Explanation A unidirectional or bidirectional mismatch was detected y the APS system.
Recommended Action Change the router configuration to match the provisioned circuit.
Error Message%SONET-3-APSNCHN : APS Local request [dec] has no corresponding channel number
Explanation APS software has malfunctioned.
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%SONET-3-APSNOINTFC : APS No interfaces available for IP connection
Explanation APS requires an out-of-band path for inter-router communication.
Recommended Action Configure an out-of-band path for inter-router APS communication
Error Message%SONET-3-BADAUTH : APS Bad authentication from [int],
Explanation APS software detected an unauthorized message.
Recommended Action This message could result from improper configuration, unauthorized access, or packet corruption. 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%SONET-3-BADVER : APS Bad version number [dec] detected in hello msg
Explanation APS software detected an invalid version number in the hello message.
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%SONET-3-NOBUFFER : No buffer available for sending APS message
Explanation No data buffer was available for sending an APS message.
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%SONET-3-NOSOCKET : Unable to open socket
Explanation APS software detected and invalid version number in the hello message.
Recommended Action This is an informational message only. No action is required.
SONETMIB Error Messages
Synchronous Optical Network Management Information Base error messages
Error Message%SONETMIB-1-DELETE : could not delete interface, if_index=[dec]
Explanation The specified interface was not successfully dequeued.
Recommended Action No action is required.
Error Message%SONETMIB-1-MALLOCNEW : Malloc failed for new interface=[dec]
Explanation Unable to allocate enough memory to create SONET MIB structure for the new interface.
Recommended Action No action is required.
SPARC Error Message
3800 SPARC coprocessor subsystem error message
Error Message%SPARC-3-DOWN : SPARC process is not responding, [chars]
Explanation The SPARC coprocessor subsystem is not responding to configuration commands.
Recommended Action The SPARC coprocessor will be restarted automatically when this error occurs. This is not a normal condition and, if the problem recurs, could indicate a hardware failure. 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.
SSE Error Messages
Silicon switching engine error messages
Error Message%SSE-3-BADMEMORY : SSE memory failure detected, orig [hex] [hex], tested [hex] [hex]
Explanation A memory 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%SSE-2-BOGUSEQ : SSE bogus equal branch [hex], [hex], [dec] [hex]
Explanation An internal inconsistency in the data structures used by the SSE 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%SSE-3-COMPERR : SSE compilation failure -- [chars]
Explanation A software failure 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%SSE-2-HUNG : SSE hung -- [chars]
Explanation The SSE is hung.
Recommended Action Reboot the SSE.
Error Message%SSE-2-HWFAILURE : SSE hardware failure -- [chars] code [hex]
Explanation A hardware error occurred, indicating an unexpected condition on the silicon switch processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. 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%SSE-2-MEMERROR : SSE memory failure, address [hex], expected [hex], got [hex]
Explanation A hardware error occurred, indicating memory failure on the silicon switch processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. 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%SSE-2-NESTADDR : SSE nested addresses detected, protocol [dec] [int]
Explanation An internal inconsistency in the data structures used by the SSE 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%SSE-2-NOMATCH : SSE delete didn't end at a match node, type [char], value [dec], address [int], bytecount [dec], high [dec], state [dec]
Explanation An internal inconsistency in the data structures used by the SSE 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%SSE-2-NOMEMORY : No memory available for [chars]
Explanation An operation could not be accomplished because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SSE-2-NOTZERO : program memory does not start at zero
Explanation A hardware error occurred, indicating an unexpected condition on the silicon switch processor (SSP) board.
Recommended Action It might be necessary to replace the SSP. 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%SSE-2-SWFAILURE : SSE software failure -- [chars] [hex]
Explanation A software failure 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.
STANDBY Error Messages
Hot Standby Router Protocol error messages
Error Message%STANDBY-3-BADAUTH : Bad authentication from [int], remote state [chars]
Explanation Two routers participating in the Hot Standby protocol disagree on the valid authentication string.
Recommended Action Use the standby authentication interface command to repair the Hot Standby protocol authentication discrepancy between the local system and the one whose IP address is reported.
Error Message%STANDBY-3-DUPADDR : Duplicate IP address [int] detected on [chars]
Explanation The IP address in an HSRP message received on the interface is the same as the router's own IP address. This may be caused by misconfiguration or a malfunctioning switch.
Recommended Action Check the configurations on all the HSRP routers, and make sure that all switches are functioning properly.
Error Message%STANDBY-3-MISCONFIG : Attempt to change [chars] MAC address to [sci_notation] when DECNET already running
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%STANDBY-3-NOSOCKET : Unable to open socket
Explanation The system was unable to initialize an IP connection for the Hot Standby protocol.
Recommended Action Ensure that there is at least one interface configured to run IP.
Error Message%STANDBY-6-STATECHANGE : Standby: [dec]: [chars] state [chars] [chars]
Explanation The router has changed state
Recommended Action No action is required.
STUN Error Messages
Serial tunneling error messages
Error Message%STUN-3-BADCONN : CONN: bad connection ([dec]), peer: [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%STUN-3-BADLENOP : [chars]: bad len or unknown op, op [dec], len [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%STUN-3-BADMAGIC : [chars]: wrong magic, mine [hex], theirs [hex] ([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%STUN-3-BADMAGICTCP : [chars]: peer [chars], wrong magic, mine [hex], theirs [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%STUN-3-BADPASSIVEOPEN : passive open from [int]([dec]) - [dec] failed
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%STUN-3-CONNILLSTATE : CONN: Peer [chars], illegal state [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%STUN-6-CONNOPENFAIL : CONN: peer [chars] open failed, [chars] [[int]]
Explanation An attempt to connect to a remote TCP STUN peer failed.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting STUN, and that it is configured correctly.
Error Message%STUN-4-ERR : [chars]: [chars]: [chars], op [hex], len [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%STUN-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, temporary.
Recommended Action Reconfigure the STUN group. If memory shortages persist, call your Cisco technical support representative for assistance.
Error Message%STUN-3-NOINPIDB : Input idb not set
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%STUN-2-NOMEMORY : No memory available: [chars]
Explanation The requested operation failed because of a low-memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%STUN-2-NOTGI : Please remove and redefine protocol group [dec]
Explanation An internal error occurred. The configuration is irregular.
Recommended Action Remove and reconfigure the STUN protocol group. Record the configuration and call your Cisco technical support representative for assistance.
Error Message%STUN-6-OPENED : [chars]: peer [chars] opened, [previous state [chars]]
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.
Error Message%STUN-6-OPENING : CONN: opening peer [chars], [dec]
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.
Error Message%STUN-6-PASSIVEOPEN : passive open [int]([dec]) - [dec]
Explanation A connection attempt to a remote peer completed successfully (OPENED, PASSIVE-OPEN) or is in the process of being opened (OPENING). This is good, expected behavior.
Recommended Action No action is required.
Error Message%STUN-6-PEERSHUTDOWN : shutting down peer [chars] on [chars]
Explanation A connection to a remote peer is being shut down. This is typically the result of user intervention in STUN reconfiguration or disabling. This is good, expected behavior.
Recommended Action No action is required.
Error Message%STUN-4-PEERSTATE : Peer [chars], wrong state [dec] ([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%STUN-6-RECONNECT : PHDR: reconnect from peer [chars]
Explanation A remote peer re-established a connection to this router.
Recommended Action No action is required.
Error Message%STUN-3-SENDPUNT : [chars]: sent [chars] to [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%STUN-3-SENDPUNTTCP : [chars]: sent [chars] to ([[int]])[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%STUN-6-TCPFINI : peer [chars] closed [previous state [chars]]
Explanation A remote peer closed a STUN connection with this router.
Recommended Action Examine the other router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)
Error Message%STUN-6-TCPPEERSHUT : [chars] [chars], [int]([dec])
Explanation This route closed a STUN connection with a remote peer.
Recommended Action Examine this router to see why it closed this connection with this peer. (This can be caused by normal events, such as reconfiguration.)
SUBSYS Error Messages
Software subsystem error messages
Error Message%SUBSYS-2-BADCLASS : Bad subsystem class ([dec]) - ignoring subsystem
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-BADSEQUENCE : Subsystem ([chars]) has cross-class sequence for ([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%SUBSYS-2-BADVERSION : Bad subsystem version number ([dec]) - ignoring subsystem
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-MISMATCH : Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystem
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-NOTFOUND : Subsystem ([chars]) needs subsystem ([chars]) to start
Explanation A software consistency check failed.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-3-PAGEZERO : The [chars] class subsystem [chars] was being initialized
Explanation In all Cisco products, the first 256 bytes of memory is unused and off-limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically perform checks on this memory. This message appears only on older platforms and indicates that this off-limits memory area was modified.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SUBSYS-2-RECURSION : Maximum sequence depth exceeded ([dec]) by ([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.
SUPERVISOR Error Messages
Error Message%SUPERVISOR-4-OVERRUN
Explanation A buffer or FIFO overrun ocurred.
Recommended Action LOG_STD_ACTION.
SW56 Error Messages
Switch 56K error messages
Error Message%SW56-3-ERR_MSGQ : [chars]
Explanation A message to the internal software process was not sent.
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%SW56-1-INITSYS : [chars]
Explanation SW56 initialization failed, probably because there is a lack of memory.
Recommended Action The amount of memory available in the router may not be sufficient. 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.
SWITCH Error Message
Switch interface error message
Error Message%SWITCH-1-NOMEMORY : msgtxt_nomemory
Explanation The CPU was unable to access the memory it needs to carry out its functions. The following are some possible causes. The network is large, requiring a great deal of memory for routing tables, and so on. The router configuration has many features enabled, each of which require a certain amount of memory. A software error (memory leak) exists.
Recommended Action Reduce system activity to ease the memory demand, or upgrade to a larger memory configuration.