-
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
C10K_QUEUE_CFG_GENERAL Messages
C6K_MWAM_CENTRALIZED_CONFIG Messages
C10K Messages
The following are Cisco 10000 messages.
Error Message%C10K-2-BADINTERFACE : Out of range Card interface, [dec] on slot [dec]
Explanation The software specified a card interface that is not in the allowable range.
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%C10K-2-BADRSRCNUM : Invalid resource number from PXF ([dec]). (PLEASE REPORT THIS!)
Explanation The PXF hardware diversion path specified an invalid resource number.
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%C10K-2-BADSLOT : Out of range card slot index[dec]
Explanation The software specified a card slot index that is not in the allowable range.
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%C10K-2-BADSLOTSUBSLOT : Out of range card slot/subslot pair[dec]/[dec]
Explanation The software specified a card slot and subslot pair that is not in the allowable range.
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%C10K-2-CARDRECUR : Recursive loop while getting the daughtercard info for card type [dec]
Explanation While retrieving the daughter card information for the chassis MIB, the platform SNMP code has gone into an infinite loop.
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%C10K-3-CHASSIS : Unknown chassis model.
Explanation The data stored in the midplane is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update the system. 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.
Error Message%C10K-3-CONFIG : Recommended port adapter configuration exceeded
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-4-COOKIE : Corrupt or missing MAC address cookie\n using random base [enet]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-DEACTIVATED : card in slot [[dec]/[dec]] disabled.
Explanation The card in the specified slot is being deactivated.
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%C10K-1-DISCOVER_ENET : Failed to init Ethernet device [dec]
Explanation The software could not initialize.
Recommended Action Power down, reseat the interface card, 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%C10K-1-DISCOVER_SAR : Failed to init SAR device [dec]
Explanation The software for the SAR device could not initialize.
Recommended Action Power down, reseat the interface card, 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%C10K-3-EEPROM_INVALID : Invalid or unprogrammed [chars] EEPROM
Explanation The EEPROM specified in the message is either unprogrammed, has a bad magic number or is of the wrong type.
Recommended Action Program the specified EEPROM or replace it if it is the wrong type.
Error Message%C10K-3-IONOT0 : IO card discover in non-zero slot [dec]/[dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-IPC : [chars]: IPC Failure
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-IPCOPENFAILED : Couldn't open IPC portfor port id [hex] slot [int]/[int]: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-1-LC_ALERT : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-2-LC_CRIT : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-7-LC_DEBUG : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-0-LC_EMERG : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-LC_ERR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-6-LC_INFO : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-5-LC_NOTICE : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-LC_UNKNOWN : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-4-LC_WARN : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-4-MACBLKSIZE : Unknown MAC address block size.
Explanation The data stored in the midplane is invalid or is incomplete.
Recommended Action Contact your Cisco technical support representative to update the system. 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.
Error Message%C10K-3-NOACK : Access to [chars] temperature sensor failed
Explanation Access to the chassis temperature sensor has 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%C10K-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from EEPROM. This condition is probably caused by a 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%C10K-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-NOMEM : OUT of Memory: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-NOPORTINFO : Port info invalid for port [dec] slot [int]/[int]: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-NOPORTINFO_ID : Port info invalid for port id [hex] slot [int]/[int]: [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-4-PCIVALID : PCI activation failed, slot [dec], [hex]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-PLUGIN_UNKNOWN : Unknown card type [hex] in slot [dec]/[dec].
Explanation The card in the specified slot is not a known type.
Recommended Action Unavailable.
Error Message%C10K-4-TEST : Test command no. [dec] executed by user
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-UNEXP_INTR : Interrupt [chars] not expected, masking off
Explanation An interrupt of a certain type was signalled, but the interrupt handler for this type of interrupt has not yet been installed. This error should be self-correcting, but indicates either a hardware or a software defect.
Recommended Action Monitor the condition. If the condition was caused by a hardware defect, further errors are to be expected. If the condition was caused by a software defect, certain types of error and alarm conditions may be left undetected. 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.
C10K_APS Messages
The following are NSP APS messages.
Error Message%C10K_APS-3-INTERNAL1 : APS internal error, [chars] [dec] [dec]
Explanation An APS internal 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%C10K_APS-3-INTERNAL2 : APS internal error, [chars] [hex] [hex] [dec]
Explanation An APS internal 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%C10K_APS-3-INTERNALCFG : APS config internal error, [dec] [dec]
Explanation An APS internal 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%C10K_APS-4-SWITCH : Interface [chars] switched from [chars] to [chars] channel
Explanation The APS logic has determined that a switchover from one port to another was required.
Recommended Action No action is required.
C10KATM Messages
The following are Cisco 10000 ATM messages.
Error Message%C10KATM-3-DICK_TRACY : [chars]
Explanation An error for which there is no valid excuse 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%C10KATM-3-INTERNAL : C10K ATM internal error, [chars] [dec] [dec]
Explanation An internal Cisco 10000 ATM 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%C10KATM-3-INTERNALCMD : C10K ATM LC command internal error, [chars] [dec] [dec]
Explanation An internal Cisco 10000 ATM line card command 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%C10KATM-3-INTERNALEVT : C10K ATM LC Event internal error, [chars] [dec] [dec]
Explanation An internal Cisco 10000 ATM line card event 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%C10KATM-3-MIBINITFAIL : Sonet MIB initialization failed, [chars] [dec]
Explanation MIB initialization for SONET has 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%C10KATM-4-QCREATEFAIL : [chars] [chars] [int]/[int]([int]) [chars]
Explanation A queue failed to be created. System limits have likely been exceeded.
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%C10KATM-4-REDINLCEVT : Redundant inactive i/f ([chars]) event: [chars], reason: [chars]
Explanation An internal redundant line card event 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%C10KATM-4-UNSUP : ([dec]/[dec]) Interface ([chars]): unsupported feature: [chars]
Explanation The feature specified in the message text is not supported by Omega.
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.
C10KEVENTMGR Messages
The following are Event Manager subsystem messages.
Error Message%C10KEVENTMGR-1-CRITICAL_FAULT : [chars], Restarting IOS
Explanation A critical fault has occurred. The system is performing a crash dump operation.
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%C10KEVENTMGR-1-IRONBUS_FAILURE : [chars], Restart Failed([hex]). Resetting line card.
Explanation An Ironbus fault has occurred. The Ironbus failed to restart.
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%C10KEVENTMGR-1-IRONBUS_FAULT : [chars], Restarting Ironbus
Explanation An Ironbus fault has occurred. The Ironbus is being restarted.
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%C10KEVENTMGR-1-IRONBUS_REOCCURRING : [chars], Resetting line card.
Explanation An Ironbus fault has reoccurred. The line card is being reset.
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%C10KEVENTMGR-1-IRONBUS_SUCCESS : [chars], Restart Successful
Explanation An Ironbus fault has occurred, and the Ironbus restarted successfully.
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%C10KEVENTMGR-1-MAJOR_FAULT : [chars], Restarting PXF
Explanation A major fault has occurred. The PXF complex is being restarted.
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%C10KEVENTMGR-1-MINOR_FAULT : [chars]
Explanation A threshold for a minor event has been reached.
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%C10KEVENTMGR-1-MINOR_REOCCURRING : [chars]
Explanation A minor fault is reoccurring.
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%C10KEVENTMGR-4-PXF_CRASHINFO : Writing PXF debug information to [chars].
Explanation A file containing information useful for diagnosing a PXF restart is being written.
Recommended Action Save the PXF crash information (pxf_crashinfo) file to assist your Cisco technical support representative in fixing the 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%C10KEVENTMGR-3-PXF_CRASHINFO_FAIL : Failed to write PXF debug information.
Explanation PXF debugging information could not be written. The device on which the write was attempted is likely out of free space, or the write has encountered some other error.
Recommended Action Free up some space on the device to which the PXF debugging information was to be written.
Error Message%C10KEVENTMGR-1-SBE_DEBUG : Address: [hex], Who: [hex], Data With ECC: [hex] [hex] [hex] [hex], Data w/o ECC: [hex] [hex] [hex] [hex]
Explanation This message provides debug data for single-bit correctable errors.
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%C10KEVENTMGR-3-UNKNOWN_EVENT : Unknown event from [chars]. Event code:[dec]
Explanation An unknown event message has been received from the line card.
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.
C10KGE Messages
The following are Gigabit Ethernet subsystem messages.
Error Message%C10KGE-3-GBIC_MISSING : Interface [chars], Gigabit Interface Converter (GBIC) missing
Explanation A Gigabit Ethernet GBIC was removed from the line card.
Recommended Action Insert a GBIC into the line card.
Error Message%C10KGE-6-GBIC_OK : Interface [chars], 1000BASE-[chars] Gigabit Interface Converter (GBIC) inserted
Explanation A Gigabit Ethernet GBIC was inserted into the line card.
Recommended Action No action is required.
Error Message%C10KGE-1-INITFAIL : [chars], initialization failure
Explanation Gigabit Ethernet hardware initialization has 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%C10KGE-4-IPCFAIL : [chars], [chars] command failure ([chars])
Explanation A command message that was sent to the line card has failed.
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%C10KGE-3-MAXADDR : [chars], total addresses greater than [chars]
Explanation The number of addresses in the address filter is too large.
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%C10KGE-4-MSGVERSION : Incompatible message version with slot [dec]
Explanation An incompatibility exists between the message version being sent by the line card and the message version used by the RP. This type of incompatibility could occur if the RP and GE line card are using different Cisco IOS software versions due to an RP OIR event.
Recommended Action Reload the microcode.
Error Message%C10KGE-6-UNKNOWN : Unknown message ([dec]) received ([chars]) from interface [chars]
Explanation An unknown message has been received from the line card.
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.
C10KINT Messages
The following are Cisco 10000 interrupt infrastructure messages.
Error Message%C10KINT-3-INTERNAL_ERROR : no handler for index [dec]
Explanation An internal error has occurred. An interrupt has been detected for which no handler has been registered.
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%C10KINT-5-SPURIOUS : Spurious level [dec] interrupt ([dec])
Explanation An interrupt for which no cause could be found 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.
C10K_QOS_GENERAL Messages
The following are Cisco 10000 Quality of Service (QoS) messages.
Error Message%C10K_QOS_GENERAL-3-EREVENT : Error @ [chars]:[dec]
Explanation This message provides sanity testing error information.
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.
C10K_QUEUE_CFG_GENERAL Messages
The following are Cisco 10000 PXF queuing configuration messages.
Error Message%C10K_QUEUE_CFG_GENERAL-3-EREVENT : Error @ [chars]:[dec]
Explanation This message provides sanity testing error information.
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.
C10K_TOASTER Messages
The following are Cisco 10000 toaster messages.
Error Message%C10K_TOASTER-2-BADCHKSUM : Bad C10K_TOASTER microcode checksum, expected [dec], got [dec].
Explanation The checksum evaluated through the microcode does not match the checksum recorded in the header. This condition indicates that the software image is likely to be corrupted.
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%C10K_TOASTER-2-BADREAD : Read failed for [chars] on C10K_TOASTER [chars].
Explanation A read error occurred on the file during the microcode image load of the C10K_TOASTER column.
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%C10K_TOASTER-1-DOWNLOAD : [chars]: Toaster microcode image [chars]: could not be downloaded.
Explanation The toaster microcode could not be downloaded. This condition could be caused by an already corrupted image or to a software or hardware 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%C10K_TOASTER-2-DUMP : C10K Toaster has crashed, attempting to write core file(s)....
Explanation The C10K toaster has crashed because of an exception condition. Depending on the current configuration, one or more core files will be generated.
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%C10K_TOASTER-2-DWNLOAD : Could not download the microcode into C10K_TOASTER processor @ column [dec] row [dec].
Explanation Microcode from could not be downloaded to the toaster. This condition could be caused by either a software or hardware 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%C10K_TOASTER-3-ERROR : [chars]
Explanation This message provides general error information.
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%C10K_TOASTER-0-FP_ERROR : FP Init error: [chars]
Explanation The FP board is not working properly or it is not compatible with this Cisco IOS software image.
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%C10K_TOASTER-0-FP_REV : FP rev [dec].[dec] is [chars], require at least [dec].[dec]
Explanation Either this Cisco IOS software image is incompatible with the hardware revision of the FP board, or the FP board is supported but with software workarounds for certain hardware errors. In the first case, the Cisco IOS software will not complete the boot process. In the second case, the Cisco IOS software will run but may exhibit unexpected behavior.
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%C10K_TOASTER-0-FP_TYPE : FP type [dec] is [chars]
Explanation This Cisco IOS software image is incompatible with the hardware type of the FP board.
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%C10K_TOASTER-1-HDRCORRUPT : Toaster microcode header of image [chars] has been corrupted, expected [hex], got [hex].
Explanation The toaster microcode appears to be corrupted. This condition might be caused by an already corrupted image or, less likely, by 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%C10K_TOASTER-1-IMAGE : Toaster microcode image [chars]: could not be read.
Explanation The toaster microcode could not be read. This condition might be caused by an already corrupted image or, less likely, by 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%C10K_TOASTER-1-INCOMPAT : This microcode image is incompatible with this Cisco IOS image.
Explanation The signature in the microcode image does not match the signature in the Cisco IOS software image.
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%C10K_TOASTER-1-METADATA : Toaster microcode meta-data [chars]: [chars], in file: [chars].
Explanation The toaster microcode appears to be corrupted. This condition might be caused by an already corrupted image or, less likely, by 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%C10K_TOASTER-2-NONEXIST : Could not open or stat [chars] for PXF [chars].
Explanation There is a possibility that the Cisco 10000 toaster microcode may not be bundled into the image correctly, or a software error occurred that prevented the microcode from being loaded.
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%C10K_TOASTER-1-OPER : Toasters not operational: [chars]
Explanation The toaster clients could not be made operational. This condition could be caused by a software or hardware 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%C10K_TOASTER-1-ROW : Toaster microcode header of image [chars] doesn't match block [chars], row [dec] not row [dec].
Explanation The toaster microcode appears to be corrupted. This condition could be caused by an already corrupted image or, less likely, by 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%C10K_TOASTER-2-STALL : Toaster Stall detected
Explanation The Cisco 10000 toaster driver detected a toaster stall condition.
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%C10K_TOASTER-1-START : Toasters not started: memory state: [dec], expected [dec].
Explanation The toaster clients could not be started. This condition could be caused by either a software or a hardware problem.
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%C10K_TOASTER-1-TDB : Could not find control block for Toaster image [chars].
Explanation A software error occurred that prevented the control block representing this toaster from being located.
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%C10K_TOASTER-1-UNUSABLE : No usable Toaster microcode
Explanation No usable toaster microcode could be loaded. This condition could be caused by an already corrupted image or by a software or hardware 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.
C1700 Messages
The following are Cisco 1700 platform messages.
Error Message%C1700-3-E1T1_SPEED_UNAVAILABLE : Requested speed is not supported on [dec]/[dec]:[dec]\n
Explanation The call speed requested by the user is not supported on the time slot indicated in the error message. The default call speed is 64 kbps. To use 48 or 56 kbps speeds, multi-channel support must be enabled on the time slots.
Recommended Action Enter the tdm multichannel command to enable multichannel support for the time slot.
C1700_EM Messages
The following are Cisco 1700 Encryption Module (EM) messages.
Error Message%C1700_EM-3-DSP_NOT_RESPONDING : Power-on Self Test failed on VPN Module.
Explanation The power-on self-test failed on 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.
C2400_DSX1 Messages
The following are Cisco 2400 DSX1 subsystem messages.
Error Message%C2400_DSX1-5-C2400_NOTICE : NULL
Explanation This is a notification message.
Recommended Action No action is required.
Error Message%C2400_DSX1-3-ERROR : NULL
Explanation This message provides information regarding 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.
C3200_FE Messages
The following are Cisco 3200 FEC messages.
Error Message%C3200_FE-4-BABBLE : C3200/FE([dec]/[dec]), Babble error, CSR[dec]=[hex]
Explanation The transmitter has been on the channel longer than the time required to transmit the largest frame.
Recommended Action The system should recover. No action is required.
Error Message%C3200_FE-5-EXECOLL : C3200/FE([dec]/[dec]), Excessive collision
Explanation Excessive collisions have occurred on the Fast Ethernet interface.
Recommended Action No action is required.
Error Message%C3200_FE-1-INITFAILP : C3200/FE([dec]/[dec]), Init failed at [chars]
Explanation Fast Ethernet could not allocate an I/O buffer pool.
Recommended Action Clear the interface. 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%C3200_FE-5-LATECOLL : C3200/FE([dec]/[dec]), Late collision
Explanation Late collisions have occurred on the Fast Ethernet interface.
Recommended Action If the interface is Fast Ethernet, verify that both peers are in the same duplex mode. No other action is required.
Error Message%C3200_FE-5-LOSTCARR : C3200/FE([dec]/[dec]), Lost carrier. Transceiver problem?
Explanation The cable or transceiver is not connected.
Recommended Action Connect the cable or the transceiver.
Error Message%C3200_FE-1-MACADDRFAIL : C3200/FE([dec]/[dec]), Unable to set the Mac-address for the interface
Explanation The FEC could not set the MAC address of the interface.
Recommended Action Clear the interface. 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%C3200_FE-2-NOISL : Interface [chars] does not support ISL
Explanation The interface cannot be configured as an ISL trunk.
Recommended Action Check the system configuration.
Error Message%C3200_FE-3-OVERFLO : C3200/FE([dec]/[dec]), Receive overflow
Explanation While a frame was being received, the local buffer of the controller chip transmitted insufficient data because data could not be transferred to DRAM quickly enough to keep pace with its input rate. Normally, such a condition is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%C3200_FE-1-SHOWFAIL : C3200/FE([dec]/[dec]), Memory error at [chars]
Explanation The FEC could not allocate memory to display the controller.
Recommended Action Clear the interface. 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%C3200_FE-3-UNDERFLO : C3200/FE([dec]/[dec]), Transmit underflow
Explanation While a frame was being transmitted, the local buffer of the controller chip received insufficient data because data could not be transferred to the chip quickly enough to keep pace with its output rate. Normally, such a condition is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
C3800 Messages
The following are Cisco 3800 platform messages.
Error Message%C3800-3-HWIC_SPURIOUS_INTR : Spurious Error interrupt on HWIC [dec]. Interrupt masked\n
Explanation An HWIC error interrupt handler could not be found.
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%C3800-3-PAK_NOT_CLEAN : Pak returned to input onboard GE interface has particles at [chars]. Particle Count = [dec]. First 40 bytes of Pak:\n[chars]\n
Explanation A packet that contains particles has been detected while the onboard GE was performing post-packet processing.
Recommended Action This is a debug message only. No action is required.
Error Message%C3800-3-RTC_CHIP_NOT_RESPONDING : RTC (real time clock) chip is not responding\n
Explanation The real time clock that operates through the SMBus has timed out. Calendar functions will not be available.
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%C3800-3-RTC_FAILURE : [chars] onboard Real Time Clock [chars] chip failed\n
Explanation The RTC chip experienced failure during a read or write operation. This condition could be due to a high system load.
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.
C3800_ENVM Messages
The following are environmental messages.
Error Message%C3800_ENVM-1-BP_THERMAL : System detected a thermal warning on the Backplane
Explanation The backplane has experienced an over-temperature condition.
Recommended Action Unavailable.
Error Message%C3800_ENVM-3-MFAIL_OFF : There is more than one failure with the Power System [dec] or this Power System has been turned off.
Explanation The power system has experienced multiple failures, or the power system has been turned off. This message indicates that a critical condition has occurred.
Recommended Action Examine the LEDs on the power supply to identify the failures or turn on the power supply.
Error Message%C3800_ENVM-3-PS_AUX_FAIL : System detected AUX(-48V) PS [dec] Fail Condition
Explanation The auxiliary -48V power supply has experienced a failure.
Recommended Action Replace the power supply.
Error Message%C3800_ENVM-3-PS_FAN_FAIL : System detected SYS PS [dec] Fan Fail Condition
Explanation The power supply has experienced a fan failure.
Recommended Action Replace the power supply.
Error Message%C3800_ENVM-3-PS_FAN_OK : SYS PS [dec] Fan Condition is now normal
Explanation The previously reported fan failure has cleared.
Recommended Action No action is required.
Error Message%C3800_ENVM-3-PS_INPUT_FAIL : System detected SYS PS [dec] Input Voltage Fail Condition
Explanation The input to the power supply has failed.
Recommended Action Verify that the power cord is plugged into the power supply and ensure that power is available to the input.
Error Message%C3800_ENVM-3-PS_INPUT_OK : Input Voltage to SYS PS [dec] is now normal
Explanation The previously reported input voltage fail condition has cleared.
Recommended Action No action is required.
Error Message%C3800_ENVM-3-PS_OUTPUT_FAIL : System detected SYS PS [dec] DC Output Voltage Fail Condition
Explanation The power supply has failed.
Recommended Action Replace the power supply.
Error Message%C3800_ENVM-3-PS_OUTPUT_OK : SYS PS [dec] Output is now normal
Explanation The previously reported output voltage fail condition has cleared.
Recommended Action No action is required.
Error Message%C3800_ENVM-1-PS_THERMAL : System detected a thermal warning on SYS PS [dec]. The PS is close to autoshutdown limit
Explanation The power supply has experienced an over-temperature condition. The specified power supply may be automatically shut down in a short period of time.
Recommended Action Unavailable.
Error Message%C3800_ENVM-5-RPS : Redundant power supply [chars]
Explanation A redundant power supply either has been attached or has been removed.
Recommended Action No action is required.
C3825 Messages
The following are Cisco 3825 messages.
Error Message%C3825-3-OIR_NOT_SUPPORTED : OIR event detected on slot [dec]. OIR not supported on this platform. Inserting or removing modules while router is powered on may cause router to crash \n
Explanation An OIR event has detected a module in the slot specified in the message text. OIR operations are not supported on this platform. Inserting or removing modules while the router is operational may cause the router to crash
Recommended Action Do not insert or remove network modules while the router is operational.
C54x Messages
The following are Voice over IP (VoIP) digital signal processor (DSP) driver messages.
Error Message%C54x-1-NO_RING_DESCRIPTORS : No more ring descriptors available on [dec] slot.
Explanation The C54x DSP driver cannot queue messages to the DMA engine for transmission.
Recommended Action Reset the DSPs on this port module. 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%C54x-1-TOOBIG : [chars], packet(size [dec]) too big.
Explanation A packet greater than the allowed maximum size of 256 bytes has been received on this interface.
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.
C5510 Messages
The following are Voice Over IP (VoIP) driver messages.
Error Message%C5510-1-C5510_CHPI_ERROR : cHPI error for pa_bay [dec] pump [dec] dsp [dec].
Explanation The FPGA has detected a protocol error involving the cHPI.
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%C5510-1-C5510_HPI_TIMEOUT : HPI Timeout error for pa_bay [dec] pump [dec] dsp [hex].
Explanation The FPGA has detected a that the DSP HPI has timed out.
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%C5510-3-C5510_INGRESS_Q_FULL : Ingress Queue Full detected for pa_bay [dec] pump [dec].
Explanation The FPGA cannot process ingress data because no ingress buffers are available.
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%C5510-3-ERROR_ANALYZE : Error analyzing the device in slot [dec].
Explanation The port module in this slot could not be recognized.
Recommended Action Power down, reinsert the port module, 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%C5510-3-ERROR_FIRMWARE_DNLD : DSP firmware download fails for slot [dec] dsp_id [dec]
Explanation An error occurred while the DSP was being initialized with the application firmware.
Recommended Action Power down, reinsert the port module, 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%C5510-3-IDB_CREATE : Error creating an idb for VoIP fastswitching in slot [dec].
Explanation The voice driver failed to create an IDB for VoIP fast switching.
Recommended Action Power down and reboot the system. If this message recurs, the Cisco IOS software image is most likely missing a required subsystem. 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%C5510-1-INCORRECT_DSP_ID : AIM VOICE at slot [dec] receives data from incorrect DSP-ID [dec].
Explanation The DSP ID provided by the FPGA for download is not valid.
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%C5510-1-NOPCIMEMORY : VPM ([dec]/[dec]), PCI memory unavailable.
Explanation The router or access server could not allocate memory for the descriptors.
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%C5510-1-NO_RING_DESCRIPTORS : No more ring descriptors available on slot [dec] dsp [dec].
Explanation The 5421 driver cannot queue messages to the egress queue so that the FPGA can transmit the messages.
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%C5510-1-TOOBIG : [chars], packet(size [dec]) too big.
Explanation A packet greater than the 264 bytes has been received on this interface.
Recommended Action The system should recover. No action is required. If the error recurs, it indicates an error that might be related to data traffic patterns. 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.
C6K_MWAM_CENTRALIZED_CONFIG Messages
The following Multiprocessor WAN Application Module (MWAM) centralized configuration messages.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-ABORT_CFG_DNLD : Aborting pending download of config from supervisor.
Explanation While the processor was attempting to download its startup configuration from the supervisor engine, the mwam config-mode local command was entered.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-BEGIN_DOWNLOAD : Downloading config from supervisor
Explanation The processor has begun attempting to download its startup configuration from the supervisor engine rather than from local NVRAM.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-DNLD_ABORT_TIMEOUT : Timeout while waiting for download to abort
Explanation The processors on an MWAM will continue to download their configurations from the supervisor engine for a maximum of 30 minutes after the mwam config-mode supervisor command has been entered to bring the MWAM into supervisor mode. If, during this time, the user enters the mwam config-mode local command, an attempt will be made to abort the download from the supervisor engine. This message indicates that the attempt to abort the download has been retried for 60 seconds and has failed.
Recommended Action Reenter the mwam config-mode local command. If this message recurs, wait for 30 minutes until the download attempts stop, and retry the operation. 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%C6K_MWAM_CENTRALIZED_CONFIG-5-DOWNLOAD_ABORTED : Aborted download of startup configuration from supervisor
Explanation The mwam config-mode supervisor command has been entered to bring the MWAM into supervisor mode. While the processor was in the process of attempting to download its startup configuration from the supervisor engine, the mwam config-mode local command was entered. This command interrupted the download process and set the processor to use NVRAM for its startup configuration. The current default running configuration has been written to NVRAM.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-DOWNLOAD_COMPLETE : Configuration retrieved from supervisor in slot [dec]
Explanation The processor has successfully retrieved its startup configuration from the supervisor engine in the indicated slot.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-2-DOWNLOAD_FAILED : Failed to download startup configuration from supervisor
Explanation The processor has failed to download its startup configuration from the supervisor engine. The processor will use the default configuration. The Gigabit Ethernet interface will be shut down.
Recommended Action Move the processing functions to an alternate processor, or manually configure the processor from the console. Alternatively, manually download the configuration from the supervisor engine by entering the copy tftp://supervisor-ip/SLOTxPCy.cfg running-config command, with supervisor-ip being replaced with 128.0.0.1 if the active supervisor engine is in slot 1, or supervisor-ip being replaced with 128.0.0.2 if the active supervisor engine is in slot 2. In the filename SLOTxPCy.cfg, x should be replaced with the slot number of the MWAM, and y should be replaced with the failed processor number. To correct the problem, verify that access to the configuration files on the supervisor engine has been enabled (the no mwam bootflash access command disables access). Verify that the supervisor engine image supports centralized configuration by entering the mwam bootflash access command. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Perform the following actions:
1.
Enter the show module command.
2.
3.
4.
5.
6.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-2-DOWNLOAD_TASK_FAILED : The MWAM centralized configuration download process failed to start
Explanation An internal error occurred that prevented a required process from starting. The configuration will not be downloaded from the supervisor engine. The processor will have to be reloaded. You may choose to run this processor in local mode until this problem is resolved.
Recommended Action Move the processing functions to an alternate processor or manually configure the processor from the console. Alternatively, manually download the configuration from the supervisor engine by entering the copy tftp://supervisor-ip/SLOTxPCy.cfg running-config command, with supervisor-ip being replaced with 128.0.0.1 if the active supervisor engine is in slot 1, or supervisor-ip being replaced with 128.0.0.2 if the active supervisor engine is in slot 2. In the filename SLOTxPCy.cfg, x should be replaced with the slot number of the MWAM, and y should be replaced with the failed processor number. 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%C6K_MWAM_CENTRALIZED_CONFIG-6-INTERFACE_CHOSEN : Preparing internal interface [dec] for config retrieval.
Explanation In MWAM config-mode supervisor, processors 6 and 7 must choose an internal interface to use for downloading the configuration. This message displays the interface that was chosen.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-INVALID_SLOT : Invalid slot: During [chars], slot/cpu number retrieved, [dec]/[dec], ROMMON may be out of date
Explanation The processor has determined that it was using an invalid slot or CPU number while the configuration information was being retrieved from the supervisor engine.
Recommended Action Verify that the ROM monitor (ROMMON) is up to date. If it is not, upgrade by entering the upgrade rom-monitor command on each processor complex on the MWAM card. 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%C6K_MWAM_CENTRALIZED_CONFIG-6-MODE_CHANGED : mwam config-mode changed to [chars]
Explanation The MWAM configuration mode has been successfully changed.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-NV_DELETE_FAIL : Failed to delete local startup-config.
Explanation Deletion of local NVRAM has failed. Continuing anyway.
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 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 gathered information.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-1-NV_EXCEEDED : Config file [chars] size ([int]) exceeds allowed size ([int]). Deleting local startup-config
Explanation There is not enough space in local NVRAM to save the configuration after reading from the supervisor. The size of configuration should be reduced.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-NVRAM_CHANGE_FAILED : Mode remains [chars], [chars]
Explanation When the configuration mode (config-mode) was being changed from supervisor to local mode, an attempt was made to copy the running configuration to NVRAM (nvram:startup-config). When the configuration mode was being changed from local to supervisor mode, an attempt was made to copy the running configuration to a file on the bootflash of the supervisor engine. One of these copy operations has failed.
Recommended Action If you are changing the configuration mode from supervisor to local mode, enter the write erase command, wait for the NVRAM to reinitialize, and then retry the operation. If you are changing the configuration mode from local to supervisor mode, verify that the no bootflash access command has not been entered on the supervisor engine. Verify that there is room on the bootflash of the supervisor engine. Enter the squeeze command to obtain more space on the bootflash memory. If the problem persists, enter the following 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 logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-UNEXPECTED_EVENT : Unexpected event while aborting download of config from supervisor: [dec]:[dec]
Explanation An unexpected internal event has occurred that interfered with completing the change in configuration modes. Your system should operate normally otherwise.
Recommended Action Reenter the mwam config-mode local command. The download attempts will retry for a maximum of 30 minutes. If this message recurs, wait 30 minutes until the download attempts stop, and retry the operation. 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%C6K_MWAM_CENTRALIZED_CONFIG-5-UPLD_FAILURE : Failed to upload config to [chars] on supervisor. slavebootflash:is hosted on the standby supervisor engine. Failure to write to the slavebootflash: may be safely ignored when there is no standby supervisor engine. Otherwise, check for space on supervisor, squeeze supervisor bootflash: and slavebootflash: as needed
Explanation The processor has failed to upload the running configuration to the indicated supervisor engine.
Recommended Action Perform one or more of the following actions:
–
–
–
–
–
–
–
–
–
–
–
–
–
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-UPLD_SUCCESS : Success: config uploaded to supervisor [chars]
Explanation The processor has successfully uploaded the running configuration to the indicated supervisor engine.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-UPLOAD_FAILED : All writes to supervisor failed.
Explanation The attempt to save the configuration in while in supervisor mode has failed.
Recommended Action Enter the mwam bootflash access command to verify that access to the bootflash has been enabled. Verify that there is space available on the bootflash of the supervisor engines. If sufficient space is not available on the bootflash, delete files or enter the squeeze bootflash: command from the supervisor engine console. If this message recurs, verify that internal communication has been enabled by entering the session slot slot-number processor processor-number command, with slot-number being the slot number of the affected line card and processor-number being the number of the affected processor. If the session fails for all processors on the MWAM card, enter the hw-module module slot-number reset command, with slot-number being the slot number of the affected line card, to reestablish the communication paths.
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. Perform the following actions and attach the following information to your case in nonzipped, plain-text (.txt) format:
–
–
–
–
–
–
–
–
–
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-UPLOAD_SUCCEEDED : Config uploaded to [dec] supervisor file system(s)
Explanation The MWAM processor is in MWAM config-mode supervisor mode, and the configuration has been successfully saved to one or more supervisor engines.
Recommended Action No action is required. If the number of supervisors indicated in the message text does not match the number that have been installed, you may have to verify that the files on the bootflash and standby bootflash of the supervisor engine are the latest versions. If the files on the active and standby bootflash are not current, perform the following actions:
1.
2.
C6KENV Messages
The following are Cisco Catalyst 6000 environmental system messages.
Error Message%C6KENV-4-CLOCKFAILED : clock [dec] failed
Explanation The indicated clock has failed. The system will continue to operate, using the redundant clock.
Recommended Action Replace the failed clock.
Error Message%C6KENV-0-CLOCKMAJFAILED : too many clocks failed to continue system operation
Explanation The system requires at least 1 clock to operate. No clocks are operational so no packets can be forwarded.
Recommended Action Replace the clocks, the backplane, or the chassis.
Error Message%C6KENV-2-CLOCKMAJRECOVERED : enough clocks operational to continue system operation
Explanation The system can continue operating using the recovered clock.
Recommended Action No action is required.
Error Message%C6KENV-4-CLOCKOK : clock [dec] operational
Explanation A previously failed clock has declared itself operational.
Recommended Action No action is required.
Error Message%C6KENV-4-FANTRAYFAILED : fan tray failed
Explanation One or more fans in the system fan tray has failed. Although this is a minor alarm, system components could overheat and be shut down.
Recommended Action Replace the system fan tray as soon as possible.
Error Message%C6KENV-4-FANTRAYOK : fan tray OK
Explanation All fans in the fan tray are operating.
Recommended Action No action is required.
Error Message%C6KENV-2-MAJORTEMPALARM : [chars] has exceeded allowed operating temperature range.
Explanation The component will be powered off. For shared components, this requires powering off the system.
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. Enter the show tech-support command to gather data that may help identify the nature of the error. 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 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 gathered information.
Error Message%C6KENV-4-MAJORTEMPALARMRECOVER : [chars] has returned to allowed operating temperature range.
Explanation The component has returned to the allowed temperature range. The scheduled shutdown is canceled and the device will continue operating.
Recommended Action No action is required.
Error Message%C6KENV-4-MINORTEMPALARM : [chars] has exceeded normal operating temperature range.
Explanation This message may indicate a trend for the component, and a trend for other components in the system.
Recommended Action Inspect the indicated component closely to determine why it is operating out of normal operating temperature range and whether it will eventually exceed the allowed operating temperature range.
Error Message%C6KENV-4-MINORTEMPALARMRECOVER : [chars] has returned to normal operating temperature range.
Explanation The component is now operating within the normal operating temperature range.
Recommended Action No action is required.
Error Message%C6KENV-4-PSFANFAILED : the fan in power supply [dec] has failed
Explanation The fan in power supply [dec] has failed. This failure could lead to the power supply overheating and being shut down.
Recommended Action Replace the power supply as soon as possible.
Error Message%C6KENV-4-PSFANOK : the fan in power supply [dec] is OK
Explanation The fan in power supply [dec] is operating.
Recommended Action No action is required.
Error Message%C6KENV-2-SHUTDOWN : shutdown [chars] now because of [chars].
Explanation The indicated component is shut down.
Recommended Action Replace the component as soon as possible.
Error Message%C6KENV-2-SHUTDOWN_CANCELLED : shutdown for [chars] cancelled
Explanation The situation that caused a shutdown to be scheduled was corrected. The shutdown has been canceled.
Recommended Action No action is required.
Error Message%C6KENV-1-SHUTDOWN_DISABLED : need to shutdown [chars] now but shutdown action is disabled!
Explanation The user has disabled the system shutdown. The system could not shut down the indicated component.
Recommended Action Manually shut down or remove the indicated component immediately.
Error Message%C6KENV-2-SHUTDOWN_SCHEDULED : shutdown for [chars] scheduled in [dec] seconds
Explanation A major alarm condition will be corrected by shutting down the affected component.
Recommended Action Replace the component as soon as possible.
Error Message%C6KENV-4-VTTFAILED : VTT [dec] failed
Explanation The indicated VTT has failed.
Recommended Action Replace the indicated VTT and/or the chassis at your earliest convenience.
Error Message%C6KENV-0-VTTMAJFAILED : Too many VTT failures to continue system operation
Explanation The Catalyst 6000 backplane data bus cannot operate without proper termination provided by the VTTs.
Recommended Action Replace the failed VTTs.
Error Message%C6KENV-2-VTTMAJRECOVERED : enough VTTs operational to continue system operation
Explanation The failed VTTs have begun operating again.
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 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 gathered information.
Error Message%C6KENV-4-VTTOK : VTT [dec] operational
Explanation The indicated VTT is operational.
Recommended Action No action is required.
C6KPWR Messages
The following are Cisco Catalyst 6000 power control system messages.
Error Message%C6KPWR-4-COULDNOTREPOWER : wanted to re-power FRU (slot [dec]) but could not.
Explanation The system was unable to repower the field replaceable unit (FRU) in the indicated slot. The slot number is [dec]. This message might display for a number of reasons. A unit cannot power up if the power supply does not meet the power requirement for that unit.
Recommended Action If a module is unable to power up due to overheating, allow sufficient time for the unit to cool down before attempting to power up the unit. If both power supplies are operational but a unit is not being powered up, contact your Cisco technical support representative.
Error Message%C6KPWR-4-DISABLED : power to module in slot [dec] set [chars]
Explanation The module in the indicated slot was powered off for the indicated reason.
Recommended Action Recovery depends on the indicated reason.
Error Message%C6KPWR-4-ENABLED : power to module in slot [dec] set on
Explanation The module in the indicated slot was powered up.
Recommended Action No action is required.
Error Message%C6KPWR-4-PSCOMBINEDMODE : power supplies set to combined mode.
Explanation The power supplies are set to combined mode.
Recommended Action No action is required.
Error Message%C6KPWR-4-PSFAIL : power supply [dec] output failed.
Explanation Power supply [dec] has failed.
Recommended Action Replace the power supply.
Error Message%C6KPWR-4-PSINSERTED : power supply inserted in slot [dec].
Explanation A power supply was inserted in slot [dec].
Recommended Action No action is required.
Error Message%C6KPWR-4-PSOK : power supply [dec] turned on.
Explanation Power supply [dec] is turned on.
Recommended Action No action is required.
Error Message%C6KPWR-4-PSREDUNDANTBOTHSUPPLY : in power-redundancy mode, system is operating on both power supplies.
Explanation When the system is in power redundancy mode, it operates on both power supplies.
Recommended Action No action is required.
Error Message%C6KPWR-4-PSREDUNDANTMISMATCH : power supplies rated outputs do not match.
Explanation The two power supplies in the system have different output ratings.
Recommended Action For more efficient load sharing, use power supplies with the same output rating.
Error Message%C6KPWR-4-PSREDUNDANTMODE : power supplies set to redundant mode.
Explanation The power suplies are set to redundant mode.
Recommended Action No action is required.
Error Message%C6KPWR-4-PSREDUNDANTONESUPPLY : in power-redundancy mode, system is operating on one power supply.
Explanation When the system is in power redundancy mode, it operates on only one power supply.
Recommended Action No action is required.
Error Message%C6KPWR-4-PSREMOVED : power supply removed from slot [dec].
Explanation A power supply was removed from slot [dec].
Recommended Action No action is required.
Error Message%C6KPWR-4-UNDERPOWERED : insufficient power to operate all FRUs in system.
Explanation There is insufficient power to operate all modules in the system.
Recommended Action Reconfigure the system or upgrade the power supplies.
Error Message%C6KPWR-4-UNSUPPORTED : unsupported module in slot [dec], power not allowed.
Explanation Power was not allocated to slot [dec], containing an unsupported module.
Recommended Action Remove the unsupported module or resolve the issue described in the message by inserting or replacing the Switch Fabric Module or by moving the module to a different slot.
C6MSFC Messages
The following are Multilayer Switching Feature Card messages.
Error Message%C6MSFC-3-BADCPUTYPE : Invalid CPU Type [dec].
Explanation The software does not recognize the MSFC on which it is operating. This problem might be caused by an improperly programmed or defective identification programmable read-only memory (IDPROM). [dec] is the invalid CPU type.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%C6MSFC-4-BADFLASH : Unsupported flash type in the bootflash - [chars].
Explanation The flash chips in the Flash SIMM are not supported by the platform.
Recommended Action Contact technical support to update your system.
Error Message%C6MSFC-3-CHASSIS : Unknown chassis model.
Explanation The data stored in the CPU IDPROM is bad or incomplete.
Recommended Action Contact technical support to update your system.
Error Message%C6MSFC-3-CONFIG : Recommended port adapter configuration exceeded
Explanation The total bandwidth of high and medium bandwidth port adapters exceeds the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high and medium bandwidth port adapters for the system.
Error Message%C6MSFC-4-COOKIE : Corrupt or missing MAC address cookie using random base [enet]
Explanation The content of the MAC address EEPROM is invalid. The system is providing a random MAC address. [enet] is the MAC address
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 that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C6MSFC-3-IONOT0 : IO card discover in non-zero slot [dec]
Explanation An I/O card has been detected in the nonzero slot indicated in the error message.
Recommended Action Verify that the card is in the correct slot and that the configuration is correct. Try the operation again.
Error Message%C6MSFC-4-MACBLKSIZE : Unknown MAC address block size.
Explanation The data stored in CPU IDPROM is bad or incomplete.
Recommended Action Contact technical support to update your system.
Error Message%C6MSFC-3-NOCPUVER : Invalid CPU Revision [dec].
Explanation The CPU ID could not be read from the EEPROM. This condition occurs when there is a hardware failure or when an incorrect Cisco IOS software image is loaded on the platform.
Recommended Action Ensure that the correct Cisco IOS software image is loaded on the platform.
Error Message%C6MSFC-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation The MAC address allocation failed because of an incorrect slot and interface combination, which exceeds the maximum available hardware. [num] / [num] are the module and interface numbers.
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 that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C6MSFC-4-PCIVALID : PCI activation failed, bay [dec], [hex]
Explanation Not available.
Recommended Action Not available.
C6SUP Messages
The following are C6SUP-specific messages.
Error Message%C6SUP-3-NOVLANMAC : Can't allocate MAC address for VLAN interface [int]
Explanation MAC address allocation failed because the VLAN number exceeds that provided for by the chassis.
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 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 gathered information.
C830_HW_CRYPTO Messages
The following are C830 Hifn messages.
Error Message%C830_HW_CRYPTO-0-HIFN_KAT_FAILURE : Hifn 7902 Known Answer Test failed ([chars])
Explanation One of the known answer tests has failed. The hardware crypto engine is not operable in this state.
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 at 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.
CALL_CONTROL Messages
The following are network call control messages.
Error Message%CALL_CONTROL-6-UNKNOWN_EXT_AGENT_RESET_ATTEMPT : Request to reset an uknown external agent (ID [dec]) attempted. Attempt ignored.\n
Explanation An attempt to reset an external agent has failed (such as the H323 Gatekeeper or the MGCP CA). A failed attempt is not a router error. However, it does indicate that the external agent never received the reset request.
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.