SNMP through TCATM

SNMP Messages
SNMP_MGR Messages
SONET Messages
SONETMIB Messages
SPARC Messages
SSE Messages
STANDBY Messages
STUN Messages
SUBSYS Messages
SW56 Messages
SWITCH Messages
SYS Messages
SYSCTLR Messages
SYSLOG_SERVER Messages
SYSMGT_RPC Messages
TAC Messages
TAGCON Messages
TBRIDGE Messages
TCATM Messages

SNMP Messages

The following are Simple Network Management Protocol (SNMP) error messages.

Error Message

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

Explanation An attempt has been made to generate an object identifier that has fewer than two subidentifiers. A valid object identifier must contain at least two subidentifiers.

Error Message

%SNMP-3-BADVALUE: Maximum number of index supported is 20

Explanation An attempt has been made to generate a Simple Network Management Protocol (SNMP) trap containing an MIB object that has exceeded the maximum size. A SNMP trap contains some number of MIB objects, and the size of the instance identifier for these objects is restricted.

Error Message

%SNMP-3-CPUHOG: Processing [chars] of [chars]

Explanation A Simple Network Management Protocol (SNMP) took too much time to process a request.

Recommended Action If conditions warrant, enter 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 on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. Include any debug output that is generated.

Error Message

%SNMP-4-NOENGINEID: Remote snmpEngineID for [int] not found when creating user: [chars]

Explanation An attempt to create a user has failed. This condition has occurred because the engine ID of the remote agent or the Simple Network Management Protocol (SNMP) Manager was not configured.

Recommended Action Configure the remote snmpEngineID and reconfigure the user. 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

%SNMP-4-NOFLASH: Reading snmpEngineBoots from flash failed

Explanation The system is unable to read the snmpEngineBoots file from flash memory. This error should occur if the flash card does not exist in the router. This message should appear only when the router is reloaded.

Recommended Action Reinstall the flash card. If the the flash card is properly installed and this message recurs, the flash card memory might be full. Erase flash memory, and reload the software image into the router. If these steps do not adequately resolve the problem, 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

%SNMP-3-TRAPBLOCK: Attempt to generate SNMP trap from a process with blocking disabled

Explanation A process with blocking disabled has attempted to generate a Simple Network Management Protocol (SNMP) trap that would block. A process that is configured this way is not allowed to use this function.

Error Message

%SNMP-4-TRAPDROP: [chars]

Explanation An attempt has been made to generate a Simple Network Management Protocol (SNMP) trap, and the trap could not be sent. This condition might have occurred because the SNMP traps process is not running. More information will be displayed in the error message.

Recommended Action Use the show process command to determine if the SNMP traps process is running. If the process is not running, reload the system. If reloading the system does not resolve the problem, there may not be enough memory to run the SNMP traps process. 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

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

Explanation The code has attempted to generate a Simple Network Management Protocol (SNMP) trap while processing an interrupt. This function is not allowed.

SNMP_MGR Messages

The following are Simple Network Management Protocol (SNMP) proxy error messages.

Error Message

%SNMP_MGR-3-BADAGETIMER: Unexpected age timer found on session [hex]

Explanation The system has found an internal timer that should not be running.

Recommended Action Enter the no snmp-server manager command to disable the Simple Network Management Protocol (SNMP) Manager. Then enter the no snmp-server manager command to reenable the SNMP Manager. Entering these commands should reset all of the internal structures. If entering this command sequence does not adequately resolve the problem, 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

%SNMP_MGR-4-BADAUTHTYPE: Unsupported SNMP authorization type: [int]

Explanation The system has found an unknown Simple Network Management Protocol (SNMP) authorization type. This condition might prevent the SNMP Manager from correctly sending or receiving SNMP messages to and from a particular SNMP agent.

Error Message

%SNMP_MGR-3-BADINFORMTRANSPORT: Unknown inform transport type: [chars]

Explanation The destination of a Simple Network Management Protocol (SNMP) inform notification has used an unknown transport type. The inform notification cannot be sent to this destination.

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 command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%SNMP_MGR-3-BADOP: Unknown operation code [int]

Explanation A Simple Network Management Protocol (SNMP) protocol data unit (PDU) that has been delivered to the SNMP Manager contains an unknown operation code.

Error Message

%SNMP_MGR-3-BADPDUTYPE: Received unknown PDU type: [int]

Explanation A protocol data unit (PDU) of an unknown type has been delivered to the Simple Network Management Protocol (SNMP) Manager.

Error Message

%SNMP_MGR-4-BADRESPONSESTATUS: Unknown response status code: [int]

Explanation The Simple Network Management Protocol (SNMP) Manager process has received an internal response with an unknown status code.

Error Message

%SNMP_MGR-3-BADTRANSPORT: Unknown transport type: [int]

Explanation A protocol data unit (PDU) from an unknown transport type has been delivered to the Simple Network Management Protocol (SNMP) Manager.

Error Message

%SNMP_MGR-3-BADUSECOUNT: Corrupted use counter found on session [hex]

Explanation A cached Simple Network Management Protocol (SNMP) session structure might have been corrupted.

Recommended Action Enter the no snmp-server manager command to disable the Simple Network Management Protocol (SNMP) Manager. Then enter the no snmp-server manager command to reenable the SNMP Manager. Entering these commands should reset all the internal structures. If entering this command sequence does not adequately resolve the problem, 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

%SNMP_MGR-4-EMPTYQUEUE: Input queue is empty

Explanation The Simple Network Management Protocol (SNMP) Manager process has received a notification to process the input queue. When the SNMP Manager examined the input queue, the SNMP Manager found the queue to be empty.

Error Message

%SNMP_MGR-3-MISSINGHOST: Cannot locate information on SNMP informs host: [int]

Explanation The system cannot locate configuration information about a Simple Network Management Protocol (SNMP) informs host. The "informs destination" table entry for SNMP cannot be found, and "inform notifications" will not be sent to this destination.

Recommended Action It might be possible to clear the condition by removing and adding the "informs destination" configuration. The "informs destination" configuration can be changed by entering the snmp-server host configuration command. If changing the configuration does not resolve the problem, the system might need to be reloaded. Enter the show snmp host and show snmp commands. Copy the error message and output from the show commands exactly as they appear, and report them to your Cisco technical support representative. Copy the error message exactly as it appears on the console or in the system log. Enter the show snmp host and show snmp commands to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show snmp host and show snmp command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%SNMP_MGR-4-NOCANCEL: Unable to cancel a previously sent inform request.

Explanation The number of unacknowledged inform requests issued has reached the configured maximum limit. To make resources available for sending out a new inform request, one of the older inform requests must be cancelled. The algorithm that is used to choose which inform request is the most appropriate one to cancel has failed to choose any. The new inform request will not be sent, and it will be dropped.

Error Message

%SNMP_MGR-3-NOPROC: Failed to create SNMP Manager process

Explanation The system was unable to initialize the Simple Network Management Protocol (SNMP) Manager process. This condition might be caused by a low memory condition.

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. Enter the show memory command to examine the amount of available memory. If free memory is low, this condition might require you to reconfigure 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 use the Simple Network Management Protocol (SNMP) Manager services, but the SNMP Manager functionality has not been enabled.

Recommended Action Enter the snmp-server manager command in configuration mode to enable SNMP Manager services for the Cisco IOS application that is requesting these services. If it is not necessary for the application to make SNMP Manager requests, disable or reconfigure the 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 A Simple Network Management Protocol (SNMP) response protocol data unit (PDU) has been received from a Cisco IOS application. There is not enough memory available to cache the response and return it to the original requesting Cisco IOS application. If this was a transient problem, the original Simple Network Management Protocol (SNMP) request will be resent, and another SNMP response will be returned and delivered to the Cisco IOS application that made the request.

