-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
DNET Messages
The following are DECnet messages.
Error Message%DNET-4-DUPENTRY : Duplicate DECnet Accounting List Entry for nodes [dec].[dec] - [dec].[dec]
Explanation A synchronization problem has occurred. When a new transit DECnet accounting list entry was being added, a duplicate entry was found.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show decnet accounting command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DNSSERVER Messages
The following are Domain Name Server (DNS) server messages.
Error Message%DNSSERVER-3-TCPDNSOVERLOAD : Low available memory: dropping TCP request from <cli [IP_address]>.
Explanation Free memory is insufficient to handle DNS queries. The DNS server is automatically discarding DNS request traffic.
Recommended Action Reduce the number of features you are trying to support, or upgrade the memory on the system router processor.
Error Message%DNSSERVER-3-UDPDNSOVERLOAD : Low available memory: dropping <id# [dec]> from <cli [IP_address]>.
Explanation There is not enough free memory to handle DNS queries. The DNS server is automatically discarding DNS request traffic.
Recommended Action Reduce the number of features you are trying to support, or upgrade the memory on the system router processor.
DOS_TRACK Messages
The following are IP source tracker messages.
Error Message%DOS_TRACK-5-CFG : IP Source Tracker configured for [dec] hosts
Explanation The IP Source tracker feature is running.
Recommended Action No action is required.
Error Message%DOS_TRACK-4-PROCESS : [chars]
Explanation A process that is required by the IP source tracker feature could not be created.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DOT1X_MOD Messages
The following are messages encountered in platform dependent code for 802.1x.
Error Message%DOT1X_MOD-3-NULLPTR : Unexpected null pointer in [chars] at [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DPM Messages
The following are AS5200 T1 BRIMUX messages.
Error Message%DPM-3-BADMAGIC : SMP hasn't initialized the DPRAM.
Explanation The remote peer has not finished initializing its DPRAM magic number.
Recommended Action Check software compatibility between peers.
Error Message%DPM-3-BADSMP : SMP hasn't initialized the DPRAM.
Explanation The remote peer hasn't finished initializing its DPRAM layout area.
Recommended Action Check software compatibility between peers.
Error Message%DPM-3-NOIDB : Copernico failed on acquiring DPRAM idb.
Explanation There are insufficient internal resources available to create an IDB.
Recommended Action Check available memory capacity on the router.
Error Message%DPM-3-OOBINIT : Copernico failed on out-of-band sub-system initialization.
Explanation There was a failure during DPRAM initialization.
Recommended Action Check software compatibility between peers.
DS1337 Messages
The following are DS1337 RTC messages.
Error Message%DS1337-3-RTC_CHIP_NOT_RESPONDING : RTC (real time clock) chip is not responding
Explanation The Real Time Clock through the SMBUS timed out. Calendar functions will not be available.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%DS1337-3-RTC_FAILURE : [chars] onboard Real Time Clock DS1337 chip failed
Explanation There was a Read or Write failure to the RTC chip, possibly due to high system load.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
DSC Messages
The following are dial shelf controller (DSC) messages.
Error Message%DSC-4-MANUALBOOT : Setting config-register to 0x0 will prevent the feature boards from booting when the controller card is rebooted
Explanation Setting the configuration register to 0x0 will prevent the feature boards from booting when the controller card is rebooted.
Recommended Action Set the configuration register to 0x2 for automatic booting.
DSI Messages
The following are Cisco AS5800 dial shelf interconnect board messages.
Error Message%DSI-3-AGENTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected an invalid state change for the MBus agent in the specified slot. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSI-3-AGENTSTSCHNG : From [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software detected a state change for the MBus agent in the specified slot.
Recommended Action This is an informational message only. No action is required.
Error Message%DSI-3-ALTTRUNK : The card in slot [dec] does not match the chassis' trunk type. The system can only either be a T1 or E1 system
Explanation The newly inserted card does not have the same trunk type as the other cards currently running on the system. T1 and E1 cards cannot reside in the same system.
Recommended Action Ensure that either E1 trunk cards or T1 trunk cards exist exclusively in the system.
Error Message%DSI-2-BADPORT : Out of range PCI port [dec]
Explanation The software specified an out-of-range port on the chassis interconnect. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSI-3-EVENT : Unknown event [dec] for slot [dec]
Explanation The software generated an unknown event for the specified slot. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSI-3-EXCEEDE1 : Cannot have more than two 24E1 cards per RSC. Powering down card in slot [dec]
Explanation More than two 24E1 cards have been installed under the same RSC. If the system is a split-shelf system, this applies to each split. Recommended limits for ingress trunks have been exceeded. The card in the slot specified in the message has been powered down.
Recommended Action If more trunks are required in the chassis, install another RSC card and try configuring the system as a split-shelf system.
Error Message%DSI-3-EXCEEDSTM1 : Cannot have more than one STM1 cards per RSC. Powering down card in slot [dec]
Explanation More than one STM1 card has been installed under the same RSC. If the system is a split-shelf system, this applies to each split. Recommended limits for ingress trunks have been exceeded. The card in the slot specified in the message has been powered down.
Recommended Action If more trunks are required in the chassis, install another RSC card and try configuring the system as a split-shelf system.
Error Message%DSI-3-EXCEEDSTM1E1 : Cannot have more than one STM1 or two 24E1 cards per RSC. Powering down card in slot [dec]
Explanation More than one STM1 or two 24E1 cards have been installed under the same RSC. If the system is a split-shelf system, this applies to each split. Recommended limits for ingress trunks have been exceeded. The card in the slot specified in the message has been powered down.
Recommended Action If more trunks are required in the chassis, install another RSC card and try configuring the system as a split-shelf system.
Error Message%DSI-3-EXCEEDT3 : Cannot have more than two CT3 cards per RSC. Powering down card in slot [dec]
Explanation More than two CT3 cards have been inserted under the same RSC. If the system is a split-shelf system, this applies to each split. Recommended limits for ingress trunks have been exceeded. The card in the slot specified in the message has been powered down.
Recommended Action If more trunks are required in the chassis, install another RSC card and try configuring the system as a split-shelf system.
Error Message%DSI-3-EXCEEDT3 : Cannot have more than two CT3 cards per RSC. Powering down card in slot [dec]
Explanation More than two CT3 cards have been inserted under the same RSC. If the system is a split-shelf system, this applies to each split. Recommended limits for ingress trunks have been exceeded. The card in the slot specified in the message has been powered down.
Recommended Action If more trunks are required in the chassis, install another RSC card and try configuring the system as a split-shelf system.
Error Message%DSI-3-EXCEEDT3T1 : Cannot have more than two CT3 or two 24T1 cards per RSC. Powering down card in slot [dec]
Explanation More than two CT3 or two 24T1 cards have been inserted under the same RSC. If the system is a split-shelf system, this applies to each split. Recommended limits for ingress trunks have been exceeded. The card in the slot specified in the message has been powered down.
Recommended Action If more trunks are required in the chassis, install another RSC card and try configuring the system as a split-shelf system.
Error Message%DSI-3-EXCESSFB : The card in slot [dec] is powered off. There are too many [chars] cards in the chassis. The maximum number of [chars] cards allowed is [dec]
Explanation There are too many cards of the same type in the chassis. The card that caused this error message has been powered off to avoid system overload.
Recommended Action Remove the excess card.
Error Message%DSI-3-MIXE1T1 : Cannot have E1 and T1/T3 trunk cards in the same chassis. Powering down card in slot [dec]
Explanation Both an E1 and a T1 or T3 trunk card have been inserted in the same chassis. If the system is a split-shelf system, both splits must have conforming card types.
Recommended Action Ensure that either E1 trunk cards or T1 or T3 trunk cards exist exclusively per chassis. If it is required to switch from one trunk card to the other, first remove all trunk cards (E1, T1 or T3) in the entire chassis and insert cards of the new type in the chassis.
Error Message%DSI-3-SLOTSTATUS : Invalid change from [chars] ([dec]) to [chars] ([dec]) for slot [dec]
Explanation The software has detected an invalid state change for the specified slot. This condition indicates a software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%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 This is an informational message only. No action is required.
DSIP Messages
The following are distributed system interconnect protocol messages.
Error Message%DSIP-3-BADINIT : Uninitialized or partially initialized DSIP client, client = [hex], client name = [chars]
Explanation A DSIP client data structure contains uninitialized fields.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-CLIENT_ADD_FAIL : Adding client [dec] after DSIP has started.
Explanation An internal error occurred while a client was being added to the Distributed System Interconnect Protocol. An attempt has been made to add a client to the protocol after the protocol has started.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-CLIENT_VERSION_MISMATCH : Some clients on this feature board are running versions which are incompatible with RS. Not initializing any DSIP clients. You can find the incompatible clients by executing the show dsip version command
Explanation There is a mismatch in versions between the clients on the feature board and the router shelf. A possible cause for this condition might be different Cisco IOS software images on the router shelf and the dial shelf.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-CLIVERSDBASE_MALLOC_FAILURE : Failed to get memory for the DSIP clients version database
Explanation A low-memory condition has occurred. This condition might be caused by a software error or by system memory that requires upgrading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-ERROR : [chars] error for client [chars]
Explanation The specified DSIP client encountered an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-GET_INTRAPI_BUF_FAILURE : Failed to get interrupt api buffers
Explanation An internal error has occurred in the Nitro interconnect protocol stack. Interrupt API buffers cannot be obtained because the queue has exhausted its buffers.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-GETPAK : Failed to get packet buffer
Explanation A packet buffer could not be obtained to allow communication between the router and the feature boards. This condition may be due to a low-memory condition and might be a transient condition.
Recommended Action If the system recovers, no action is required. Otherwise, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%DSIP-3-GET_VERSBUF_FAILURE : Failed to get version buffers
Explanation An internal error has occurred in the Nitro interconnect protocol stack. This condition is due to a failure to get version buffers because the queue has exhausted its buffers.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-INCOMPATIBLE_CLIENT : Incompatible client [chars] on DS slot [dec] with major version [dec] and minor version [dec]. Shutting down all the DSIP clients on this slot
Explanation The DSIP has detected incompatible clients. This condition might be caused by a mismatch in the major and minor numbers of the client.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-INTRAPI_BUF_MALLOC_FAILURE : Failed to get memory for the DSIP interrupt api buffers
Explanation A low-memory condition has occurred. This condition might be due to a software error or system memory that requires upgrading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-IPC_CLIENT : IPC subsystem API error([chars]), [chars], [dec]
Explanation A client has encountered a problem with the Nitro interconnect protocol reliable stack. The exact problem can be decoded further by the parameters of the message, as follows:
–
The first parameter of the message is the IPC error message itself.
–
–
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-IPC_PORT : IPC subsystem API error([chars]), [chars], [chars]
Explanation The Nitro interconnect protocol has encountered a problem while processing an action involving the port specified in the error message. The exact problem can be decoded further by the parameters of the message, as follows:
–
–
–
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-IPC_SEAT : IPC subsystem API error, can not create seat by
the seatid [dec] for the slot [dec]Explanation The Nitro interconnect protocol reliable stack has failed to create a seat for the specified slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-6-NIP_SEND_BUF : DSIP send data failed, slot [dec] nip client id [dec]
Explanation A failure occurred while a communication packet was being sent from the router to the feature board in the slot specified in the message. This situation might be a transient condition.
Recommended Action No action is required.
Error Message%DSIP-3-NO_COMMS_PROC : Failed to create a process to initiate DSIP communications with the RSC
Explanation The DSIP is not functioning because it failed to create the process that initiates DSIP communications with the RSC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_COMMS_UP_EVENTS : Exceeded the maximum number of comms up messages in use ([dec])
Explanation The number of communications-up messages (
comms_up) in use has exceeded the allowed limit, causing the DSIP to function erratically. After some events are put in the queue, the system should recover.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_COMMS_UP_PROC : Failed to create a process to inform clients that comms are up
Explanation The DSIP is not functioning because it failed to create the process that informs clients that communications are up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_COMMS_UP_Q : Failed to create a the queue for informing clients that comms are up
Explanation The DSIP is not functioning because it failed to create the process and queue that inform clients when communications are up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_DSIP_OUTPUT_ENCAPS : Unable to queue DSIP output for slot [dec] client [dec]
Explanation The output buffer lacks encapsulation space, causing the DSIP output to hold for this client and slot. Because of the lack of space, the output cannot be queued for later delivery.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_IPC_TO_DSIP_DEQ_PROC : Failed to create a process to dequeue elements from the IPC-to-DSIP queue
Explanation The DSIP is not functioning because it failed to create the process that dequeues the IPC-to-DSIP messages and passes each message on to the destination client.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_IPC_TO_DSIP_Q : Failed to create a watched queue to store the IPC-to-DSIP data
Explanation The DSIP is not functioning because it failed to create a watched queue for storing DSIP data delivered by way of IPC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-NO_MAJOR_VERSION : Client addition to DSIP has failed, [chars], [dec]
Explanation An internal error occurred while a client was being added to the distributed system interconnect protocol. A minor version of the client was specified, and the major version was not specified.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-4-PING_TEST_REPLY_ERROR : Cannot send a ping test reply message from DSIP slave client [[chars]] to DSIP master.
Explanation The DSIP client failed to send a ping test reply message to the DSIP active.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-PRIVPOOL : Failed to create DSIP private buffer pool
Explanation An internal error has occurred in the Nitro interconnect protocol stack. A buffer pool could not be created.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-RANGE : DSIP parameter range error, [chars], [dec]
Explanation An internal error has occurred in the distributed system interconnect protocol module. This condition is caused by an invalid range parameter specification while the module was when communicating with the feature board in the slot specified in the message. This situation is a transient condition.
Recommended Action No action is required.
Error Message%DSIP-3-TXCONTEXT : ([chars]), slot [dec], client [dec]
Explanation An internal error has occurred in the Nitro interconnect protocol stack. A free transmit context block could not be obtained. This is a transient condition.
Recommended Action No action is required.
Error Message%DSIP-3-TXCONTEXT_ACTIVE_USE : Waiting for the active transmit contexts to become inactive
Explanation There are active transmit contexts in use. This message will be displayed until all contexts are no longer being used and the cleanup operation is ready to begin.
Recommended Action This message occurs during normal system operation. No action is required.
Error Message%DSIP-3-VERSBUF_MALLOC_FAILURE : Failed to get memory for the DSIP version buffers
Explanation A low-memory condition has occurred. This condition might be due to a software error or system memory that requires upgrading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP-3-VERSDBASE_MALLOC_FAILURE : Failed to get memory for the DSIP version database
Explanation A low-memory condition has occurred. This condition might be due to a software error or system memory that requires upgrading.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DSIP_IOSDIAG Messages
The following are DSIP diagnostic test messages.
Error Message%DSIP_IOSDIAG-3-PING_TEST_INTERNAL_ERROR : DSIP ping test internal error: [chars].
Explanation The DSIP client ping test has failed because of an internal software error. The most likely software errors are:
–
–
–
–
Recommended Action If the test does not recover within the next few scheduled tests, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP_IOSDIAG-3-PING_TEST_NO_RESPONSE : DSIP master on the RSC failed to receive ping test response from slave client [chars] in FB slot [dec].
Explanation The active DSIP on the RSC failed to receive a ping test response from the specified client on the feature board in the specified slot. The feature board cannot communicate with the RSC.
Recommended Action If the test does not recover itself within the next few scheduled tests, reload the feature board reported in the error to reestablish the communication with the RSC. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSIP_IOSDIAG-3-PING_TEST_OK : DSIP slave client [chars] in FB slot [dec] is pinged.
Explanation An error condition that was detected during the DSIP ping test has cleared. The active DSIP on the RSC has now successfully received a ping test response from the specified DSIP client on the feature board. The RSC and feature board are now communicating normally.
Recommended Action No action is required.
Error Message%DSIP_IOSDIAG-3-PING_TEST_SEND_ERROR : DSIP master on the RSC failed to send a ping to slave client [chars] in FB slot [dec].
Explanation The active DSIP client on the RSC failed to send a ping test message to the specified standby DSIP client on the feature board in the specified slot. The RSC can no longer communicate with the feature board.
Recommended Action If the test does not recover within the next few scheduled tests, reload the feature board reported in the error to reestablish the communication with the RSC. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DSIPPF Messages
The following are DSIP packet forwarding messages.
Error Message%DSIPPF-5-COMMS_STATUS : DSIP/IPC communications to slot [dec] are [chars].
Explanation Full DSIP and IPC communications to this slot have gone up or down.
Recommended Action No action is required.
Error Message%DSIPPF-4-SWITCHOVER : Reloading slot [dec], DSIP/IPC communications failed to come up within [dec] secs.
Explanation The system is reloading the FB in this slot because the DSIP and IPC communications did not come up within the specified number of seconds after a switchover.
Recommended Action No action is required.
DSLSAR Messages
The following are digital subscriber line (DSL) segmentation and reassembly (SAR) messages.
Error Message%DSLSAR-3-FAILTEARDOWNVC : Interface [chars], Failed to down vc [dec], vc_state [dec] (Cause: [chars])
Explanation The ATM network module hardware might have failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSLSAR-1-NO_LED_BLINK : Failed to create LED blink process
Explanation The system failed to create the LED blink process.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSLSAR-1-NO_SCC_CLK_ERR : [chars]: Interface is DOWN because the sum of the clock rate values for both the WICs in slots 0 and 1 exceeded maximum capacity. Please configure clock rates using clock rate command in interface mode such that the sum of clock rate on both the WICs does not exceed [dec] bps. For a DSL wic, please include aal5 and aal2 clock rate values while calculating the total.
Explanation An adjacent interface might be using more of the clock function than what is currently configured.
Recommended Action Ensure that SCC clock rates are configured properly. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSLSAR-1-SCC_ERR : Interface [chars]: SCC Error: [chars]
Explanation Either an SCC underrun or overrun has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DSMP Messages
The following are DSP Stream Manager messages.
Error Message%DSMP-3-DSPALARM : channel [chars], DSP ID [hex]: status=[hex] message=[hex] text=[chars]
Explanation The DSP has reported a fatal error. All sessions on the DSP were dropped and a DSP reload was attempted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-3-DSP_TIMEOUT : DSP timeout on channel [chars], event [hex]: DSP ID=[hex]: [chars]
Explanation A DSP response was not received before the timeout period expired. The DSP has been automatically reset.
Recommended Action If this problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-3-INTERNAL : Internal Error : [chars]
Explanation An internal error involving DSMP has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-3-INVALID_EVENT : Unhandled event: current state:[chars] event:[chars]
Explanation An event could not be processed by the DSMP gateway state machine configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-3-MSGSNDFAIL : channel:[chars] DSP ID:[hex] Message ID:[hex]
Explanation A message could not be sent to the DSP. The session will continue, but there may be problems.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-3-NOEVENT : no free event structure available from [chars] for DSMP message
Explanation No event structures were remaining in the system pools to alert the router to a voice or signaling event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-3-PRG_ERROR : Programming Error : [chars]
Explanation A programming error has occurred in the DSMP subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSMP-6-SESSION_DATABASE_FAILED : Cannot create DSMP session database\n
Explanation A DSMP session could not be created.
Recommended Action Check the size of free memory to ensure that there is enough memory.
Error Message%DSMP-3-SUBSYS_UNINITIALIZED : Internal Error : [chars]
Explanation The DSMP subsystem could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DSP_CONN Messages
The following are TDM connection messages.
Error Message%DSP_CONN-3-INVALID_CONNECTION_TYPE : Invalid connection type [dec]
Explanation The connection type is invalid. It is neither a TDM-to-DSP-or-HWECAN connection nor a HWECAN-to-DSP connection.
Recommended Action No action is required.
DSPDUMP Messages
The following are Digital Signal Processor crash dump facility messages.
Error Message%DSPDUMP-5-DUMPSTART : DSP [dec] ([hex]) in slot [dec] starting dump
Explanation The DSP resource is beginning crash dump collection.
Recommended Action No action is required.
DSPFARM Messages
The following are DSP resource management messages.
Error Message%DSPFARM-3-ERROR : Errors on DSPFARM module [chars]\n
Explanation Errors have occurred on the DSPFARM module.
Recommended Action Enter the show dspfarm all command to attempt to determine the nature of the problem.
Error Message%DSPFARM-4-INFO : Info on DSPFARM module [chars]\n
Explanation This message provides information regarding the DSPFARM module.
Recommended Action Enter the show dspfarm command for more information on the nature of the message.
Error Message%DSPFARM-4-NOTICE : Failure on DSPFARM module [chars]\n
Explanation A failure has occurred on the DSPFARM module.
Recommended Action Enter the show dspfarm command for more information on the nature of the failure.
Error Message%DSPFARM-4-WARNING : Warning on DSPFARM module [chars]\n
Explanation A warning error has occurred on the DSPFARM module.
Recommended Action Enter the show dspfarm all command to attempt to determine the nature of the problem.
DSPRM Messages
The following are Digital Signal Processor Device Driver (DSPDD) messages.
Error Message%DSPRM-5-DSPMSGFAIL : Failed to get dsprm msg for msg id [chars]
Explanation A DSPRM control message could not be obtained.
Recommended Action No action is required.
DSXPNM Messages
The following are T3 network module messages.
Error Message%DSXPNM-3-0 : Slot [dec], ([chars])
Explanation The internal data structure for the TE3 driver has become corrupted.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-BOOTDNLD : Slot([dec]) WAN H/W init failed (download bootcode)\n
Explanation The TE3 network module boot code download could not be initialized.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-CONFIGURE : Failed to configure [dec] interfaces in bay [dec], shutting down bay\n
Explanation The TE3 network module hardware in the specified bay has failed. Some components on the board have failed to initialize. The network module in the specified bay has been shut down.
Recommended Action Replace the TE3 network module in the specified bay.
Error Message%DSXPNM-1-DISCOVER : Found [dec] interfaces in bay [dec], shutting down bay\n
Explanation The TE3 network module hardware in the specified bay has failed. Some components on the board have failed to initialize. The network module in the specified bay has been shut down.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-2-DSXPNM_BAD_CARD_TYPE : [chars]: Unknown card_type [hex], slot [hex]\n
Explanation The network module that has been inserted is not recognized by the Cisco IOS software.
Recommended Action Check the part number on the network module to verify that the network module is supported by the Cisco IOS release that is running on the router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_BAD_SLOT : [chars]: invalid slot [dec]\n
Explanation An invalid slot number for the TE3 network module has been detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_FWDNLD_BAD_FILE_SIZE : Bad size for file [[chars]] during downloading firmware\n
Explanation The firmware download from the URL was not successful. The size of the firmware file is invalid. The system is using the firmware bundled version that was in use before the firmware download.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_FWDNLD_BAD_FOPEN : cannot open file [chars], using bundled firmware image\n
Explanation The firmware download failed because the URL path that was specified could not be opened. The system is using the firmware bundled version that was in use before the firmware download.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-2-DSXPNM_GET_LCN_RESOURCE : [chars]: No more ch SCCs slot [dec].\n
Explanation The TE3 network module driver for the specified slot could not allocate a channel resource for the port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_HWIDB_NOT_NULL : [chars]: hwidb passed is non-zero, slot [dec], port [dec]\n
Explanation The system has failed to create a serial interface. This condition is the result of an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_INVALID_PHY_PORT : [chars]: slot [dec] invalid phy port [dec]\n
Explanation The system has determined that an invalid port configuration is present on the system. This condition is the result of an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_IS_NOT_DSXPNM : [chars]: Not a valid dsxpnm NM, slot [dec], port [dec]\n
Explanation The network module that has been inserted is not recognized by the Cisco IOS Software.
Recommended Action Check the part number on the network module to verify that the network module is supported by the Cisco IOS software release that is operational on the router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_NO_DS : [chars] ds is not allocated!\n
Explanation The system has determined that an invalid card configuration is present on the system. This condition is the result of an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-2-DSXPNM_NO_WPI : [chars]: no wpi struct for slot [dec]\n
Explanation The TE3 network module driver for the specified slot has encountered an invalid channel resource error. This condition is the result of an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_PUT_LCN_RESOURCE : dsxpnm_put_lcn_resource: invalid lcn specifiedlcn->channel_num=[dec], lcn->free=[dec], lcn->blk=[dec], lcn->blk_index=[dec], slot=[dec]\n
Explanation The TE3 network module driver for the specified slot has encountered an invalid channel resource error. This condition is the result of an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_SER_IDB_INIT_FAIL : [chars]: serial_idb_init failed! slot=[dec]
Explanation The TE3 network module driver encountered an error while the serial interface was being created. This condition is due an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-2-DSXPNM_SHMEM_ALLOC_FAIL : I/O Shared Memory Malloc failed\n
Explanation A firmware initialization failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_UNKNOWN_GT_PORT_USE : [chars]: unknown gt_port_use [dec]\n
Explanation The TE3 network module driver for the specified port has encountered an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_VCON_ARG_READ_FAIL : [chars]: couldn't read the process argument\n
Explanation The TE3 network module could not start the console logging process for the network module. This condition is due to an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DSXPNM_VCON_NOT_INIT : [chars]: Virtual console debug buffer not initialized !! \n
Explanation The TE3 network module driver could not set up the network buffers for the virtual console logs of the network module. This condition is due to an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-DWNLDFAIL : Microcode to slot [dec]\n
Explanation Firmware failed to be downloaded into the TE3 network module in the specified slot.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-FWDNLD : Slot([dec]) WAN H/W init failed (download firmware)\n
Explanation The TE3 network module firmware for the port module in the specified slot failed to be downloaded.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-GT96K : Slot([dec]) WAN H/W init failed (gt96k init on NM)\n
Explanation The WAN interface for the TE3 network module for the specified slot could not be initialized.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-3-HWIDBFAILED : Controller [dec]/[dec] does not have idb\n
Explanation The system does not have a hardware IDB registered for the serial interface.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-3-HWIDBMISMATCH : Controller [dec]/[dec] channel [dec] idb does not match the system idb for that channel\n
Explanation The system does not have a valid hardware IDB registered for the serial interface.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-INITFAIL : Slot([dec]) firmware init fail ([chars])\n
Explanation The TE3 network module firmware could not be initialized for the network module in the specified slot.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-INITFAIL1 : Slot([dec]) Pa_type([hex]) firmware init fail ([chars])\n
Explanation The TE3 network module firmware could not be initialized for the network module in the specified slot.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-3-INITFAILURE : Slot [dec], Unit [dec] initialization failure - [chars]\n
Explanation The TE3 network module driver detected an error during the initialization of the port module.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-2-NM_WATCH_DOG : Got WATCHDOG Interrupt from NM at slot [dec] \n
Explanation A firmware crash has been detected.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-2-NM_WATCH_DOG_NO_INFO : Cannot display watchdog information for the TE3 network module.\n
Explanation The firmware has crashed, and the firmware crash information for the network module could not be saved.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-NOTREADY : Slot [dec] for microcode download\n
Explanation An error has been detected on the communication path between the host and the network module in the specified slot. The TE3 hardware or firmware has failed. Some components on the network module have failed to initialize.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-3-"NULL" : Slot [dec], ([chars])
Explanation The internal data structure for the TE3 driver is corrupted.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, and reboot the system. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DSXPNM-1-UNSUPPORTED : \n[chars]\n
Explanation Unavailable.
Recommended Action Unavailable.
E1T1MODULE Messages
The following are messages generated by the E1T1 module.
Error Message%E1T1_MODULE-5-RELAY_STATE_CHANGE : [chars] - [dec]/[dec]
Explanation The E1T1 VWIC relays have undergone a state change.
Recommended Action This is indicative of normal system behavior. No action is required.
EAP Messages
The following are Extensible Authentication Protocol messages.
Error Message%EAP-4-BADPKT : IP=[IP_address]| HOST=[chars]
Explanation The router has received an invalid or malformed EAP packet from the specified host.
Recommended Action Check specified host for EAP operation.
Error Message%EAP-6-MPPE_KEY : IP=[chars]| MPPE_RECV_KEY_LENGTH=[dec]
Explanation The router has received in MPPE key for the specified host.
Recommended Action No action is required.
Error Message%EAP-2-PROCESS_ERR : [chars]
Explanation A critical condition has occurred. The router could not perform an EAP process-related operation.
Recommended Action Reload the device.
EC Messages
The following are Port Aggregation Protocol messages.
Error Message%EC-5-UNSUITABLE : [chars] will not join any port-channel, [chars]
Explanation Port-fast, VMPS, or Dest-SPAN cannot be configured for EtherChannel.
Recommended Action Unconfigure Port-fast, VMPS, or Dest-SPAN.
EM_FPGA Messages
The following are messages for the Cisco 1840 FPGA encryption, decryption and hash message authentication codes (HMAC) for IP Security (IPSec).
Error Message%EM_FPGA-3-EM_PROC_ERR : VPN Module Command Processor error: ([chars])
Explanation A VPN module command processor error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-1-EM_PROC_INIT : VPN Module Command Processor initialization failed: ([chars])
Explanation The VPN module command processor could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-1-ERROR : [chars]
Explanation An error occurred in the application that is using the VPN module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-1-FPGA_ALIGN : [chars] Alignment failure on packet buffer: [hex]
Explanation A software error has occurred. The FPGA driver has detected that the buffer is not aligned correctly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-3-FPGA_INT : Wrong crypto IPSec interrup
Explanation An incorrect encryption (crypto) IPSec interrupt operation was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-1-FPGA_PARTICLE : We do not support particle so far
Explanation A packet with multiple particles was received. Packets with multiple particles are not supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-1-FPGA_RING_FULL : FPGA buffer descripter is full
Explanation The FPGA buffer descriptor is full.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-1-NOMEMORY : [chars] creation failed for FPGA
Explanation The VPN module driver could not allocate memory for the specified data structure.
Recommended Action Consider adding more memory. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%EM_FPGA-0-SELF_TEST_FAILURE : Encryption self-test failed ([chars])
Explanation One of the encryption self-tests has failed. The encryption engine cannot operate in its current state.
Recommended Action If the message persists, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical support representative to obtain a replacement Cisco IOS software image.
Error Message%EM_FPGA-6-SHUTDOWN : [chars] shutting down
Explanation The specified VPN module is shutting down. It may have been physically removed.
Recommended Action This is an informational message only. No action is required.
ENTITY_ALARM Messages
The following are entity alarm messages.
Error Message%ENTITY_ALARM-6-INFO : [chars] [chars] [chars] [chars] [chars]
Explanation Alarm assertion or deassertion information.
Recommended Action No action is required.
ENVM Messages
The following are environmental monitor messages.
Error Message%ENVM-3-BLOWER : [chars] may have failed
Explanation One of the cooling fans in the system might have failed. The hardware has reported a fan failure alarm to the system, or the system has detected a large temperature difference between the inlet and outlet temperature sensors.
Recommended Action Perform one or more of the following actions:
–
–
1.
2.
In this way, you can replace a faulty fan in a nonredundant power supply module without shutting down the system. Contact your Cisco technical support representative for help in replacing a faulty fan module.
–
Error Message%ENVM-2-CRITICAL : [chars] measured at [chars]
Explanation One of the measured environmental test points for voltage or temperature, as indicated by the message, has exceeded a critical level.
Recommended Action Correct the specified condition as quickly as possible or take the system offline and power down. If the system fails, it shuts down automatically as a preventive measure.
If the message is a temperature warning, perform the following checks:
1.
2.
3.
If it is a voltage problem on multiple cards, check your input AC/DC voltage source. If it is a voltage problem on a single card, ensure that a backup or spare card is available for replacement in case the voltage continues to deteriorate on that card.
If you think the message is in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-2-ENVCRIT : [chars] measured at [chars]
Explanation One of the measured environmental test points has exceeded an extreme threshold.
Recommended Action Correct the specified condition, or the system may shut itself down as a preventive measure. This condition could cause the system to fail to operate properly. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-ENVDATA : Environment data in [chars] invalid at slot [dec]
Explanation The environmental threshold data in the ID EEPROM of the system board is corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support and show diag slot-number commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-ENVM_NULL : [chars]
Explanation The software pointer for the environmental monitor table is empty. The platform subsystem may not have been initialized properly.
Recommended Action Shut down and restart the system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-ENVM_TBL_NULL : [chars]
Explanation The pointer table for a temperature, voltage, or power supply environmental component is empty. The platform subsystem may not have been initialized properly.
Recommended Action Shut down and restart the system. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-ENVWARN : [chars] measured at [chars]
Explanation One of the measured environmental test points has exceeded the warning threshold.
Recommended Action Closely monitor the condition, and correct it if possible. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-6-FANCHANGE : [chars] changed from [chars] to [chars]
Explanation The fan has changed its status because of the removal or insertion of a fan module in the system.
Recommended Action This is an informational message only. No action is required.
Error Message%ENVM-6-FANMISSING : Fan may have been removed
Explanation The software has detected that a fan is missing. If the system is not using a redundant power supply module, a fan module might be missing from the power supply bay.
Recommended Action Ensure that you have installed two power supply modules or one power supply module and one fan module. If the error message recurs despite the installation of the correct number of power supply and fan modules, copy the message exactly as it appears on the console or in the system log, and enter the show diag chassis command. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show diag chassis, show logging, and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-FRUUNKNOWN : Power supply or fan module in bay [dec] type unknown
Explanation The power supply or fan module type is unknown. The ID EEPROM of the module might not have been programmed or might have been corrupted, or the module might be an unsupported type.
Recommended Action Use only system-supported power supply or fan module types.
–
–
–
–
–
Error Message%ENVM-3-IDPROM : Access to [chars] failed at slot [dec]
Explanation Environmental monitoring threshold levels could not be read from the specified ID EEPROM for the specified card. The ID EEPROM is not accessible because of a hardware failure, because of incompatible Cisco IOS software, or because the ID EEPROM contents have been corrupted.
Recommended Action Enter the show diag slot-number command, with slot-number being the slot number of the affected card, and perform one of the following actions:
–
–
Error Message%ENVM-3-IOCARD_REV : [chars]
Explanation The revision number of the I/O card is not known. The I/O card plug-in is not recognized.
Recommended Action Insert the correct version of the I/O card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-LASTENV : [chars]
Explanation Operational data related to environmental monitoring could not be saved to nonvolatile storage in the chassis backplane EEPROM. This condition can be caused by an EEPROM (hardware) failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-LONGBUSY : C2W Interface busy for long time reading temperature sensor [dec]
Explanation Not available.
Recommended Action Not available.
Error Message%ENVM-3-NOACK : Access to [chars] in slot [dec] failed
Explanation Access to one of the temperature sensors failed because the device was not ready. The software will attempt to access the sensor again.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-3-NOFORK : Could not start environment polling process
Explanation The software could not start the environmental monitoring process. This condition can be caused by a low-memory condition. No monitoring will be performed. Without environmental monitoring, abnormal system conditions will not be detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show version and show processes memory commands. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show version, and show processes memory commands and your pertinent troubleshooting logs.
Error Message%ENVM-6-PSCHANGE : [chars] changed from [chars] to [chars]
Explanation A change has occurred to the status of the power supply. A power supply module has been inserted into or removed from the system.
Recommended Action This is an informational message only. No action is required.
Error Message%ENVM-6-PSLEV : [chars] state changed from [chars] to [chars]
Explanation One of the power supply test points has undergone a state change from a normal state to a shutdown state, or from a shutdown state to a normal state. This condition should occur only in a system with dual power supply modules. A state change from normal to shutdown is probably due to overheating caused by the failure of a power supply fan.
Recommended Action If the power supply has been shut down, replace the power supply module. If you believe this message to be in error, copy the message exactly as it appears on the console or in the system log. Enter the show diag chassis and show environment all commands. Contact your Cisco technical support representative and provide the representative with the gathered information. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-6-PSMISMATCH : Both AC and DC power supplies detected
Explanation A mix of AC and DC power supply modules has been detected. Such a mix is not supported. Both power supply modules must be of the same type, either AC or DC.
Recommended Action Use only one type of power supply. Remove one of the two power supply modules and either replace the removed one with the same type as the other power supply or operate the system on a single power supply.
If you think the message is in error, enter the show diag chassis and show environment all commands. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show commands and your pertinent troubleshooting logs.
Error Message%ENVM-4-READERROR : Error reading temperature sensor [dec]
Explanation Not available.
Recommended Action Not available.
Error Message%ENVM-3-REFVOLT : [chars]
Explanation The reference voltage has been measured as zero volts.
Recommended Action If this message is displayed 3 or more times, check the power supply. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-0-SHUT : Environmental Monitor initiated shutdown
Explanation The environmental monitor has initiated a system shutdown.
Recommended Action Look at previous environmental messages to determine the cause of the shutdown, and correct the condition if possible. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-0-SHUTDOWN : Environmental Monitor initiated shutdown due to [chars]in slot [dec] \n\n
Explanation The environmental monitor initiated a system shutdown because of a temperature or voltage condition.
Recommended Action Read any previous environmental messages to determine the cause of the shutdown and correct the cause, if possible. If you determine that the shutdown was in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%ENVM-0-STATUS_NOT_READY : Environmental Monitor temperature sensor not ready
Explanation The temperature sensor is not ready.
Recommended Action The temperature hardware might have to be replaced. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Recommended Action Check with hardware engineer on Mistral temperature hardware.Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ENVM-3-VOLT_NORMAL : System sensor Voltage name: [chars], is now operating under NORMAL voltage at [dec] mV.
Explanation One of the measured environmental test points is below normal operating voltage.
Recommended Action Not available.
Error Message%ENVM-1-VOLT_WARNING : Environmental monitor detects voltage out-of-range warning. Voltage name: [chars], Nominal: [dec] Voltage sensor reading: [dec]
Explanation The voltage is either too high or too low. For AS5400/AS5350, a warning message is displayed on the console and an SNMP trap is sent out.
Recommended Action Make sure that the power supply to the AS5400/AS5350 is normal. If the problem can not be corrected, power off the system to avoid damage to the internal parts.
Error Message%ENVM-4-WARNING : [chars] measured at [chars]
Explanation One of the measured environmental test points for voltage or temperature has exceeded the warning level.
Recommended Action Closely monitor the condition and correct it if possible.
If the message is a temperature warning, perform the following checks:
1.
2.
3.
If it is a voltage problem on multiple cards, check your input AC/DC voltage source. If it is a voltage problem on a single card, ensure that a backup or spare card is available for replacement in case the voltage continues to deteriorate on that card.
If you think the message is in error, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.