-
Cisco IOS System Error Messages, Volume 1 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
AT through BERT
-
BGP through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBCONN
-
DBUS through DSCREDCLK
-
DSC_REDUNDANCY through ENT_API
-
ENVM through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFS through ISA
-
ISDN through LCCOREDUMP
-
LCFE through MBRI
-
MBUS through MODEM
-
MODEMCALLRECORD through NSP
-
Glossary of Acronyms
-
Table Of Contents
DSC_REDUNDANCY Messages
The following are Cisco AS5800 dial shelf controller redundancy error messages.
Error Message%DSC_REDUNDANCY-3-MODECONFLICT : Other DSC/router in split mode
Explanation There is another router connected to the dial shelf. In this situation, both routers must be configured in split mode.
Recommended Action Configure the other router in split mode.
Error Message%DSC_REDUNDANCY-3-SLOTCONFLICT : Slot ownership conflict detected for slot [dec]
Explanation Another router that is connected to the dial shelf is claiming ownership of a slot that this router is also claiming.
Recommended Action Resolve the ownership conflict by reconfiguring one of the routers so that it does not own the slot.
Error Message%DSC_REDUNDANCY-3-TDMSPLITCONFLICT : Tdm Split conflict detected,my tdm [dec], other rs [dec]
Explanation Another router connected to the dial shelf is claiming ownership of backplane time slots that this router requires. This error is likely caused by OIR activity that is moving trunk cards from one half of the split to the other.
Recommended Action Resolve the ownership conflict by reloading the router that has a TDM number greater than the trunk capacity for that router. In some situations, it may be necessary to reset both routers.
DSI Messages
The following are Cisco AS5800 dial-shelf interconnect (DSI) board error messages.
Error Message%DSI-3-AGENTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation An internal software error has occurred. The software detected an invalid state change for the MBus agent of the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSI-3-AGENTSTSCHNG : From [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software has detected an MBus agent state change for the specified slot.
Recommended Action No action is required.
Error Message%DSI-2-BADPORT : Out of range PCI port [dec]
Explanation An internal software error has occurred. The software specified an out-of-range port on the dial shelf interconnect board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSI-3-EVENT : Unknown event [dec] for slot [dec]
Explanation An internal software error has occurred. The software has generated an unknown event for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSI-3-SLOTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation An internal software error has occurred. The software detected an invalid state change for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSI-3-SLOTSTSCHNG : From [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software has detected a state change for the specified slot.
Recommended Action No action is required.
DSIP Messages
The following are distributed system interconnect protocol (DSIP) error messages.
Error Message%DSIP-3-IPC_CLIENT : IPC subsystem API error([chars]), [chars], [dec]
Explanation A problem has occurred with the NIP reliable stack. The exact problem can be decoded further by the IPC error message (first parameter), the action involved (second parameter), and the client ID (third parameter).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSIP-3-IPC_PORT : IPC subsystem API error([chars]), [chars], [chars]
Explanation The NIP has encountered a problem with the port specified in the error message. The exact problem can be decoded further by the IPC error message (first parameter), the action involved (second parameter), and the port name (third parameter).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSIP-3-IPC_SEAT : IPC subsystem API error, can not create seat by
the seatid [dec] for the slot [dec]Explanation The NIP reliable stack has failed to create a seat for the specified slot.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DSIPPF Messages
The following are Nitro Interconnect Protocol error messages.
Error Message%DSIPPF-3-DSIP_SEND_FAILURE : Failed to send DSIP message - number of failures [dec]
Explanation The NIP encountered an error when it sent a message, and the message has been discarded after three unsuccessful resends.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DS_MODEM Messages
The following are feature board (FB) modem card error messages.
Error Message%DS_MODEM-3-BADCB : Unexpected DSIP data callback for modem
Explanation An unexpected software event has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-FLOW_CONTROL : DS-RS flow control has got out of sync, connection has too many particles free. slot:[dec] ttynum:[dec] parts_avail:[dec]
Explanation The flow control accounting on the DS has gotten out of synchronization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-LOW_PARTICLES : Not enough particles - modem number:[dec] particles needed:[dec] available:[dec]; CTS [chars]
Explanation A breakdown of flow control between the RS and the DS has occurred. The RS has sent more particles than are available for this connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-NORXPAK : Static receive paktype unavailable
Explanation A software structure was found in an unexpected state during run time for the indicated modem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_MODEM-3-OUTPUT_DROP : Output drop - modem number:[dec] refunded [dec]; particle count [dec], pool size [dec], queue size [dec]
Explanation The system was unable to allocate particles for sending traffic to the modem module, indicating a breakdown of flow control between the RS and DS.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DSPDD Messages
The following are Digital Signal Processor Device Driver (DSPDD) error messages.
Error Message%DSPDD-1-DSPFWFAILURE : DSPDD internal firmware error[[chars]:[dec]
Explanation The router or access server has detected an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-INTERNALERROR : DSPDD internal error[[chars]:[dec]
Explanation The router or access server has detected an internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-NOBUFFERS : IOS buffer pool unavailable [[chars]:[dec]]
Explanation The router or access server could not allocate internal resources.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-NOIOSBUFFERS : IOS buffer pool unavailable [[chars]:[dec]]
Explanation The router or access server could not allocate internal resources.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-NOIOSMEMORY : IOS memory unavailable [[chars]:[dec]]
Explanation The router or access server could not allocate memory for internal data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPDD-1-NOMEMORY : IOS memory unavailable [[chars]:[dec]]
Explanation The router or access server could not allocate memory for internal data structures.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DSPRM Messages
The following are Digital Signal Processor Device Driver (DSPDD) error messages.
Error Message%DSPRM-5-DSPFAIL : DSP [dec] in slot [chars], is in the failed state
Explanation The DSP entered the FAILED state because of alarm indications.
Recommended Action Replace the DSP resource.
Error Message%DSPRM-3-INSUFFICIENT : Insufficient DSP resources for timeslot [dec] on port [chars]
Explanation The configuration requires more DSP resources than are available.
Recommended Action Change the configuration to specify fewer used time slots. Install additional DSP resources to allow for more complex configurations.
Error Message%DSPRM-5-JUKEBOX : Jukebox transmit overlay resp [dec] on slot [chars], failed
Explanation The jukebox received a FAILED response code.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPRM-5-JUKEBOX_UPDOWN : DSP Jukebox([dec]) in slot [chars], changed state to [chars]
Explanation The DSP jukebox has changed state.
Recommended Action No action is required.
Error Message%DSPRM-5-KEEPALIVE : DSP [dec] in slot [chars], NOT RESPONDING - auto restart([dec] times)
Explanation The DSP has failed the background keepalive test.
Recommended Action No action is required.
Error Message%DSPRM-5-SETCODEC : Configured codec [dec] is not supported with this dsp image.
Explanation Codec negotiation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPRM-5-UPDOWN : DSP [dec] in slot [chars], changed state to [chars]
Explanation The DSP resource has changed state.
Recommended Action No action is required.
DSPU Messages
The following are downstream physical unit (DSPU) error messages.
Error Message%DSPU-3-ActpuNegResponse : ACTPU Neg rsp received from PU [chars]
Explanation The remote PU has rejected the request from the router for an SSCP-PU session.
Recommended Action Verify the PU configuration parameters at the router and at the remote PU. Determine whether the problem exists at the remote PU, and if so, correct it. If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadAdptCorr : CLSI bad Adaptor correlator, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadIdentifier : CLSI bad identifier, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadIdentifierType : CLSI bad identifier type, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadLength : CLSI bad length, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadPrimitiveCmd : CLSI bad primitive command, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadPrimitiveType : CLSI bad primitive type, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIBadReturnCode : CLSI bad return code: [dec], header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIUnexpctActSapCnf : CLSI unexpected ActivateSapCnf, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIUnexpctDeactSapCnf : CLSI unexpected DeactivateSapCnf, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIUnexpctEnableCnf : CLSI unexpected EnableCnf, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-CLSIUnexpctIdStnInd : CLSI unexpected IdStnInd, header= [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-DSPU_BufferCorrupted : DSPU could not free buffer - buffer corrupted
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-LSConnInFailed : Connect in from remote address [chars] failed.
Explanation A connection with the remote station could not be established.
Recommended Action Verify the configuration parameters at the router and at the remote station. Determine whether the router is configured to accept connections from this remote station.
Error Message%DSPU-3-LSConnInFailedNoMem : Connect in from remote address [chars] failed; insufficient memory.
Explanation A connection with the remote station could not be established because of insufficient memory in the router.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%DSPU-3-LSConnInFromHostFailed : Connect in from host [chars] with remote address [chars] failed.
Explanation A connection with the remote host could not be established.
Recommended Action Verify the host configuration parameters at the router and at the host. Determine whether the router is configured to accept connection from this host.
Error Message%DSPU-3-LSConnInFromPuFailed : Connect in from pu [chars] with remote address [chars] failed.
Explanation A connection with the remote PU could not be established.
Recommended Action Verify the PU configuration parameters at the router and at the remote PU. Determine whether the router is configured to accept a connection from this remote PU.
Error Message%DSPU-3-LSConnOutToHostFailed : Connect out to host [chars] failed.
Explanation A connection with the remote host could not be established.
Recommended Action Verify the host configuration parameters at the router and at the host. Determine whether the host is active and responding to connection requests.
Error Message%DSPU-3-LSConnOutToPuFailed : Connect out to pu [chars] failed.
Explanation A connection with the remote PU could not be established.
Recommended Action Verify the PU configuration parameters at the router and at the remote PU. Determine whether the remote PU is active and responding to connection requests.
Error Message%DSPU-3-LSInvalidMaxIFrame : Connection attempt failed from XID= [chars], Invalid MaxIFrame= [dec]
Explanation An invalid MaxIFrame value in an XID was received from the remote station; connection with the remote station could not be established.
Recommended Action Correct the link-station configuration at the remote station.
Error Message%DSPU-3-LSInvalidWindowSize : Connection attempt failed from XID= [chars], Invalid WindowSize= [dec]
Explanation An invalid WindowSize value in an XID was received from the remote station; connection with the remote station could not be established.
Recommended Action Correct the link-station configuration at the remote station.
Error Message%DSPU-3-LSNoACTPUCapability : Connection attempt failed from XID= [chars], ACTPU not supported
Explanation The remote station did not request PU 2.0 activation; connection with the remote station is terminated.
Recommended Action Correct the link-station configuration parameters at the remote station to request an SSCP-PU session with the router.
Error Message%DSPU-3-LSXIDNegotiationError : XID Negotiation Error, bad byte= [dec], bad bit= [dec], sense data= [chars]
Explanation An XID3 with an error indication was received from the remote station; connection with the remote station could not be established.
Recommended Action From the CV 22 byte or bit information, determine which field in the XID3 is rejected by the remote station, and correct the link-station configuration parameters at either the router or the remote station.
Error Message%DSPU-3-NotifyNegRsp : LU [dec] received a Notify Neg Resp from host [chars]
Explanation The remote host rejected the request from the router to activate or deactivate an SSCP-LU session.
Recommended Action Verify the host configuration parameters at the router and at the remote host. Determine whether the problem exists at the remote host and, if so, correct it. If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-SnaBadData : Bad SNA data received from PU [chars], data= [chars]
Explanation Unrecognized SNA data was received from the remote PU.
Recommended Action Correct the problem at the remote PU. If the problem persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSPU-3-UnknownXid : XID Format not supported, XID= [chars]
Explanation Unsupported XID was received from the remote station. A connection with the remote station could not be established.
Recommended Action Configure the remote station to send supported XID (if possible). Supported XID formats are XID Format 0 XID Format 3.
DS_TDM Messages
The following are dial shelf time-division multiplexing (TDM) error messages.
Error Message%DS_TDM-3-ASSERT_FAIL : Slot [dec]: Assertion failed: file `[chars]', line [dec]
Explanation An internal sanity check has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-ATTACH_ERR : Slot [dec]: tried but failed to set COMBO_SELECT bit on [chars] FB; cannot attach to backplane
Explanation The TDM subsystem could not configure the FB to attach to the backplane in the manner desired. The FB is defective.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_CONN : Slot [dec]: unrecognized TDM connect message received ([dec]) on [chars] feature board
Explanation An unrecognized TDM connect message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_DISCONN : Slot [dec]: unrecognized TDM disconnect message received ([dec]) on [chars] feature board
Explanation An unrecognized TDM disconnect message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_DSIP : Slot [dec]: unrecognized DSIP message received ([dec]) on [chars] feature board
Explanation An unrecognized DSIP message has been received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_MAPPING : Slot [dec]: Legacy FB ([chars]), with static port-to-DS0 mapping, was passed dynamic mapping info
Explanation A software error has caused dynamic port-to-DS0 mapping information to be passed to a statically mapped FB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-BAD_S4_POWER_UP : Slot [dec]: [chars] powered-up with one or more incorrect default settings([chars])
Explanation The specified S4 ASIC did not power up with some of the default settings expected by the software. Therefore, the integrity of the TDM data could have been compromised.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONN_FAILED : Slot [dec]: handling of sub-msg ([dec]/[int]/[int]/[int]/[int]/[int]) [int] of [int] failed; processing of rest of DSIP msg aborted
Explanation The processing of a submessage encapsulated within a DSIP TDM_CONNECT message has failed. Any remaining submessages with in the DSIP message were not processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONV_CLOSE : Slot [dec]: open MT8986 (addr: [hex]) connection failed - STo[dec], CHo[dec]
Explanation An attempt to disable a rate-converted connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-CONV_OPEN : Slot [dec]: open MT8986 (addr: [hex]) [chars] connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]
Explanation An attempt to establish a rate-converted connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-DISC_FAILED : Slot [dec]: handling of sub-msg ([dec]/[int]/[int]/[int]/[int]/[int]) [int] of [int] failed; processing of rest of DSIP msg aborted
Explanation The processing of a submessage encapsulated within a DSIP TDM_DISCONNECT message has failed. Any remaining submessages within the DSIP message have not been processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-DISC_FOR_NO_CONN : Slot [dec]: got disc msg for non-existent conn: [chars]-st[int]-ts[int]/gts>[int]><[int]</[chars]-st[int]-ts[int]
Explanation The FB has received a request to disconnect an unrecognized connection.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-NO_RECOMB_BUS_DS0 : Slot [dec]: no free Recombination bus DS0s left; connection not made
Explanation The TDM mezzanine card of the Raiko-based FB does not have any free recombination bus DS0s.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-RECOMB_BUS_TS_BAD_USE : Slot [dec]: convention broken for Mezz's Recomb. bus t'slots: [chars]-st[int]-ts[int]/gts>[int]><[int]</[chars]-st[int]-ts[int]
Explanation The usage convention has been broken for recombination bus time slots. This broken usage convention is a TDM error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-S4_INT : Slot [dec]: [chars] generated interrupt [chars]
Explanation The S4 ASIC has generated the specified interrupt message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-TDM_CLOSE : Slot [dec]: close MT90820 (addr: [hex]) connection failed - STo[dec], CHo[dec]
Explanation An attempt to disable a digitally switched connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-TDM_OPEN : Slot [dec]: open MT90820 (addr: [hex]) connection failed - STi[dec], CHi[dec], STo[dec], CHo[dec]
Explanation An attempt to establish a digitally switched connection has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-UNEXPECTED_INT : Slot [dec]: got unexpected interrupt from masked-out source '[chars]'
Explanation Although it has been masked out, an interrupt has been received from the specified source.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-UNSUPPORTED_MEZZ_VER : Slot [dec]: the detected version ([int]) of Mezzanine card is not supported by this software image
Explanation The software does not support the mezzanine card that is currently installed on the Raiko card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-VERIFY_DISCONN : Slot [dec]: [chars] failed to veryify disconnect: sto = [dec], ch_out = [dec]
Explanation An attempt to verify a TDM hardware component has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-VERIFY_HILOWMEM : Slot [dec]: [chars] failed to veryify himem, or lowmem: sto = [dec], ch_out = [dec], sti = [dec], ch_in = [dec]
Explanation An attempt to verify a TDM hardware component has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DS_TDM-3-VERIFY_IMS : Slot [dec]: [chars] failed to veryify IMS: [hex]
Explanation An attempt to verify a TDM hardware component has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DSX0 Messages
The following are CT1 RBS time slot status error messages.
Error Message%DSX0-5-RBSLINEDBUSYOUT : RBS of slot [dec] controller [dec] timeslot [dec] is dynamic busyout
Explanation RBS has been dynamically busied out on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX0-5-RBSLINEDOWN : RBS of controller [dec] timeslot [dec] is down
Explanation RBS has been disabled on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX0-5-RBSLINESBUSYOUT : RBS of slot [dec] controller [dec] timeslot [dec] is static busyout
Explanation RBS has been statically busied out on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX0-5-RBSLINEUNBUSYOUT : RBS of slot [dec] controller [dec] timeslot [dec] is unbusyout
Explanation RBS has been restored from a busied out condition on the specified time slot and controller.
Recommended Action No action is required.
Error Message%DSX0-5-RBSLINEUP : RBS of controller [dec] timeslot [dec] is up
Explanation RBS has been enabled on the specified time slot and controller.
Recommended Action No action is required.
DSX1 Messages
The following are Channelized E1 (Europe) and T1 (US) telephony standard error messages.
Error Message%DSX1-6-CLOCK_CHANGE : [chars] clock is now selected as clock source
Explanation The los, ais, or cli command was entered, causing a change to the selected clock.
Recommended Action No action is required.
Error Message%DSX1-3-FIRMWARE_RESTART : T1/E1 Firmware in slot [dec] restarted
Explanation The T1/E1 firmware has restarted. All of the active calls on the T1/E1 lines will be disconnected, and the controllers will come back up within few seconds.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-1-FIRMWARE_RESTART_FAILED : Trunk Firmware in slot [dec] reset failed
Explanation The trunk could not be restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-1-FIRMWARE_RUNNING : T1/E1 Firmware in slot [dec] is running
Explanation The T1/E1 firmware is now running after recovering from critical error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-1-FIRMWARE_STOPPED : T1/E1 Firmware in slot [dec] is not running
Explanation A critical error has occurred in the T1/E1 firmware, and it has stopped running. The access server must be reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-3-M32_AR_FAILURE : Munich 32 action request failure: Ctrl = [hex], Channel = [dec]
Explanation Munich 32 is not responding to a request.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-3-M32_AR_TIMEOUT : Munich 32 action request timeout: Ctrl = [hex], Channel = [dec]
Explanation Munich 32 is not responding to an action request.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-3-M32_BAD_BITRATE : Munich 32 bit rate not match: Ctrl = [hex], Channel = [dec]
Explanation The command cannot be carried out because of a bit rate mismatch.
Recommended Action Ensure that the configured data matches the supported speed.
Error Message%DSX1-3-M32_BAD_INTQ : Munich 32 bad interrupt queue: Ctrl = [hex], Channel = [dec]
Explanation There might be an overflow on the interrupt queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-3-M32_BAD_STATE : Munich 32 in unknown state: Ctrl = [hex], Channel = [dec]
Explanation Munich 32 has gone into an unknown state.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-3-M32_ERR : Munich 32 error configuring channelized interface: Ctrl = [hex], Channel = [dec]
Explanation Unidentified errors have occurred on Munich 32.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DSX1-3-M32_ILLEGAL_CHANNEL : Munich 32 channel invalid: Ctrl = [hex], Channel = [dec]
Explanation The channel select is not valid.
Recommended Action Ensure that the channel supports the needed feature.
Error Message%DSX1-1-M32_INPUT_CONGEST : Munich 32 channel input queue is congested
Explanation The receiver cannot allocate receive buffers because the input queue is at its maximum. Data is coming in faster than the receiver can handle.
Recommended Action Reduce the volume of data that goes into this channel or increase the number of input queues for the channel.
Error Message%DSX1-3-M32_MEM_ALLOC : Munich 32 channel memory allocation error: Ctrl = [hex], Channel = [dec]
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%DSX1-3-M32_NO_TIMESLOT : Munich 32 no timeslot available: Ctrl = [hex], Channel = [dec]
Explanation All of the time slots on Munich 32 are assigned.
Recommended Action Ensure that there are time slots available before choosing one.
Error Message%DSX1-3-M32_TIMESLOT_IN_USE : Munich 32 timeslot already configured: Ctrl = [hex], Channel = [dec]
Explanation This time slot has already been assigned and cannot be used
Recommended Action Ensure that the time slot is available before choosing it.
Error Message%DSX1-3-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.
DTP Messages
The following are Dynamic Trunking Protocol (DTP) filtering error messages.
Error Message%DTP-5-ILGLCFG : Illegal config(on,isl--on,dot1q) on [chars]
Explanation The two ports on the specified link are set to the ON mode, but one port is set to 802.1Q encapsulation, and the other port is set to ISL encapsulation. When both ports on a link are set to the ON mode, their encapsulation types must match.
Recommended Action Configure both ports on the link to have the same encapsulation type.
Error Message%DTP-4-MEM_UNAVAIL : Memory was not available to perform the trunk negotiation action
Explanation There is not enough memory to negotiate trunks.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%DTP-5-NONTRUNKPORTON : Port [chars] has become non-trunk
Explanation The specified port has changed its status from trunk port to access port.
Recommended Action No action is required.
Error Message%DTP-4-TMRERR : An internal timer error occurred when trunking on interface [chars]
Explanation A timer that is used by the trunking protocol has expired at an unexpected time. This problem is corrected internally.
Recommended Action There are likely no long-term problems associated with the timer expiration. However, if further problems with trunking occur, it is recommended that you reload the device.
Error Message%DTP-5-TRUNKPORTCHG : Port [chars] has changed from [chars] trunk to [chars] trunk
Explanation The specified trunk port has changed the encapsulation type it uses.
Recommended Action No action is required.
Error Message%DTP-5-TRUNKPORTON : Port [chars] has become [chars] trunk
Explanation The specified port has changed from being an access port to a trunk port, using the specified encapsulation.
Recommended Action No action is required.
Error Message%DTP-4-UNKN_ERR : An unknown operational error occurred
Explanation The device could not negotiate the trunks because an internal operation has generated an unknown error.
Recommended Action Reload the device.
DUAL Messages
The following are Enhanced Interior Gateway Routing Protocol (EIGRP) error messages.
Error Message%DUAL-3-ANCHORCOUNT : Anchor count negative
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-BADCOUNT : Route [chars], [dec] successors, [dec] rdbs
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-6-EVENT : [chars], [chars]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-INTERNAL : [chars] [dec]: Internal Error
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-LINKSEXIST : Interface [chars] going down and [dec] links exist
Explanation An interface is going down or is being removed from routing through the IGRP, but not all links (neighbors) have been removed from the topology table.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-LINKSTILLUP : Link [dec] [chars] still exists on [chars]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-MULTIFLOW : Flow control error, [chars], on [chars]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-5-NBRCHANGE : [chars] [dec]: Neighbor [chars] ([chars]) is [chars]: [chars]
Explanation A neighbor has gone up or down.
Recommended Action No action is required.
Error Message%DUAL-3-NOBUFFER : No buffers available for [int] byte packet
Explanation The DUAL software was unable to allocate a packet buffer. The system may be out of memory.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DUAL-3-NOHANDLE : Handle [dec] is not allocated in pool.
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-NOMATCH : Nexthop and infosource don't match. N = [chars], I = [chars]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-NOSOCKET : Unable to open socket for AS [dec]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-PEERSEXIST : [dec] peers exist on IIDB [chars]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-PROBESEQ : Bad probe sequence [dec] from [chars], expecting [dec]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-RDBLEFT : Lingering DRDB deleting IIDB, dest [chars], nexthop [chars] ([chars]), origin [chars]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-REFCOUNT : Negative refcount in pakdesc [hex]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-SIA : Route [chars] stuck-in-active state in [chars] [dec]. Cleaning up
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%DUAL-3-UNKTIMER : Unknown timer type [dec] expiration
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
DVMRP Messages
The following are Distance Vector Multicast Routing Protocol (DVMRP) error messages.
Error Message%DVMRP-5-BADMASK : Bad mask [IP_address] received from [IP_address], Report ignored
Explanation A DVMRP route that has corrupted information was received and discarded by another system.
Recommended Action No immediate action is required. This error indicates a problem with the system that sent the bad routes or with the network media connected to that system. If the condition persists, contact the administrator of the malfunctioning system.
Error Message%DVMRP-5-NBRDOWN : Neighbor [IP_address] went down on [chars]
Explanation DVMRP activity has been shut down on the specified interface. This may be because the interface has been taken down or because the DVMRP routes on that interface have all expired. Note that DVMRP activity is mutually exclusive of tagswitching, so if the interface itself is still up, tagswitching will be automatically reenabled on that interface.
Recommended Action No action is required.
Error Message%DVMRP-5-NBRUP : Neighbor [IP_address] is up on [chars]
Explanation A DVMRP multicast neighbor is active on the specified interface because of the arrival and acceptance of DVMRP probes via that interface. A multicast session has been subscribed via a path passing through this router. Note that DVMRP activity is mutually exclusive of tagswitching, so tag switching may be disabled on that interface.
Recommended Action No action is required.
Error Message%DVMRP-4-NONPRUNER : Rejecting non-pruning peer [IP_address] ([chars])
Explanation The router has rejected an IGMP report from a peer that is not capable of DVMRP pruning and grafting. This is because the router was configured with the ip dvmrp reject-non-pruners command to reject nonpruning peers.
Recommended Action If rejection of nonpruning DVMRP hosts is consistent with site policy, no action is required. Otherwise, the configuration can be changed by using the no ip dvmrp reject-non-pruners command.
Error Message%DVMRP-4-REJDEFROUTE : Rejecting default route from [IP_address]
Explanation Two routers on each side of a tunnel are sending the default route to each other.
Recommended Action Correct the router configuration.
Error Message%DVMRP-4-ROUTEHOG : Receiving [dec] routes from [IP_address] ([chars]) in the last [chars]
Explanation The number of DVMRP routes that were received from the specified system exceeds the warning threshold for the DVMRP route traffic.
Recommended Action Use the ip dvmrp routehog-notification command to change the warning threshold if necessary. Otherwise, check the system that is generating excessive DVMRP route traffic to find out the reason. The system may be in a loop and generating invalid information.
Error Message%DVMRP-4-ROUTELIMIT : Exceeded route-limit of [dec] routes, check your access-lists
Explanation The number of DVMRP multicast routes exceeds the configured maximum number. New routes (subscribers and viewers) cannot be added unless the configuration is changed.
Recommended Action If priority multicast traffic is carried by this router, use the ip dvmrp route-limit command to increase the number of DVMRP routes. Otherwise, no action is required.
E1T1_MODULE Messages
The following are E1T1 module error messages.
Error Message%E1T1_MODULE-3-BERTBUSY : Controller [chars] - BERT hardware in use, command refused.
Explanation The current task requires BERT hardware resources that are currently occupied with other tasks. The BERT chip could be in use by either sending V.54 loopup or loopdown code to the remote end or running a BERT test.
Recommended Action Determine if either of the tasks is in progress on this controller.
Error Message%E1T1_MODULE-3-FDLLLOOPDOWN : Controller [chars] - FDL line loopdown code detected, deactivating line loopback.
Explanation The system has detected FDL line loopdown code on the unit, and it is deactivating the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-FDLLLOOPUP : Controller [chars] - FDL line loopup code detected, activating line loopback mode.
Explanation The system has detected FDL line loopup code on the unit, and it is activating the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-FDLLREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via FDL.
Explanation The T1 FDL line loopup code was sent to the remote end, but the remote end did not activate the line loopback.
Recommended Action This error could be caused by the controller configuration or by a line problem. Ensure that both controllers are up.
Error Message%E1T1_MODULE-3-FDLLREQOK : Controller [chars] - Remote end is put in line loopback mode via FDL.
Explanation The T1 FDL line loopup code was sent to the remote end, and the remote end has activated the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-FDLPLOOPDOWN : Controller [chars] - FDL payload loopdown code detected, deactivating payload loopback.
Explanation The system has detected FDL payload loopdown code on the unit, and it is deactivating the payload loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-FDLPLOOPUP : Controller [chars] - FDL payload loopup code detected, activating payload loopback mode.
Explanation The system has detected FDL payload loopup code on the unit, and it is activating payload loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-FDLPREQFAILED : Controller [chars] - Failed to put the remote end in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code was sent to the remote end, but the remote end did not activate payload loopback. This error could be caused by a controller configuration or line problem.
Recommended Action Ensure that both controllers are up.
Error Message%E1T1_MODULE-3-FDLPREQOK : Controller [chars] - Remote end is put in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code was sent to the remote end from the unit, and the remote end has activated the payload loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-HWIDBFAILED : Controller [dec]/[dec] does not have idb
Explanation The system did not have a HWIDB registered for the serial interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%E1T1_MODULE-3-IBOCLOOPDOWN : Controller [chars] - IBOC loopdown code detected, deactivating line loopback.
Explanation The system has detected IBOC loopdown code on the unit, and it is deactivating the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-IBOCLOOPUP : Controller [chars] - IBOC loopup code detected, activating line loopback mode.
Explanation The system has detected IBOC loopup code on the unit, and is activating the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-IBOCREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code was sent to the remote end, but the remote end did not activate the line loopback. The remote end may not have activated the payload loopback because of a controller configuration or line problem.
Recommended Action Ensure that both controllers are up.
Error Message%E1T1_MODULE-3-IBOCREQOK : Controller [chars] - Remote end is put in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code was sent to the remote end from the unit, and the remote end has activated the line loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-INITFAILURE : Slot [dec], Unit [dec] initialization failure - [chars]
Explanation The E1T1 driver detected an error while initializing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%E1T1_MODULE-3-LINEFLAP : Interface [chars] receiving excessive errored packets
Explanation The serial interface is receiving an excessive number of error packets. This problem is caused by a controller configuration mismatch.
Recommended Action Check the settings for line code, framing, time slots, and speed.
Error Message%E1T1_MODULE-3-T1REQCANCELLED : Controller [chars] - T1 remote loopback has been cancelled.
Explanation T1 loopdown code has been sent to the remote end from the specified unit. The remote end is assumed to have received the loopdown code and deactivated the loopback mode. However, no test has been performed to ensure that the remote end has deactivated the loopback mode.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-V54LOOPDOWN : Unit [chars] - V.54 loopdown code detected, deactivating V.54 payload loopback.
Explanation The system has detected V.54 loopdown code on the unit, and it is deactivating the V.54 payload loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-V54LOOPUP : Unit [chars] - V.54 loopup code detected, activating V.54 payload loopback mode.
Explanation The system has detected V.54 loopup code on the unit, and it is activating the V.54 payload loopback.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-V54REQCANCELLED : Unit [chars] - Remote V.54 loopback has been cancelled.
Explanation V.54 loopdown code has been sent to the remote end from this unit. The remote end is assumed to have received the loopdown code and deactivated the loopback mode. However, no test was performed to ensure the remote end has deactivated loopback mode.
Recommended Action No action is required.
Error Message%E1T1_MODULE-3-V54REQFAILED : Unit [chars] - Failed to put the remote end in V.54 payload loopback mode.
Explanation The V.54 loopup code was sent to the remote end, but the remote end did not activate loopback. This error could be caused by controller configuration mismatch or a line problem.
Recommended Action Check the time slots and speed setting for the channel group in question on both ends, and ensure that V.54 detection is enabled on the remote end.
Error Message%E1T1_MODULE-3-V54REQOK : Unit [chars] - Remote end is put in V.54 payload loopback mode.
Explanation The V.54 loopup code was sent to the remote end from the unit, and the remote end has activated V.54 payload loopback.
Recommended Action No action is required.
EC Messages
The following are Port Aggregation Protocol (PAgP) error messages.
Error Message%EC-5-BUNDLE : Interface [chars] joined port-channel [chars]
Explanation The specified interface has joined the port channel bundle.
Recommended Action No action is required.
Error Message%EC-5-CANNOT_BUNDLE1 : Port-channel [chars] is admin-down, port [chars] will remain stand-alone.
Explanation The port channel is administratively down.
Recommended Action Reconfigure the port channel to form a bundle.
Error Message%EC-5-CANNOT_BUNDLE2 : [chars] is not compatible with [chars] and will be suspended ([chars])
Explanation The specified port has different port attributes from those of the port channel or ports within the port channel.
Recommended Action To join this port to the bundle, change its port attributes to match the port attributes of the port channel.
Error Message%EC-5-L3DONTBNDL1 : [chars] suspended: PAgP not enabled on the remote port.
Explanation PAgP is enabled on the Layer 3 interface, but the remote partner port does not have PAgP enabled. In this mode, the port is placed in a suspended state.
Recommended Action Enable PAgP on the remote partner port.
Error Message%EC-5-L3DONTBNDL2 : [chars] suspended: incompatible partner port with [chars]
Explanation The partner port has been configured with a GC that is different from the GCs on the other ports in the bundle.
Recommended Action For a port to join a bundle, the local GC and the partner GC should match the GC on the other ports in the bundle. Ensure that the partner GCs for all the ports in the group are same.
Error Message%EC-5-L3PORTDOWN : Shutting down [chars] as it's port-channelis admin-down
Explanation The administrative state of the Layer 3 port is ruled by the administrative state of its aggregation port. If the administrative state of the aggregation port is down, the administrative state of the Layer 3 port will be forced to go down.
Recommended Action Change the administrative state of the aggregation port to up.
Error Message%EC-5-L3STAYDOWN : [chars] will remain down as it's port-channel[chars] is admin-down
Explanation The administrative state of the Layer 3 port is ruled by the administrative state of its aggregation port. If the administrative state of the aggregation port is down, the administrative state of the Layer 3 port will be forced to go down.
Recommended Action Change the administrative state of the aggregation port to up.
Error Message%EC-4-NOMEM : Not enough memory available for [chars]
Explanation The PAgP Shim/EtherChannel could not obtain the amount of memory it needed.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%EC-5-NOPAGP : Invalid EC mode, PAgP not enabled
Explanation The EtherChannel (EC) mode could not be set to the mode requested because the PAgP had not been included in the software image.
Recommended Action Get an image that includes PAgP or set the EC mode to on.
Error Message%EC-5-UNBUNDLE : Interface [chars] left the port-channel [chars]
Explanation The interface has been disconnected from the bundle.
Recommended Action No action is required.
Error Message%EC-5-UNSUITABLE : [chars] will not join any port-channel,unsuitable attributes configured
Explanation An attempt was made to configure Port-fast, VMPS, and Dest-SPAN for Etherchannel. Port-fast, VMPS, and Dest-SPAN cannot be configured for Etherchannel.
Recommended Action Undo the attempted configuration.
EGP Messages
The following are Exterior Gateway Protocol (EGP) error messages.
Error Message%EGP-3-NOPDB : No pdb for [IP_address]
Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EGP-3-TOOBIG : Insufficient ([dec]) buffering for update message
Explanation An EGP update message was too large to fit into a single buffer.
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 help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
EHSA Messages
The following are Cisco 6400 Enhanced High System Availability (EHSA) error messages.
Error Message%EHSA-3-CONFIG_SYNC : [chars]
Explanation An EHSA configuration synchronization error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%EHSA-3-EHSA_ALARMS : [chars]
Explanation An EHSA alarm assertion error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%EHSA-3-EHSABADST : [chars] [[dec]] [[dec]]
Explanation An EHSA internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-3-EHSAINT : '[chars]' at level [dec]
Explanation An EHSA internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-2-EHSALOAD : [chars]
Explanation The system attempted to boot from the network on an EHSA secondary unit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-2-EHSASW : [chars]
Explanation The primary unit has crashed or is unresponsive. The secondary unit is taking over.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-3-FSM : [chars]
Explanation An EHSA FSM error has occurred. The details about what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%EHSA-3-GENERAL : [chars]
Explanation An EHSA error has occurred. The details about what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%EHSA-3-IPC : [chars] [chars]
Explanation An IPC error has occurred. The details of what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%EHSA-3-IPCERR : [chars] [[chars]]
Explanation IPC has failed for EHSA, and EHSA messages cannot be transmitted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-3-KEEPTO : No keepalive seen in [[dec]] secs: Failover [chars]
Explanation An EHSA keepalive failure has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-3-NOBUF : [chars]
Explanation The IPC has run out of memory buffers.
Recommended Action Reduce the number of applications currently running on the IPC. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%EHSA-3-PEER_MONITOR : [chars]
Explanation An EHSA Peer Monitor error has occurred. The details about what action was attempted and what malfunctioned will be printed.
Recommended Action Copy the error message exactly as it appears, contact your Cisco technical support representative, and provide the representative with the gathered information. Also provide the system configuration information along with any other relevant information.
Error Message%EHSA-5-PEER_MONITOR_EVENT : [chars] ([chars][chars]([dec]))
Explanation An EHSA Peer Monitor event has occurred and was reported. The report indicates the reason for a switchover.
Recommended Action No action is required.
Error Message%EHSA-3-STCHNG : [chars] [[dec]]
Explanation An EHSA state change has been detected.
Recommended Action Copy the error message exactly as it appears. Include the system configuration information along with any other relevant information. Contact your Cisco technical support representative, and provide the representative with the gathered information.
ENSP Messages
The following are Enhanced Network Service Provider (ENSP) error messages.
Error Message%ENSP-4-FMAIL_BAD_MESSAGE : FAXMAIL- Bad message received
Explanation An unexpected message has been received.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENSP-2-FMAIL_INTERNAL_ERROR : Internal software error
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENSP-2-FMAIL_NO_AUTH_STARTED : AAA authentication startup failed
Explanation AAA authentication startup has failed.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENSP-4-FMAIL_NO_SMTP : FAXMAIL- Can not connect to the SMTP server
Explanation No connection could be made to any of the specified SMTP servers.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENSP-4-FMAIL_NO_SMTP_SEND : FAXMAIL- Could not send data to the SMTP server
Explanation A connection was made to the SMTP server, but data cannot be sent.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENSP-2-INTERNAL_ERROR : FAX- Internal software error
Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%ENSP-1-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%ENSP-4-SMTP_NOT_CONNECTED : SMTP- failed [chars], [dec]
Explanation A connection attempt to a remote mail server has failed. This is unexpected behavior.
Recommended Action No action is required.
Error Message%ENSP-6-SMTP_OPEN : SMTP- opening [chars], [dec]
Explanation An attempt to connect to a remote mail server has failed. This is unexpected behavior.
Recommended Action No action is required.
ENT_API Messages
The following are Entity MIB Application Programming Interface error messages.
Error Message%ENT_API-4-NOALIAS : [chars] entity not found when adding an alias with physical index = [int] and logical index = [int] to the Entity MIB
Explanation An attempt to add an alias entry to the Entity MIB has failed. The logical or physical entity with the specified index does not exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-3-NOCREAT : EntityApiProcess not created - Entity MIB will not be initialised
Explanation An attempt to start the routine failed when the entity subsystem was initialized. The Entity MIB will not be populated. The Entity MIB API process was not created, possibly because of a lack of memory.
Recommended Action To use the Entity MIB API, reconfigure the system so that less memory is used by other features, or add more memory to the system. Reload the system after reconfiguring it.
Error Message%ENT_API-4-NOENT : Trying to add or delete an unknown entity to the Entity MIB
Explanation An attempt to add or delete an unknown entity to the Entity MIB was made. The request could not be processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-4-NOLPMAP : [chars] entity not found when adding an LPMapping entry with logical index = [int] and physical index = [int] to the Entity MIB
Explanation An attempt to add an LPMapping entry to the Entity MIB was made. Because a logical or physical entity having the specified index does not exist, the LPMapping entry creation failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-4-NOPARENT : Parent physical entity [int] did not exist when trying to add child physical entity [int].
Explanation An attempt to add a physical entity has failed because its parent physical entity does not exist in the entPhysicalTable of the Entity MIB.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.
Error Message%ENT_API-4-NOPORT : Physical entity does not have a Port PhysicalClass when adding an alias with physical index = [int] and logical index = [int] to the Entity MIB
Explanation An attempt to add an alias entry to the Entity MIB was made. The physical entity having the specified index does not have an entPhysicalClass of 10 (Port class), and so the alias entry creation failed. Refer to the RFC2037 document for the definition of the PhysicalClass textual-convention and the aliasMappingEntry object.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Using your NMS tool, also provide the content of the Entity MIB table.