Recommended Action If this message recurs, you will be required to free up some memory for the SNMP Manager to function. Enter the show memory command to verify that the available amount of memory. You may be required to reconfigure or reload the system to make memory available. You can disable the SNMP Manager by entering 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 has been made to remove a cached Simple Network Management Protocol (SNMP) session structure. The session is still in use, and the session should not be removed.

SONET Messages

The following are SONET error messages.

Error Message

%SONET-4-ALARM: [chars]: [chars] [chars]

Explanation The specified SONET alarm has been declared or released.

Recommended Action Repair the source of the alarm.

Error Message

%SONET-4-APSMM: APS mode mismatch - [chars]

Explanation A unidirectional/bidirectional mismatch has been detected in the automatic protection switching (APS) system.

Recommended Action It is recommended that the router configuration match the provisioned circuit.

Error Message

%SONET-3-APSNCHN: APS Local request [dec] has no corresponding channel number

Explanation Automatic protection switching (APS) software has malfunctioned.

Error Message

%SONET-3-APSNOINTFC: APS No interfaces available for IP connection

Explanation Automatic protection switching (APS) requires an out-of-band path for interrouter communication.

Recommended Action Configure an out-of-band path for interrouter APS communication.

Error Message

%SONET-3-BADAUTH: APS Bad authentication from [int],

Explanation Automatic protection switching (APS) software has detected an unauthorized message. This condition could be the result of an improper configuration, unauthorized access, or packet corruption.

Error Message

%SONET-3-BADVER: APS Bad version number [dec] detected in hello msg

Explanation Automatic protection switching (APS) software has detected an invalid version number in the hello message.

Error Message

%SONET-3-NOBUFFER: No buffer available for sending APS message

Explanation The data buffer was unavailable to send an automatic protection switching (APS) message.

Error Message

%SONET-3-NOSOCKET: Unable to open socket

Explanation Automatic protection switching (APS) software has detected an invalid version number in the hello message. This is an informational message only.

Recommended Action No action is required.

SONETMIB Messages

The following are SONET MIB error messages.

Error Message

%SONETMIB-1-DELETE: could not delete interface, if_index=[dec]

Explanation The system could not remove the queue for the specified interface.

Recommended Action No action is required.

Error Message

%SONETMIB-1-MALLOCNEW: Malloc failed for new interface=[dec]

Explanation The system is unable to allocate enough memory to create a SONET MIB structure for a new interface.

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

SPARC Messages

The following are 3800 SPARC coprocessor subsystem error messages.

Error Message

%SPARC-3-DOWN: SPARC process is not responding, [chars]

Explanation The SPARC coprocessor subsystem is not responding to configuration commands. The SPARC coprocessor will be restarted automatically when this condition occurs. This is not a normal condition. The recurrence of this problem might indicate a hardware failure.

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.

SSE Messages

The following are silicon switching engine (SSE) error messages.

Error Message

%SSE-3-BADMEMORY: SSE memory failure detected, orig [hex] [hex], tested [hex] [hex]

Explanation A memory failure has been detected.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter 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 The data structures that are used by the silicon switching engine (SSE) have an internal inconsistency.

Error Message

%SSE-3-COMPERR: SSE compilation failure -- [chars]

Explanation A software error has occurred.

Error Message

%SSE-2-HUNG: SSE hung -- [chars]

Explanation The silicon switching engine (SSE) has locked up.

Recommended Action Reboot the SSE.

Error Message

%SSE-2-HWFAILURE: SSE hardware failure -- [chars] code [hex]

Explanation A hardware error has occurred. This condition indicates 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. Enter 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 has occurred. This condition indicates a memory failure has occurred on the Silicon Switch Processor (SSP) board.

Error Message

%SSE-2-NESTADDR: SSE nested addresses detected, protocol [dec] [int]

Explanation The data structures that are used by the silicon switching engine (SSE) have an internal inconsistency.

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 has occurred in the data structures that are used by the silicon switching engine (SSE).

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 An unexpected condition has occurred on the Silicon Switch Processor (SSP) board.

Error Message

%SSE-2-SWFAILURE: SSE software failure -- [chars] [hex]

Explanation A software failure has occurred.

STANDBY Messages

The following are Hot Standby Router Protocol (HSRP) error messages.

Error Message

%STANDBY-3-BADAUTH: Bad authentication from [int], remote state [chars]

Explanation Two routers that are using the Hot Standby Router Protocol (HSRP) disagree about the valid authentication string.

Recommended Action Enter the standby authentication interface command to repair the HSRP authentication discrepancy between the local system and the router whose IP address is reported.

Error Message

%STANDBY-3-DUPADDR: Duplicate address [int] on [chars], sourced by [sci_notation]

Explanation An IP address for a router that uses Hot Standby Router Protocol (HSRP) is the same as the IP address for another router. This condition might be caused by a misconfiguration or a malfunctioning switch.

Recommended Action Check the configurations on all the HSRP routers, and ensure that all the 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 has occurred.

Error Message

%STANDBY-3-NOSOCKET: Unable to open socket

Explanation The system has been unable to initialize an IP connection for the Hot Standby Router Protocol (HSRP).

Recommended Action Ensure that there is at least one interface configured to run IP.

Error Message

%STANDBY-6-STATECHANGE: Standby: [dec]: [chars] state [chars]011 -> [chars]

Explanation The router state has changed.

Recommended Action No action is required.

STUN Messages

The following are serial tunnel (STUN) error messages.

Error Message

%STUN-3-BADCONN: CONN: bad connection ([dec]), peer: [chars]

Explanation An internal software error has occurred.

Error Message

%STUN-3-BADLENOP: [chars]: bad len or unknown op, op [dec], len [dec]

Explanation An internal software error has occurred.

Error Message

%STUN-3-BADMAGIC: [chars]: wrong magic, mine [hex], theirs [hex] ([dec])

Explanation An internal software error has occurred.

Error Message

%STUN-3-BADMAGICTCP: [chars]: peer [chars], wrong magic, mine [hex], theirs [hex]

Explanation An internal software error has occurred.

Error Message

%STUN-3-BADPASSIVEOPEN: passive open from [int]([dec]) -> [dec] failed

Explanation An internal software error has occurred.

Error Message

%STUN-6-CONNOPENFAIL: CONN: peer [chars] open failed, [chars] [[int]]

Explanation An attempt to connect to a remote Transmission Control Protocol (TCP) serial tunnel (STUN) peer has failed.

Recommended Action Verify that the remote peer is accessible from this router. Also verify that the remote peer is running software that is capable of supporting STUN and that the remote peer is configured correctly.

Error Message

%STUN-3-CONNILLSTATE: CONN: Peer [chars], illegal state [dec]

Explanation An internal software error has occurred.

Error Message

%STUN-4-ERR: [chars]: [chars]: [chars], op [hex], len [dec]

Explanation An internal software error has occurred.

Error Message

%STUN-2-NOBUF: Interface [chars], no buffer available to [chars]

Explanation A low memory condition has occurred at the time that a configuration command was issued. This condition seldom occurs, and this is normally a temporary condition.

Recommended Action Reconfigure the serial tunnel (STUN) group. If the memory shortages recur, 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

%STUN-3-NOINPIDB: Input idb not set

Explanation A software or hardware error has occurred.

Error Message

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

Explanation The requested operation has 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 software error has occurred because the configuration is irregular.

Recommended Action Remove and reconfigure the serial tunnel (STUN) protocol group, and record the system configuration. 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

%STUN-6-OPENED: [chars]: peer [chars] opened, [previous state [chars]]

Explanation A connection to a remote peer has been completed successfully (OPENED, PASSIVE-OPEN), or the connection to a remote peer is in the process of being opened (OPENING). This condition is normal.

Recommended Action No action is required.

Error Message

%STUN-6-OPENING: CONN: opening peer [chars], [dec]

Recommended Action No action is required.

Error Message

%STUN-6-PASSIVEOPEN: passive open [int]([dec]) -> [dec]

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. Serial tunneling (STUN) has been reconfigured or disabled as a result of user intervention. This is expected behavior.

