|
|
The following are Transmission Control Protocol (TCP) error messages.
Error Message
%TCP-2-ACCEPT: Callback failed to accept connection from [int]:[dec] to [int]:[dec] -- discardingExplanation An internal software error has occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your Cisco technical support representative for assistance.
Error Message
%TCP-6-BADAUTH: [chars] MD5 digest from [int]:[dec] to [int]:[dec][chars]Explanation The system has received a TCP packet with an invalid MD5 authentication digest on a connection endpoint. The message ends with the string (RST) if the incoming packet was a TCP reset packet.
Recommended Action Determine why the source of the packet is not generating correct digests on the connection. This could be caused by either misconfiguration or security weaknesses.
Error Message
%TCP-2-BADQUEUE: Multiple entry for packet [hex]Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your Cisco technical support representative for assistance.
Error Message
%TCP-2-BADREFCNT: Tty[t-line]: Bad refcnt for packet 0x[hex] during retransmit, [chars]:[dec] to [chars]:[dec], state [dec]Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy it down exactly as it appears and contact your Cisco technical support representative for assistance.
Error Message
%TCP-2-BADTCBREFCNT: Bad TCB refcount: TCB 0x[hex], refcnt [dec]Explanation An internal software error has occurred
Recommended Action If this message recurs, copy it down exactly as it appears and contact your Cisco technical support representative for assistance.
Error Message
%TCP-2-BUFFER: Tty[t-line], buffering bugExplanation An internal software error has occurred.
Recommended Action If this message recurs, contact your Cisco technical support representative.
Error Message
%TCP-2-HALFCLOSE: Tty[t-line], tcp_putbyte() write disabledExplanation TCP has received a packet from a user application after the connection was already half closed.
Recommended Action Determine which TCP application is still sending after the connection was half closed.
Error Message
%TCP-6-INTERCEPT: [chars], count ([dec]/[dec]) 1 min [dec]Explanation The TCP Intercept code has changed state.
Recommended Action This message is for informational purposes, but it may indicate a security problem.
Error Message
%TCP-2-INVALIDTCB: Invalid TCB pointer: 0x[hex]Explanation An invalid Transmission Control Block (TCB) is being used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TCP-2-INVALIDTCPENCAPS: Invalid TCB encaps pointer: 0x[hex]Explanation An invalid TCP ENCAPS is being used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TCP-3-NOTFOUND: Connection info for ([int]:[dec]) => ([int]:[dec]) not found.Explanation The TCP Intercept code was searching its database for information for a particular connection, but this information was not found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TCP-2-NOTREADY: [chars] called but TCP not initializedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TCP-2-PUTBYTE: Tty[t-line], tcp_putbyte() with blocking disabledExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TCP-6-TOOBIG: Tty[t-line], too many bytes of options ([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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are time-division multiplexing (TDM) error messages.
Error Message
%TDM-3-TDM_BADUNIT: Slot [dec] bad board ID 0x[hex] detected.Explanation The specified board returned an ID that was not recognized by the Cisco IOS software. This error could be caused by a hardware failure or because this software predates the hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDM-4-TDM_BAD_CONNECT: Bad connection requested: slot [dec], stream [dec], channel [dec] to slot [dec], stream [dec], channel [dec].Explanation The time-division multiplexing (TDM) cross-connect request has been ignored. One of the devices either does not exist or is not properly configured for TDM.
Recommended Action Check the request for errors and ensure that the ports are correctly configured 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-connect pass-through from UIO serial port 0 or 1 to a controller, the encapsulation clear-channel command must be configured on the serial port.
Error Message
%TDM-1-TDM_INITFAIL: Slot [dec] TDM init failure:Explanation The specified time-division multiplexing (TDM) port could not be initialized. The error is possibly caused by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDM-1-TDM_MB_INITFAIL: Motherboard TDM init failure:Explanation The specified time-division multiplexing (TDM) port on the system motherboard could not be initialized. The error is possibly caused by a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are specified time-division multiplexing (TDM) frame clock error 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 This debug message indicates a clock state change.
Recommended Action 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.
The following are Tag Distribution Protocol (TDP) error messages.
Error Message
%TDP-3-BAD_ADDRESS_LEN: peer [chars]; address len [dec]Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-BAD_METRIC_LEN: peer [chars]; metric len [dec]Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer. 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-BAD_MLIST_TYPE: peer [chars]; mlist_type [dec]; [chars] pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an unknown metric list type or one that is unexpected for the situation has been received from a peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-BAD_PIE: peer [chars]; unknown pie type 0x[hex]Explanation An unknown Tag Distribution Protocol (TDP) protocol information element (PIE) type has been received from a peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-BAD_PREFIX_LEN: peer [chars]; prefix len [dec]Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing a destination prefix with a bad length has been received from a peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-CONSISTENCY: [chars]Explanation An action attempted by the Tag Distribution Protocol (TDP) has encountered an unexpected condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-GENERAL: [chars]Explanation An action attempted by the Tag Distribution Protocol (TDP) implementation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-4-IDENT: cannot set chassis TDP identExplanation The Tag Distribution Protocol (TDP) requires that each chassis have a TDP identifier. An attempt to set the TDP identifier for the chassis has failed.
Recommended Action This is an informational message. As long as it must set its chassis TDP identifier, the system will periodically attempt to do so until it succeeds. If this message occurs repeatedly, copy it exactly as it appears and report it to your Cisco technical service representative.
Error Message
%TDP-5-INFO: [chars]Explanation This is an informational message generated by the Tag Distribution Protocol (TDP) implementation.
Recommended Action No action is required.
Error Message
%TDP-3-KA_NOMEMORY: Can't alloc KA PIEExplanation An attempt to allocate a buffer for a Tag Distribution Protocol (TDP) keepalive protocol information element (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 call your Cisco technical service representative for assistance.
Error Message
%TDP-3-MALFORMED_PIE: peer [chars]; format error for pie type 0x[hex]Explanation A corrupted Tag Distribution Protocol (TDP) protocol information element (PIE) has been received from a TDP peer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-4-PTCL: peer [chars], [chars]Explanation A violation of the Tag Distribution Protocol (TDP) protocol by a TDP peer has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-PTCLREAD: peer [chars], read failureExplanation An error has occurred during an attempt to read a Tag Distribution Protocol (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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-SM: unexpected event: peer [int]([chars]), state=[chars], event=[chars][chars]Explanation An operation on the state machine for a Tag Distribution Protocol (TDP) peer has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-TAGATM_BAD_RANGE: Interface [chars], Bad VPI range. Can't start a TDP sessionExplanation The virtual path identifier (VPI) range exchanged between the Tag Distribution Protocol (TDP) 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 sessionExplanation An attempt to allocate a buffer for the Tag Distribution Protocol (TDP) TAGATM virtual path identifier (VPI) or the virtual circuit identifier (VPI) 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 call your Cisco technical service representative for assistance.
Error Message
%TDP-3-UNEXPECTED_ALIST_TYPE: peer [chars]; alist_type [dec]; [chars] pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer. 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-UNEXPECTED_BLIST_TYPE: peer [chars]; blist_type [dec]; [chars] pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer. 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-UNEXPECTED_PIE: peer [chars]; unexpected pie type 0x[hex]Explanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer. 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-UNKNOWN_ALIST_TYPE: peer [chars]; alist_type [dec]; [chars] pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer. 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TDP-3-UNKNOWN_BLIST_TYPE: peer [chars]; blist_type [dec]; [chars] pieExplanation A Tag Distribution Protocol (TDP) protocol information element (PIE) containing an address list type that is unexpected for the situation has been received from a peer. 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are TestPA port adapter messages.
Error Message
%TESTPA-3-DMAERROR: bay [[dec]] dma error: [chars]Explanation A direct memory access (DMA) failure has occurred.
Recommended Action Verify 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 failedExplanation 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 offExplanation 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 the error persists, ensure that the port adapter is properly seated in the bay.
The following are Tag Forwarding Information Base (TFIB) error messages.
Error Message
%TFIB-2-BADENCAPLEN: Invalid encaps length [dec], tag size [dec], at incoming tag [chars]Explanation An unexpected operation on a Tag Forwarding Information Base (TFIB) entry for a recursive route has occurred, or an adjacency has an invalid MAC rewrite string.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 Multiprotocol Label Switching (MPLS) Tag Forwarding Information Base (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, call 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 [int][inet], CEF entry has [dec] pathsExplanation The system has detected an invalid index while performing an action on the Tag Forwarding Information Base (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, call 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, call 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 Tag Forwarding Information Base (TFIB).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TFIB-2-MEMORY: No memory for [chars]Explanation An operation on the Tag Forwarding Information Base (TFIB) has failed because of insufficient free memory.
Recommended Action Reduce other system activity if possible. If this message persists, call your Cisco technical service representative for assistance.
Error Message
%TFIB-7-NONDB: Null ndb value passed to TFIB [chars]Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TFIB-7-NOPATH: No fib_path at index [dec] for [int][inet]Explanation An unexpected operation on the Tag Forwarding Information Base (TFIB) has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TFIB-7-NULLFIB: Programming error: NULL cef entry pointer passed to tfib codeExplanation An unexpected operation on the Tag Forwarding Information Base (TFIB) has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TFIB-7-NULLPATH: NULL fib path value passed to TFIBExplanation An unexpected operation on the Tag Forwarding Information Base (TFIB) has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TFIB-7-NULLREWRITE: NULL tag rewrite pointer value passed to TFIB for deletionExplanation An unexpected operation on the Tag Forwarding Information Base (TFIB) has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TFIB-7-RESOLUTION: Temporarily unable to resolve TFIB loadinfo entry [dec] for [int][inet], fib has [dec] pathsExplanation A temporary difference has occurred between the Cisco Express Fowarding (CEF) database and the Tag Forwarding Information Base (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, call 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 Tag Forwarding Information Base (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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are PCI/TI1570-based ATM port adapter error messages.
Error Message
%TI1570-5-BADVCSETUP: ti1570_vc_setup failed. (vci [dec] of the last vpi [dec] exceeds (vc-per-vp - 3)).Explanation The TI1570 chip reserves 3 RX DMA channels for OAM cells. As a result, the last 3 virtual circuit identifiers (VCIs) of the last VPI block cannot be used for regular traffic.
Recommended Action Avoid trying combinations of different virtual circuit identifiers (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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-1-DEVICEINITFAIL: PCI configuration for [chars] in slot [dec]Explanation The ATM port adapter has failed to complete hardware initialization. This error should not be a recurring condition.
Recommended Action Reset the adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-DISCOVER: Found [dec] out of [dec] devices (ID [hex]) in bay [dec]Explanation The ATM-PCI port adapter software driver has 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-FAILSETUPVC: Interface [chars], Failed to setup vc [dec] (Cause: [chars])Explanation This error probably indicates a hardware failure in the ATM-PCI port adapter.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-FAILTEARDOWNVC: Interface [chars], Failed to down vc [dec] (Cause: [chars])Explanation An ATM virtual circuit could not be shut down for the reason shown in the error message 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-7-FRAMERINT: TI1500 framer interrupt isr1 0x[hex], isr2 0x[hex], isr3 0x[hex]Explanation The ATM-PCI port adapter driver 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 should not be a recurring condition.
Recommended Action Reset the adapter. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-1-INVALIDCONFIG: VIP only supports one PA-A1 ATM LITE PA. The other PA bay must be emptied in order for the PA-A1 ATM LITE PA to function.Explanation The bandwidth requirements for the installed port adapters exceed the rated capability of the processor.
Recommended Action Remove one of the port adapters or upgrade the Versatile Interface Processor (VIP).
Error Message
%TI1570-3-NOPCIMB: TI1570 unit [dec]: PCI mini buffer unavailable.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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-NOPCIMEMORY: TI1570 unit [dec]: PCI memory unavailable.Explanation The system 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-NOSYSMEMORY: TI1570 unit [dec]: SYSTEM memory unavailable.Explanation Memory exhaustion has occurred in the ATM-PCI port adapter driver.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-NOTTI1570: Bay [dec] device ID seen as [hex], expected [hex]Explanation The ATM-PCI port adapter driver could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-NOTXDESCSPACE: [chars] No tx buffer descriptor space in particle, data block 0x[hex], data start 0x[hex]Explanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-PCI_PERROR: TI1570 unit [dec]: PCI parity error (0x[hex])Explanation A parity error 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-PLXNOTFOUND: Bay [dec] device ID seen as [hex], expected #[hex]Explanation The ATM-PCI port adapter driver 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-RBDCORRUPT: TI1570: received corrupted shadow particle pointerExplanation The ATM-PCI port adapter driver has experienced an internal error that was caused by software or hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-RXDMANOTINACT: RX DMA entry [hex] not going inactiveExplanation A direct memory access (DMA) channel has failed to deactivate during the shutdown of a virtual circuit. This failure error could indicate either a hardware or software failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-RXFREEZE: [chars] receive freeze [dec]Explanation This message indicates that excessive traffic congestion on the ATM interface may 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 error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-RX_HALT: TI1570 unit [dec]: Receive Channel HaltExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-TXDATANOTALIGNED: [chars] tx buffer data start not aligned to 32 bit boundary, data block0x[hex], data start 0x[hex]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-TXDMANOTFLUSHED: TX DMA not flushedExplanation A transmit direct memory access (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, call 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 error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TI1570-3-UNSUPPORTED: Interface [chars], [chars] not supportedExplanation 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.
The following are Tag Information Base (TIB) error messages.
Error Message
%TIB-3-GENERAL: [chars]Explanation An action attempted by the Tag Information Base (TIB) implementation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIB-3-INIT: Cannot allocate TIBExplanation During initialization for tag switching, an attempt to allocate the Tag Information Base (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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIB-3-LCLTAG: [int]/[int], [chars]; unexpected tag state=[dec]Explanation An operation on the Tag Information Base (TIB) involving a locally assigned (incoming) tag has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIB-3-RADIXTREE: [int]/[int]; [chars]Explanation An operation on the Tag Information Base (TIB) data structure has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIB-3-REMOTETAG: [int]/[int], peer [chars]; tag [dec]; [chars]Explanation An operation on the Tag Information Base (TIB) involving a tag assigned by a TDP peer has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIB-3-SM: Unexpected event; state=[chars], event=[chars]Explanation An operation on the Tag Information Base (TIB) state machine has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIB-3-TIBREVNUMWRAP: TIB revision number wrapped; toggling dynamic tag switching off and on to recover.Explanation The Tag Information Base (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.
The following are error-correcting code (ECC) and parity-related error messages.
Error Message
%TIGER-3-BADADDR_MBE: Invalid MBE dram address: 0x[hex] latched by TigerExplanation The address latched by the Tiger when detecting an MBE is not a valid DRAM address. This kind of error is not one that the Tiger should report under its normal operating conditions. When this error occurs, it 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-3-BADADDR_MBE_RMW: Invalid MBE dram address: 0x[hex] latched by Tiger during a RMW cycleExplanation The address latched by the Tiger when detecting an MBE during a read-modify-write cycle is not a valid DRAM address. This kind of error is not one that the Tiger should report under its normal operating conditions. When this error occurs, it 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-3-BADADDR_SBE: Invalid SBE dram address: 0x[hex] latched by TigerExplanation The address latched by the Tiger when detecting a SBE is not a valid DRAM address. This kind of error is not one that the Tiger should report under its normal operating conditions. When this error occurs, it 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-2-MBE: Multiple bit error detected at 0x[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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-2-MBE_RMW: Multiple bit error detectedExplanation A multibit uncorrectable error has been detected during a read-modify-write cycle on a CPU read from DRAM for a non-8-byte access.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-2-PARITY: Parity error on CPU write to address: 0x[hex]Explanation Bad parity on data 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, call 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 following byte(s) of a double word: [chars] [chars] [chars]Explanation This message indicates which bytes of a 64 bit word had bad parity that caused the Tiger to generate an interrupt.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-3-SBE: Single bit error detected and corrected at 0x[hex]Explanation A single-bit correctable error was detected on a read from the DRAM. To dump the single-bit errors that have been logged up to this point, enter the show ecc command.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-3-SBE_HARD: Single bit *hard* error detected at 0x[hex]Explanation A single-bit uncorrectable error (hard error) was detected on a CPU read from DRAM.
Recommended Action Enter the show 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 0x[hex] on a read-modify-write cycleExplanation A single-bit correctable error was detected on a CPU read from the DRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TIGER-3-SBE_RMW: Single bit error detected and corrected atExplanation A single-bit correctable error was detected and corrected during a read-modify-write cycle on a CPU read from the DRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, enter the show ecc command to dump the single-bit errors that have been logged up to this point.
Error Message
%TIGER-3-SBE_RMW_LIMIT: Single bit error detected and correctedExplanation A single-bit correctable error was detected and corrected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information. If possible, enter the show ecc command to dump the single-bit errors that have been logged up to this point.
Error Message
%TIGER-3-SYNDROME: 8-bit Syndrome for the detected Multibit error: 0x[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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are EEPROM error 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TLV-3-UPDATE: Unable to write type [dec]Explanation An attempt to update an EEPROM entry has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are inbound terminal port queueing (TMQ) error messages.
Error Message
%TMQ-3-NOTFOUND: TMQ, Attempt to delete entry not in queueExplanation An attempt was made to delete an entry that was not in the queue.
Recommended Action No action is required.
The following are Telnet error 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, call 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, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are TN3270 error messages that are related to the TN3270 protocol, a variation of the IBM virtual terminal (VT) protocol.
Error Message
%TN3270-2-INP_OVF1: Input Buffer overflowExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Token Ring (TR) error 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, call 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, call your Cisco technical support representative for assistance.
Error Message
%TR-3-BADBRDGPARMS: Unit [dec], bad bridge parameters: bridge_num=[dec], max_rd=[dec]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. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-BADBUFFSIZE: Unit [dec], bad buffersize = [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. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-BADFIRM: Unit [dec], Tokenring firmware download failedExplanation 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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-BADFUNC: Unit [dec], bad functional address=0x[hex], ring mode=0x[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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-BADMUL: [chars]: Can't set address to a multicast ([sci_notation])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 Token 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-DIAGFAIL: Interface [chars] failed init diags (0x[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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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 media attachment unit (MAU) and try to open the interface again by entering the clear interface tokenring command. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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, call 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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-2-PANICTYPE: Unit [dec], [chars] errorExplanation 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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-RESETFAIL: Unit [dec], reset failed, error code [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, call 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 source routing accelerator (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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TR-3-SETFUNFAIL: Unit [dec], set functional address failed (code [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, call 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 Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%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.
Recommended Action Check the Token Ring for the indicated condition.
| Code | Explanation | Fatal |
|---|---|---|
0x8000 | Signal loss | Yes |
0x4000 | Hard error | Yes |
0x2000 | Soft error | No |
0x1000 | Transmit beacon | Yes |
0x0800 | Lobe wire fault | Yes |
0x0400 | Auto-removal error | Yes |
0x0100 | Receive request removed | Yes |
0x0080 | Counter overflow | No |
0x0040 | Single station | No |
0x0020 | Ring recovery | No |
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 media attachment unit (MAU).
The following are E1/T1 trunk card error messages.
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 into the port or 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, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
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, call 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, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TRUNK-3-NOMSGS: Cannot send message to framer; no more messages availableExplanation The memory buffer for messages 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are tag-switched path (TSP) error messages.
Error Message
%TSP-3-CAPABILITYMISMATCH: voice port [chars]: call connection id [0x[hex] 0x[hex] 0x[hex] 0x[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 ensure that the configuration on the interface is correct.
Error Message
%TSP-3-DSPALARM: voice port [chars]: status=0x[hex] message=0x[hex]Explanation The digital signal processor (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, call 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, call 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 messageExplanation There were no event structures remaining in the system pools to alert the router of a voice or signalling 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 Primary Rate Interface (PRI) signalling channel has been added to or deleted from the tag-switched path (TSP) inventory of signalling channels.
Recommended Action No action is required.
The following are tty-related error messages for all platforms.
Error Message
%TTY-3-AUTOCONFIG: TTY[t-line]: Modem auto-configuration failedExplanation Modem autoconfiguration has failed either because the modem rejected the configuration string or because of a timeout.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TTY-3-NOPROCESS: Cannot create [chars] processExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are router shelf asynchronous driver error messages.
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, call your Cisco technical support representative, and provide the representative with the gathered information.
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, call 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 and left 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%TTYDRIVER-3-RTSLOW: RTS is deasserted though rx queue is emptyExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are tunnel error messages.
Error Message
%TUN-5-RECURDOWN: [chars] temporarily disabled due to recursive routingExplanation 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.
The following are Cisco Transaction Connection (CTRC) error 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 feature module Configuring Cisco Transaction Connection for more 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 Cisco Transaction Connection (CTRC) server was rejected by the remote database server.
Recommended Action Contact your Systems Network Architecture (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 logical unit (LU) configured for the txconn server is incorrect.
Recommended Action Contact your Systems Network Architecture (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 [int] connected to server [chars] has timed out after %TE.Explanation The client was idle for too long, and the idle timeout configured for the Cisco Transaction Connection (CTRC) server has expired.
Recommended Action No action is required.
Error Message
%TXCONN-3-INVALIDTRANS: Bad Transaction ID, flushing out request for client [int] connected server [chars], killing connection.Explanation An invalid input stream was detected and ignored.
Recommended Action No action is required.
Error Message
%TXCONN-3-NOSESSION: Out of resource, cannot create transaction for client [int] 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 [int] 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 Customer Information Control System (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 Customer Information Control System (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 [int] connected to server [chars] has timed out after %TE.Explanation The transaction was idle for too long, and the idle timeout configured for the Cisco Transaction Connection (CTRC) server has expired.
Recommended Action No action is required.
Error Message
%TXCONN-3-TXEXCEPTION: error has occurred from transaction [hex] of client [int] connected to server [chars], exception type is [dec]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, call 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 [int] connected server [chars].Explanation An invalid input stream was detected and ignored.
Recommended Action No action is required.
The following are cable modem termination system error messages.
Error Message
%UBR7200-5-AUTHFAIL: Authorization failed for Cable Modem [sci_notation] on interface [chars]Explanation The registration of the cable modem has failed because of an invalid media interface connector (MIC) string.
Recommended Action Ensure that the shared secret in the configuration file matches the shared secret configured in the cable modem.
Error Message
%UBR7200-3-BADARPREPLY: Interface [chars], ARP reply from invalid source. Expected SID=[dec], Actual SID=[dec]Explanation A spoofing attempt might have been detected.
Recommended Action Look for a possible spoofing attempt.
Error Message
%UBR7200-3-BADARPREQUEST: Interface [chars], ARP request from invalid source. IP=[int], MAC=[sci_notation],Explanation A spoofing attempt might have been detected.
Recommended Action Look for a possible spoofing attempt
Error Message
%UBR7200-3-BADIPSOURCE: Interface [chars], IP packet from invalid source. IP=[int], MAC=[sci_notation], Expected SID=[dec], Actual SID=[dec]Explanation A spoofing attempt might have been detected.
Recommended Action Look for a possible spoofing attempt
Error Message
%UBR7200-3-BADUSPORT: Interface [chars] Port U[dec] invalid, highest port number is U[dec]Explanation The upstream port number is invalid.
Recommended Action Reenter the command using a valid upstream port number.
Error Message
%UBR7200-4-BADTXOFFSET: Bad timing offset %ld detected for cable modem [sci_notation].Explanation The cable modem is not using the correct starting offset during initial ranging, causing a zero, negative timing offset to be recorded by the cable modem termination system (CMTS) for this modem. The CMTS internal algorithms that rely on the timing offset parameter will exclude from analysis any modems that do not use the correct starting offset. The modems may not be able to function, depending on their physical location on the cable plant.
Recommended Action Locate the cable modem based on the MAC address and report the initial timing offset problem to the cable modem vendor.
Error Message
%UBR7200-5-BADMNCSMSG: Invalid DOCSIS Message received from a Cable Modem for interface [chars]Explanation A cable modem has attempted to send a Data-Over-Cable Service Interface Specifications (DOCSIS) message.
Recommended Action Replace the cable modem with a DOCSIS-compliant modem.
Error Message
%UBR7200-3-BURSTINUSE: Can not remove Burst Profile. Burst Profile is in useExplanation The currently defined modulation profiles use the specified burst profile, and therefore it cannot be removed.
Recommended Action Remove any modulation profiles that use this burst profile, and then reenter the command.
Error Message
%UBR7200-3-CHASSIS: Unknown chassis model.Explanation Data stored in the midplane is corrupted or incomplete.
Recommended Action Contact a Cisco technical support representative to update your system.
Error Message
%UBR7200-5-CLASSFAIL: Registration failed for Cable Modem [sci_notation] on interface [chars]: [chars]Explanation The registration of the specified modem has failed because of an invalid or unsupported class-of-service setting.
Recommended Action Ensure that the class-of-service fields in the configuration file are set correctly.
Error Message
%UBR7200-6-CMMOVED: Cable modem [sci_notation] has been moved from interface [chars] to interface [chars].Explanation The cable modem has been detected on a new interface.
Recommended Action No action is required.
Error Message
%UBR7200-3-CONFIG: Exceeds [dec] [chars]Explanation The total bandwidth of fast and medium bandwidth port adapters exceeds the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
Error Message
%UBR7200-4-COOKIE: Corrupt or missing MAC address cookieExplanation Data stored in the midplane is defective.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message
%UBR7200-0-CPUCARD: CMTS([dec]/[dec]), Init failed, CSR[dec]=0x[hex].Explanation A hardware failure involving the line card has occurred.
Recommended Action Replace the defective line card.
Error Message
%UBR7200-1-DISCOVER: Only found [dec] interfaces on bay [dec], shutting down bayExplanation A system or hardware failure involving the line card has occurred.
Recommended Action Replace the defective line card.
Error Message
%UBR7200-4-DUPLICATEMAC: Cable modem [sci_notation] is online on both interface [chars] and interface [chars].Explanation The cable modem has been detected on two interfaces. This message indicates that two cable modems are using the same MAC address.
Recommended Action Check for cable modems with duplicate MAC addresses and reassign a unique MAC address to one of the cable modems.
Error Message
%UBR7200-3-INTERCEPT: Interface [chars], Failed to send intercept packet to server [int]:[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. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-0-LOWPOWERCPU: uBR requires CPU card type NPE150 or higherExplanation The NPE100 CPU card is not supported in the uBR7200.
Recommended Action Upgrade the CPU card to NPE150 or higher.
Error Message
%UBR7200-4-MACBLKSIZE: Unknown MAC address block size.Explanation Data stored in the midplane is defective.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message
%UBR7200-5-MAXHOST: New host with IP address [int] and MAC [sci_notation] on SID [dec] is ignored.Explanation The maximum number of hosts on the Service ID (SID) has been exceeded. Therefore, the cable modem with the new IP address will be ignored.
Recommended Action Place the cable modem on a new SID.
Error Message
%UBR7200-4-NOCPUVER: Invalid CPU ID, assuming revision 1Explanation The CPU revision ID is invalid.
Recommended Action Update the CPU board.
Error Message
%UBR7200-3-NOFORK: Could not start Spectrum Management processExplanation 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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message
%UBR7200-3-NOMAC: Can't allocate MAC address for interface [int]/[int]Explanation The system is out of available MAC addresses.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-3-NOMEM: [chars]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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-3-NOMORESIDS: Maximum number of SIDS have been allocated for interface [chars]Explanation The maximum number of cable modems are allocated to the specified line card.
Recommended Action Assign a cable modem to another line card.
Error Message
%UBR7200-5-NOMULTIPLEUPSTREAMS: Upstream Channel Change not valid for interface [chars]Explanation The Cisco IOS software does not support this command for this interface.
Recommended Action Use this command on a multiple upstream line card.
Error Message
%UBR7200-3-NOTCMTS: Device reported [hex]Explanation A hardware failure involving the specified device has occurred.
Recommended Action Replace the defective hardware.
Error Message
%UBR7200-5-NOTIMPLMENTEDMNCSMSG: Not implemented DOCSIS MESSAGE received from a Cable Modem for interface [chars]Explanation This cable modem does not support the type of message specified in the error message string. The system may be connected to a noncompliant modem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-3-NULLMAPPTR: Cannot send maps as current_map ptr is NULL,Explanation An internal software error has occurred. This error may have been caused by a memory problem.
Recommended Action Check the available memory. If necessary, add more memory to the system.
Error Message
%UBR7200-3-OVERLAPIP: Interface [chars], IP address [int] from MAC [sci_notation] is already in use. SID = [dec]Explanation A spoofing attempt may have been detected.
Recommended Action Look for a possible spoofing attempt.
Error Message
%UBR7200-5-OVERLIMIT: Interface [chars] Current total reservation of [dec] bps on Port U[dec], exceeds its maximum configured reservation limit of [dec] bps.Explanation The currently reserved capacity on the upstream channel already exceeds its virtual reservation capacity, based on the configured subscription level limit. Increasing the subscription level limit on the current upstream channel will place you at risk of being unable to guarantee the individual reserved rates for modems since this upstream channel is already oversubscribed.
Recommended Action Load-balance the modems that are requesting reserved upstream rate on another upstream channel.
Error Message
%UBR7200-3-OWNERR: CMTS([dec]/[dec]), Buffer ownership error, pak=0x[hex].Explanation A hardware failure involving a board has occurred.
Recommended Action Replace the defective board.
Error Message
%UBR7200-6-PREAMLENADJUST: [chars] burst's preamble length in modulation profile [dec] is adjusted to the operable value.Explanation The preamble length in the burst profile has been adjusted to the valid value.
Recommended Action No action is required.
Error Message
%UBR7200-4-RECALLED_NPE: Old version NPE-175/225 with Rev = 0x[hex] system controller. Contact upgrades-info@cisco.com for replacementExplanation An NPE-175/225 board has been recalled because of an error in the system controller chip.
Recommended Action Replace the NPE-175/225 board.
Error Message
%UBR7200-3-SLOTS: Number of slots in chassis is undefined.Explanation Data stored in the midplane is corrupted or incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message
%UBR7200-3-SPIERRNRD: SPI PENDING NO READ DATA([chars]): spistat=0x[hex], chid=0x[hex], cmd=0x[hex], regaddr=0x[hex]Explanation A read error on the PHY chip serial communications bus has occurred. This condition indicates a defective line card.
Recommended Action Replace the defective line card.
Error Message
%UBR7200-3-SPIERRR: SPI PENDING READ ERROR([chars]): spistat=0x[hex], chid=0x[hex], cmd=0x[hex], regaddr=0x[hex]Explanation A read error on the PHY chip serial communications bus has occurred. This condition indicates a defective line card.
Recommended Action Replace the defective line card.
Error Message
%UBR7200-3-SPIERRRBS: SPI BUS READ 0x[hex] BYTES SHORT([chars]): spistat=0x[hex], chid=0x[hex], cmd=0x[hex], regaddr=0x[hex]Explanation A read error on the PHY chip serial communications bus has occurred. This condition indicates a defective line card.
Recommended Action Replace the defective line card.
Error Message
%UBR7200-3-SPIERRW: SPI PENDING WRITE ERROR([chars]): spistat=0x[hex], chid=0x[hex], cmd=0x[hex], regaddr=0x[hex]Explanation A write error on the PHY chip serial communications bus has occurred. This condition indicates a defective line card.
Recommended Action Replace the defective line card.
Error Message
%UBR7200-3-SPIERRW_CHID: Invalid Channel ID([chars]): chid=0x[hex], cmd=0x[hex], regaddr=0x[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 may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-0-TEMPHIGH: [chars] measured at [chars] is too high: shutdown temperature [chars]Explanation The current temperature exceeds the maximum shutdown temperature.
Recommended Action Determine the cause of the high temperature and correct it if possible.
Error Message
%UBR7200-5-TIMESCH: Time scheduled event, spectrum group [int], [chars]Explanation A time-scheduled reconfiguration event has occurred on the specified interface.
Recommended Action No action is required.
Error Message
%UBR7200-5-TRAFSHAPBADTIMER: Bad timer expiry in downstream traffic shaper process, Timer [hex]Explanation An invalid timer expiration in the downstream traffic shaping process has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-5-TRAFSHAPNOCREAT: Unable to create downstream traffic shaping queuesExplanation An attempt to create downstream traffic shaping queues has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-5-TRAFSHAPPROCFAIL: Unable to fork downstream shaper processExplanation An attempt to fork the downstream traffic shaping process has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%UBR7200-5-UNAUTHSIDTIMEOUT: CMTS deleted BPI unauthorized Cable Modem [sci_notation]Explanation An unauthorized cable modem has been deleted.
Recommended Action Check the modem interface configuration for privacy mandatory and check for errors in the Trivial File Transfer Protocol (TFTP) configuration file.
Error Message
%UBR7200-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem [sci_notation]Explanation An unregistered cable modem has been deleted to avoid unaccounted bandwidth usage.
Recommended Action Check the cable modem configuration for registration bypass, and check for errors in the Trivial File Transfer Protocol (TFTP) configuration file.
Error Message
%UBR7200-5-UPDOWN: Interface [chars] Port U[dec], changed state to [chars]Explanation The upstream port was brought up or down.
Recommended Action No action is required.
Error Message
%UBR7200-5-USCONTEND: Interface [chars] Port U[dec], continuous frequency hop ended at [int].%03u MHzExplanation At least one cable modem has come back online. This message logs the abortion of continuous frequency hop.
Recommended Action No action is required.
Error Message
%UBR7200-5-USCONTHOP: Interface [chars] Port U[dec], continuous frequency hop startedExplanation All cable modems have gone offline. This message logs the start of continuous frequency hop.
Recommended Action No action is required.
Error Message
%UBR7200-5-USFREQCHG: Interface [chars] Port U[dec], frequency changed to [int].%03u MHzExplanation The upstream channel frequency has been changed.
Recommended Action No action is required.
Error Message
%UBR7200-5-USIPLCHG: Interface [chars] Port U[dec], input power level changed to [dec] dBmVExplanation The upstream channel input power level has been changed.
Recommended Action No action is required.
Error Message
%UBR7200-5-USIPLFIX: Interface [chars] Port U[dec], input power level fixed at [dec] dBmVExplanation Setting the upstream frequency to a fixed value has caused the upstream input power level to assume a fixed value.
Recommended Action No action is required.
Error Message
%UBR7200-4-VERSION_MISMATCH: Midplane data version mismatch.Explanation Data stored in the midplane is out of date and requires an update.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message
%UBR7200-0-VOLTHIGH: [chars] measured at [chars] is too high: shutdown voltage [chars]Explanation The current voltage exceeds the maximum shutdown voltage.
Recommended Action Determine the cause of the high voltage and correct it if possible.
Error Message
%UBR7200-0-VOLTLOW: [chars] measured at [chars] is too low: shutdown voltage [chars]Explanation The current voltage exceeds the minimum shutdown voltage.
Recommended Action Determine the cause of the low voltage and correct it if possible.
Posted: Fri Jun 16 11:54:49 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.