-
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
SYS Error Messages
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.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADBLOCK : Bad block pointer [hex]
Explanation A block of memory at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-BADBUFFER : Attempt to use [chars] buffer as [chars], ptr= [hex], pool= [hex]
Explanation A hardware or software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADDISP : Bad disposal code [hex] in [chars]
Explanation An invalid status code has been passed to a buffer-deletion routine. The buffer will be correctly returned to the free pool, but will not be correctly counted in the per-protocol statistics.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADFREEMAGIC : Corrupt free block at [hex] (magic [hex])
Explanation A block of memory at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADFREEPTRS : Bad [chars] pointer [hex] at [hex] ([chars] = [hex])
Explanation A pointer in the block header at the indicated location is corrupt.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADLINKTYPE : Unexpected linktype [dec]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BADLIST : Regular expression access check with bad list [dec]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADMAGIC : Corrupt block at [hex] (magic [hex])
Explanation The free memory pool is corrupt.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADPARAM : Function [chars]: value [hex] passed in parameter [chars]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BADPID : Bad pid [dec] for tty [t-line]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-BADPOOL : Attempt to use buffer with corrupt pool pointer, ptr= [hex], pool= [hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-BADPOOLMAGIC : Attempt to use pool pointer with corrupt header, pool= [hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-BADPRINT : Process has no associated tty (in [chars])
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-BADPROCESS : Bad process ID ([dec]) when [chars] process table
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%SYS-3-BADRESID : Clock hardware returned bad residual [dec]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-BADSHARE : Bad refcount in [chars], ptr=[hex], count=[hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-BADSTACK : Process [chars] has trashed stack, old size [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-6-BLKINFO : [chars]blk [hex], words [int], alloc [hex], [chars], dealloc [hex], rfcnt [hex]
Explanation This is an auxiliary message to several memory-related messages. It provides a formatted display of some of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Error Message%SYS-2-BLOCKHUNG : Task hung with blocking disabled, value = 0x[hex]
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%SYS-6-BOOT_MESSAGES : Messages above this line are from the boot loader
Explanation At least one informational or error message was printed by the boot loader.
Recommended Action If the system image was loaded, no action is recommended. If the system image did not load as configured, send a log file and configuration information to your technical support representative.
Error Message%SYS-2-CFORKBADFUNCT : Can't create process with start address = [hex]
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%SYS-2-CFORKLEV : Process creation of [chars] failed (at level [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%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 technical support representative. If a memory leak does not appear to be the problem, ensure that more memory is available to support the additional features.
Error Message%SYS-2-CHUNKBADFREEMAGIC : Bad free magic number in chunk header, chunk [hex] data [hex] chunk_freemagic [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKBADMAGIC : Bad magic number in chunk header, chunk [hex] data [hex] chunkmagic [hex] chunk_freemagic [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKBADREFCOUNT : Bad chunk reference count, chunk [hex] data [hex].
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKBOUNDS : Attempted to exceed free list chunk bounds, chunk [hex], data [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKFREE : Attempted to free nonchunk memory, chunk [hex], data [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKINVALIDHDR : Invalid chunk header type [dec] for chunk [hex], data [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKNOMEMORY : Could not allocate chunks for [chars]. No memory
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKNOROOT : Root chunk need to be specified for [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKPARTIAL : Attempted to destroy partially full chunk, chunk [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-CHUNKSIBLINGS : Attempted to destroy chunk with siblings, chunk [hex]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-5-CONFIG : Configured from [chars] by [chars]
Explanation The router's configuration was changed.
Recommended Action This is a notification message only. 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 release. 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 release, 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's configuration was changed.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-4-CONFIG_NEWER : Configuration from version [dec].[dec] may not be correctly understood
Explanation The software detected that the configuration saved in memory was written by a newer software release. There might be commands saved in memory that are not implemented by the older software release.
Recommended Action Examine all the messages printed while the router was booting. For each message about an unknown command, determine whether that feature is required. If so, upgrade to a newer software release that supports that feature.
Error Message%SYS-4-CONFIG_NOLOCK : The configuration could not be locked
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-CONFIG_NO_PRIVATE : No space remaining to save private config
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%SYS-5-CONFIG_NV : Nonvolatile storage configured from [chars] by [chars]
Explanation The configuration was written successfully.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-3-CONFIG_NV_DATA : Variable [chars] not set properly in the routine [chars].
Explanation The write of the nonvolatile configuration failed because an internal variable was not set properly.
Recommended Action If this messages occurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-CONFIG_NV_ERR : Nonvolatile storage write error; configuration failed
Explanation The write of the nonvolatile configuration failed.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-CPUHOG : Task ran for [dec] msec ([dec]/[dec]), process = [chars], PC = [hex]
Explanation The indicated process ran too long without relinquishing the processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-3-DMPMEM : [hex]: [hex] [hex] [hex] [hex] [hex] [hex]
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%SYS-4-DUAL_MESSAGE : SNMP system message request [dec] denied because of pending job
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-2-FREEBAD : Attempted to free memory at [hex], not part of buffer pool
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-FREEFREE : Attempted to free unassigned memory at %lx, alloc %lx, dealloc %lx
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-GETBUF : Bad getbuffer, bytes= [dec]
Explanation The software requested a buffer that is larger than the largest configured buffer size, or it requested a negative-sized buffer.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
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's memory.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-HARIKARI : Process [chars] top-level routine exited
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-INLIST : Buffer in list, ptr= [hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-INPUTQ : INPUTQ set, but no IDB, ptr=[hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-INSCHED : [chars] within scheduler
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%SYS-3-INTPRINT : Illegal printing attempt from interrupt level
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%SYS-2-INTSCHED : '[chars]' at level [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%SYS-3-INUSEFREE : Block [hex] on free list [dec] in use
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-4-INVALID_IMAGE : Running invalid image for platform!
Explanation The software image being run is for a different hardware architecture. This problem can occur on a Cisco 1003, Cisco 1004, or Cisco 1005. The Cisco 1003 and Cisco 1004 use a different image from the Cisco 1005.
Recommended Action Install the correct software image.
Error Message%SYS-3-INVMEMINT : Invalid memory action ([chars]) at interrupt level
Explanation This message indicates that a memory allocation or deallocation was attempted from an interrupt handler.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-LINKED : Bad [chars] of [hex] in queue [hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
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. That threshold has been reached.
Recommended Action It might be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
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's memory.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-6-MEMDUMP : [hex]: [hex] [hex] [hex] [hex]
Explanation This is an auxiliary message to several memory-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of the previously printed error message.
Error Message%SYS-3-MGDTIMER : [chars][chars], timer = [hex]
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%SYS-3-MSGLOST : [dec] messages lost because of queue overflow
Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%SYS-6-MTRACE : [chars]: addr, pc ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC ADDRPC
Explanation This is an auxiliary message to several memory-related messages. It 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.
Recommended Action This message provides additional information only. Copy the error message exactly as it appears, and report it to your technical support representative as part of a previously printed error message.
Error Message%SYS-2-NOBLOCK : [chars] with blocking disabled
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%SYS-6-NOBRIDGE : Bridging software not present
Explanation Your system is not configured to be 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 that may help identify 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. That threshold has been reached.
Recommended Action It might be necessary to free some memory by exiting a program. If this message recurs, call your technical support representative for assistance.
Error Message%SYS-2-NOMEMORY : No memory available for [chars] [dec]
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's memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a configuration that has more memory.
Error Message%SYS-2-NOPROCESS : No such process [dec]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-NOTDEAD : Killing process [chars], pid [dec] again
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-NOTQ : [chars] didn't find [hex] in queue [hex]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-NULLIDB : Null IDB in [chars]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-NZREFCNT : Block [hex] on free list [dec] with refcount [dec]
Explanation A block of memory in the free pool is actually in use. The message indicates the number of processes using the memory block.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-5-OUTSETUP : Configuration file [chars] accepted, aborting setup
Explanation A configuration was accepted over the network, so the setup session will be aborted.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-3-OVERRUN : Block overrun at [hex] (red zone [hex])
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-1-OVERTEMP : System detected OVERTEMPERATURE condition. Please resolve cooling problem immediately!
Explanation The environmental monitor detected a high-temperature condition.
Recommended Action Ensure that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Call your technical support representative for assistance, if necessary.
Error Message%SYS-3-OVFPRINT : Overflow in [chars], chars [dec], buffer size [dec]
Explanation A software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%SYS-6-PROCINFO : Process [chars] just finished executing
Explanation This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.
Recommended Action Copy this messages exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative.
Error Message%SYS-2-QCOUNT : Bad [chars] [hex] count [dec]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-4-REGEXP : [chars]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-5-RELOAD : Reload requested
Explanation A reload or restart was requested.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-4-RELOAD_ATTEMPT : Attempt via SNMP failed, system shutdown not configured
Explanation SNMP cannot be used to reload the router unless this functionality has been previously configured. This message reports that an attempt to reload the router failed because SNMP reloads are not currently configured on the router.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-5-RESTART : System restarted --[chars]
Explanation A reload or restart was requested.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-2-SELFLINKED : Buffer [hex] linked to itself in free pool [chars]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-SHARED : Attempt to return buffer with sharecount [dec], ptr= [hex]
Explanation An internal software error has occurred as the result of an SNMP authentication failure. For example, if the SNMP request is for a community that is not configured on the switch, then this message would be posted. This condition has no impact on the normal functioning of the switch.
Recommended Action Ensure that there is no SNMP authentication failure. Even in the case of authentication failure, SNMP traps for authentication failure are sent to the Network Management System (NMS) as expected. If these messages become a nuisance, configure the no logging console command. If the message is received even after the command is configured, upgrade to Cisco IOS® Software Release 12.2(18)EW2 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%SYS-2-SNMP0IDX : Attempt to [chars] snmpidb with if_index of 0
Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears and report it your technical support representative.
Error Message%SYS-4-SNMP_HOSTCONFIGSET : SNMP hostConfigSet request. Loading configuration from [int]
Explanation SNMP is reading the host configuration from a network host.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-4-SNMP_NETCONFIGSET : SNMP netConfigSet request. Loading configuration from [int]
Explanation SNMP is reading the network configuration from a network host.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-4-SNMP_WRITENET : SNMP WriteNet request. Writing current configuration to [int]
Explanation SNMP is writing the current configuration to a network host.
Recommended Action This is a notification message only. No action is required.
Error Message%SYS-3-SOCKUNKN : Unknown socket protocol [dec]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-SPEC : Trying to set unknown special character [dec] to [dec]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-6-STACKLOW : Stack for [chars] [chars] running low, [dec]/[dec]
Explanation An internal software error occurred.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-5-TABLEERR : [chars] table [chars] damaged: [chars]
Explanation An internal table entry became corrupt.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%SYS-6-TESTINFO : Scheduler test [hex] (for [chars]) just executed
Explanation This message is an auxiliary to the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages. It identifies the process or process fragment that was executing when the error occurred.
Recommended Action Copy this message exactly as it appears, and report it, along with the SYS-3-OVERRUN and SYS-3-BADMAGIC error messages, to your technical support representative.
Error Message%SYS-3-TIMERHOG : Timer callback ran long, PC = [hex]
Explanation The indicated callback routine ran for too long without relinquishing the processor.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
Error Message%SYS-3-TIMERNEG : Cannot start timer ([hex]) with negative offset ([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%SYS-2-WATCHDOG : Process aborted on watchdog timeout, process = [chars].
Explanation The indicated process ran for too long without relinquishing the processor. The system killed it as a runaway process.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-3-WRONGFREELIST : Block [hex], size [dec], on wrong free list ([dec], [dec])
Explanation A freed buffer was placed on the wrong list of free buffers.
Recommended Action If this messages recurs, copy it exactly as it appears and report it to your technical support representative.
Error Message%SYS-2-WRONGPOOL : Buffer [hex] found in pool [hex], should be in pool [hex]
Explanation A software error occurred.
Recommended Action Copy the message exactly as it appears, and report it your technical support representative.
SYSCTLR Error Messages
System controller subsystem error messages
Error Message%SYSCTLR-5-AUTH_FAILED : MD5 digest does not match, SDP packet received from, [int] rejected
Explanation A 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%SYSCTLR-3-BAD_CALL : Invalid parameter/mangled pointer
routine: [chars], file: [chars], line: [dec]Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-6-BAD_IP_ADDR : Found Shelf [dec] with an invalid IP address [chars]
Explanation The system controller found a shelf with an invalid IP address.
Recommended Action Check the IP address set on the shelf.
Error Message%SYSCTLR-3-DISCOVER_SOCKET_BIND : socket bind failed
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-DISCOVER_SOCKET_OPEN : socket open failed
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-DUPLICATE_SHELF : SDP packet with duplicate shelf-id [dec] received from [chars],already discovered
elf located at [chars]Explanation Two shelves with same the shelf-id are configured in the system.
Recommended Action Change the shelf-id for one of the shelves.
Error Message%SYSCTLR-4-HMON_POLL : Local time [chars]
[chars] on shelfid [dec] is not active, resetting monitor_type [dec]Explanation This message contains health monitor setup commands polling information. If you see this message every ten minutes, the health monitor is not able to set that corresponding entry on that shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-HMON_SETUP_FAILED : Health monitoring setup failed on shelf_id [dec]
Explanation The health monitor failed to setup the monitoring command on a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-INVALID_SDP_VERSION : SDP packet received by system controller contained invalid version number
Explanation The SDP packet received by the system controller contained an invalid version number.
Recommended Action Check that the shelf is running a compatible version of SDP. If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-4-SDP_TIMEOUT : Hello packet from shelf [dec] not received, shelf removed.
Explanation No SDP hello packets were received from the particular shelf, which could indicate that the particular router shelf is down or is misconfigured.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-SDP_TIMER_ERROR : No context associated with the expired SDP timer
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-6-SHELF_ADD : Shelf [dec] discovered located at address [int]
Explanation The SDP protocol on the system controller has detected a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-4-SHELF_CONF_CHANGED : Configuration for the shelf [dec] located [int] changed
Explanation The SDP protocol on the system controller has detected that a particular shelf configuration has changed.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-SHELF_MSGFAIL : Unable to send message [dec] to process with pid [dec].
Explanation A likely cause of this error message is that the performance collector process has terminated.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-3-SHELF_PROTO : Shelf id protocol error
Explanation An internal software error occurred.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-4-SHELF_RELOAD : Shelf [dec] located [int] reloaded
Explanation The SDP protocol on the system controller has detected that a particular shelf has reloaded.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-4-SHELF_REMOVE : Shelf [dec] located at address [int] removed
Explanation The SDP protocol on the system controller did not receive hello packets from a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-6-SHELF_RESTORED : Communication with shelf [dec] located at address [int]
Explanation The SDP protocol on the system controller has detected a particular shelf.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSCTLR-4-SNMP_NOT_RESPONDING : Shelf [dec] not reachable via SNMP
Explanation The indicated shelf is not responding to SNMP requests.
Recommended Action Check the SNMP configuration for the above shelf and also check that the correct community string is specified in the system-controller community command on the system controller.
SYSLOG_SERVER Error Messages
Syslog-server file system routines error messages
Error Message%SYSLOG_SERVER-3-CREATE_ERR : Failed to create a Syslog file
Explanation A syslog file was not created.
Recommended Action There is probably no PCMCIA disk on slot0 on the system controller. Check to see if it is a PCMCIA Flash.
Error Message%SYSLOG_SERVER-4-DUP_FILE : Syslog file [[chars]] exists
Explanation You may have issued a directory name that already exists on the PCMCIA disk.
Recommended Action Check to see if the directory name you supplied already exists on the PCMCIA disk and re-enter a different name.
Error Message%SYSLOG_SERVER-4-FILE_CORRUPTED : syslog records do not appear to be timestamped
Explanation The syslog records are not timestamped, possibly because the service timestamps command was not issued.
Recommended Action Issue the service timestamps log datetime command on your router. This will cause the system to timestamp debugging or logging messages. At a minimum, use the datetime keyword.
Error Message%SYSLOG_SERVER-3-ILLEGAL_FS : Illegal file system [chars]
Explanation Illegal file system.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-3-MFS_MAX : Failed to add Syslog file [chars], maximum Syslog files [dec]
Explanation The maximum allowed syslog files was exceeded.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-4-NO_CONFIG_CHANGE : No configuration change
Explanation There was no configuration change to the syslog-server.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-4-NO_MEM : No memory left
Explanation There is no memory left.
Recommended Action The system controller is running very low on memory. If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-4-NO_MOBIUS : No syslog file
Explanation There is no syslog file.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-3-OPEN_FILE_ERR : Failed to open [chars].[dec] syslog file
Explanation A syslog file was not opened. One or more of the subfiles may have been deleted or there is no PCMCIA disk.
Recommended Action You may not have a PCMCIA disk in slot 0 on the system controller. Check to see if it is a PCMCIA Flash. If one or more of the subfiles is missing, they will be automatically restored when the current file reaches its capacity and gets archived.
Error Message%SYSLOG_SERVER-3-PARSING_ERR : Parsing file error
Explanation The router is not configured to timestamp all the log messages.
Recommended Action Configure your router with appropriate commands to timestamp the log messages (for example, use the service timestamps command).
Error Message%SYSLOG_SERVER-3-READ_ERR : Failed to read a file
Explanation A file was not read.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-3-UNKNOWN_NAME : Unknown command or device name, or unable to find device address
Explanation The command or device name is unknown, or the router was unable to find the device address.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%SYSLOG_SERVER-3-WRITE_ERR : Failed to write a syslog file
Explanation A syslog file was not written.
Recommended Action If this message recurs, call your technical support representative for assistance.
SYSMGT_RPC Error Messages
System Management error messages
Error Message%SYSMGT_RPC-3-IPC_ERROR : SYSMGT RPC - IPC [chars] [chars] failed ([chars])
Explanation System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, and report it to your Cisco technical support representative.
Error Message%SYSMGT_RPC-3-NETMGT_EVENT : SYSMGT RPC - NETMGT Event: [chars] ([dec])
Explanation System Management Remote Procedure Call Network management event error detected.
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%SYSMGT_RPC-3-RPC_ERROR : SYSMGT RPC - RPC [chars] [chars] failed ([chars] [dec])
Explanation System Management Remote Procedure Call operation failure. Request for information from the CIP card will not be processed.
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.
TAC Error Messages
Terminal Access Controller Access Control System (TACACS) protocol error messages
Error Message%TAC-4-NOTIMEOUT : Warning: This command has been deprecated in favor of the line-command timeout login response
Explanation This command is deprecated and should no longer be used. Instead, the timeout login response command now provides this functionality.
Recommended Action Use the line-command timeout user-response.
Error Message%TAC-6-SENDTMO : Send type [dec] to [int] timed out
Explanation A background TACACS notification (enabled with the tacacs notify command) was not acknowledged by the TACACS server processor within the timeout period (5 minutes). The information contained in that notification was lost. This loss of information may interfere with accounting or auditing on the server. This condition arises when the TACACS server is misconfigured, crashed, or became unreachable via the network.
Recommended Action Check the TACACS server and the network attached to it.
Error Message%TAC-4-UNEXREP : Reply for non-existent request, [dec] on queue
Explanation The TACACS facility received a message it was not expecting. This may occur when a TACACS server sends duplicate responses or when it responds to a request that has already timed out. It also may be caused by an internal software problem.
Recommended Action If this message recurs, call your technical support representative for assistance.
Error Message%TAC-3-XTACACL : [chars]: access list 0x[hex] out of range for [chars]
Explanation The TACACS facility created a message that contains an access list that is not a valid access list (out of bounds).
Recommended Action If this message recurs, call your technical support representative for assistance.
TAGCON Error Messages
Tag distribution and control error messages
Error Message%TAGCON-4-ADDR_PROC : Can't create tagcon addr proc
Explanation When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an address process. This message is generated when an attempt to create the address process fails.
Recommended Action This is an informational message. As long as it needs the process, the system will regularly attempt to create it. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-4-ADDRQ : Can't alloc work item for [int]
Explanation When a new IP address for a TDP peer is learned, it may be necessary to update the Tag Forwarding Information Base (TFIB) for any routes for which the new address is a next hop. Deciding whether it is necessary to update the TFIB is the responsibility of an address process. This message is generated when an attempt to queue work for the address process fails.
Recommended Action This is an informational message. The system remembers that it needs to do this work and will regularly attempt to queue the necessary work item. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-ALLOC : Cannot alloc [chars]
Explanation An attempt to allocate a tag-switching data structure failed because of a low memory condition.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Error Message%TAGCON-3-BUFFERBIND : unexpected error [dec]; peer [chars]; [chars]
Explanation An unexpected failure occurred while building a TDP protocol information element (PIE) for transmission to a TDP peer. It occurred when attempting to add a tag binding or an address to the PIE.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-CONSISTENCY : [chars]
Explanation An action attempted by the Tag Control process encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-DEADADJ : [int]/[int], [chars]
Explanation A problem was encountered in clean up following termination of a Tag Distribution Protocol (TDP) session.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-DEFCASE_BINDING_PIE : Unexpected blist_type ([dec]) for [chars] PIE from peer [chars]
Explanation A TDP protocol information element (PIE) received from a TDP peer contained an unexpected binding list type. The PIE will be ignored.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag-switching ip), waiting 15 to 20 seconds, and then reenabling it (tag-switching ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-DIRADJTREE : [int]/[int]; [chars]
Explanation An operation on the TDP Directed Adjacency data structure failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-EVENTQ : Can't alloc work item for [chars]
Explanation Internally when a process, such as the TDP process, must request the tag distribution and control process to take some action, it queues a work item 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.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-INIT : process cannot initialize
Explanation The tag distribution and control process failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Error Message%TAGCON-4-INIT_TAG_ALLOC : Failure to initialize tag allocation pool [dec]
Explanation The system was unable to initialize the data structure used to support allocation of tags for tag switching for the specified tag pool.
Recommended Action The system proceeds by ignoring the event. However, since the system will not be able to allocate tags from the tag pool, it will not advertise them to peers. Therefore, it will not be able to forward tagged packets it receives (because it does not advertise tags, it should not receive tagged packets). Copy the message exactly as it appears and report it along with the startup and running configuration to your technical service representative.
Error Message%TAGCON-3-LATREVNUMWRAP : Tag Local Address Table revision number wrapped
Explanation The revision number used to manage advertisement of interface addresses to TDP peers overflowed. This will result in faulty advertisement of interface addresses to TDP peers and faulty tag switching on those peers.
Recommended Action To restore proper interface address advertisement, reboot the platform. Report this condition to your technical service representative.
Error Message%TAGCON-3-NOTIMPL : peer [chars]; [chars] not implemented
Explanation A tag distribution protocol (TDP) peer requested an action that is not currently implemented by the tag distribution and control subsystem.
Recommended Action The request will be ignored. If the message recurs, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-PEERSM : TDP peer [int]([chars]): [chars]
Explanation An operation involving the state machine for a TDP peer failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-PROCESS : process not created
Explanation An attempt to create the tag distribution and control process failed. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
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.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-5-SEND : cannot queue TDP [chars] pie for [int]([chars])
Explanation An attempt to queue a TDP protocol information element (PIE) for transmission to a TDP peer failed.
Recommended Action This is an informational message. Failure to queue a PIE for a peer should occur only when the TDP session with the peer no longer exists. The software should recover from this situation by discarding the TDP session and trying to establish a new one. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-SM : Unexpected event; state=[chars], event=[chars]
Explanation An operation on the state machine for the tag distribution and control process failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
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 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 (no tag-switching ip), wait 15 to 20 seconds, and then reenable it (tag-switching ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TAGCON-3-TDPID_ADDR_TBL : [chars] sort bad; item [dec]
Explanation The tag distribution and control process maintains a data structure that is used to convert between the 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 (no tag-switching ip), wait 15 to 20 seconds, and then reenable it (tag-switching ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
TBRIDGE Error Messages
Transparent bridging error messages
Error Message%TBRIDGE-4-BAD_ENCAP : Unexpected encapsulation received on [chars] [chars]
Explanation The transparent bridging driver received a packet with unrecognizable encapsulation. The packet had to be discarded.
Recommended Action This could indicate that a network media error occurred or that a protocol is being used that is newer than this Cisco IOS software release. If it is believed that the dropped packets are of a real protocol, upgrade to a new release of the software that handles the protocol.
Error Message%TBRIDGE-4-BADXMAC : XMACACCESS: Invalid extended access list [dec]
Explanation There is a configuration problem. The specified extended access list either does not exist or contains an error.
Recommended Action Correct the configuration problem.
Error Message%TBRIDGE-4-GIANT : Giant received on [chars], [dec] exceeds [dec] DA [sci_notation] SA [sci_notation] [0x[hex]]
Explanation A packet was received that exceeds the expected maximum transmission unit (MTU) length for the receiving interface. The first 4 bytes of the packet following the source address are also provided to assist diagnosis.
Recommended Action Use the address and packet information provided to trace the source of these packets and reduce its MTU to conform to the standard for the given media.
Error Message%TBRIDGE-4-INVALIDMEDIA : [chars] received on [chars] - invalid media for transparent bridging
Explanation Transparent bridging was configured 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 transparently bridged packet destined for an ATM interface cannot be fully addressed.
Recommended Action Clear the bridge table to force relearning of all addresses.
Error Message%TBRIDGE-4-NOVCFLOOD : No VC's configured for bridging on [chars]
Explanation An ATM interface was configured for transparent bridging without also specifying the associated virtual circuits.
Recommended Action Configure the required virtual circuits 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 occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
TCATM Error Messages
ATM TAG control error messages
Error Message%TCATM-3-BADINSERT : [int][inet] x[hex] to 0x[hex]
Explanation An internal inconsistency was detected when an attempt was made to insert an item in a list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TCATM-3-BADSTATE : [int][inet] [chars] [chars]->[chars]
Explanation ATM TAG Control uses a table driven state machine to keep track and transition a TVC through various states. A state transition occurs when a TVC receives one of many possible events. When this error occurs, it means that a TVC received an event that it did not expect while in this state.
Recommended Action The system can continue but may lose the TVC that generated this error. Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TCATM-4-HOPCOUNT_EQUALLED : Maxhop=[dec] hopcount=[dec] for [int][inet] on [chars]
Explanation This message appears when a loop is discovered in the network.
Recommended Action Check the configuration and network path for the relevant prefix.
Error Message%TCATM-4-MALFORMED_PIE : Interface [chars] malformed TDP PIE
Explanation ATM TAG Control received a malformed PIE from TDP.
Recommended Action This does not affect system operation. However if this message recurs, report it to your technical service representative.
Error Message%TCATM-4-NOTAGIP : Tag switching disabled on [chars]
Explanation Tag switching is not enabled on the specified interface. Tag VCI requests and advertising will be rejected. As a side effect, the VCI requests at the upstream device can remain in the BindWait state until tag switching is re-enabled 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 failed while the ATM tag-control system was not initialized. Probable causes are misconfiguration or low memory.
Recommended Action Reduce other system activity if possible, and call your technical service representative for assistance.
Error Message%TCATM-3-OFFLIST : [int][inet] 0x[hex] not on list 0x[hex]
Explanation An internal inconsistency was detected when an attempt was made to remove an item from a list not on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TCATM-3-ONLIST : [int][inet] 0x[hex] on list 0x[hex]
Explanation An internal inconsistency was detected when an attempt was made to add an item to a list already on the list.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TCATM-3-PROCESS : process not created
Explanation An attempt to create the ATM tag control process failed. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible, and call your technical service representative for assistance.
Error Message%TCATM-4-RESOURCE_LIMIT : VC resource exhausted on [chars]
Explanation The system ran out of VC resources for the specified interface. Tagged virtual circuits (TVCs) for some destination prefixes will not be established, possibly resulting in degraded network performance.
Recommended Action Ensure that the negotiated 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-4-ROUTING_LOOP : Possible routing loop [int][inet] on [chars]
Explanation This message appears when a loop is discovered in the network.
Recommended Action Check the configuration and network path for the relevant prefix.
Error Message%TCATM-3-UNEXPECTEDBIND : Interface [chars] received unexpected bind for [int][inet]
Explanation An unexpected bind is received for a prefix. This message appears only when a memory resource allocation failure prevents this peer from informing the neighbor to release the bind. The system will continue but the downstream neighbor could be holding a binding for which there is no matching VCI at this end.
Recommended Action Reduce other system activity if possible, and call your technical service representative for assistance.
Error Message%TCATM-4-XCONNECT_FAILED : [int][inet] [chars] [chars] [chars]
Explanation The system ran out of resources to setup a switch cross-connect for the specified interfaces. Tagged virtual circuits (TVCs) for some destination prefixes will not be established, possibly resulting in degraded network performance.
Recommended Action Ensure that the negotiated VPI range is sufficient to permit usage of the maximum number of TVCs available on the hardware. If the negotiated VPI range is sufficient, reconfigure the network so that fewer TVCs are required on this interface.
TCP Error Messages
Transmission Control Protocol error messages
Error Message%TCP-2-ACCEPT : Callback failed to accept connection from [int]:[dec] to [int]:[dec] -- discarding
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-6-BADAUTH : [chars] MD5 digest from [int]:[dec] to [int]:[dec][chars]
Explanation The system received a TCP packet with an invalid MD5 authentication digest on a connection endpoint. The message ends with the string (RST) if the incoming packet was a TCP reset packet.
Recommended Action Determine why the source of the packet is not generating correct digests on the connection. This could be because of either misconfiguration or security weaknesses.
Error Message%TCP-2-BADQUEUE : Multiple entry for packet [hex]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-2-BADREFCNT : Tty[t-line]: Bad refcnt for packet 0x[hex] during retransmit, [chars]:[dec] to [chars]:[dec], state [dec]
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-2-BADTCBREFCNT : Bad TCB refcount: TCB 0x[hex], refcnt [dec]
Explanation An internal software error occurred
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-2-BUFFER : Tty[t-line], buffering bug
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%TCP-2-HALFCLOSE : Tty[t-line], tcp_putbyte() write disabled
Explanation TCP received a packet from a user application after the connection was already half-closed.
Recommended Action Determine which TCP application is still sending after the connection was half-closed.
Error Message%TCP-6-INTERCEPT : [chars], count ([dec]/[dec]) 1 min [dec]
Explanation The TCP Intercept code has changed state.
Recommended Action This message is for informational purposes, but it may indicate a security problem.
Error Message%TCP-2-INVALIDTCB : Invalid TCB pointer: 0x[hex]
Explanation An invalid TCB is used.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-2-INVALIDTCPENCAPS : Invalid TCB encaps pointer: 0x[hex]
Explanation An invalid TCP ENCAPS was used.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-3-NOTFOUND : Connection info for ([int]:[dec]) = ([int]:[dec]) not found
Explanation The TCP Intercept code was searching its database for information for a particular connection, but this information was not found.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your technical support representative for assistance.
Error Message%TCP-2-NOTREADY : [chars] called but TCP not initialized
Explanation An internal software error occurred.
Recommended Action If this message recurs, copy the message exactly as it appears and contact your technical support.
Error Message%TCP-2-PUTBYTE : Tty[t-line], tcp_putbyte() with blocking disabled
Explanation An internal software error occurred.
Recommended Action If this message recurs, contact your technical support representative.
Error Message%TCP-6-TOOBIG : Tty[t-line], too many bytes of options ([dec])
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
TDM Error Messages
Time-division multiplexing error messages
Error Message%TDM-4-TDM_BAD_CONNECT : Bad connection requested: slot [dec], stream [dec], channel [dec] to slot [dec], stream [dec], channel [dec]
Explanation The TDM cross-connect that was requested was not possible. This is probably because one of the devices either does not exist or is not properly configured for TDM.
Recommended Action Check the command for errors and the ports for correct configuration before trying again. Note that the type argument of the tdm-group command only applies if the mode cas command is enabled. If configuring a cross-connect pass-through from UIO serial port 0 or 1 to a controller, the encapsulation clear-channel command must be configured on the serial port.
Error Message%TDM-3-TDM_BADUNIT : Slot [dec] bad board ID 0x[hex] detected
Explanation The specified board returned an ID that was not recognized by the operating system. This could be caused by a hardware failure reporting an incorrect ID or because this software predates the hardware.
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%TDM-1-TDM_INITFAIL : Slot [dec] TDM init failure:
stream [dec], channel [dec], channel register 0x[hex], control register 0x[hex]Explanation The specified TDM port failed to be initialized. This error is possibly caused by a hardware failure.
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%TDM-1-TDM_MB_INITFAIL : Motherboard TDM init failure:
stream [dec], channel [dec], channel register 0x[hex], control register 0x[hex]Explanation The specified TDM port on the system motherboard failed to be initialized. This is possibly caused by a hardware failure.
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.
TDP Error Messages
Tag Distribution Protocol (TDP) error messages
Error Message%TDP-5-ACL : tag advertise-tags has no effect for tc-atm
Explanation The tag-switching advertise-tags configuration command has no effect for tag-controlled ATM interfaces. The rationale for this behavior is:
•
The purpose of the tag-switching advertise-tags command is to restrict the set of tags that are advertised, and thereby restrict which packets are tagged. Its effect is to cause some packets that might otherwise be tagged to be sent untagged over tag-enabled interfaces.
•
Recommended Action No action is required.
Error Message%TDP-5-ACL1 : tag advertise-tags has no effect for tc-atm
Explanation The tag-switching advertise-tags configuration command has no effect for tag-controlled ATM interfaces. The rationale for this behavior is:
•
•
Recommended Action No action is required.
Error Message%TDP-3-BAD_ADDRESS_LEN : peer [chars]; address len [dec]
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address with a bad length was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-BAD_METRIC_LEN : peer [chars]; metric len [dec]
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a metric with a bad length was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-BAD_MLIST_TYPE : peer [chars]; mlist_type [dec]; [chars] pie
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown metric list type or one that is unexpected for the situation was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-BAD_PIE : peer [chars]; unknown pie type 0x[hex]
Explanation An unknown Tag Distribution Protocol (TDP) protocol information element (PIE) type has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-BAD_PREFIX_LEN : peer [chars]; prefix len [dec]
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a destination prefix with a bad length has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the remainder of the PIE beyond the bad item. The partially processed PIE may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-CONSISTENCY : [chars]
Explanation An action attempted by the Tag Distribution Protocol (TDP) encountered an unexpected condition.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-GENERAL : [chars]
Explanation An action attempted by the Tag Distribution Protocol (TDP) implementation failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-4-IDENT : cannot set chassis TDP ident
Explanation The Tag Distribution Protocol (TDP) requires that each chassis have a TDP identifier. An attempt to set the TDP identifier for the chassis failed.
Recommended Action This is an informational message. As long as it needs to set its chassis TDP identifier the system will periodically attempt to do so until it succeeds. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TDP-5-INFO : [chars]
Explanation This is an informational message generated by the Tag Distribution Protocol (TDP) implementation.
Recommended Action No action is required.
Error Message%TDP-3-KA_NOMEMORY : Can't alloc KA PIE
Explanation An attempt to allocate a buffer for Tag Distribution Protocol (TDP) Keep Alive protocol information element (PIE) has failed.
Recommended Action The system will continue by omitting transmission of the TDP Keep Alive PIE. This may result in termination of one or more TDP sessions as the peers time out the sessions. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance.
Error Message%TDP-3-MALFORMED_PIE : peer [chars]; format error for pie type 0x[hex]
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) that is malformed was received from a TDP peer.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TDP-4-PTCL : peer [chars], [chars]
Explanation A violation of the TDP protocol by a TDP peer was detected.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-PTCLREAD : peer [chars], read failure
Explanation An error occurred while attempting to read a TDP PDU received from a peer.
Recommended Action This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message recurs, copy it exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-SM : unexpected event: peer [int]([chars]), state=[chars], event=[chars][chars]
Explanation An operation on the state machine for a TDP peer failed.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-TAGATM_BAD_RANGE : Interface [chars], Bad VPI range. Can't start a TDP session
Explanation The VPI range exchanged between the Tag Distribution Protocol (TDP) peers is non-overlapping.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. Reissue the tag-switching vpi command on the appropriate interface with the correct VPI range.
Error Message%TDP-3-TAGATM_NOMEM : Interface [chars], Resource failure. Can't start a TDP session
Explanation An attempt to allocate a buffer for Tag Distribution Protocol (TDP) TAGATM VPI/VCI ranges failed.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. If this message persists, reduce other system activity if possible, and call your technical service representative for assistance.
Error Message%TDP-3-UNEXPECTED_ALIST_TYPE : peer [chars]; alist_type [dec]; [chars] pie
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-UNEXPECTED_BLIST_TYPE : peer [chars]; blist_type [dec]; [chars] pie
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a binding list type that is unexpected for the situation has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-UNEXPECTED_PIE : peer [chars]; unexpected pie type 0x[hex]
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) that is unexpected for the situation was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-UNKNOWN_ALIST_TYPE : peer [chars]; alist_type [dec]; [chars] pie
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown address list type was received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
Error Message%TDP-3-UNKNOWN_BLIST_TYPE : peer [chars]; blist_type [dec]; [chars] pie
Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown binding list type has been received from a peer.
Recommended Action This is an informational message. The system proceeds by ignoring the PIE. This may result in impaired or faulty tag switching with the peer. The situation might be corrected by disabling dynamic tag switching at the chassis level (no tag ip), waiting 15 to 20 seconds, and then reenabling it (tag ip). In addition, copy the message exactly as it appears and report it to your technical service representative.
TE_LPDB Error Messages
Traffic engineering loop prevention error messages
Error Message%TE_LPDB-3-BUFFERMETRIC : unexpected error [dec]
Explanation An unexpected failure occurred while building a TDP protocol information element (PIE) for transmission to a TDP peer. It occurred during an attempt to add a metric to the PIE.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TE_LPDB-3-CONSISTENCY : [chars]
Explanation An action attempted by the traffic engineering loop prevention implementation encountered an unexpected condition
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
Error Message%TE_LPDB-3-INIT : uninitialized
Explanation The loop prevention database failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Error Message%TE_LPDB-3-PROCESS : no such process
Explanation The loop prevention control process failed to initialize itself. The probable cause is insufficient memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical support representative for assistance.
Error Message%TE_LPDB-3-RADIXTREE : [int]/[int]; [chars]
Explanation An operation on the traffic engineering metric database failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
TFIB Error Messages
Tag Forwarding Information Base error messages
Error Message%TFIB-2-BADENCAPLEN : Invalid encaps length [dec], tag size [dec], at incoming tag [chars]
Explanation An unexpected operation on a Tag Forwarding Information Base (TFIB) entry for a recursive route occurred, or an adjacency has an invalid mac rewrite string.
Recommended Action The system proceeds by creating an untagged entry in the TFIB. This will cause tagged packets for this destination being dropped or stripped of their tag. Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-INVALIDINDEX : Temporary path count difference for [int][inet], tfib entry [dec],loadinfo has [dec],fib has [dec]
Explanation A temporary difference occurred between the CEF database and the Tag Forwarding Information Base (TFIB). This difference will be resolved later.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-INVALIDTAG : Invalid tag [chars] [chars]
Explanation An invalid tag was seen while performing an operation on the Tag Forwarding Information Base (TFIB)
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-2-MEMORY : No memory for [chars]
Explanation An operation on the Tag Forwarding Information Base (TFIB) that requires memory failed because of insufficient free memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your technical service representative for assistance.
Error Message%TFIB-7-NONDB : Null ndb value passed to TFIB [chars]
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-NOPATH : No fib_path at index [dec] for [int][inet]
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-NULLFIB : Programming error: NULL fib or fibidb pointer passed to tfib code
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-NULLPATH : NULL fib path value passed to TFIB
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-NULLREWRITE : NULL tag rewrite pointer value passed to TFIB for deletion
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This may result in impaired or faulty behavior for tagged packets for this destination. Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-RESOLUTION : Temporarily unable to resolve TFIB loadinfo entry [dec] for [int][inet], fib has [dec] paths
Explanation A temporary difference occurred between the CEF database and the Tag Forwarding Information Base (TFIB). This difference will be resolved later.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%TFIB-7-SPECIALIDB : TFIB attempt to resolve entry with [chars] fibidb and incoming tag [chars]
Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) occurred.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
TI1570 Error Messages
PCI/TI1570-based ATM port adapter error messages
Error Message%TI1570-5-BADVCSETUP : ti1570_vc_setup failed. (vci [dec] of the last vpi [dec] exceeds (vc-per-vp - 3)).
Explanation The TI1570 chip reserves three RX DMA channels for OAM cells. As a result, the last three VCIs of the last VPI block cannot be used for regular traffic.
Recommended Action Try different VCI/VPI combinations.
Error Message%TI1570-3-BLOCKCMDFAIL : [chars] block command (code [dec]) failed, error code [dec]
Explanation An internal hardware or 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, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TI1570-1-DEVICEINITFAIL : PCI configuration for [chars] in slot [dec]
Explanation The ATM port adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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%TI1570-3-DISCOVER : Found [dec] out of [dec] devices (ID [hex]) in bay [dec]
Explanation The ATM-PCI port adapter software driver found fewer devices than it was configured to expect. This could mean that the missing device(s) failed to start and may have failed.
Recommended Action Try shutting off the power, reseating the card, and rebooting. 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%TI1570-3-FAILSETUPVC : Interface [chars], Failed to setup vc [dec] (Cause: [chars])
Explanation This error message probably indicates a hardware failure in the ATM-PCI port adapter.
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%TI1570-3-FAILTEARDOWNVC : Interface [chars], Failed to down vc [dec] (Cause: [chars])
Explanation An ATM virtual circuit could not be shut down for the reason shown in the error message. This probably indicates 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%TI1570-7-FRAMERINT : TI1500 framer interrupt isr1 0x[hex], isr2 0x[hex], isr3 0x[hex]
Explanation The ATM-PCI port adapter driver received and handled a framer interrupt.
Recommended Action This is an informational message only. No action is required.
Error Message%TI1570-1-IDBINITFAIL : [chars] for subunit [dec] in bay [dec]
Explanation The ATM port adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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%TI1570-1-INITFAIL : [chars] [chars]
Explanation The ATM port adapter failed to complete hardware initialization. Details of the failure are shown in the error message.
Recommended Action Reset the adapter. This should not be a recurring condition. 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%TI1570-1-INVALIDCONFIG : VIP only supports one PA-A1 ATM LITE PA. The other PA bay must be emptied in order for the PA-A1 ATM LITE PA to function
Explanation The bandwidth requirements of the installed port adapters exceed the processor's rated capability.
Recommended Action Either remove one of the port adapters or upgrade the VIP.
Error Message%TI1570-3-NOPCIMB : TI1570 unit [dec]: PCI mini buffer unavailable.
Explanation An internal hardware or 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, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TI1570-3-NOPCIMEMORY : TI1570 unit [dec]: PCI memory unavailable
Explanation The system experienced memory exhaustion in the PCI/packet memory. This was probably caused by heavy traffic congestion but could also be a software error.
Recommended Action Review the configuration for performance bottlenecks. 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%TI1570-3-NOSYSMEMORY : TI1570 unit [dec]: SYSTEM memory unavailable
Explanation Memory exhaustion has occurred in the ATM-PCI port adapter driver.
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%TI1570-3-NOTTI1570 : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The ATM-PCI port adapter driver could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. 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%TI1570-3-NOTXDESCSPACE : [chars] No tx buffer descriptor space in particle, data block 0x[hex], data start 0x[hex]
Explanation This message is probably caused by memory exhaustion. Memory could not be allocated by the driver for a packet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TI1570-1-PCIMEMNOTENOUGH : [hex] bytes available for PA in bay [dec]
Explanation The port adapter needs more PCI memory. The installed amount is less than is required by the drivers for packet buffers.
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%TI1570-3-PCI_PERROR : TI1570 unit [dec]: PCI parity error (0x[hex])
Explanation A parity error occurred on the PCI bus. This probably indicates an existing or developing hardware failure.
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%TI1570-3-PLXNOTFOUND : Bay [dec] device ID seen as [hex], expected #[hex]
Explanation The ATM-PCI port adapter driver found incorrect device IDs on the specified card. This could indicate either a hardware failure or that the software must be upgraded to recognize newer hardware.
Recommended Action Power down, reseat the interface card, and reboot. Or investigate if newer software is needed for your hardware. 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%TI1570-3-RBDCORRUPT : TI1570: received corrupted shadow particle pointer
Explanation The ATM-PCI port adapter driver experienced an internal error, probably caused by software but possibly 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.
Error Message%TI1570-3-RXDMANOTINACT : RX DMA entry [hex] not going inactive
Explanation A receive DMA channel failed to deactivate during shutdown of a virtual circuit. This failure could originate in hardware or software.
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%TI1570-3-RXFREEZE : [chars] receive freeze [dec]
Explanation This message indicates that excessive traffic congestion on the ATM interface may have resulted in cell loss. The PCI-ATM interface's cell buffers were full when a cell arrived on the interface, resulting in a receive freeze condition. A small number of freezes might not be a cause for concern.
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%TI1570-3-RX_HALT : TI1570 unit [dec]: Receive Channel Halt
Explanation This error message probably indicates a hardware failure on the ATM-PCI port adapter.
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%TI1570-3-TXDATANOTALIGNED : [chars] tx buffer data start not aligned to 32 bit boundary, data block0x[hex], data start 0x[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.
Error Message%TI1570-3-TXDMANOTFLUSHED : TX DMA not flushed
Explanation A transmit DMA channel failed to flush its buffers during shutdown of an ATM interface. This failure could originate in hardware or software.
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%TI1570-3-TXFREEZE : [chars] transmit freeze [dec]
Explanation This message indicates the PCI-ATM interface had to stop the transmitter while waiting for data. A small number of freezes might not be a cause for concern.
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%TI1570-3-UNSUPPORTED : Interface [chars], [chars] not supported
Explanation An attempt was made to configure a rate queue on an ATM Lite port adapter that does not support rate queues.
Recommended Action Check the configuration and try again, avoiding unsupported features.