Recommended Action No action is required.

Error Message

%STUN-4-PEERSTATE: Peer [chars], wrong state [dec] ([dec])

Explanation An internal software error has occurred.

Error Message

%STUN-6-RECONNECT: PHDR: reconnect from peer [chars]

Explanation A remote peer has reestablished 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 has occurred.

Error Message

%STUN-3-SENDPUNTTCP: [chars]: sent [chars] to ([[int]])[int]

Explanation An internal software error has occurred.

Error Message

%STUN-6-TCPFINI: peer [chars] closed [previous state [chars]]

Explanation A remote peer has closed a serial tunnel (STUN) connection with this router. This condition can be caused by normal events (for example, reconfiguring the router).

Recommended Action Examine the other router to see why it closed this connection with this router.

Error Message

%STUN-6-TCPPEERSHUT: [chars] [chars], [int]([dec])

Explanation This router has closed a serial tunnel (STUN) connection with a remote peer. This condition can be caused by normal events (for example, reconfiguring the router).

Recommended Action Examine this router to see why it closed this connection with this peer.

SUBSYS Messages

The following are software subsystems error messages.

Error Message

%SUBSYS-2-BADCLASS: Bad subsystem class ([dec]) - ignoring subsystem

Explanation A software consistency check has failed.

Error Message

%SUBSYS-2-BADSEQUENCE: Subsystem ([chars]) has cross-class sequence for ([chars])

Explanation A software or hardware error has occurred.

Error Message

%SUBSYS-2-BADVERSION: Bad subsystem version number ([dec]) - ignoring subsystem

Explanation A software consistency check has failed.

Error Message

%SUBSYS-2-MISMATCH: Kernel and subsystem version differ ([dec].[dec]) - ignoring subsystem

Explanation A software consistency check has failed.

Error Message

%SUBSYS-2-NOTFOUND: Subsystem ([chars]) needs subsystem ([chars]) to start

Explanation A software consistency check has failed.

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 has been modified.

Error Message

%SUBSYS-2-RECURSION: Maximum sequence depth exceeded ([dec]) by ([chars])

Explanation A software or hardware error has occurred.

SW56 Messages

The following are switch 56K (SW56) error messages.

Error Message

%SW56-3-ERR_MSGQ: [chars]

Explanation The system has failed to send a message to the internal software process.

Error Message

%SW56-1-INITSYS: [chars]

Explanation A low memory condition has caused the SW56 initialization to fail.

Recommended Action The amount of memory that is available in the router might be insufficient. 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 Messages

The following are switch interface error messages.

Error Message

%SWITCH-1-NOMEMORY: msgtxt_nomemory

Explanation The CPU has been unable to access the required memory to carry out its functions. This condition might be caused by a large network that requires a significant amount of memory for routing tables and to support the features that are enabled. This condition might also occur if there is a software error such as a memory leak.

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

SYS Messages

The following are operating system error messages.

Error Message

%SYS-2-ALREADYFREE: Buffer [hex] already in free pool [chars]

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

Error Message

%SYS-3-BADBLOCK: Bad block pointer [hex]

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

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

Error Message

%SYS-2-BADBUFFER: Attempt to use [chars] buffer as [chars], ptr= [hex], pool= [hex]

Explanation A hardware or software error has occurred.

Error Message

%SYS-3-BADDISP: Bad disposal code [hex] in [chars]

Explanation A buffer deletion routine has received an invalid status code. The buffer memory will be correctly returned to the free pool, but it will not be correctly counted in the per-protocol statistics.

Error Message

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

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

Error Message

%SYS-3-BADFREEPTRS: Bad [chars] pointer [hex] at [hex] ([chars] = [hex])

Explanation At the indicated litigation there is a corrupt pointer in the block header. If this messages recurs, copy it exactly as it appears and report it to your Cisco technical support representative.

Error Message

%SYS-3-BADLINKTYPE: Unexpected linktype [dec]

Explanation A software error has occurred.

Error Message

%SYS-3-BADMAGIC: Corrupt block at [hex] (magic [hex])

Explanation The free memory pool is corrupted.

Error Message

%SYS-2-BADLIST: Regular expression access check with bad list [dec]

Explanation A software error has occurred.

Error Message

%SYS-3-BADPARAM: Function [chars]: value [hex] passed in parameter [chars]

Explanation A software error has occurred.

Error Message

%SYS-2-BADPID: Bad pid [dec] for tty [t-line]

Explanation An internal software error has occurred.

Error Message

%SYS-2-BADPOOL: Attempt to use buffer with corrupt pool pointer, ptr= [hex], pool= [hex]

Explanation An internal software error has occurred.

Error Message

%SYS-2-BADPOOLMAGIC: Attempt to use pool pointer with corrupt header, pool= [hex]

Explanation An internal software error has occurred.

Error Message

%SYS-3-BADPRINT: Process has no associated tty (in [chars]).

Explanation An internal software error has occurred.

Error Message

%SYS-3-BADPROCESS: Bad process ID ([dec]) when [chars] process table

Explanation An internal software error has occurred.

Error Message

%SYS-3-BADRESID: Clock hardware returned bad residual [dec].

Explanation A software error has occurred.

Error Message

%SYS-2-BADSHARE: Bad refcount in [chars], ptr=[hex], count=[hex]

Explanation An internal software error has occurred.

Error Message

%SYS-2-BADSTACK: Process [chars] has trashed stack, old size [dec]

Explanation An internal software error has occurred.

Error Message

%SYS-3-BAD_RESET: Questionable reset of process [dec] on tty[t-line]

Explanation A process has been reset before the process was complete.

Error Message

%SYS-6-BLKINFO: [chars]blk [hex], words [int], alloc [hex], [chars], dealloc [hex], rfcnt [hex]

Explanation This is an auxiliary message that is generated by one of several memory-related messages. This message provides a formatted display of some of the information in the header of a corrupted data block. This message provides additional information only.

Error Message

%SYS-2-BLOCKHUNG: Task hung with blocking disabled, value = 0x[hex].

Explanation An internal software error has occurred.

Error Message

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

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

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

Error Message

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

Explanation An internal software error has occurred.

Error Message

%SYS-2-CFORKLEV: Process creation of [chars] failed (at level [dec]).

Explanation An internal software error has occurred.

Error Message

%SYS-2-CFORKMEM: Process creation of [chars] failed (no memory).

Explanation No memory was available to create a process.

Recommended Action If you suspect a memory leak, copy this message exactly as it appears, and report it to your Cisco technical support representative. If this condition does not appear to be caused by a memory leak and the conditions warrant, upgrade to a larger memory configuration to support the additional features.

Error Message

%SYS-2-CHUNKBADELESIZE: Chunk element size is more than 64k for [chars]

Explanation The chunk manager cannot function properly with big chunk elements.

Error Message

%SYS-2-CHUNKBADFREEMAGIC: Bad free magic number in chunk header, chunk [hex] data [hex] chunk_freemagic [hex]

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKBADMAGIC: Bad magic number in chunk header, chunk [hex] data [hex] chunkmagic [hex] chunk_freemagic [hex]

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKBADPOOLSIZE: Bad poolsize returned by the system : [int]

Explanation The system has returned an inappropriate pool size.

Recommended Action Ensure that the pool sizes are changed. 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

%SYS-2-CHUNKBADREFCOUNT: Bad chunk reference count, chunk [hex] data [hex].

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKBOUNDS: Could not find the sibling to allocate memory from. Chunk [chars], total free [dec] inuse [dec].

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKBOUNDSIB: Error noticed in the sibling of the chunk [chars], Chunk index : [dec], Chunk real max : [dec]

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKEXPANDFAIL: Could not expand chunk pool for [chars]. No memory available

Explanation There is not enough processor memory left to expand this chunk pool.

Error Message

