-
Cisco IOS System Messages, Volume 2 of 2
-
System Messages Overview
-
MBUF through MODEM
-
MODEM_HIST through NSP
-
NSP_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SWITCH_IF
-
SYS through TCPIP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
Volume 2 Glossary
-
Table Of Contents
TDM_CLOCK_SYNCHRONIZATION Messages
TDM Messages
The following are Time Division Multiplexing (TDM) 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 request has been ignored. One of the devices either does not exist or is not configured properly for TDM.
Recommended Action Check the request for errors and ensure that the ports are configured correctly before reissuing the tdm-group command. Note that the type argument used in the tdm-group command applies only if the mode cas command has been enabled. If you are configuring cross-connectpass-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 [hex] detected.
Explanation The specified board returned an ID that was not recognized by the Cisco IOS software. This error could be caused by a hardware failure or by software that predates the hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM-1-TDM_INITFAIL : Slot [dec] TDM init failure: \n stream [dec], channel [dec], channel register [hex], control register [hex].
Explanation The specified TDM port could not be initialized. The error could be caused by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM-1-TDM_MB_INITFAIL : Motherboard TDM init failure:\nstream [dec], channel [dec], channel register [hex], control register [hex].
Explanation The specified TDM port on the system motherboard could not be initialized. The error could be caused by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TDM_CLOCK_SYNCHRONIZATION Messages
The following are specified Time Division Multiplexing (TDM) frame clock messages.
Error Message%TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_CHANGE : TDM frame clock source transitioned from Priority [dec] [chars] [chars] to Priority [dec] [chars] [chars]
Explanation A change in the clock source has occurred.
Recommended Action No action is required.
Error Message%TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_LOST_LOCK : TDM frame clock [chars] lost lock - clock source failed.
Explanation The clock source has failed.
Recommended Action If an alternate source is available, it will be used.
Error Message%TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_STATE_CHG : TDM frame clock state change, state: [chars]
Explanation A clock state change has occurred.
Recommended Action This is a debug error message only. No action is required.
Error Message%TDM_CLOCK_SYNCHRONIZATION-4-TDMCLK_STATE_ERR : TDM frame clock state error, state: [chars] event: [chars]
Explanation An invalid clock event has occurred.
Recommended Action No action is required.
TDM_CONN Messages
The following are messages related to TDM connections in the system.
Error Message%TDM_CONN-3-BOUND_CHK : Bounds check failed for [chars] TDM stream/channel [dec]/[dec] in slot [dec]
Explanation An invalid stream or channel pair has been given to the TDM driver.
Recommended Action Check the connection parameters by performing the TDM connection setup and teardown process. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-3-COUNT_MISMATCH : Timeslot Count1 [dec] and Count2 [dec] are expected to be equal
Explanation A wrong TDM connection setup request has been given to the TDM driver.
Recommended Action Check the connection parameters by performing the TDM connection setup and teardown process. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-4-EADI_CHECK : EADI Check passed for [dec] out of [dec] Timeslots
Explanation The TDM connections are kept active, even during a software reload. During the software reload process, some time-slots were present in the hardware, and some were not.
Recommended Action This is a transient condition, and recovery occurs automatically. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-4-EADI_CHECK2 : EADI Check passed for [dec] out of [dec] Timeslots
Explanation The TDM connections are kept active, even during a software reload. During the software reload process, some time-slots were present in the hardware, and some were not.
Recommended Action This is a transient condition, and recovery occurs automatically. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-3-INTERNAL_ERR : [chars]
Explanation The TDM system has encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TDM_CONN-0-MALLOC_FAIL : Malloc Failure
Explanation A memory allocation failure has occurred.
Recommended Action Reboot the system. If the error message recurs, the system likely does not have enough memory to function. Upgrade to more memory. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-2-MT90863_TYPE : Conn type [dec] passed to setup/teardown a MT90863 conn is invalid
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-3-SETUP : Setup of a TDM connection [dec]/[dec] to [dec]/[dec] in slot [dec] failed
Explanation During the TDM connection setup process, an invalid source, destination stream, or channel pair has been passed.
Recommended Action Check the connection parameters by performing the TDM connection setup and teardown process. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-3-TEARDOWN : Teardown of a TDM connection [dec]/[dec] to [dec]/[dec] in slot [dec] failed
Explanation During a TDM connection and teardown process, it was discovered that the connection does not exist.
Recommended Action Check the connection parameters by performing the TDM connection setup and teardown process. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDM_CONN-4-UNSUPPORTED : TDM connection from [dec]/[dec]/[dec] to [dec]/[dec]/[dec] is not supported
Explanation The requested TDM connection is not supported.
Recommended Action Review the product documentation to find the different types of TDM connections that are supported.
Error Message%TDM_CONN-4-UNSUPPORTED_END : TDM connection to [dec]/[dec]/[dec] is not supported
Explanation The requested TDM connection is not supported.
Recommended Action Review the product documentation to find the different types of TDM connections that are supported.
TDP Messages
The following are Tag Distribution Protocol (TDP) 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 purpose of the tag-switching advertise-tags command is to restrict the set of tags that are advertised, therefore restricting which packets are tagged. Its effect is to cause some packets that might otherwise be tagged to be sent untagged over tag-enabled interfaces. Because untagged packets typically cannot be forwarded at acceptable performance by the ATM switches within the cloud, the access controls configured by the tag-switching advertise-tags command are not supported for tag-controlled ATM 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 purpose of the tag-switching advertise-tags command is to restrict the set of tags that are advertised, therefore restricting which packets are tagged. Its effect is to cause some packets that might otherwise be tagged to be sent untagged over tag-enabled interfaces. Because untagged packets typically cannot be forwarded at acceptable performance by the ATM switches within the cloud, the access controls configured by the tag-switching advertise-tags command are not supported for tag-controlled ATM interfaces.
Recommended Action No action is required.
Error Message%TDP-3-BAD_ADDRESS_LEN : peer [chars]; address len [dec]
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-BAD_METRIC_LEN : peer [chars]; metric len [dec]
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-BAD_MLIST_TYPE : peer [chars]; mlist_type [dec]; [chars] pie
Explanation A TDP PIE containing an unknown metric list type or one that is unexpected for the situation has been received from a peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-BAD_PIE : peer [chars]; unknown pie type [hex]
Explanation An unknown TDP PIE type has been received from a peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-BAD_PREFIX_LEN : peer [chars]; prefix len [dec]
Explanation A TDP PIE containing a destination prefix with a bad length has been received from a peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-CONSISTENCY : [chars]
Explanation An action attempted by the TDP has encountered an unexpected condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-GENERAL : [chars]
Explanation An action attempted by the TDP implementation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-4-HOPCOUNT_EXCEEDED : Peer = [chars] [chars]([IP_address][IP_netmask]) Maxhop=[dec] hopcount=[dec] [chars]
Explanation This message appeared when the router signaled to establish an MPLS LSP or a tag switching TSP and, at that time, detected a transient loop in the path to the LSP destination. Normally, this is a transient condition.
Recommended Action If the LSP or TSP fails to come up, check that a path from MPLS ingress to MPLS egress exists with fewer hops than the maximum hops value configured in the mpls ldp maxhops command. If such a path exists, contact your Cisco technical support representative.
Error Message%TDP-4-IDENT : cannot set [chars][chars] TDP ident
Explanation The TDP requires that each TDP instance have a TDP identifier. An attempt to set the TDP identifier for the shown VRF or TDP instance has failed.
Recommended Action This is an informational message only. At intervals, the system continues attempting to set its chassis TDP identifier until it is successful. If this message occurs repeatedly, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-5-INFO : [chars]
Explanation This is an informational message generated by the 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 a TDP keepalive PIE has failed.
Recommended Action The system will continue by omitting transmission of the TDP keepalive PIE. This error may result in the termination of one or more TDP sessions as the peers time out the sessions. If this message recurs, reduce other system activity if possible, and contact your Cisco technical service representative for assistance.
Error Message%TDP-4-LDP_SESSION_PARAM : Peer [chars]; [chars]
Explanation The session parameters proposed by an LDP peer differ from those preferred by the platform. The differences are not sufficient to prevent the LDP session from being established, but they may have an impact on the label distribution operation. The parameters identified may relate to the optional path vector-based loop detection mechanism. If so, the IETF LDP specification recommends that when loop detection is enabled in part of a network, all LSRs in that portion of the network must be configured with loop detection enabled and with the same path vector limit.
Recommended Action If the parameters identified relate to some other aspect of the LDP session and the message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-MALFORMED_PIE : peer [chars]; format error for pie type [hex]
Explanation A corrupted TDP PIE has been received from a TDP peer.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-4-PATH_VEC : Peer = [chars] [chars]([IP_address][IP_netmask]) hopcount=[dec] [chars]
Explanation This message appears when LDP loop detection is configured. While signaling to establish an MPLS LSP, the loop detection function finds a transient loop in the path to the LSP destination. Normally, this is a transient condition.
Recommended Action If the LSP or TSP fails to come up, check that a path from the MPLS ingress to MPLS egress exists with fewer hops that the maximum hops value configured in the mpls ldp maxhops command. If such a path exists, report this problem to your Cisco technical service representative.
Error Message%TDP-4-PTCL : peer [chars], [chars]
Explanation A violation of the TDP by a TDP peer has been detected.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-PTCLREAD : peer [chars], read failure
Explanation An error has occurred during an attempt to read a TDP PDU that was received from a peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-SM : unexpected event: peer [IP_address]([chars]), state=[chars], event=[chars][chars]
Explanation An operation on the state machine for a TDP peer has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-TAGATM_BAD_RANGE : Interface [chars], Bad VPI/VCI range. Can't start a TDP session
Explanation The VPI range exchanged between the Tag Distribution Protocol peers is nonoverlapping.
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 the TDP TAGATM VPI or VCI ranges has failed.
Recommended Action The system will not be able to create a TDP session between the affected TDP peers. If this message recurs, reduce other system activity if possible, and contact your Cisco technical service representative for assistance.
Error Message%TDP-3-UNEXPECTED_ALIST_TYPE : peer [chars]; alist_type [dec]; [chars] pie
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-UNEXPECTED_BLIST_TYPE : peer [chars]; blist_type [dec]; [chars] pie
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-UNEXPECTED_PIE : peer [chars]; unexpected pie type [hex]
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-UNKNOWN_ALIST_TYPE : peer [chars]; alist_type [dec]; [chars] pie
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TDP-3-UNKNOWN_BLIST_TYPE : peer [chars]; blist_type [dec]; [chars] pie
Explanation A TDP PIE containing an address list type that is unexpected for the situation has been received from a peer. The system proceeds by ignoring the PIE. Ignoring the PIE may cause the system to experience impaired or faulty tag switching with the peer.
Recommended Action Disable dynamic tag switching at the chassis level by entering the no tag ip command, waiting 15 to 20 seconds, and then reenabling dynamic tag switching by entering the tag ip command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TESTPA Messages
The following are TestPA port adapter messages.
Error Message%TESTPA-3-DMAERROR : bay [[dec]] dma error: [chars]
Explanation A DMA failure has occurred.
Recommended Action Ensure that the port adapter is properly seated in the bay.
Error Message%TESTPA-3-INITFAIL : bay [[dec]] initialization failed: [chars]
Explanation The TestPA port adapter driver has failed to successfully initialize the hardware on the TestPA port adapter. The port adapter will be deactivated.
Recommended Action Ensure that the port adapter is properly seated in the bay.
Error Message%TESTPA-3-NOTANALYZED : bay [[dec]] analyze failed
Explanation The TestPA port adapter driver has failed to successfully complete the necessary tasks for initial bringup of the port adapter. This error is usually caused by a shortage of memory. Previous messages in the log will indicate the exact reason for the failure. The port adapter will be deactivated.
Recommended Action Ensure that the port adapter is properly seated in the bay.
Error Message%TESTPA-3-POWEREDOFF : bay [[dec]] powered off
Explanation The port adapter has been powered off. Other messages in the log will report the cause of this event.
Recommended Action If possible, correct any errors indicated by the other messages occurring at the time of this message. If this message persists, ensure that the port adapter is properly seated in the bay.
TFIB Messages
The following are Tag Forwarding Information Base (TFIB) messages.
Error Message%TFIB-2-BADENCAPLEN : Invalid encaps length [dec], tag size [dec], at incoming tag [chars]
Explanation An unexpected operation on a TFIB entry for a recursive route has occurred, or an adjacency has an invalid MAC rewrite string. The system proceeds by not creating or updating a TFIB entry for this route. Packets that are tagged for this destination will be dropped or stripped of their tags.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-5-CLEAR_COUNTERS : Clear tagswitch forwarding counters by [chars]
Explanation The tagswitch forwarding counters have been cleared.
Recommended Action No action is required.
Error Message%TFIB-2-CONSISTENCY : [chars]: [chars] [chars] [chars]
Explanation The MPLS TFIB implementation has encountered an unexpected condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-4-FIBCBLK : Missing MPLS Forwarding Information Base table for tableid [dec] during [chars] event
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-INVALIDINDEX : Invalid index [dec] passed to TFIB for [IP_address][IP_netmask], CEF entry has [dec] paths
Explanation The system has detected an invalid index while performing an action on the TFIB. The system proceeds by not creating or updating a TFIB entry for this route. Packets that are tagged for this destination will be dropped or stripped of their tags.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-2-INVALIDLIST : Invalid circular list for tags [chars] [chars]
Explanation The circular list of tag rewrites for the specified incoming tag has been corrupted. The system will proceed, but the list remains corrupted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-INVALIDTAG : Invalid tag [chars] [chars]
Explanation An invalid tag was seen while performing an operation on the TFIB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-2-MEMORY : No memory for [chars]
Explanation An operation on the TFIB has failed because of insufficient free memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TFIB-7-NONDB : Null ndb value passed to TFIB [chars]
Explanation An unexpected operation on the TFIB has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-NOPATH : No fib_path at index [dec] for [IP_address][IP_netmask]
Explanation An unexpected operation on the TFIB has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-NULLFIB : Programming error: NULL cef entry pointer passed to tfib code
Explanation An unexpected operation on the TFIB has occurred. The system proceeds by omitting the tag operation. This error may cause packets tagged for this destination to exhibit impaired or faulty behavior.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-NULLPATH : NULL fib path value passed to TFIB
Explanation An unexpected operation on the TFIB has occurred. The system proceeds by omitting the tag operation. This error may cause packets tagged for this destination to exhibit impaired or faulty behavior.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-NULLREWRITE : NULL tag rewrite pointer value passed to TFIB for deletion
Explanation An unexpected operation on the TFIB has occurred. The system proceeds by omitting the tag operation. This error may cause packets tagged for this destination to exhibit impaired or faulty behavior.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-RESOLUTION : Temporarily unable to resolve TFIB loadinfo entry [dec] for [IP_address][IP_netmask], fib has [dec] paths
Explanation A temporary difference has occurred between the CEF database and the TFIB. This difference will be resolved later.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-SCANSABORTED : TFIB scan not completing. [chars] [chars]
Explanation The periodic TFIB scan is being repeatedly aborted because of a problem such as an unresolved adjacency.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-TAGALLOCERR : Error [dec] while allocating a label in TFIB.
Explanation An unexpected operation has occurred on the Tag Forwarding Information Base.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This action may result in impaired or faulty behavior for tagged packets for this destination. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-TFIBNOTINIT : Trying to access TFIB which is not initialized.
Explanation An unexpected operation has occurred on the Tag Forwarding Information Base.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This action may result in impaired or faulty behavior for tagged packets for this destination. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TFIB-7-UNEQUAL : Can't use path [dec] with labels in = [chars], out = [chars], for [chars] to [IP_address][IP_netmask] in table [dec], n.h [IP_address]
Explanation When attempting to set up the load balancing infrastructure for a prefix with unequal path weightings, MPLS has discovered that the range of weightings caused one or more paths to be excluded from the final set of load-balancing paths. Load balancing will continue with the remaining paths.
Recommended Action Reduce the range of weightings to allow all the paths to be used.
THERMAL Messages
The following are power supply messages.
Error Message%THERMAL-3-PS: System detected Power System[dec] THERMAL FAIL condition
Explanation The operating temperature of the specified power supply (1 or 2) exceeded the acceptable range possibly caused by one or more of the following conditions:
–
Fan Failure
–
–
Recommended Action Check the possible causes. If you need to replace the Cisco 3745 fan assembly, refer to the Installing Field-Replaceable Units in the Cisco 3745 Routers hardware configuration note.
TI1570 Messages
The following are PCI/TI1570-based ATM port adapter 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 Avoid trying combinations of different VCIs and VPIs.
Error Message%TI1570-3-BLOCKCMDFAIL : [chars] block command (code [dec]) failed, error code [dec]
Explanation An internal hardware or software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-1-DEVICEINITFAIL : PCI configuration for [chars] in slot [dec]
Explanation The ATM port adapter has failed to complete hardware initialization. This error should not be a recurring condition.
Recommended Action Reset the adapter. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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 error could indicate that the missing devices have failed.
Recommended Action Power down, reseat the card, and reboot. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-FAILSETUPVC : Interface [chars], Failed to setup vc [dec] (Cause: [chars])
Explanation This error 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, contact 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 VC could not be shut down for the reason shown in the error message string. An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-7-FRAMERINT : TI1500 framer interrupt isr1 [hex], isr2 [hex], isr3 [hex]
Explanation The ATM-PCI port adapter driver has received and handled a framer interrupt.
Recommended Action No action is required.
Error Message%TI1570-1-IDBINITFAIL : [chars] for subunit [dec] in bay [dec]
Explanation The ATM port adapter has failed to complete hardware initialization. This error should not be a recurring condition.
Recommended Action Reset the adapter. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-1-INITFAIL : [chars] [chars]
Explanation The ATM port adapter has 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 this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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 rated capability of the processor.
Recommended Action 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 has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-NOPCIMEMORY : TI1570 unit [dec]: PCI memory unavailable.
Explanation The system has experienced PCI memory exhaustion. This condition is probably caused by heavy traffic congestion but could also be caused by an internal software error.
Recommended Action Review the configuration for performance bottlenecks. If this error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-NOSYSMEMORY : TI1570 unit [dec]: SYSTEM memory unavailable.
Explanation Memory exhaustion has occurred in the ATM-PCI port adapter driver.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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 this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-NOTXDESCSPACE : [chars] No tx buffer descriptor space in particle, data block [hex], data start [hex]
Explanation Memory could not be allocated by the driver for a packet. This error indicates memory exhaustion.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TI1570-1-PCIMEMNOTENOUGH : Only [hex] bytes of memory available for [chars]
Explanation The port adapter requires more PCI memory. The installed amount is less than what 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, contact 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 ([hex])
Explanation A parity error has occurred on the PCI bus. This error 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, contact 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 has found invalid device IDs on the specified card. This error could indicate a hardware failure, or it may signify that the Cisco IOS software must be upgraded to recognize newer hardware.
Recommended Action Power down, reseat the interface card, and reboot. Find out if newer software is required for your hardware. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-RBDCORRUPT : TI1570: received corrupted shadow particle pointer
Explanation The ATM-PCI port adapter driver has experienced an internal error that was caused by a software or hardware failure.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-RXDMANOTINACT : RX DMA entry [hex] not going inactive
Explanation A DMA channel has failed to deactivate during the shutdown of a VC. This failure error could indicate either a hardware or a software failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-RXFREEZE : [chars] receive freeze [dec]
Explanation This message indicates that excessive traffic congestion on the ATM interface might have resulted in cell loss. The cell buffers of the PCI-ATM interface 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 this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-RX_HALT : TI1570 unit [dec]: Receive Channel Halt
Explanation A hardware failure involving the ATM-PCI port adapter has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-TXDATANOTALIGNED : [chars] tx buffer data start not aligned to 32 bit boundary, data block[hex], data start [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-TXDMANOTFLUSHED : TX DMA not flushed
Explanation A transmit DMA channel failed to flush its buffers during the shutdown of an ATM interface. This failure error could indicate either a hardware or a software failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TI1570-3-TXFREEZE : [chars] transmit freeze [dec]
Explanation 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 this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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.
TIB Messages
The following are Tag Information Base (TIB) messages.
Error Message%TIB-3-GENERAL : [chars]
Explanation An action attempted by the TIB implementation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIB-3-INIT : Cannot allocate TIB
Explanation During initialization for tag switching, an attempt to initialize the TIB failed. This error may be caused by insufficient memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIB-3-LCLTAG : [IP_address]/[IP_address], [chars]; unexpected tag state=[dec]
Explanation An operation on the TIB involving a locally assigned (incoming) tag has failed. The system proceeds by omitting the tag operation. This error may cause packets tagged for this destination to exhibit impaired or faulty behavior.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIB-3-RADIXTREE : [IP_address]/[IP_address]; [chars]
Explanation An operation on the TIB data structure has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIB-5-RELTAG : [IP_address]/[IP_address], peer [chars]; tag [dec]; Unexpected LDP label release; [chars]
Explanation An operation on the Tag Information Base involving a tag assigned by a TDP peer has failed.
Recommended Action This is an informational message. The system proceeds by omitting the tag operation. This condition will not result in impaired or faulty behavior for tagged packets for this destination.
Error Message%TIB-3-REMOTETAG : [IP_address]/[IP_address], peer [chars]; tag [dec]; [chars]
Explanation An operation on the TIB involving a tag assigned by a TDP peer has failed. The system proceeds by omitting the tag operation. This error may cause packets tagged for this destination to exhibit impaired or faulty behavior.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIB-3-SM : Unexpected event; state=[chars], event=[chars]
Explanation An operation on the TIB state machine has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIB-3-TIBREVNUMWRAP : TIB revision number wrapped; toggling dynamic tag switching off and on to recover.
Explanation The TIB revision number used to manage advertisement of tags to TDP peers has overflowed. This error will result in tag distribution to TDP peers. The system recovers by toggling dynamic tag switching off and on, forcing the revision number to be reinitialized.
Recommended Action No action is required.
Error Message%TIB-5-WDRAWTAG : [IP_address]/[IP_address], tag [dec]; Withdrawn tag record has timed out.
Explanation A record associated with a withdrawn label has timed out before receiving acknowledgements from all peers.
Recommended Action This is an informational message. This condition will not have any operational system impact. The system will ignore any subsequently received release messages associated with the label.
TIGER Messages
The following are error-correcting code (ECC) and parity-related messages.
Error Message%TIGER-3-BADADDR_MBE : Invalid MBE dram address: [hex] latched by Tiger
Explanation The address latched by the Tiger when detecting an MBE is not a valid DRAM address. The Tiger should not report this kind of error under its normal operating conditions. This error probably indicates that a malfunctioning Tiger needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-BADADDR_MBE_RMW : Invalid MBE dram address: [hex] latched by Tiger during a RMW cycle
Explanation The address latched by the Tiger when detecting an MBE during a read-modify-write cycle is not a valid DRAM address. The Tiger should not report this kind of error under its normal operating conditions. This error probably indicates that a malfunctioning Tiger needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-BADADDR_SBE : Invalid SBE dram address: [hex] latched by Tiger
Explanation The address latched by the Tiger when detecting a SBE is not a valid DRAM address. The Tiger should not report this kind of error under its normal operating conditions. This error probably indicates that a malfunctioning Tiger needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-BADADDR_SBE_RMW : Invalid SBE dram address: [hex] latched by Tiger during a RMW cycle
Explanation The address latched by the Tiger when detecting a SBE is not a valid DRAM address. The Tiger should not report this kind of error under its normal operating conditions. This error probably indicates that a malfunctioning Tiger needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-2-MALLOC : Attempt to malloc [dec] bytes for the ECC error log failed.
ECC errors will only be reported and not recorded.Explanation Memory allocation for the ECC error log has failed.
Recommended Action If the system has 32MB or less of memory, upgrade the memory.
Error Message%TIGER-2-MBE : Multiple bit error detected at [hex]
Explanation A multibit uncorrectable error has been detected on a CPU read from DRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-2-MBE_RMW : Multiple bit error detected at [hex] on a read-modify-write cycle
Explanation The system detected a multiple bit error that cannot be corrected. This error occurred a during the non 8-byte access of the CPU read instruction that was part of a read-modify-write cycle from DRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-2-PARITY : Parity error on CPU write to address: [hex]
Explanation A parity error was detected by the Tiger during a CPU write operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-2-PARITY_INFO : Parity error was detected on the\n following byte(s) of a double word: [chars] [chars] [chars]
Explanation A 64-bit word contained invalid parity values that caused the Tiger ASIC to generate an interrupt. The message tells which bytes contained the invalid parity values.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SBE : Single bit error detected and corrected at [hex]
Explanation A single-bit correctable error was detected on a read from DRAM.
Recommended Action Enter the show memory ecc command to view the single-bit errors that have been logged. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SBE_HARD : Single bit *hard* error detected at [hex]
Explanation A single-bit uncorrectable error (hard error) was detected on a CPU read from DRAM.
Recommended Action Enter the show memory ecc command to dump the single-bit errors that have been logged up to this point and to confirm the address locations for the detected hard errors. If this error recurs, replace the DRAM.
Error Message%TIGER-3-SBE_LIMIT : Single bit error detected and corrected at [hex]
Explanation A single-bit correctable error was detected on a CPU read from DRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SBE_RMW : Single bit error detected and corrected at [hex] on a read-modify-write cycle
Explanation The system detected a single-bit correctable error. This error occurred a during the non 8-byte access of the CPU read instruction that was part of a read-modify-write cycle from DRAM
Recommended Action Enter the show memory ecc command to view the single-bit errors that have been logged. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SBE_RMW_LIMIT : Single bit error detected and corrected at [hex] on a read-modify-write cycle
Explanation The system detected a single-bit correctable error. This error occurred a during the non 8-byte access of the CPU read instruction that was part of a read-modify-write cycle from DRAM
Recommended Action Enter the show memory ecc command to view the single-bit errors that have been logged. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SYNDROME_MBE : 8-bit Syndrome for the detected Multi-bit error: [hex]
Explanation This message provides the 8-bit syndrome for detected multibit errors. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SYNDROME_SBE : 8-bit Syndrome for the detected Single-bit error: [hex]
Explanation This message provides the 8-bit syndrome for detected single-bit errors. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TIGER-3-SYNDROME_SBE_LIMIT : 8-bit Syndrome for the detected Single-bit error: [hex]
Explanation This message provides the 8-bit syndrome for detected single-bit errors. This value does not indicate the exact positions of the bits in error but can be used to approximate their positions.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TLV Messages
The following are EEPROM messages.
Error Message%TLV-3-GET : Reading data type [dec]
Explanation An expected field in the EEPROM buffer was either missing or malformed.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TLV-3-UPDATE : Unable to write type [dec]
Explanation An attempt to update an EEPROM entry has failed.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TMQ Messages
The following are inbound terminal port queuing (TMQ) messages.
Error Message%TMQ-3-NOTFOUND : TMQ, Attempt to delete entry not in queue
Explanation An attempt was made to delete an entry that was not in the queue.
Recommended Action No action is required.
TN Messages
The following are Telnet messages.
Error Message%TN-2-BADLOGIN : Bad login string pointer [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN-3-BADSTATE : Illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN-3-READLINE : Unknown return code [dec] from telnet_readline()
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TN3270 Messages
The following are TN3270 messages that are related to the TN3270 protocol, a variation of the IBM VT protocol.
Error Message%TN3270-2-INP_OVF1 : Input Buffer overflow
Explanation A problem in relating to the TN3270 protocol has occurred. Data without a TN3270 end-of-packet indicator was received, causing the TN3270 buffer to overflow.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TN3270S Messages
The following messages relate to the TN3270 server terminal emulation feature of the Channel Interface Processor (CIP) card.
Error Message%TN3270S-1-ADJUST_POOL_FAILED : A TN3270 server related buffer pool could not be adjusted
Explanation The size of an important buffer pool could not be increased. This error is due to either insufficient memory on the board or an internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message%TN3270S-6-AVL_INSERT_FAILED : An AVL Insert failed in [chars]
Explanation An attempt to add information to the AVL tree has failed. This is an indication of an internal program logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-6-BADCIRCBUF : CopyCmd failure. bufsize=[dec],Length=[dec],Index=[dec], \n CircBuf= [hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex][hex]
Explanation A Copy Command call has failed because a write operation calculated a buffer length of zero. The session for which the write was intended will be terminated. An internal program logic error has occurred.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-4-BAD_MAX_LUS_CFG : Could not change maximum LUs to [dec]
Explanation The TN3270 server could not change the maximum number of LUs to the requested value. The previous number is still in use.
Recommended Action Review the previous messages to discover what caused the failure, and take action based on those messages.
Error Message%TN3270S-6-BADTIMER : Bad timer operation([dec]),ra=[hex],funcPtr=[hex],oldFuncPtr=[hex]
Explanation A bad timer operation was detected and aborted. The rest of the information given is useful only to developers to debug the problem. Such bad-timer occurrences are usually harmless but are reported because they may accompany a more serious problem.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-6-CONFLICTING_LU_SEEDS : The lu-seed conflicts with the lu-seed of [chars]
Explanation The LU-seed is generating illegally duplicated LU names. For example, lu-seed ABC### and lu-seed ABC1## both generate LU name ABC101. The current PU definition has been rejected.
Recommended Action Use another LU-seed to define the current PU.
Error Message%TN3270S-1-CREATE_MUXWAIT_FAILED : A TN3270 server related semaphore could not be created.
Explanation An important semaphore could not be created. This failure is due to either memory shortage or some internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message%TN3270S-1-CREATE_POOL_FAILED : A TN3270 server related buffer pool could not be created.
Explanation An important buffer pool could not be created. This failure is due to either memory shortage or some internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message%TN3270S-1-CREATE_THREAD_FAILED : A TN3270 server related thread could not be started
Explanation An important thread could not be created. This failure is due to either a memory shortage or some internal code error.
Recommended Action This error is most probably due to insufficient memory. Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message%TN3270S-4-DDDLU_NOT_SUPPORTED : Host does not support dddlu at IP addr [chars], port [dec]
Explanation The TN3270 server cannot complete one or more connection requests from a TN3270/E client because the host does not support DDDLU.
Recommended Action Check that all PUs configured for use with DDDLU have the LUGROUP operand defined. Also check that the specified VTAM LUGROUP major node is active.
Error Message%TN3270S-1-DNS_NAIL_LOOKUP_FAILED : A connection attempt from client ([chars]) was refused because its DNS name could not be obtained, error code = [dec].
Explanation The TN3270 server had to do a DNS lookup because Inverse DNS Nailing is configured, but the lookup failed. Since the TN3270 server could not be determined if the client is nailed, the client was disconnected.
Recommended Action Configure a DNS server or remove the Inverse DNS Nailing configuration.
Error Message%TN3270S-1-DNS_NAIL_NO_SERVER : A connection attempt from client ([chars]) was refused because a DNS server is not configured.
Explanation The TN3270 server had to do a DNS lookup because Inverse DNS Nailing is configured, but the lookup failed. Since it could not be determined if the client is nailed, it was disconnected.
Recommended Action Configure a DNS server or remove the Inverse DNS Nailing configuration.
Error Message%TN3270S-1-DNS_NAIL_NOT_FOUND : Deletion of the Client Name ([chars]) LU Nailing first ([dec]) to last ([dec]) failed because the configuration was not found.
Explanation The deletion of the Client IP LU nailing command has failed because the configuration could not be found.
Recommended Action No action is required.
Error Message%TN3270S-1-DNS_NAIL_QUERY_TIMED_OUT : A connection attempt from client ([chars]) was refused because no response was received from the DNS server.
Explanation The TN3270 server had to do a DNS lookup because Inverse DNS Nailing is configured, but the lookup failed. Since it could not be determined if the client is nailed, it was disconnected.
Recommended Action Verify that the DNS server is operating correctly.
Error Message%TN3270S-1-DNS_NAIL_QUEUE_ERROR : An internal queueing error occurred, error code = [dec].
Explanation The TN3270 server had to do a DNS lookup because Inverse DNS Nailing is configured, but the response could not be matched with an outstanding query. An internal program logic error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-1-DNS_NAIL_SERVER_UNREACHABLE : A connection attempt from client ([chars]) was refused because the DNS server is unreachable.
Explanation The TN3270 server had to do a DNS lookup because Inverse DNS Nailing is configured, but the lookup failed. Since it could not be determined if the client is nailed, it was disconnected.
Recommended Action Troubleshoot the route to the DNS server.
Error Message%TN3270S-4-FUNC_NEGOT_LOOP : Client [chars]:[dec] in loop on TN3270E function negotiation [dec].
Explanation The client software is not behaving as specified by the RFC requirements.
Recommended Action Try to locate the TN3270 client that caused the problem. There could be a bug in the client.
Error Message%TN3270S-0-ILLEGAL_CCMUTEX_RELEASE : Releasing unacquired semaphore,lock_held [hex] lock_value [hex] ccMutex tcb [hex] thread tcb [hex]
Explanation An exclusive lock is being released illegally by an executing thread. The lock is held either by no one or by some other thread.
Recommended Action Reload the CIP. Since this problem is very serious, the error might recur. In any case, send the output of this message and tasks on the CIP console to your Cisco technical support representative. Also send information about your configuration and any action required to reproduce this problem.
Error Message%TN3270S-4-ILLEGAL_SUBOPTION : Client [chars]:[dec] sent Telnet suboption [dec] illegally.
Explanation The TN3270 client software is not behaving as specified by the RFC requirements.
Recommended Action Try to locate the TN3270 client that caused the problem. There could be a bug in the client.
Error Message%TN3270S-6-INVALID_RESOURCE_LENGTH : Resource name length [chars] is greater than 8 bytes
Explanation The resource name has a length greater than the prescribed maximum length, which is 8 bytes. This is an indication of an internal program logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-1-LISTENFAIL : Listening on [hex] [dec] Failed; err [dec]
Explanation An attempt was made to bring up a PU, but listening on the corresponding TCP/IP port could not be started.
Recommended Action Ensure that there is sufficient memory on the CIP card. If insufficient memory is not the problem, report this message to your Cisco technical support representative.
Error Message%TN3270S-2-LOW_MEM : Insufficient memory for TN3270 server, [dec] KBytes available, [dec] required
Explanation Insufficient memory is preventing proper operation of the TN3270 server.
Recommended Action Make sure there is enough memory available. Upgrade the memory on board or cancel other services running on the CIP. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message%TN3270S-1-LU_ERROR : lu error [chars]: [chars]:[dec] pu:[hex], tnet:[hex]
Explanation An unexpected event was presented to the LU named by the LOCADDR and PU. The error may cause the TN3270 session to work improperly. More detail on this error is contained in the LU_ERROR_INFO messages immediately following this message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-1-LU_ERROR_INFO : LU info: Event [chars], state = [hex], snaState = [hex], flag = [hex]
Explanation An internal software error has occurred. This message provides information about LU state, history, and flags that were present before the error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-1-LU_NO_BUFFER : No buffer for lu: [chars]
Explanation Some preallocated LU buffer space for transmissions has run out. The transmission of the message is aborted. The LU session is left incomplete. In addition, the LU session could hang.
Recommended Action Use show commands to find out as much about the LU state as possible and report the findings to your Cisco technical support representative.
Error Message%TN3270S-6-LU_THRESHOLD : \n Warning: TN3270 sessions are at [dec]% of maximum-lus\n
Explanation The number of LU sessions is approaching the configured limit.
Recommended Action No action is required.
Error Message%TN3270S-1-MEMORY_SHORTAGE : Insufficient memory on board; failed to allocate [dec] bytes
Explanation Memory could not be allocated for an important operation.
Recommended Action Upgrade your board with additional memory. If you believe there is sufficient memory, it is possible that there is a memory leak. Report details of your configuration, output of the show controller cxbus command, and any action needed to reproduce this problem to your Cisco technical support representative.
Error Message%TN3270S-1-NAIL_NOT_FOUND : Deletion of the Client IP ([chars]) LU Nailing first ([dec]) to last ([dec]) failed because the configuration was not found.
Explanation Deletion of the Client IP LU nailing command has failed because the command could not be found.
Recommended Action No action is required.
Error Message%TN3270S-1-NegRsp_NO_CORRELATOR : TN3270E negative response correlation: [chars].[dec], client IP addr [chars],nextSqn=[dec],rspSqn=[dec]
Explanation A TN3270E client has sent a negative response to a TN3270 request sent previously by the server. The negative response does not have a sequence number that can be correlated to a TN3270 request sent by the server.
Recommended Action Determine the DLOGMOD used for the session. Review the outbound pacing bits used for this session and ensure that the pacing value is no bigger than 4. If the problem persists, contact the client software vendor and file a problem report.
Error Message%TN3270S-3-NO_ADAPTIVE_SNA_BUFFERS : SNA buffer pool depleted: buffers: [dec], max lus: [dec]
Explanation The SNA buffer pool has been depleted. This pool has been grown dynamically but has reached the maximum allocation based on the configured maximum LUs.
Recommended Action Verify that the configured maximum LUs does not exceed recommended CIP memory. 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%TN3270S-3-NO_BIND_REQ_RCVD : No BIND REQ received on LU [chars].[dec]
Explanation Either a BIND REQUEST or SSCP-LU data was expected (but not received) from the host within 30 seconds of the start of the SSCP-LU session for this TN3270 session. If this condition persists for another two minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. A temporary workaround is to simply recycle the affected LU at the VTAM console. This will put the LU back into normal circulation.
Error Message%TN3270S-3-NO_DYN_ACTLU_REQ_RCVD : No ACTLU REQ received on LU [chars].[dec]
Explanation The host has not sent an ACTLU REQUEST within 30 seconds of sending a Reply-PSID RSP. If this condition persists for another two minutes, the TN3270 session currently connected to the LU is disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message%TN3270S-1-NO_EVENT_BUFS : No IPC sysmgt event buffers for at least one minute
Explanation The TN3270 server has events that will result in SNMP traps and SNA alerts, but it has not been able to allocate IPC buffer resources to report the events to the router system code. The TN3270 server will continue to try to report these events, but lack of buffers may continue until reload of the CIP microcode.
Recommended Action Report this problem to your Cisco technical representative. Include output from the following commands: show ipc status, show ipc queue, show ipc ports, show ipc nodes, show controller cbus, and show version As a workaround, reload the CIP microcode.
Error Message%TN3270S-1-NO_LU_MEMORY : No memory on the CIP was available for completing a requested TN3270 LU session
Explanation The memory available to the TN3270 server is insufficient to complete one or more requests by TN3270/E clients for LU sessions. The sessions have been disconnected.
Recommended Action Review the memory required to run the TN3270 server application in light of the current client load. Install additional memory if necessary.
Error Message%TN3270S-4-NO_LU_SESSIONS : Client session [chars]:[dec] requested a generic LU from IP [chars]:[dec], but no LU is available.
Explanation The TN3270 server cannot complete one or more connection requests from a TN3270/E client because there are no more available LUs left in the generic pool associated with the specified IP listening-point address.
Recommended Action Review the LU requirements for endpoints of this application. Configure additional PUs listening at the specified IP address and port number.
Error Message%TN3270S-1-NO_NAIL_MEMORY : Insufficient memory available on the cip for Client IP LU Nailing
Explanation Insufficient memory is available to process the Client IP LU nailing command on the CIP.
Recommended Action No action is required.
Error Message%TN3270S-6-NON_E_IPADDR_ELEMENT_NOT_FOUND : Deletion of the tn-parameter IP ([chars]) value ([dec]) command failed because \n the configuration was not found.
Explanation Deletion of the tn-parameter command has failed because the command could not be found. This is an indication of an internal program logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-3-NO_NTFY_AV_RSP_RCVD : No NOTIFY(available) RSP received on LU [chars].[dec]
Explanation No response to a power-on (available) notify request was received by the TN3270 server within 30 seconds of sending it to the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU will be disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message%TN3270S-3-NO_NTFY_UA_RSP_RCVD : No NOTIFY(UA) RSP received on LU [chars].[dec]
Explanation No response to a power-off (unavailable) notify request was received by the TN3270 server within 30 seconds of sending it to the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU will be disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening-point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message%TN3270S-3-NO_PSID_RSP_RCVD : No NMVT Reply PSID received on LU [chars].[dec]
Explanation No response to a reply PSID was received by the TN3270 server within 30 seconds of sending it to the host. This fault can occur only on dynamic LUs that have been misconfigured or deactivated at the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU will be disconnected. Bad dynamic LUs are placed in a special area where no attempt to reuse them is made until all other generic-pool LUs of the IP listening have been exhausted.
Recommended Action Check the status of the LU through the VTAM, and vary the LU active if appropriate. This action must happen within two minutes of the time this message appears; otherwise, the LU is placed in the "bad" LU area and will not be reused unless all good LUs are in use. Examine the host VTAM log for trouble. In particular, look for messages indicating a badly configured LUGROUP resource definition or file. Fix the configuration and recycle the affected major nodes.
Error Message%TN3270S-3-NO_SDT_REQ_RCVD : No SDT REQ received on LU [chars].[dec]
Explanation No SDT (Start Data Transfer) REQ was received by the TN3270 server from the PLU host for the specified LU. If the condition persists for another two minutes, the LU is declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message%TN3270S-3-NO_SDT_TMARK_RCVD : No SDT TIMING-MARK received on LU [chars].[dec]
Explanation No SDT (Start Data Transfer) TIMING-MARK response was received by the TN3270 server from the TN3270 client software for the specified TN3270 session. If this condition persists for another two minutes, the LU will be declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Some TN3270 clients may not fully handle the TN3270 RFCs. Enable the client-side trace to figure out what the client is failing on. Replace the failing client software with software from the list of TN3270 software types that are known to work with the TN3270 server (see your Cisco technical support representative for this). If the problem persists, report this error to your Cisco technical support representative.
Error Message%TN3270S-6-NOSESSHNDL : TN negotiation complete, but no handle for session [dec].
Explanation The TN negotiation complete routine was called, but no LU has been assigned to the session (socket). The session will be terminated. A bad-timer operation was detected and aborted. The rest of the information is useful only to developers to debug the problem. Such bad-timer occurrences are usually harmless, but are reported because they may accompany a more serious problem.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-3-NO_TERMSELF_RSP_RCVD : No TERMSELF RSP received on LU [chars].[dec]
Explanation No response to a TERMSELF request was received by the TN3270 server within 30 seconds of sending the request to the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU will be disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message%TN3270S-3-NO_UNBIND_RSP_RCVD : No UNBIND RSP received on LU [chars].[dec]
Explanation No response to an UNBIND request was received by the TN3270 server within 30 seconds of sending the request to the host. If this condition persists for another two minutes, the current TN3270 session connected to the LU will be disconnected. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Examine the SSCP host VTAM console for the status of the specified PU and LU. Review the VTAM console log output for relevant events, such as deactivation of the PU or LU. If, after VTAM console review, the cause is still unknown, report this error to your Cisco technical support representative. As a temporary workaround, recycle the affected LU at the VTAM console. This action will put the LU back into normal circulation.
Error Message%TN3270S-3-NO_UNBIND_TMARK_RCVD : No UNBIND-time TIMING-MARK received from client for LU [chars].[dec]
Explanation No UNBIND TIMING-MARK response was received by TN3270 server from the TN3270 client software for the specified TN3270 session. If this condition persists for another two minutes, the LU will be declared bad. Bad dynamic LUs will not be reused until all good dynamic LUs associated with the IP listening point are in use.
Recommended Action Some TN3270 clients may not fully handle the TN3270 RFCs. Enable the client-side trace to figure out what the client is failing on. Replace the failing client software with software from the list of TN3270 software types that are known to work with TN3270 server (see your Cisco technical representative for this). If the problem persists, report this error to your Cisco technical support representative.
Error Message%TN3270S-6-NOWRBUFR : Allocation failed for TCP write buffer, session [dec], [dec] supposedly on queue.
Explanation A CopyCmd or MsgQueRemoveFirst call failed to produce a memory buffer for a TCP write operation. However, prior checks had shown available buffers on the free queue. The session for which the write was intended will be terminated.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-6-PARAMETERINIT : An Invalid parameter registry code [dec]
Explanation During the TN3270 initialization, the supported tn-parameter codes have registered a routine. This routine will be used to process the configuration command. In this case an incorrect code was used. This is an indication of an internal program logic error.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-1-POOL_NOT_FOUND : Could not find the Pool [chars]
Explanation The search routines could not find this pool in the AVL tree. This message is usually the consequence of another problem. This is an indication of an internal program logic error.
Recommended Action It is important to report this problem to your Cisco technical support representative, because it reflects an internal program logic error.
Error Message%TN3270S-1-PROFILE_NOT_FOUND : Could not find the Profile [chars]
Explanation The search routines could not find this profile in the AVL tree. This message is usually the consequence of another problem. This is an indication of an internal program logic error.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-1-RESOURCE_POOL_NOT_FOUND : Could not find the ResourceCB associated with the Pool [chars]
Explanation The ResourceCB associated with the pool could not be found. This message is usually the consequence of another problem. This is an indication of an internal program logic error.
Recommended Action It is important to report this problem to your Cisco technical support representative because it reflects an internal program logic error.
Error Message%TN3270S-1-RP_PU_CONFLICT : RP & CIP hold conflicting PU name([chars]) or index([dec])
Explanation The RP has requested action (update or delete) on a PU resource from the CIP TN3270 server that is stale or incorrect.
Recommended Action Reload the CIP microcode. If the problem recurs, run the following commands before reloading the CIP microcode (! for each CIP in router): show ext chan /2 tn3270, show controllers cbus wr t. Report all findings to your Cisco technical support representative.
Error Message%TN3270S-1-RP_RTGROUP_CONFLICT : RP & CIP hold conflicting Response Time Group name([chars])
Explanation The RP has requested action (update or delete) on a Response Time Group resource from the CIP TN3270 server that is stale or incorrect.
Recommended Action Reload the CIP microcode. If the problem recurs, run the following commands before reloading the CIP microcode (! for each CIP in router): show ext chan /2 tn3270, show controllers cbus wr t. Report all findings to your Cisco technical support representative.
Error Message%TN3270S-4-SESSION_NEGOT_TIME_EXPIRED : A client session from [chars]:[dec] failed to negotiate TN3270/TN3270E.
Explanation A Telnet session that failed to negotiate TN3270/TN3270E within a specified time period has been disconnected. There could be a bug in the client, or it could be a transient network problem.
Recommended Action Try to locate the TN3270 client that caused the problem.
Error Message%TN3270S-1-SNA_BAD_SEQUENCE : LU-LU session bad sequence number, lu [chars].[dec] expected snf = [dec], current snf = [dec]
Explanation An unexpected LU-LU session sequence has been received. The LU was presented to the LU named by the LOCADDR and PU. The error will cause a negative response of sense code X2001 to be sent to the host.
Recommended Action Examine the SSCP host VTAM console for the status of the specified LU. Get a trace output for the specified LU and report this problem to your Cisco technical support representative.
Error Message%TN3270S-1-SNA_BAD_WSF : LU-LU session [chars].[dec] WSF data is illegal
Explanation A WSF 3270DS write with an invalid data length has been received.
Recommended Action Examine what application in the host sends this WSF, and report this problem to your Cisco technical representative.
Error Message%TN3270S-1-SNA_NO_PU_RESPONSE : PU [chars] locaddr [dec] does not get a response in 30 seconds
Explanation A PU had sent a request to the host but did not receive a response within the 30-second time limit.
Recommended Action Check to see if the PU is still in an active or busy state. Verify that the VTAM can talk to the PU. Check the LLC2 connection.
Error Message%TN3270S-4-SO_SNDBUF_FAILED : TNSetBindParam:SO_SNDBUF setsockopt for session failed sendSize [dec] err [dec]
Explanation An internal error occurred during the setting of the transmit window size for a TCP session. The session is using the default window size.
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. Also send information about your configuration, output of the show controller cxbus command, and any action required to reproduce this problem.
Error Message%TN3270S-1-START_FAIL : Failed to start Tn3270-server
Explanation The TN3270 server failed to start correctly and is now not running. The immediately preceding messages point to the cause of the failure.
Recommended Action Review the previous messages to discover what caused the start failure, and take action based on those messages.
Error Message%TN3270S-6-START_OK : Starting Tn3270-server
Explanation The TN3270 server subsystem has been brought up.
Recommended Action No action is required.
Error Message%TN3270S-1-STARTUP_RACE : InitTimerService Failed;Previous timer service still up
Explanation An attempt to restart the TN3270 server occurred before the previous shutdown could be completed.
Recommended Action If this problem is due to quick restart of TN3270 server, try again to start the TN3270 server. 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. Also send information about your configuration, output of the show controller cxbus command, and any action required to reproduce this problem.
Error Message%TN3270S-6-STOPPING : Stopping Tn3270-server
Explanation The TN3270 server subsystem has been shut down.
Recommended Action No action is required.
Error Message%TN3270S-2-TELNETINITFAIL : Initialization of TN3270 server Failed
Explanation Initialization of the Telnet component of the TN3270 server has failed.
Recommended Action This error is most probably caused by inadequate memory on the CIP card. If the memory on the CIP card is not the problem, report this message to your Cisco technical support representative.
Error Message%TN3270S-4-TN3270_CONFIG_INCOMPATIBLE : IOS sub-codepoint [dec] with length [dec] not understood
Explanation The TN3270 server has received a configuration command from the Cisco IOS software that the CIP does not recognize; some functionality may not be implemented.
Recommended Action Ensure that the Cisco IOS software version is compatible with the version of software running on the CIP.
Error Message%TN3270S-6-TOOBIG : [dec] byte IP datagram exceeds TN3270 Server receive buffer limit
Explanation The router has sent an IP datagram to the TN3270 server IP address that is larger than the maximum size of 4096. The IP datagram has been dropped.
Recommended Action No action is required.
Error Message%TN3270S-4-TOO_MANY_HOST_WRITES : Client on PU [dec]:locaddr [dec] ip [chars]:[dec] is being disconnected;Check outbound LU pacing.
Explanation The TN3270 client is being disconnected. This could either be a transient network problem or an internal error in the server.
Recommended Action Ensure that LU outbound pacing is configured. If that is correct, try to locate the TN3270 client that caused the problem. There could be bug in the client. Also try to get a Telnet trace of the session by reproducing the problem. Report this error to your Cisco technical support representative.
Error Message%TN3270S-7-UNKNOWN_SNA_MSG : Unknown message for PU [chars], data: [chars]
Explanation An SNA message from the host is invalid.
Recommended Action If it only happens once, this could a transient problem caused by a high volume of network activity. Record the message for later reference. If the error persists, ensure that the host is configured correctly.
Error Message%TN3270S-6-UNSUPPORTED_FUNCTIONALITY : The requested functionality is not currently supported
Explanation This functionality is not currently supported.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TN3270S-6-UNSUPPORTED_LU_DELETION_OPTION : The LU Deletion Option is not supported.
Explanation The LU deletion option is not supported by this version of the CIP.
Recommended Action Ensure that the Cisco IOS software and CIP versions match.
TOASTER_IPC Messages
The following are Toaster Interprocess Communication (IPC) messages.
Error Message%TOASTER_IPC-3-BAD_TIMEOUT : Invalid timeout parameter ([dec]ms is < [dec], or > [dec]).
Explanation The system has encountered an invalid timeout parameter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TOASTER_IPC-3-NO_RES : Could not allocate resource: [chars]
Explanation The resource specified in the error message could not be allocated. This condition might have occurred at initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TOASTER_IPC-3-NO_STATE : Attempt to pass a bad message to the Toaster.
Explanation A null pointer or an invalid message buffer was detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TOASTER_IPC-3-TOO_LONG : Invalid message length.
Explanation The requested message exceeded the maximum size of a Toaster IPC message as specified by "TT_IPC_MESSAGE_MAX_SIZE".
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TPLUS Messages
The following are TACACS protocol messages.
Error Message%TPLUS-3-FORKFAIL : Failed to fork process for [chars].
Explanation The system has most likely run out of memory; however, other explanations are possible.
Recommended Action If this messages recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TR Messages
The following are Token Ring messages.
Error Message%TR-3-ADPCHK : Interface [chars], adapter check error (non-fatal)([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware has detected a nonfatal error on the interface card.
Recommended Action Issue a clear interface command. If this message recurs, contact your Cisco technical support representative for assistance.
Error Message%TR-3-ADPCHKFATAL : Interface [chars], adapter check error (fatal) ([hex] [hex] [hex] [hex])
Explanation The Token Ring monitor firmware has detected a fatal error on the interface card. The interface card may be defective.
Recommended Action Issue a clear interface command. If this message recurs, contact your Cisco technical support representative for assistance.
Error Message%TR-3-BADBRDGPARMS : Unit [dec], bad bridge parameters: bridge_num=[dec], max_rd=[dec]\n thisring=[dec], targetring=[dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-BADBUFFSIZE : Unit [dec], bad buffersize = [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-BADFIRM : Unit [dec], Tokenring firmware download failed\n got [hex], expected [hex], at address [hex].[hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-BADFIRMTYPE : Unit [dec], bad firmware type code during [chars]. type=[hex], fw=[hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-BADFUNC : Unit [dec], bad functional address=[hex], ring mode=[hex]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-BADMUL : [chars]: Can't set address to a multicast ([enet])
Explanation An attempt was made to set the Token Ring interface MAC address to a reserved multicast address.
Recommended Action Check your configuration. Ensure that your XNS or Novell IPX Token Ring addresses have not inadvertently been set to reserved multicast addresses.
Error Message%TR-3-BADRNGNUM : Unit [dec], ring number ([dec]) doesn't match established number ([dec]).
Explanation The number you have configured for the local Token Ring does not match the value currently in use on the ring.
Recommended Action Check the configuration to ensure that you used the correct Token Ring number. If it is correct, confirm the configuration of all other bridges on the ring to ensure that they are using the same ring number.
Error Message%TR-3-BADSTART : Unit [dec], Start completion and wrong idb state - state= [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-BADUNIT : Bad unit number [dec]
Explanation This error message pertains only to the Cisco IGS series routers. The system cannot find the chipset registers where it expects them to be. This is most likely a hardware error.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-DIAGFAIL : Interface [chars] failed init diags ([hex]), [chars]
Explanation The microcode has attempted to run its diagnostics on the chip and has failed.
Recommended Action Issue a clear interface command. If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-INITFAIL : Unit [dec], init failed. result code=[hex], error code=[hex]
Explanation The Token Ring hardware has failed to initialize properly.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-INTFAIL : Unit [dec] interface failure: [hex] [hex] [hex], idb state [dec]
Explanation The Token Ring Monitor firmware has detected a fatal error due either to an internal software problem or to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-MODEFAIL : Unit [dec], change mode failed. result code=[hex], error code=[hex]
Explanation An internal hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-NOFIRM : Unit [dec], no TMS380 firmware present. eagle=[hex], magic=[hex]
Explanation An internal hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-2-NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TR-3-OPENFAIL : Unit [dec], open failed: [chars], [chars]
Explanation The Token Ring interface was unable to insert itself into a Token Ring that is either busy or broken. The first character string in this error message indicates the stage of initialization at which the error has occurred, and the second provides information about the error.
Recommended Action To open the interface again, enter clear interface tokenring command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-OPENFAIL2 : Unit [dec], open failed: check the lobe cable DB-9 connection.
Explanation The Token Ring interface was unable to insert itself into the Token Ring because of an error involving a wiring problem.
Recommended Action Check the cable connecting the router to the Token Ring MAU and try to open the interface again by entering the clear interface tokenring command. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-2-PANIC : Unit [dec], panic [hex] [hex] [hex]
Explanation The Token Ring monitor firmware has detected a fatal error that indicates an impending interface failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-2-PANICINF : Unit [dec], PI [hex] [hex] [hex] [hex] [hex] [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-2-PANICTYPE : Unit [dec], [chars] error
Explanation This message is similar to the
Unrecognized format ` %T'R-3-PANICerror message, but it indicates a nonfatal error. This message appears only in very unusual situations that should not arise in normal operation.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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-RESETFAIL : Unit [dec], reset failed, error code [hex].
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-SETBRIDGEFAIL : Unit [dec], set bridge failed (code [hex]).
Explanation A hardware error has occurred. The SRA chip on the Token Ring card could not be initialized.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TR-3-SETFUNFAIL : Unit [dec], set functional address failed (code [hex]).
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-3-SETGRPFAIL : Unit [dec], set group address failed (code [hex]).
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TR-6-STATE : [chars]: Ring Status: [chars]
Explanation This message is displayed when the chipset reports a status change for the Token Ring. This information also is used to determine automatically whether the interface is still available for propagating network traffic.
Recommended Action No action is required.
Error Message%TR-6-STATRING : TR[dec]: Ring Status: [chars] [chars]
Explanation This message is displayed when the chipset reports a status change for the Token Ring. This information also is used to determine automatically whether the interface is still usable to propagate network traffic. Table 4 shows the meaning of each status code.
Table 4
Token Ring Status Codes
Recommended Action Check the Token Ring for the indicated condition.
Error Message%TR-3-WIREFAULT : Unit [dec], wire fault: check the lobe cable MAU connection.
Explanation The Token Ring hardware is reporting a wire fault condition.
Recommended Action Check the cable that connects the router to the Token Ring MAU.
TRANGE Messages
The following are time-range messages.
Error Message%TRANGE-2-NOMEMORY : Alloc fail for time-range config buffer. Disabling distributed mode on lc
Explanation The router is unable to allocate memory to a buffer to send a time-range configuration to line cards.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show chunks command to gather data that might 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 chunks command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TRANGE-2-WRONGSIZE : Incorrect length trange ipc xdr of len=[dec] received
Explanation The RP sent a time-range configuration message of the wrong size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TRUNK Messages
The following are E1/T1 trunk card messages.
Error Message%TRUNK-3-BADCARDTYPE : Unknown type [hex] in shelf [dec] slot [dec]
Explanation The card in the specified slot and shelf was not recognized as either a T1 or E1 interface. This error indicates either a hardware or a software failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-BADCB : Unexpected data callback for trunk port
Explanation An unexpected software event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-BADCLOCK : selected clock on slot [dec] port [dec] is bad.Accepting the config.
Explanation The clock status as reported by the framer is invalid. Either no cable is plugged in or that the port is defective. The configuration is accepted, and as soon as the corresponding port becomes valid, it will be applied.
Recommended Action If you are configuring the clocks while there is no card in the corresponding slot (or the cable is not plugged in yet), no action is required. Otherwise, choose another clock.
Error Message%TRUNK-3-BADFW : Invalid framer firmware code file.
Explanation The software has detected an invalid framer firmware image that cannot be downloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-BADLOGICALIDX : Invalid Logical timeslot index = [dec]. Expect logical index starting from 1.
Explanation An invalid logical time slot index has been passed down to the physical time slot mapping function. The logical time slot index is 1-based.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-BADMSG : Bad doorbell message type to framer: [dec]
Explanation An invalid or undefined message type has been sent to the framer processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-BADSLOT : Invalid value ([dec]) for shelf [dec]; exceeds [dec]
Explanation An internal software error has occurred. An attempt has been made to reference a shelf number that is larger than the installed maximum configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-5-DROPMONITOR : Slot [dec], port [dec] put in [chars] mode
Explanation The test port on the specified card is now active. The ingress port is in drop-insert or monitor mode.
Recommended Action No action is required.
Error Message%TRUNK-3-HBEAT : No longer receiving heartbeats from framer CPU.
Explanation Communication from the framer processor to the trunk card processor has stopped. The framer processor is no longer passing status to the trunk card processor or accepting messages from the trunk card processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-INITFAIL : Trunk card initialization failed due to: [chars]
Explanation Trunk card initialization has failed for the reason that is reported within the error message string.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-MSGTMOUT : Timed out waiting for framer CPU to respond.
Explanation The framer processor did not reply to the read request during a specified amount of time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-NEATPPCCRASH : DFC ([dec]) Trunk Firmware crashed, FP [hex] RA [hex] EPC [hex]
Explanation The NEAT PPC firmware has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-NEATPPCWDOG : DFC ([dec]) Trunk Firmware watchdog timeout, Link Register [hex]
Explanation The NEAT PPC firmware has experienced a watchdog timeout.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-NEATROMCRASH : DFC ([dec]) ROM crashed, version [hex] CAUSE [hex] FP [hex]
Explanation The NEAT firmware has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-5-NODROPMONITOR : Slot [dec], port [dec] taken out of [chars] mode
Explanation The test port on the specified card is inactive. The ingress port is no longer in drop-insert or monitor mode.
Recommended Action No action is required.
Error Message%TRUNK-3-NODSIPBUFS : Cannot send DSIP message to RSC; no more buffers available
Explanation The memory buffers for message passing between the trunk card and RSC are exhausted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-NOMEM : Insufficient memory for slot: [dec] in shelf: [dec]
Explanation Router memory was exhausted while allocating memory for use with the specified slot and shelf.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TRUNK-3-NOMSGS : Cannot send message to framer; no more messages available
Explanation The memory buffer for message passing between the trunk card and the framer processors has been exhausted. Either the messages are not being picked up or they are being generated too quickly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK-3-TPMISMATCH : Stored port ([int]) does not match passed unit ([int]) for slot [int]'s Test Port
Explanation The port value stored on the trunk card does not match the port value passed down to the FB for a "monitor off" request. This condition indicates a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TRUNK_CLOCK Messages
The following are Cisco AS5400 clocking messages.
Error Message%TRUNK_CLOCK-6-BAD_CLOCKS : There are no good clocks in the system. Remain in HOLDOVER mode
Explanation The clock selection algorithm has failed to select any clock as the TDM primary clock.
Recommended Action No action is required.
Error Message%TRUNK_CLOCK-6-EXTERNAL : Switching to the external clock on motherboard
Explanation The TDM primary clock is switching to the external clock on the motherboard.
Recommended Action No action is required.
Error Message%TRUNK_CLOCK-6-FREERUN : Switching to the freerunning clock on motherboard
Explanation The TDM primary clock is switching to the free running clock on the motherboard.
Recommended Action No action is required.
Error Message%TRUNK_CLOCK-3-NOMEMORY : Failed to allocate memory for the clocks
Explanation The clock switching software has failed to allocate memory while adding a clock.
Recommended Action No action is required.
Error Message%TRUNK_CLOCK-6-SWITCH : Switching to the clock on slot [dec] port [dec] priority [dec] as the current primary has gone bad
Explanation The TDM primary clock has switched to a backup clock that is coming in through the specified trunk because the current primary clock has failed.
Recommended Action No action is required.
Error Message%TRUNK_CLOCK-6-TRUNK : Switching to the trunk clock on slot [dec] port [dec] priority [dec]
Explanation The TDM primary clock is switching to the newly selected trunk clock.
Recommended Action No action is required.
TRUNK_DFC Messages
The following are trunk dial feature card messages.
Error Message%TRUNK_DFC-3-CONTRCREATE : Failed to create controller for [dec]/[dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-DSX3CONTEXT : Failed to create context for dsx3 controller in [dec]/[dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-SDRAM_TEST_FAILED : Trunk DFC in slot [dec]: SDRAM failed [[hex]..[hex]]
Explanation The trunk DFC SDRAM test has failed, indicating a failed memory location.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-TRUNK_FIRMWARE_DOWNLOAD_FAILED : Could not download trunk firmware in slot [dec]
Explanation The trunk firmware cannot be downloaded.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-TRUNK_FIRMWARE_NOT_READY : Trunk DFC firmware in slot [dec] is not ready
Explanation The trunk DFC firmware has failed to start.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-TRUNK_RESET_FAILED : Reset failed for Trunk DFC ROM in slot [dec]
Explanation The trunk DFC cannot be taken out of reset mode.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-TRUNK_ROM_FAILED : Trunk DFC ROM in slot [dec] failed: [chars]
Explanation The trunk DFC ROM has failed to boot properly.
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 might 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 tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%TRUNK_DFC-3-TRUNK_SLOT_CREATE : Failed to create trunk slot instance for slot [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TRUNK_SERIAL Messages
The following are trunk serial device messages.
Error Message%TRUNK_SERIAL-3-ANALYZE_DEVICE_FAILURE : Trunk-[dec]: Device initialization failed.
Explanation The system detects a trunk serial analyze device failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TSP Messages
The following are TSP messages.
Error Message%TSP-3-CAPABILITYMISMATCH : voice port [chars]: call connection id [[hex] [hex] [hex] [hex]]
Explanation There was a capabilities mismatch between the two call legs. The capabilities are negotiated between the call legs for CODEC, VAD, and FAX rate.
Recommended Action Ensure that the dial peer configuration is appropriate for the interface in question. Also check that the configuration on the interface is correct.
Error Message%TSP-3-DSPALARM : voice port [chars]: status=[hex] message=[hex]
Explanation The DSP has reported a fatal error. All calls on the DSP were dropped, and a DSP reload was attempted.
Recommended Action Verify that the DSP has reloaded properly by attempting to place a call on the affected voice port. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TSP-3-FSM_ERROR : [chars]
Explanation An internal finite state machine error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TSP-3-NOEVENT : no free event structure available from [chars] for DSP message
Explanation There were no event structures remaining in the system pools to alert the router to a voice or signaling event.
Recommended Action Ensure that the voice port for which the event was reported is still operational. If not, clear the voice port.
Error Message%TSP-5-PRI : [chars] at slot [dec], unit [dec], channel [dec]
Explanation A PRI signaling channel has been added to or deleted from the TSP inventory of signaling channels.
Recommended Action No action is required.
TTY Messages
The following are tty-related messages for all platforms.
Error Message%TTY-3-AUTOCONFIG : TTY[t-line]: Modem auto-configuration failed
Explanation Modem autoconfiguration has failed either because the modem rejected the configuration string or because of a timeout.
Recommended Action Attempt to apply the configuration string manually. If this message reoccurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTY-3-NOPROCESS : Cannot create [chars] process
Explanation An attempt to create the specified process has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TTYDRIVER Messages
The following are router shelf asynchronous driver messages.
Error Message%TTYDRIVER-3-BADCB : Unexpected data callback for modem [chars]
Explanation An unexpected software event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTYDRIVER-3-BADENCAP : Unknown encapsulation on interface [chars]
Explanation A software error has caused an unknown encapsulation type to appear on the interface specified by the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTYDRIVER-2-NOBRKPAK : Unable to allocate break block from I/O mem
Explanation The router does not have enough I/O memory available for buffers.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TTYDRIVER-2-NOBUF : Unable to allocate [dec] I/O buffers
Explanation A buffer memory shortage existed at the time that the configuration command was issued. This condition is temporary.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTYDRIVER-2-NOBUFPOOL_ASYNC : Unable to create buffer pool for async. mode interface
Explanation There is not enough memory for a per-channel control block of the asynchronous tty driver.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TTYDRIVER-2-NOMEM : Unable to allocate [dec] byte status block
Explanation The asynchronous tty driver was unable to create an internal structure because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TTYDRIVER-3-NOPARTS : No particles available to set up for output on tty [chars]
Explanation A software error has occurred, resulting in an unexpected exhaustion of the pool of data buffers used by the modem drivers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTYDRIVER-3-NOTXPART : Non-zero outcount but no transmit particle on tty [chars]
Explanation A software error has occurred, leaving a software structure in an unexpected state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTYDRIVER-3-RTSLOW : RTS is incorrectly deasserted for tty [chars]; reasserting now
Explanation A software error has occurred, resulting in an invalid state for the RTS modem signal.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%TTYDRIVER-3-UNKNOWN_PORT_ARCH_TYPE : Unknown port type ([dec])
Explanation An unrecognized port type has caused a software error to occur.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TUN Messages
The following are tunnel messages.
Error Message%TUN-5-RECURDOWN : [chars] temporarily disabled due to recursive routing
Explanation When you are routing a payload protocol over a carrier protocol (tunneling IP over IP, for example), it is possible to misconfigure your network so that you will try to route to the tunnel destination address via the tunnel. This condition is usually caused by a misconfiguration of the tunnel or a temporary instability caused by route flapping elsewhere in your network. It is important to take steps to ensure that routing information between the carrier networks and the payload networks is not allowed to mix. If the router discovers a recursive routing problem, it will shut down the tunnel interface for a few minutes so that the situation that is causing this problem can resolve itself as routing protocols converge. If the problem is caused by misconfiguration, the link may oscillate indefinitely.
Recommended Action No action is required.
TUNSS Messages
The following are tunnel security messages.
Error Message%TUNSS-3-PROTECTION_PROCESS_FAIL : Failed to create tunnel security process
Explanation A start process for tunnel protection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
TXCONN Messages
The following are Cisco Transaction Connection (CTRC) messages.
Error Message%TXCONN-3-BADLICENSEKEY : Bad license key configured for Transaction Connection.
Explanation The license key configured with the txconn license configuration command is not valid.
Recommended Action Ensure that the license key was entered correctly in the txconn license configuration command. Refer to the CTRC documentation for information on how to obtain a valid license key.
Error Message%TXCONN-3-BADMODE : Unknown mode '[chars]' configured for server [chars]
Explanation The mode configured for the CTRC server was rejected by the remote database server.
Recommended Action Contact your SNA network administrator to determine the correct name of the mode to use to connect to DB2 on the remote database server.
Error Message%TXCONN-3-BADRLU : Bad remote LU '[chars]' configured for server [chars]
Explanation The remote LU configured for the CTRC server is incorrect.
Recommended Action Contact your SNA network administrator to determine the correct name of the remote LU for DB2 on the remote database server. Ensure that both the SNA network name and the LU name are correct.
Error Message%TXCONN-5-CONNIDLETIMEOUT : Client [IP_address] connected to server [chars] has timed out after [time-stamp].
Explanation The client was idle for too long, and the idle timeout configured for the CTRC server has expired.
Recommended Action No action is required.
Error Message%TXCONN-3-INVALIDTRANS : Bad Transaction ID, flushing out request for client [IP_address] connected server [chars], killing connection.
Explanation An invalid input stream has been detected and ignored.
Recommended Action No action is required.
Error Message%TXCONN-3-NOSESSION : Out of resource, cannot create transaction for client [IP_address] connected server [chars], killing connection.
Explanation The router is out of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%TXCONN-5-SECFAIL : APPC security failed, client [IP_address] using userid '[chars]' for server [chars]
Explanation The user ID or password issued by the client was rejected by the remote database server.
Recommended Action No action is required.
Error Message%TXCONN-5-TARGETDOWN : CICS server [chars] has become unavailable. Recovery is in progress.
Explanation A CICS server for a configured destination has become unavailable. All client connections to this server will be rejected until it becomes available again.
Recommended Action No action is required.
Error Message%TXCONN-5-TARGETUP : CICS server [chars] is now available.
Explanation A CICS server that was previously unavailable has become available. All client connections to this server will now be accepted.
Recommended Action No action is required.
Error Message%TXCONN-5-TRANSIDLETIMEOUT : Transaction [hex] of Client [IP_address] connected to server [chars] has timed out after [time-stamp].
Explanation The transaction was idle for too long, and the idle timeout configured for the CTRC server has expired.
Recommended Action No action is required.
Error Message%TXCONN-3-TXEXCEPTION : Exception [chars] from transaction [chars] to [chars] from client [IP_address]
Explanation An unexpected transaction error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If possible, also provide the output of the debug txconn data command and an SNA line trace between the router and the remote database server for the period during which this message appeared.
Error Message%TXCONN-3-UNEXPECTEDREQ : Unexpected client data, flushing out the request for client [IP_address] connected server [chars].
Explanation An invalid input stream has been detected and ignored.
Recommended Action No action is required.