%SYS-2-CHUNKFREE: Attempted to free nonchunk memory, chunk [hex], data [hex].

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKINCONSIS: Inconsistant counters for chunk : [chars] total free [dec]/[dec], total sibs [dec]/[dec], total alloc [dec]/[dec]

Explanation The system has returned an inappropriate pool size.

Error Message

%SYS-2-CHUNKINVALIDHDR: Invalid chunk header type [dec] for chunk [hex], data [hex]

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKNOMEMORY: Could not allocate chunks for [chars]. No memory

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKNOROOT: Root chunk need to be specified for [hex]

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKPARTIAL: Attempted to destroy partially full chunk, chunk [hex].

Explanation A software error has occurred.

Error Message

%SYS-2-CHUNKSIBLINGS: Attempted to destroy chunk with siblings, chunk [hex].

Explanation A software error has occurred.

Error Message

%SYS-5-CONFIG: Configured from [chars]

Explanation The router configuration has been changed. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-2-CONFIG_DOWNFAIL: Generated configuration not backward compatible

Explanation The router has been configured to generate nonvolatile memory using the commands of an older software version. The current configuration of the router contains a command that cannot be saved using only the older command set.

Recommended Action Allow the router to save the configuration using the command set of the current software version, or remove the commands that cannot be saved using the older command set.

Error Message

%SYS-5-CONFIG_I: Configured from [chars] by [chars]

Explanation The router configuration has been changed. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-4-CONFIG_NEWER: Configuration from version [dec].[dec] may not be correctly understood

Explanation The software has detected that the configuration saved in memory was written by a newer version of software. There might be commands saved in memory that are not implemented by the older software version.

Recommended Action Examine all the messages printed while the router was booting. For each message about an unknown command, determine if that feature is required. If any of the unknown command features is required, upgrade to a newer version of software that supports the required feature.

Error Message

%SYS-4-CONFIG_NOLOCK: The configuration could not be locked

Explanation A software error has occurred.

Error Message

%SYS-3-CONFIG_NO_PRIVATE: No space remaining to save private config

Explanation A software or hardware error has occurred.

Error Message

%SYS-5-CONFIG_NV: Nonvolatile storage configured from [chars]

Explanation The configuration has been written successfully. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-5-CONFIG_NV_I: Nonvolatile storage configured from [chars] by [chars]

Explanation The configuration has been written successfully. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-3-CONFIG_NV_DATA: Variable [chars] not set properly in the routine [chars].

Explanation A write error has occurred to a nonvolatile configuration because an internal variable was not set properly.

Error Message

%SYS-3-CONFIG_NV_ERR: Nonvolatile storage write error; configuration failed

Explanation A write error has occurred for a nonvolatile configuration.

Error Message

%SYS-3-CONFIG_SYS_ERR: System running-config write error; configuration failed

Explanation A write error has occurred for a running configuration.

Error Message

%SYS-3-CPUHOG: Task ran for [dec] msec ([dec]/[dec]), process = [chars], PC = [hex].

Explanation The indicated process has run for too long a period of time without relinquishing the processor.

Error Message

%SYS-3-CRASHINFOINITFAIL: Crashinfo subsys initialization did not add registry crashinfo_get_default_file_name.

Explanation The crash information subsystem could not add the specified registry entry and therefore cannot identify the device, to which the crash information file has been written. The contents of the crash information file are necessary for proper analysis.

Error Message

%SYS-3-DMPMEM: [hex]: [hex] [hex] [hex] [hex] [hex] [hex]

Explanation A software or hardware error has occurred.

Error Message

%SYS-4-DUAL_MESSAGE: SNMP system message request [dec] denied because of pending job

Explanation A software error has occurred.

Error Message

%SYS-3-DUP_TIMER: Same tty[t-line] in linewatch_timers, type [dec]

Explanation A tty appeared twice in a timer list where the tty should have appeared only once.

Error Message

%SYS-2-EXCEPTIONDUMP: System Crashed, Writing Core....

Explanation The system has crashed because of an exception. A core dump is being generated.

Error Message

%SYS-2-FREEBAD: Attempted to free memory at [hex], not part of buffer pool

Explanation An internal software error has occurred.

Error Message

%SYS-2-FREEFREE: Attempted to free unassigned memory at %lx, alloc %lx, dealloc %lx

Explanation An internal software error has occurred.

Error Message

%SYS-2-GETBUF: Bad getbuffer, bytes= [dec]

Explanation The software has requested a buffer that is larger in size than the largest configured buffer size, or the software has requested a negative-sized buffer.

Error Message

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

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

Error Message

%SYS-3-HARIKARI: Process [chars] top-level routine exited

Explanation An internal software error has occurred.

Error Message

%SYS-2-INLIST: Buffer in list, ptr= [hex]

Explanation An internal software error has occurred.

Error Message

%SYS-2-INPUTQ: INPUTQ set, but no IDB, ptr=[hex]

Explanation An internal software error has occurred.

Error Message

%SYS-2-INSCHED: [chars] within scheduler

Explanation An internal software error has occurred.

Error Message

%SYS-3-INTPRINT: Illegal printing attempt from interrupt level.

Explanation An internal software error has occurred.

Error Message

%SYS-2-INTSCHED: '[chars]' at level [dec]

Explanation An internal software error has occurred.

Error Message

%SYS-3-INUSEFREE: Block [hex] on free list [dec] in use

Explanation An internal software error has occurred.

Error Message

%SYS-4-INVALID_IMAGE: Running invalid image for platform!

Explanation The software image that is being run is intended for a different hardware architecture. This problem can occur on a Cisco 1003, Cisco 1004, or Cisco 1005 router. The Cisco 1003 and Cisco 1004 routers use a different image from the Cisco 1005 router.

Recommended Action Install the correct software image.

Error Message

%SYS-3-INVMEMINT: Invalid memory action ([chars]) at interrupt level

Explanation An interrupt handler has attempted to allocate or deallocate memory.

Error Message

%SYS-2-LINKED: Bad [chars] of [hex] in queue [hex]

Explanation An internal software error has occurred.

Error Message

%SYS-3-LOGGER_FLUSHED: System was paused for %TE to ensure console debugging output.

Explanation Debugging or informational messages are being generated faster than they can be displayed on the console. To ensure that the messages could be seen, the rest of the system has been paused until the console output could catch up. This condition might cause an interruption in time-critical operations (for example, maintaining an ISDN link).

Recommended Action To reduce the number of debugging or informational messages that are displayed, use conditional debugging and turn off console logging. Enter the no logging console guaranteed command, or turn off link-state messages for some other interfaces.

Error Message

%SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging output.

Explanation Debugging or informational messages are being generated faster than they can be displayed on the console. To ensure that the messages could be seen, the rest of the system has been paused until the console output catches up. This condition might cause an interruption in time-critical operations (for example, maintaining an ISDN link).

Error Message

%SYS-2-LOWMEM: Low-memory debug exception (limit=[int] free=[int])

Explanation The router is configured to crash when total available memory drops below a specified threshold. The specified threshold has been reached.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. 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

%SYS-2-MALLOCFAIL: Memory allocation of [dec] bytes failed from [hex], pool [chars], alignment [dec]

Explanation The requested memory allocation is not available from the specified memory pool. The current system configuration, network environment, or possibly a software error might have exhausted or fragmented the router memory.

Error Message

%SYS-6-MEMDUMP: [hex]: [hex] [hex] [hex] [hex]

Error Message

%SYS-3-MGDTIMER: [chars][chars], timer = [hex].

Explanation A software or hardware error has occurred.

Error Message

%SYS-3-MSGLOST: [dec] messages lost because of queue overflow

Explanation A software error has occurred.

Error Message

%SYS-6-MTRACE: [chars]: addr, pc ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC

Explanation This is an auxiliary message that is generated by one of several memory-related messages. This message provides the address of the memory block and the calling program counter for the last eight blocks allocated and for the last eight blocks freed. This message provides additional information only.

Error Message

%SYS-2-NOBLOCK: [chars] with blocking disabled.

Explanation An internal software error has occurred.

Error Message

%SYS-6-NOBRIDGE: Bridging software not present

Explanation An attempt has been made to use bridging software when the system is not configured to be used as a bridge.

Recommended Action Configure the bridging software.

Error Message

%SYS-3-NOELEMENT: [chars]:Ran out of buffer elements for enqueue

Explanation The process has run out of buffer elements and is unable to enqueue data.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show buffers command to gather data to 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 buffers command output, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message

%SYS-2-NOMEMFRG: Memory fragmentation check debug exception (fragment size [int])

Explanation The router is configured to crash when the largest available contiguous memory block drops below a specified threshold. The specified threshold has been reached.

Error Message

%SYS-2-NOMEMORY: No memory available for [chars] [dec]

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

Error Message

%SYS-2-NOPROCESS: No such process [dec]

Explanation An internal software error has occurred.

Error Message

%SYS-2-NOTDEAD: Killing process [chars], pid [dec] again

Explanation An internal software error has occurred.

Error Message

%SYS-2-NOTQ: [chars] didn't find [hex] in queue [hex]

Explanation An internal software error has occurred.

Error Message

%SYS-2-NULLCHUNK: Memory requested from Null Chunk

Explanation The chunk manager cannot allocate memory from null chunks.

Error Message

%SYS-3-NULLIDB: Null IDB in [chars]

Explanation An internal software error has occurred.

Error Message

%SYS-4-NV_CHKSUM: An nvram checksum is already in progress

Explanation The user has attempted to perform multiple NVRAM operations at the same time. If the interrupt is not set to 011, the system will attempt the NVRAM operation again.

Recommended Action No action is required unless the command fails. If the command fails, reset the interrupt to 011.

Error Message

%SYS-4-NV_CHKSUM_INTR: An nvram checksum is already in progress; the interrupt cannot be serviced

Explanation An interrupt service routine has attempted to perform a checksum on the NVRAM contents. The interrupt service found that the resource was in use.

Error Message

%SYS-4-NV_NOLOCK: Failed to acquire an nvram lock

Explanation An interrupt service routine has attempted to acquire a semaphore lock 011. The attempted operation has failed.

Error Message

%SYS-3-NZREFCNT: Block [hex] on free list [dec] with refcount [dec]

Explanation A block of memory that is in the free pool is in use by a process. The message will indicate the number of processes using the memory block.

Error Message

%SYS-5-OUTSETUP: Configuration file [chars] accepted, aborting setup

Explanation The system has accepted a configuration over the network. The setup session will be aborted. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-3-OVERRUN: Block overrun at [hex] (red zone [hex])

Explanation An internal software error has occurred.

Error Message

%SYS-1-OVERTEMP: System detected OVERTEMPERATURE condition. Please resolve cooling problem immediately!

Explanation The environmental monitor has detected a high-temperature condition.

Recommended Action Make sure that the room temperature is not too high and that air flow to the card is not blocked. If this condition 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

%SYS-3-OVFPRINT: Overflow in [chars], chars [dec], buffer size [dec]

Explanation A software error has occurred.

Error Message

%SYS-6-PROCINFO: Process [chars] just finished executing

Explanation This message is an auxiliary message to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. This message identifies the process or process fragment that was executing when the 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. Include the information gathered with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages.

Error Message

%SYS-2-QCOUNT: Bad [chars] [hex] count [dec]

Explanation An internal software error has occurred.

Error Message

%SYS-6-READ_BOOTFILE_FAIL: [chars] [chars].

Explanation A configured boot system command has failed.

Recommended Action If the system image was sucessfully loaded, no action is required. If the system image did not load as it was configured, 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

%SYS-4-REGEXP: [chars].

Explanation An internal software error has occurred.

Error Message

%SYS-5-RELOAD: Reload requested

Explanation A request to reload or restart the system has been made. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-4-RELOAD_ATTEMPT: Attempt via SNMP failed, system shutdown not configured

Explanation An attempt to reload the router has failed because Simple Network Management Protocol (SNMP) reloads are not currently configured on the router. SNMP cannot be used to reload the router unless this functionality has been previously configured. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-5-RESTART: System restarted --[chars]

Explanation A request to reload or restart the system has been made. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-2-SELFLINKED: Buffer [hex] linked to itself in free pool [chars]

Explanation An internal software error has occurred.

Error Message

%SYS-2-SHARED: Attempt to return buffer with sharecount [dec], ptr= [hex]

Explanation An internal software error has occurred.

Error Message

%SYS-2-SNMP0IDX: Attempt to [chars] snmpidb with if_index of 0

Explanation A software error has occurred.

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

Error Message

%SYS-4-SNMP_HOSTCONFIGSET: SNMP hostConfigSet request. Loading configuration from [int]

Explanation Simple Network Management Protocol (SNMP) is reading the host configuration from a network host. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-4-SNMP_NETCONFIGSET: SNMP netConfigSet request. Loading configuration from [int].

Explanation Simple Network Management Protocol (SNMP) is reading the network configuration from a network host. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-4-SNMP_WRITENET: SNMP WriteNet request. Writing current configuration to [int]

Explanation Simple Network Management Protocol (SNMP) is writing the current configuration to a network host. This is an informational message only.

Recommended Action No action is required.

Error Message

%SYS-3-SOCKUNKN: Unknown socket protocol [dec]

Explanation An internal software error has occurred.

Error Message

%SYS-2-SPEC: Trying to set unknown special character [dec] to [dec]

Explanation An internal software error has occurred.

Error Message

%SYS-6-STACKLOW: Stack for [chars] [chars] running low, [dec]/[dec]

Explanation An internal software error has occurred.

Error Message

%SYS-5-TABLEERR: [chars] table [chars] damaged: [chars].

Explanation An internal table entry has become corrupt.

Error Message

%SYS-6-TESTINFO: Scheduler test [hex] (for [chars]) just executed

Explanation This is an auxiliary message to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. This message identifies the process or process fragment that was executing when the 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. Include the information that was gathered with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages.

Error Message

%SYS-3-TIMERHOG: Timer callback ran long, PC = [hex].

Explanation The indicated callback routine has run for too long of a period of time without relinquishing the processor.

Error Message

%SYS-3-TIMERNEG: Cannot start timer ([hex]) with negative offset ([dec]).

Explanation An internal software error has occurred.

Error Message

%SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = [chars].

Explanation The indicated process has run for too long a period of time without relinquishing the processor. The system has shut down the indicated process.

Error Message

%SYS-2-WRONGPOOL: Buffer [hex] found in pool [hex], should be in pool [hex]

Explanation A software error has occurred.

Error Message

%SYS-3-WRONGFREELIST: Block [hex], size [dec], on wrong free list ([dec], [dec])

Explanation A free buffer has been placed in a list of free buffers that was not the correct list for the indicated buffer.

SYSCTLR Messages

The following are system controller subsystem error messages.

Error Message

%SYSCTLR-5-AUTH_FAILED: MD5 digest does not match, SDP packet received from, [int] rejected

Explanation A Shelf Discovery Protocol (SDP) hello packet has been received from a shelf that is not trusted.

Recommended Action Either specify the correct SDP password or specify the correct destination on the shelf from which this message was received.

Error Message

%SYSCTLR-3-BAD_CALL: Invalid parameter/mangled pointer routine: [chars], file: [chars], line: [dec]

Explanation An internal software error has occurred.

Error Message

%SYSCTLR-6-BAD_IP_ADDR: Found Shelf [dec] with an invalid IP address [chars]

Explanation The system controller has found a shelf that has an invalid IP address.

Recommended Action Configure a valid IP address for the shelf that has an invalid IP address.

Error Message

%SYSCTLR-3-DISCOVER_SOCKET_BIND: socket bind failed

Explanation An internal software error has occurred.

Error Message

%SYSCTLR-3-DISCOVER_SOCKET_OPEN: socket open failed

Explanation An internal software error has occurred.

Error Message

%SYSCTLR-3-DUPLICATE_SHELF: SDP packet with duplicate shelf-id [dec] received from [chars],already discovered elf located at [chars]

Explanation A shelf has been configured to use a shelf ID that is already in use by another shelf. Two shelves cannot be configured to use the same shelf ID.

Recommended Action Change the shelf ID for one of the two shelves.

Error Message

%SYSCTLR-4-HMON_POLL: Local time [chars] [chars] on shelfid [dec] is not active, resetting monitor_type [dec]

Explanation Health monitor setup commands poll the system for information. If this message is displayed every ten minutes, then the health monitor has been unable to set the corresponding entry on the shelf.

Error Message

%SYSCTLR-3-HMON_SETUP_FAILED: Health monitoring setup failed on shelf_id [dec]

Explanation The health monitor has failed to set up the monitoring command on a particular shelf.

Error Message

%SYSCTLR-3-INVALID_SDP_VERSION: SDP packet received by system controller contained invalid version number.

Explanation The system has received a Shelf Discovery Protocol (SDP) packet that contains an invalid version number.

Recommended Action Ensure that the shelf is running a compatible version of SDP. 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

%SYSCTLR-4-SDP_TIMEOUT: Hello packet from shelf [dec] not received, shelf removed.

Explanation No Shelf Discovery Protocol (SDP) hello packets have been received from a particular router shelf. That shelf could be down or misconfigured.

Recommended Action Verify the status of the router and the router configuration. 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

%SYSCTLR-3-SDP_TIMER_ERROR: No context associated with the expired SDP timer

Explanation An internal software error has occurred.

Error Message

%SYSCTLR-6-SHELF_ADD: Shelf [dec] discovered located at address [int]

Explanation Shelf Discovery Protocol (SDP) on a system controller has detected a particular shelf.

Error Message

%SYSCTLR-4-SHELF_CONF_CHANGED: Configuration for the shelf [dec] located [int] changed

Explanation Shelf Discovery Protocol (SDP) protocol on a system controller has detected that a particular shelf configuration has changed.

Error Message

%SYSCTLR-3-SHELF_MSGFAIL: Unable to send message [dec] to process with pid [dec].

Explanation The system is unable to send a message to a specific process because the performance collector process has terminated.

Error Message

%SYSCTLR-3-SHELF_PROTO: Shelf id protocol error

Explanation An internal software error has occurred.

Error Message

%SYSCTLR-4-SHELF_RELOAD: Shelf [dec] located [int] reloaded

Explanation A system controller that is using Shelf Discovery Protocol (SDP) has detected that a particular shelf has reloaded.

Error Message

%SYSCTLR-4-SHELF_REMOVE: Shelf [dec] located at address [int] removed.

Explanation A system controller that is using Shelf Discovery Protocol (SDP) has not received hello packets from a particular shelf.

Error Message

%SYSCTLR-6-SHELF_RESTORED: Communication with shelf [dec] located at address [int]

Explanation Shelf Discovery Protocol (SDP) on a system controller has detected a particular shelf.

Recommended Action No action is required.

Error Message

%SYSCTLR-4-SNMP_NOT_RESPONDING: Shelf [dec] not reachable via SNMP

Explanation The shelf that is indicated in this error message is not responding to Simple Network Management Protocol (SNMP) requests.

Recommended Action Verify that the SNMP configuration for the shelf that is indicated is correct. Also verify that the correct community string has been specified in the configuration command system-controller community on the system controller.

SYSLOG_SERVER Messages

The following are syslog-server file system routines error messages.

Error Message

%SYSLOG_SERVER-3-CREATE_ERR: Failed to create a Syslog file.

Explanation The system has failed to create a syslog file. This condition occurs if there is not a PCMCIA disk in slot0 of the system controller.

Recommended Action Verify that the PCMCIA disk is properly installed.

Error Message

%SYSLOG_SERVER-4-DUP_FILE: Syslog file [[chars]] exists.

Explanation An attempt has been made to use a directory name that already exists on the PCMCIA disk.

Recommended Action Verify that the name that was supplied already exists on the PCMCIA disk and enter a new directory name.

Error Message

%SYSLOG_SERVER-4-FILE_CORRUPTED: syslog records do not appear to be timestamped.

Explanation The system has been unable to detect a time stamp on a system log. This error might be the result of not using the service timestamp command.

Recommended Action Use the service timestamps log datetime command on your router. This command will tell the system to time-stamp both debugging and logging messages. To use this function, the date and time must be set.

Error Message

%SYSLOG_SERVER-3-ILLEGAL_FS: Illegal file system [chars].

Explanation The system has detected an illegal file system.

Error Message

%SYSLOG_SERVER-3-MFS_MAX: Failed to add Syslog file [chars], maximum Syslog files [dec].

Explanation The system was unable to add a syslog file because the system has already exceeded the maximum number of syslog files allowed.

Error Message

%SYSLOG_SERVER-4-NO_CONFIG_CHANGE: No configuration change.

Explanation No configuration change to the syslog server has occurred.

Error Message

%SYSLOG_SERVER-4-NO_MEM: No memory left.

Explanation No more memory is available for the system controller.

Recommended Action Provide the system controller with more memory. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message

%SYSLOG_SERVER-4-NO_MOBIUS: No syslog file.

Explanation There is no syslog file.

Error Message

%SYSLOG_SERVER-3-OPEN_FILE_ERR: Failed to open [chars].[dec] syslog file.

Explanation The system has failed to open a syslog file. This condition might have occurred because one or more subfiles have been deleted or because there is no PCMCIA disk in slot0. If one or more subfiles are missing, the subfiles will be automatically restored when the current file reaches its capacity and is archived.

Recommended Action Verify that there is a PCMCIA disk in slot0 .

Error Message

%SYSLOG_SERVER-3-PARSING_ERR: Parsing file error.

Explanation The router is not configured to time stamp all of the log messages.

Recommended Action Configure your router to time stamp the log messages by entering the service timestamps command.

Error Message

%SYSLOG_SERVER-3-READ_ERR: Failed to read a file.

Explanation The system has failed to read a file.

Error Message

%SYSLOG_SERVER-3-UNKNOWN_NAME: Unknown command or device name, or unable to find device address.

Explanation The system could not find a device address, or an unknown command or device name has been used.

Error Message

%SYSLOG_SERVER-3-WRITE_ERR: Failed to write a syslog file.

Explanation The system has failed to write a syslog file.

SYSMGT_RPC Messages

The following are system management error messages.

Error Message

%SYSMGT_RPC-3-IPC_ERROR: SYSMGT RPC - IPC [chars] [chars] failed ([chars])

Explanation A system management remote-procedure call (RPC) operation failure has occurred. The request for information from the Channel Interface Processor (CIP) card will not be processed.

Error Message

%SYSMGT_RPC-3-NETMGT_EVENT: SYSMGT RPC - NETMGT Event: [chars] ([dec])

Explanation A system management remote-procedure call (RPC) network management event error has occurred.

Error Message

%SYSMGT_RPC-3-RPC_ERROR: SYSMGT RPC - RPC [chars] [chars] failed ([chars] [dec])

Explanation A system management remote-procedure call (RPC) operation failure has occurred. The request for information from the Channel Interface Processor (CIP) card will not be processed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that will 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.

TAC Messages

The following are TACACS protocol error messages.

Error Message

%TAC-4-NOTIMEOUT: Warning: This command has been deprecated in favor of the line-command imeout login response

Explanation This command has been phased out and should no longer be used.

Recommended Action You can use the timeout login response command. The timeout login response command now provides the required functionality.

Error Message

%TAC-3-PICKCTX: No pick-context

Explanation The context for picking the next server has disappeared.

Error Message

%TAC-6-SENDTMO: Send type [dec] to [int] timed out

Explanation A background TACACS notification (enabled with the command tacacs notify) has not been acknowledged by the TACACS server processor within the 5-minute timeout period. The information contained in that notification was lost. This loss of information might interfere with accounting or auditing on the server. This condition occurs when the TACACS server is misconfigured, has crashed, or has become unreachable through the network.

Recommended Action Ensure that the TACACS server is correctly configured. Also verify that the network attached to the TACACS server is not causing this condition to occur.

Error Message

%TAC-4-SERVREF: Warning: Server [int]:[dec] is still referenced by server group.

Explanation The server that is being removed is still being referenced by a server group

Recommended Action Remove the server from the server group configuration as soon as possible.

Error Message

%TAC-4-UNEXREP: Reply for non-existent request, [dec] on queue

Explanation The TACACS server has received an unexpected message. This condition might occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. This condition might also be caused by an internal software error.

Error Message

%TAC-3-XTACACL: [chars]: accesslist 0x[hex] out of range for [chars]

Explanation The TACACS facility has created a message that contains an invalid access list (out of bounds).

TAGCON Messages

The following are tag distribution and control error messages.

Error Message

%TAGCON-4-ADDRQ: Can't alloc work item for [int]

Explanation When a new IP address for a tag distribution protocol (TDP) peer is added to the system, it might be necessary to update the Tag Forwarding Information Base (TFIB) for any routes where the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of the address process. This message is generated when an attempt to queue work for the address process has failed. The system will regularly attempt to queue the necessary work item. This is an informational message.

Error Message

%TAGCON-4-ADDR_PROC: Can't create tagcon addr proc

Explanation When a new IP address for a tag distribution protocol (TDP) peer is learned, it might be necessary to update the Tag Forwarding Information Base (TFIB) for any routes where the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of the address process. This message is generated when an attempt to create the address process fails. This is an informational message. As long as the system requires the process, the system will regularly attempt to create the process.

Error Message

%TAGCON-3-ALLOC: Cannot alloc [chars]

Explanation An attempt to allocate a tag-switching data structure has 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

%TAGCON-3-BUFFERBIND: unexpected error [dec]; peer [chars]; [chars]

Explanation An unexpected failure has occurred during the building of a tag distribution protocol (TDP) protocol information element (PIE) for transmission to a TDP peer. This condition occurred while the system was attempting to add a tag binding or an address to the PIE.

Error Message

%TAGCON-3-CONSISTENCY: [chars]

Explanation An action attempted by the tag control process has encountered an unexpected condition.

Error Message

%TAGCON-3-DEADADJ: [int]/[int], [chars]

Explanation A problem has occurred in cleanup following termination of a tag distribution protocol (TDP) session.

Error Message

%TAGCON-3-DEFCASE_BINDING_PIE: Unexpected blist_type ([dec]) for [chars] PIE from peer [chars]

Explanation A tag distribution protocol (TDP) protocol information element (PIE) that was received from a TDP peer contained an unexpected binding list type. The PIE will be be ignored.

Error Message

%TAGCON-3-DIRADJTREE: [int]/[int]; [chars]

Explanation An operation on the tag distribution protocol (TDP) directed adjacency data structure failed.

Error Message

%TAGCON-3-EVENTQ: Can't alloc work item for [chars]

Explanation When a process such as the tag distribution protocol (TDP) process must request that the tag distribution and control process take some action, a work item is queued for the tag distribution and control process. This message is generated when an attempt to queue work for the tag distribution and control process fails. The failure can occur if the system is unable to allocate memory to hold the work request or if the process has stopped processing requests on its work queue.

Error Message

%TAGCON-3-INIT: process cannot initialize

Explanation The tag distribution and control processes have failed to initialize. The condition has most likely occurred because of a low memory condition.

Error Message

%TAGCON-4-INIT_TAG_ALLOC: Failure to initialize tag allocation pool [dec]

Explanation The system has been unable to initialize the data structure that is used to support the allocation of tags for tag switching, and the system proceeds by ignoring the event. Because the system cannot allocate tags from the tag pool, the system will not advertise the tags to peers. Because the system advertises no tags, the system will not be able to receive any tagged packets or forward any tagged packets that are received.

Error Message

%TAGCON-3-LATREVNUMWRAP: Tag Local Address Table revision number wrapped

Explanation The revision number that is used to manage the advertisement of interface addresses to tag distribution protocol (TDP) peers has overflowed. This condition will cause faulty advertisements of interface addresses to TDP peers and faulty tag switching on those peers.

Recommended Action Reboot the system to correct the faulty interface address advertisements. 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

%TAGCON-3-LCLTAG_ALLOC: Cannot allocate local tag

Explanation An attempt to allocate a local (incoming) tag has failed. This condition should occur only when the system has allocated all available local tags.

Recommended Action The number of tags available for allocation can be changed by entering the tag-switching tag-range configuration command. Consult with your Cisco technical service representative to determine whether you should use this command to increase the number of available tags.

Error Message

%TAGCON-3-NOTIMPL: peer [chars]; [chars] not implemented

Explanation A tag distribution protocol (TDP) peer has requested an action that is not currently implemented by the tag distribution and control subsystem. The request will be ignored.

Error Message

%TAGCON-3-PEERSM: TDP peer [int]([chars]): [chars]

Explanation An operation involving the state machine for a tag distribution protocol (TDP) peer has failed.

Error Message

%TAGCON-3-PROCESS: process not created

Explanation An attempt to create the tag distribution and control process has failed. This condition is most likely caused by 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

%TAGCON-3-RADIXTREE: TIB walk failed ([chars])

Explanation Some Tag Information Base (TIB) maintenance operations involve a complete scan (walk) of the TIB radix tree data structure. This message is generated when a TIB walk encounters an unexpected failure.

Error Message

%TAGCON-5-SEND: cannot queue TDP [chars] pie for [int]([chars])

Explanation An attempt to queue a tag distribution protocol (TDP) protocol information element (PIE) for transmission to a TDP peer has failed. This failure should occur only when the TDP session with the peer no longer exists. The system should recover from this condition by discarding the TDP session and establishing a new session.

Error Message

%TAGCON-3-SM: Unnexpected event; state=[chars], event=[chars]

Explanation An operation on the state machine for the tag distribution and control process has failed.

Error Message

%TAGCON-3-TDPID: peer [chars], TDP Id/Addr mapping problem ([chars])

Explanation The tag distribution and control process maintains a data structure used to convert between the tag distribution protocol (TDP) identifier for a TDP peer and the IP addresses of that peer. This message is generated when an internal inconsistency is discovered in that data structure.

Recommended Action Disable dynamic tag switching at the chassis level by entering the no_tag-switching ip command. Wait 15 to 20 seconds, and enable dynamic tag switching by entering the tag-switching ip command. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message

%TAGCON-3-TDPID_ADDR_TBL: [chars] sort bad; item [dec]

TBRIDGE Messages

The following are transparent bridging error messages.

Error Message

%TBRIDGE-4-BADXMAC: XMACACCESS: Invalid extended access list [dec]

Explanation The specified extended access list contains an error, or the specified extended access list does not exist. This condition is caused by a configuration error.

Recommended Action Verify that the configuration is correct.

Error Message

%TBRIDGE-4-BAD_ENCAP: Unexpected encapsulation received on [chars] [chars]

Explanation The transparent bridging driver has received a packet with encapsulation that is not recognized. The packet has been discarded. This condition might indicate that a network media error has occurred or a protocol that is not supported by this version of the Cisco IOS software is being used.

Recommended Action If the dropped packets are data from a valid protocol, upgrade to a newer version of the Cisco IOS software that supports the protocol.

Error Message

%TBRIDGE-4-GIANT: Giant received on [chars], [dec] exceeds [dec] DA [sci_notation] SA [sci_notation] [0x[hex]]

Explanation A packet has been received that exceeds the expected maximum transmission unit (MTU) length for the receiving interface. The first four bytes of the packet that follow the source address are also provided to help diagnosis the problem.

Recommended Action Use the address and packet information to trace the source of these packets. Configure the MTU at the source to conform to the standard size for the given media.

Error Message

%TBRIDGE-4-INVALIDMEDIA: [chars] received on [chars] - invalid media for transparent bridging

Explanation An attempt has been made to configure transparent bridging on an interface that does not support it.

Recommended Action Remove transparent bridging from the configuration on the specified interface.

Error Message

%TBRIDGE-4-NOVCDROP: Destination VC unknown for packet

Explanation A transparent bridged packet that is destined for an ATM interface cannot be completely addressed.

Recommended Action Clear the bridge table to force the system to relearn all the addresses.

Error Message

%TBRIDGE-4-NOVCFLOOD: No VC's configured for bridging on [chars]

Explanation An ATM interface was configured for transparent bridging without specifying the associated virtual circuits (VCs).

Recommended Action Configure the required VCs on the specified interface.

Error Message

%TBRIDGE-4-SMF_ACTION: invalid action found for [sci_notation] on [chars] - [hex]

Explanation A software or hardware error has occurred.

Error Message

%TBRIDGE-4-VCPAKDROP: Subscriber SA [sci_notation] moved or loop between circuits [dec] and [dec]

Explanation A subscriber bridged packet has been dropped because of a potential circuit loop or a roaming host at the subscriber end of the network.

Recommended Action Clear the bridge table. If this error recurs, the error is not caused by a roaming host. This condition might indicate a loop between virtual circuits (VCs) at the subscriber end of the network. Take looping virtual circuits out of service or shut down the software interface they are on while the subscriber is contacted and asked to remove the loop condition at the subscriber end of network.

TCATM Messages

The following are ATM TAG control error messages.

Error Message

%TCATM-3-BADINSERT: [int][inet] x[hex] to 0x[hex]

Explanation An attempt has been made to insert an item on a list and an internal inconsistency has been detected.

Error Message

%TCATM-3-BADSTATE: [int][inet] [chars] [chars]->[chars]

Explanation ATM TAG control uses a table-driven state machine to keep track of and transition Tagged Virtual Circuits (TVCs) through various states. A state transition occurs when a TVC receives one of many possible events. When this error occurred, the TVC had received an event that it did not expect while in this state.

Recommended Action The system can continue, but the system might lose the TVC that generated this error. 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

%TCATM-4-HOPCOUNT_EQUALLED: Maxhop=[dec] hopcount=[dec] for [int][inet] on [chars]

Explanation A loop has been discovered in the network.

Recommended Action Check the configuration and network path for the relevant prefix.

Error Message

%TCATM-4-INTERFACE: Request bind interface [chars] same as output interface for [int][inet]

Explanation The incoming interface of a request bind protocol information element (PIE) is the same interface as the next hop for the prefix. This condition might be caused by a transient routing loop that has occurred during a routing protocol convergence or a permanent routing loop that was caused by a configuration error. As a result of this condition, the Tagged Virtual Circuit (TVC) requests to the upstream neighbor will remain in a BIND_WAIT state until this condition clears up.

Recommended Action If this condition recurs, verify that the configuration and network paths for the relevant prefix are correct.

Error Message

%TCATM-4-MALFORMED_PIE: Interface [chars] malformed TDP PIE

Explanation ATM tag control has received a malformed protocol information element (PIE) from tag distribution protocol (TDP). This condition does not affect system operation.

Error Message

%TCATM-4-NEWVCINRANGE: VC created on [chars] in range reserved for TC-ATM (VPIs [int]-[int], VCIs [int]-[int])

Explanation A virtual circuit (VC) has been created with a virtual path identifier/virtual channel identifier (VPI/VCI) that is in the range configured for use by the ATM tag control. The ATM tag control will not be able to create a Tagged Virtual Circuit (TVC) with that VPI/VCI, and packets that are going to and coming from the corresponding address prefix will be dropped. The new VC might be on a primary interface or a subinterface.

Recommended Action Reconfigure the new VC so that it does not fall into the range reserved for ATM tag control, or reconfigure the reserved VPI/VCI range in the interface configuration to exclude the VPI/VCI of the new VC. Use the tag-switching atm vpi command and the tag-switching atm vci-range command to reconfigure the interface.

Error Message

%TCATM-4-NOTAGIP: Tag switching disabled on [chars]

Explanation Tag switching is not enabled on the specified interface. This condition will cause tag virtual channel identifier (VCI) requests and advertising to be rejected. This condition might also cause VCI requests that are at the upstream device to remain in a BIND_WAIT state until tag switching is reenabled on this interface.

Recommended Action Enable tag switching.

Error Message

%TCATM-3-NOTRUNNING: ATM-TAGCONTROL is not running

Explanation An attempt to request or to create a binding has failed while the ATM tag control system is not initialized. This condition is most likely caused by an incorrect configuration or a low memory condition.

Recommended Action If this condition is a result of an incorrect configuration, correct the configuration. If this condition is the result of a low memory condition, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message

%TCATM-3-OFFLIST: [int][inet] 0x[hex] not on list 0x[hex]

Explanation An internal inconsistency has been detected during an attempt to remove an item from a list that was not on the list.

Error Message

%TCATM-4-OLDVCINRANGE: VC exists on [chars] in range reserved for TC-ATM (VPIs [int]-[int], VCIs [int]-[int])

Explanation A virtual circuit (VC) already exists with a virtual path identifier/virtual channel identifier (VPI/VCI) in the range configured for use by the ATM tag control. The ATM tag control will be unable to create a Tagged Virtual Circuit with that VPI/VCI, and packets to or from the corresponding address prefix will be dropped. The existing VC might be on either the primary interface or a subinterface. This message is issued only once, even if there are multiple existing VCs in the reserved range.

Recommended Action Reconfigure the existing VCs so that they do not fall into the range reserved for ATM tag control, or use the tag-switching atm vpi and tag-switching atm vci-range interface configuration commands to reconfigure the reserved VPI/VCI range so that it excludes the VPI/VCIs of existing VCs.

Message

%TCATM-3-ONLIST: [int][inet] 0x[hex] on list 0x[hex]

Explanation An internal inconsistency has been detected during an attempt to remove an item from a list that was not on the list.

Error Message

%TCATM-3-PROCESS: process not created

Explanation An attempt to create the ATM tag control process has failed. This condition might be caused by low memory.

Recommended Action Reduce other system activity if possible. 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

%TCATM-4-RESOURCE_LIMIT: VC resource exhausted on [chars]

Explanation The system has run out of virtual circuit (VC) resources for the specified interface. Tagged Virtual Circuits (TVCs) for some destination prefixes will not be established, and the result might be degraded network performance.

Recommended Action Check to make sure that the negotiated virtual path identifier (VPI) range is sufficient to permit usage of the maximum number of TVCs available on the hardware. If the negotiated VPI range is sufficient, then reconfigure the network so that fewer TVCs are required on this interface.

Error Message

%TCATM-3-UNEXPECTEDBIND: Interface [chars] received unexpected bind for [int][inet]

Explanation An unexpected Berkeley Internet Name Domain (BIND) has been received for a prefix. A memory resource allocation failure has prevented this peer from sending a message to the neighbor to release the bind. The system will continue to function normally, but the downstream neighbor might be holding a binding, for which there is no matching virtual channel identifier (VCI) at this end.

Error Message

%TCATM-4-XCONNECT_FAILED: [int][inet] [chars] [chars] [chars]

Explanation The system has rUn out of resources to set up a switch cross-connect for the specified interfaces. Tagged Virtual Circuits (TVCs) for some destination prefixes will not be established. This condition might cause network performance to degrade.

Recommended Action Ensure that the negotiated virtual path identifier (VPI) range will allow the system to use the maximum number of available TVCs. If the negotiated VPI range will support the maximum number of available TVCs, reconfigure the network so that fewer TVCs are required for this interface.

Table of Contents