-
Cisco IOS Release 12.4 System Messages, Volume 1 of 2
-
System Messages Overview
-
AAA through ASPP
-
AT through BGP
-
BIT through C6KPWR
-
C6MSFC through CHOPIN_MAINBOARD_ASYNC_PQII
-
CI through COT
-
CPAD through DBUS
-
DCV through DSCREDCLK
-
DSI through ENT
-
ENV_MON through FR_FRAG
-
FR_LMI through GSR_ENV
-
GSRIPC through IF
-
IFINDEX through ISA
-
ISDN through LCCOREDUMP
-
LCINFO through MBRI
-
Volume 1 Glossary
-
Table Of Contents
C10K_QUEUE_CFG_GENERAL Messages
C2600_MAINBOARD_ASYNC_PQUICC Messages
C6K_MWAM_CENTRALIZED_CONFIG Messages
BIT Messages
The following are dynamic bitlist messages.
Error Message%BIT-4-OUTOFRANGE : bit [dec] is not in the expected range of [dec] to [dec]
Explanation An invalid request was detected by the bit list subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
BOOMERANG Messages
The following are boomerang distributed reverse proxy server messages.
Error Message%BOOMERANG-2-CIPHER_ERROR : The RC4 cipher check failed for domain [chars]. Boomerang packet dropped.
Explanation The system could not decipher the packet received from the boomerang server.
Recommended Action Ensure that the key that is configured on this router matches the key that is configured on the boomerang server. If the keys are identical, this situation may indicate a hostile attack.
Error Message%BOOMERANG-1-CONTENT_SERVER_DOWN : The content server [IP_address] is not responding to probes. Boomerang packets will be dropped.
Explanation The boomerang client is not receiving a valid response to probes. Probes, for which HTTP requests are used, are used to verify the health of the configured content server.
Recommended Action Ensure that the configured content server IP address and optional file to be probed are correct, and that the content server is operational.
Error Message%BOOMERANG-5-CONTENT_SERVER_UP : The content server [IP_address] is responding to probes.
Explanation The boomerang client is receiving a valid response to probes. Probes, for which HTTP requests are used, are used to verify the health of the configured content server.
Recommended Action No action is required.
Error Message%BOOMERANG-2-FUTURE_TRIGGER : Received trigger too far in the future. now=[hex]:[hex] trigger=[hex]:[hex]\n
Explanation The packet that was received from the boomerang server contained an NTP trigger with a trigger time that was too far ahead of the present time. The trigger time was adjusted to a reasonable value.
Recommended Action Ensure that the NTP server configured for this router is operational and that the NTP server configured for the boomerang server is operational.
Error Message%BOOMERANG-2-INVALID_DOMAIN : The domain [chars] in the DNS request is not configured. Boomerang packet dropped.
Explanation The domain name included in the DNS request received from the boomerang server is not configured on this router.
Recommended Action Configure a client domain for the domain name. This situation may indicate a hostile attack.
Error Message%BOOMERANG-4-SEQ_NBR_ERROR : The packet from the Boomerang Server contained an unexpected sequence number.
Explanation Packets sent by the boomerang server contain a sequence number. This sequence number is used to detect packet loss.
Recommended Action If the percentage of errors is high, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
BRI Messages
The following are ISDN Basic Rate Interface (BRI) messages.
Error Message%BRI-1-INITFAIL : Unit [dec], initialization timeout failure, csr[dec]=[hex]
Explanation The hardware has failed to initialize correctly.
Recommended Action Repair or replace the controller indicated in the error message.
Error Message%BRI-1-NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%BRI-4-NOSWITCH : Unit [dec], initialization timeout failure, csr[dec]=[hex]
Explanation The ISDN leased line requires that an ISDN switch type be configured.
Recommended Action Choose and configure a BRI switch type. If you are unsure of the switch type, choose any switch.
BRIMUX Messages
The following are Cisco AS5200 BRIMUX board messages.
Error Message%BRIMUX-3-BADBRIMUX : Slot [dec] [chars]
Explanation A BRIMUX firmware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-1-BADCODE : Software error: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-3-BADDLACK : Slot [dec] BRIC, failed to acknowledge download data block [dec]
Explanation A BRIMUX firmware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-3-BADDPM : Slot [dec] DPM, test failed at offset [hex], expect [hex], read [hex]
Explanation A BRIMUX board hardware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-3-BADULADDR : Slot [dec] BRIC, wrong upload address received [hex], requested [hex]
Explanation A BRIMUX firmware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-3-BADULBLK : Slot [dec] BRIC, wrong block [dec] for data upload, expect [dec]
Explanation A BRIMUX firmware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-3-BADULLEN : Slot [dec] BRIC, upload data length read [dec], truncate to [dec] bytes
Explanation A BRIMUX firmware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-3-BADULREQ : Slot [dec] BRIC, failed to send upload data block [dec]
Explanation A BRIMUX firmware problem might be present.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-5-CHANUPDOWN : B[dec] of BRI[dec] on slot [dec] BRIC, changed state to [chars]
Explanation A state change has occurred on a B channel of the BRIMUX board.
Recommended Action No action is required.
Error Message%BRIMUX-4-HEARTBEAT : Slot [dec] BRIC, lost heartbeat for [dec] seconds
Explanation A BRIMUX board hardware or firmware problem might be present.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BRIMUX-5-PORTUPDOWN : BRI[dec] on slot [dec] BRIC, changed state to [chars]
Explanation A state change has occurred on a port on the BRIMUX board.
Recommended Action No action is required.
Error Message%BRIMUX-5-UPDOWN : Slot [dec] BRIC, changed state to [chars]
Explanation A state change has occurred on the BRIMUX board.
Recommended Action No action is required.
BSC Messages
The following are Binary Synchronous Communications (BSC) protocol messages.
Error Message%BSC-3-BADLINESTATE : Line state Tx when receiving [chars] on line [chars]
Explanation An unexpected receive operation occurred during a transmission.
Recommended Action Verify that the line has been consistently defined in relation to the carrier. If a message report was sent, perform a hard stop and start the bisynchronous interface in question.
Error Message%BSC-3-BADPEERTYPE : Peer [chars] is incorrect type
Explanation This message occurs only when BSC local acknowledgment is configured. It indicates that the serial interfaces that are using the BSTUN tunnel are configured incorrectly; that is, both interfaces have been configured as secondary.
Recommended Action Reconfigure the serial interfaces correctly so that they form a primary and secondary pair.
Error Message%BSC-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation An attempt to allocate a memory buffer was not successful. This condition is rare and, under normal conditions, temporary.
Recommended Action If memory allocation failures persist, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSC-2-NOMEM : No buffers available on interface [chars].
Explanation Memory in the router has been exhausted.
Recommended Action Perform diagnostics on the router to locate the subsystem or interface responsible for consuming memory. The only method that will clear this situation is to reload the router.
BSQ Messages
The following are buffer status queue processing messages.
Error Message%BSQ-0-INCMPLT_XFER : Incomplete Data Transfer received for non-read operation
Explanation An Incomplete Data Transfer Notice was received for a CCW that did not perform a read or that has read data backward. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSQ-0-MTC_CHAIN : Incomplete More-To-Come chain queued
Explanation The CIP could not find the end of a more-to-come chain. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSQ-0-NULLREAD : Unexpected read of zero bytes, BSQ=[hex] [hex] [hex] [hex]
Explanation The CIP was notified that an I/O operation has been completed with a storage control block that had a length of 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSQ-0-SCB_CHAIN : Read SCB chain is out of sequence
Explanation The sequence of buffer status queue entries received for read commands does not match the sequence of the storage control blocks used for the reads. This is a fatal internal logic error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
BSR Messages
The following are BSR messages.
Error Message%BSR-5-CBSR_REMOVED : Candidate-BSR on interface [chars] has been removed
Explanation The interface card has been removed.
Recommended Action No action is required.
Error Message%BSR-5-CRP_REMOVED : Candidate-RP on interface [chars] has been removed
Explanation The interface card has been removed.
Recommended Action No action is required.
BSTUN Messages
The following are block serial tunneling (BSTUN) messages.
Error Message%BSTUN-3-BADCONN : CONN: bad connection ([dec]), peer: [chars]
Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-BADLENOP : [chars]: bad len or unknown op, op [dec], len [dec]
Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-BADMAGIC : [chars]: wrong magic, mine [hex], theirs [hex] ([dec])
Explanation An internal software error has occurred. .
Recommended Action Verify that the configuration is correct and that the peer is configured correctly and try again. If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-BADMAGICTCP : [chars]: peer [chars], wrong magic, mine [hex], theirs [hex]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-BADPASSIVEOPEN : passive open from [IP_address]([dec]) -> [dec] failed
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-CONNILLSTATE : CONN: Peer [chars], illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-6-CONNOPENFAIL : CONN: peer [chars] open failed, [chars] [[int]]
Explanation An attempt to connect to a remote outbound TCP BSTUN peer was not successful.
Recommended Action Verify that the remote peer is accessible from this router, that it is running software capable of supporting BSTUN, and that it is configured correctly.
Error Message%BSTUN-3-DROPTIMERERR : The peer drop timer has incorrectly expired for the peer with CU address [hex] \n on interface [chars]. The peer type defined for this peer is [hex]. The state of the \n peer tunnel is [chars].
Explanation The peer drop timer did not start correctly or has been left running.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-4-DUPROUTE : Cannot define duplicate route on the
same groupExplanation This route command is defined on another interface belonging to the same group. Duplicate routes cannot be defined for the same group.
Recommended Action Define a new group and verify that the route information for each BSTUN route is unique.
Error Message%BSTUN-6-ERR : [chars]: [chars]: [chars], op [hex], len [dec]
Recommended Action An internal software error has occurred. If sense code 0x82 is received, verify that the head and tail routers are configured properly. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-IFNOTSETUP : Could not setup interface for protocol [chars]
Explanation Even though BSTUN is configured on the interface, it could not start the interface to handle the specified protocol traffic.
Recommended Action If this message appears while you are configuring BSTUN, check for other system errors. Possible problems include a lack of available memory in the router and a shutdown. If no obvious problem can be detected, record all the displayed values and any other BSTUN messages, copy the messages exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-2-NOBUF : Interface [chars], no buffer available to [chars]
Explanation A memory shortage existed at the time that the configuration command was issued. This condition is rare and, under normal conditions, is temporary.
Recommended Action Reconfigure the BSTUN group. If memory shortages persist, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-3-NOGRPDEF : No bstun group defined on interface [chars]
Explanation An action was taken that requires the previous definition of a BSTUN group number.
Recommended Action Verify that the BSTUN definitions are complete, make any necessary corrections, and try again.
Error Message%BSTUN-3-NOPEER : No peer configured to route frame with destination address [chars] (bstun group [dec])
Explanation A BSTUN route has not been configured for the frame being received. The destination address of the frame is indicated in the error message. If this message appears while you are debugging BSTUN, it indicates that no specific BSTUN route has been configured for the frames being received; the device address for those frames is listed in the packet debug trace.
Recommended Action You may choose to configure a BSTUN route or ignore this message.
Error Message%BSTUN-6-OPENED : [chars]: peer [chars] opened, [previous state [chars]]
Explanation An attempt to connect to a remote peer has been either completed successfully or is in the process of being opened. This activity indicates that BSTUN is working as expected.
Recommended Action No action is required.
Error Message%BSTUN-6-OPENING : CONN: opening peer [chars], [dec]
Explanation An attempt to connect to a remote peer has been either completed successfully or is in the process of being opened. This activity indicates that BSTUN is working as expected.
Recommended Action No action is required.
Error Message%BSTUN-6-PASSIVEOPEN : passive open [IP_address]([dec]) -> [dec]
Explanation An attempt to connect to a remote peer has been either completed successfully or is in the process of being opened. This activity indicates that BSTUN is working as expected.
Recommended Action No action is required.
Error Message%BSTUN-6-PEERSHUTDOWN : shutting down peer [chars] on [chars]
Explanation A connection to a remote peer is being shut down. This is typically the result of user intervention during a BSTUN reconfiguring or disabling process. This activity indicates that BSTUN is working as expected.
Recommended Action No action is required.
Error Message%BSTUN-4-PEERSTATE : Peer [chars], wrong state [dec] ([dec])
Explanation An internal software error has occurred.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-6-PROCEXIT : Process terminating. Due to signal [dec]. Subcode [dec]. Address [hex].
Explanation The BSTUN background process is terminating.
Recommended Action If this message appears while you are disabling BSTUN, no action is required. Otherwise, record all the displayed values and any other BSTUN messages, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-4-RECONFAPIPROUT : Duplicate APIP route found - nailing the duplicate and reconfiguring
Explanation The system has detected a duplicate set of connection parameters for this command. The system has unconfigured the command and created a new set of connection parameters.
Recommended Action No action is required.
Error Message%BSTUN-4-RECONFBIPROUT : Duplicate BIP route found - nailing the duplicate and reconfiguring
Explanation The connection parameters for this command have already been used. To configure this route, the duplicate command has been unconfigured and a new one created.
Recommended Action No action is required.
Error Message%BSTUN-6-RECONNECT : PHDR: reconnect from peer [chars]
Explanation A remote peer has reestablished a connection to this router as indicated in the error message.
Recommended Action No action is required.
Error Message%BSTUN-3-SENDPUNT : [chars]: sent [chars] to [chars]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-4-SENDPUNTTCP : [chars]: sent [chars] to ([[int]])[IP_address]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%BSTUN-6-TCPFINI : peer [chars] closed [previous state [chars]]
Explanation A remote peer has closed a BSTUN connection with this router.
Recommended Action Examine the remote router to determine why it closed the connection with the specified peer. The closing of the connection can be caused by normal events, such as reconfiguration.
Error Message%BSTUN-6-TCPPEERSHUT : [chars] [chars], [IP_address]([dec])
Explanation This router has closed a BSTUN connection with a remote peer.
Recommended Action Examine this router to determine why it closed the connection with the remote peer. This action can be caused by normal events, such as reconfiguration.
Error Message%BSTUN-3-UNKPROTOEV : Unknown protocol event [dec] on interface [chars]
Explanation An event that was passed to the BSTUN layer for processing could not be decoded.
Recommended Action Perform a hard restart on the indicated interface.
C_GIGE Messages
The following are common device driver messages for the dual-port Gigabit Ethernet back card subsystem.
Error Message%C_GIGE-3-GEMAXADDR : [chars], expected [hex], actual [hex]
Explanation There are too many MAC addresses in the filter table.
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%C_GIGE-3-GEMISMATCH : [chars], expected [hex], actual [hex]
Explanation PCI initialization for the common Gigabit Ethernet subsystem 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%C_GIGE-3-INITFAIL : C_GIGE initialization failed, [chars]
Explanation Initialization for the common Gigabit Ethernet subsystem 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%C_GIGE-3-INTERNAL : C_GIGE internal error, [chars]
Explanation The system has detected an error in the internal common Gigabit Ethernet subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C_GIGE-3-MAJOR_FAULT : C_GIGE unrecoverable error, [chars], error_code=[hex]
Explanation The system has detected an operation error in the common Gigabit Ethernet subsystem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C_GIGE-3-MIBINITFAIL : C_GIGE MIB initialization failed, [chars]
Explanation MIB initialization for the common Gigabit Ethernet subsystem 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%C_GIGE-4-TOOBIG : C_GIGE - interface: [chars]: size [dec]: pak size
Explanation A packet larger than the maximum allowed packet size has been received.
Recommended Action The system will correct this condition. No action is required.
Error Message%C_GIGE-6-UNKNOWN : Unknown message ([dec]) received ([chars]) from interface [chars]
Explanation The driver has received an unknown message from the back 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.
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 signaled, 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.
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.
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.
C1400_PCI Messages
The following are protocol control information (PCI) bus for Cisco 1400 platform messages.
Error Message%C1400_PCI-3-BADADDR : Conversion of address ([hex]) to little_endian failed.
Explanation A software error occurred in trying to determine PCI device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1400_PCI-3-BADADDR2 : Conversion of address ([hex]) to big_endian failed.
Explanation A software error occurred in trying to determine PCI device addressing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1400_PCI-3-BADPCIRD : PCI Configuration Read Cycle Failed for bus [dec], Device [dec], function [dec], \n register [dec]
Explanation The system could not read from the PCI Bus. It might be necessary to replace the board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1400_PCI-3-BADPCIWR : PCI Configuration Write Failed for bus [dec], Device [dec], function [dec], \n register [dec]
Explanation The device initialization code was unable to write to the PCI Bus. It might be necessary to replace the board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1400_PCI-3-BIG_ENDIAN_ADDR : Conversion of address ([hex]) to big_endian is not supported
Explanation Conversion of an address to an equivalent big endian address is not supported by QSpan PCI device.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1400_PCI-3-LITTLE_ENDIAN_ADDR : Conversion of address ([hex]) to little_endian is not supported
Explanation Conversion of an address to an equivalent little endian address is not supported by QSpan PCI device.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C1400_PCI-3-PCI_NOT_EXIST : PCI Bus bridge does not exist
Explanation The device initialization code was unable to locate the PCI bus bridge. It might be necessary to replace the board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
C1600 Messages
The following are Cisco 1600 platform messages.
Error Message%C1600-4-BADINTFC : Interface [dec], (0-1 Onboard interfaces 2=WIC)
Invalid interface (Unknown, Uninitialized or Bad Cookie value read)Explanation The router is functional; however, there is an interface that the software does not recognize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1600-4-INTFCNOFLH : Unable to load images or communicate over interface
Explanation Access to the interface might have failed because of a transient network problem.
Recommended Action Retry the operation. If the problem persists, call your technical support representative for assistance.
C1700 Messages
The following are Cisco 1700 platform messages.
Error Message%C1700-3-BAD_EEPROM_VERSION : The eeprom version field has an invalid entry ([char])
Explanation The cookie has an invalid version number and could possibly be corrupt.
Recommended Action Unavailable
Error Message%C1700-3-BADIMAGE : The IOS image loaded supports voice. The platform you are running is not voice capable.
Explanation The voice-capable Cisco IOS software detects that it is running on a platform that does not support voice features.
Recommended Action Check the image and the platform. If you need to use voice features, you should get a Cisco 1750 router. If you do not need voice, you should load an image that does not include voice features.
Error Message%C1700-3-BADPA : Invalid Port Adaptor type ([dec]) reported for mainboard
Explanation The virtual port adapter type derived from the main board type is not one of the supported types. It may be that this main board is a new main board type and the software release you are running does not support the new main board type.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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 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.
Error Message%C1700-3-NOCONFIG : Could not download startup configuration from the tftp server.
Explanation A startup configuration could not be downloaded from the TFTP server. The specified file might not be available, or the server might be unreachable.
Recommended Action Check the filename and availability on the server. Verify that the network is up and that the TFTP server can be reached.
Error Message%C1700-1-OVERTEMP : System detected OVERTEMPERATURE condition. Putting the system in Power save mode and going to rommon. Please resolve cooling problem and restart system!
Explanation The environmental monitor has detected a high-temperature condition.
Recommended Action Verify that the room temperature is low enough and that air flow to the card is not blocked. If this condition persists, the environmental monitor might shut down the system. Contact your Cisco technical support representative for assistance if necessary.
Error Message%C1700-1-SHTDN : The shutdown button is pressed, MRP will be into shutdown mode
Explanation The machine has entered the checkstop state, which has stopped all tasks. The hardware will have to be reset for the system to be restarted.
Note
This message appears on the ICS 7750 system only.
Recommended Action Perform a power cycle and reset the system.
Error Message%C1700-3-TDMMODIFUNKNOWN : TDM Module does not support WAN Interface module [hex] in slot [dec]
Explanation The WAN interface card was not recognized by the TDM module. Internal connections required for this WAN interface card to function were not made.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700-5-WRITEMEM : NVRAM configuration is not supported.
Explanation A startup configuration could not be stored in NVRAM. It is stored in the single-board computer.
Recommended Action The configuration is automatically saved by the management application. You can also save the configuration by copying the running configuration file to a server using the FTP function.
C1700_EM Messages
The following are Cisco 1700 VPN module hardware accelerator for IP security messages.
Error Message%C1700_EM-1-ALIGN : Alignment failure on packet buffer: [hex]
Explanation A software error has occurred. The VPN module driver detected that the buffer is not aligned correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-BADBOOTSTATUS : VPN Module returned bad boot status: ([dec])
Explanation A VPN module boot sequence error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-BADSEMAPHORE : VPN Module cannot lock semaphore sem=[dec]
Explanation The VPN module is not responding correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-DOWNLOADFAIL : VPN Module firmware download failed: [chars]
Explanation An attempt to download firmware to the VPN module has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-DSP_NOT_RESPONDING : VPN Module DSP is not responding.
Explanation The digital signal processor (DSP) portion of the ATM address for the VPN module might be incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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.
Error Message%C1700_EM-1-EM_MULTDEV : Multiple VPN Modules not supported, ([dec]) found
Explanation Multiple VPN modules are not supported in the current configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-EM_PROC_ALIGN : VPN Module Command Processor alignment error: ([chars]=[hex])
Explanation An alignment error has occurred in the VPN module command processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-EM_PROC_ERR : VPN Module Command Processor error: ([chars])
Explanation A VPN module command processor error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-EM_PROC_INIT : VPN Module Command Processor initialization failed: ([chars])
Explanation An attempt to initialize the VPN module command processor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-ERROR : [chars]
Explanation An error has occurred in an application using the VPN module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-INITFAIL : Slot [dec]: [chars]
Explanation The VPN module driver could not be initialized at the specified point.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-MBX_BADSTATE : VPN Module CGX mailbox bad state: found=[hex], expect=[hex]
Explanation A state change has occurred, causing the VPN module CGX Library mailbox to become unstable.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-MEMTESTFAIL : VPN Module failed its onboard memory test. Page [hex], Addr [hex], Wrote [hex], Read [hex]
Explanation A memory test error has occurred in the VPN module.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-NOMEMORY : [chars] creation failed for slot [dec]
Explanation The VPN module driver could not allocate memory for the specified data structure.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem is not resolved by applying these actions, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-NVRAMFAIL : VPN Module could not read its own NVRAM configuration: ([dec])
Explanation An NVRAM error has occurred, preventing the VPN module from being able to read its own NVRAM configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-1-OWNER : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The VPN module driver has detected that the buffer ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-3-PROC_BADEVENT : VPN Module Command Processor got event: major=[dec], minor=[dec]
Explanation An error has occurred in the VPN module command processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C1700_EM-6-SHUTDOWN : [chars] shutting down
Explanation The specified VPN module is shutting down. It may have been physically removed.
Recommended Action This is an informational message only. It occurs in normal operation.
Error Message%C1700_EM-1-TOOBIG : [chars] received a packet with size [dec].
Explanation A packet received from the specified peer exceeds the specified MTU size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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.
C2600 Messages
The following are Cisco 2600 platform messages.
Error Message%C2600-3-BADADDR : c2600_little_endian_addr: Attempted conversion of invalid address ([hex])
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADADDR2 : c2600_big_endian_addr: Attempted conversion of invalid address ([hex])
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADBAYDEV : get_pci_dev_num: Invalid bay ([dec]) or device number offset ([dec])
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADDEVNO : pas_get_device_subunit: Invalid PCI device number: [dec]
Explanation A software error occurred during an attempt to determine PCI device addressing. This condition is most likely caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The detected size of the NVRAM is not one of the supported sizes. The NVRAM might have failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADPA : Invalid Port Adaptor type ([dec]) reported for mainboard
Explanation The virtual port adapter type derived from the main board type is not one of the supported types. This main board might be a new type of main board that is not supported by the software release you are running.
Recommended Action Verify that the installed main board is compatible with the release of Cisco IOS software you are running. If you cannot resolve the discrepancy, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADPCIRD : PCI Configuration Read Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]
Explanation An attempt to read the PCI bus configuration has failed. The main board needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-BADPCIWR : PCI Configuration Write Cycle Failed for bus [dec], Device [dec], function [dec], register [dec]
Explanation An attempt to write the PCI bus configuration has failed. The main board needs to be replaced.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation An attempt to allocate the MAC address for the specified interface has failed; all the available MAC addresses for the system have been allocated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-3-NVERASEFAIL : Failed to erase config due to internal error
Explanation The password protection feature has failed to erase the configuration because of an internal error.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2600-1-OVERTEMP : System detected OVERTEMPERATURE condition.\n Putting the system in Power save mode and going to rommon.\n Please resolve cooling problem and restart system!\n
Explanation The environmental monitor has detected a high-temperature condition.
Recommended Action Verify that the room temperature is not too high and that air flow to the card is not blocked. If this condition persists, the environmental monitor may shut down the system. If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
C2600_MAINBOARD_ASYNC_PQUICC Messages
The following are MPC860 quad integrated communications controller messages for the Cisco 2600 platform.
Error Message%C2600_MAINBOARD_ASYNC_PQUICC-3-NOMEMORY : No memory for [chars] of unit [dec]
Explanation Memory cannot be allocated to perform the function indicated in the message.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. If the problem persists, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
C29ATM Messages
The following are messages for the Catalyst 2900XL address table management module.
Error Message%C29ATM-4-AT_DEBUG : [chars]: [chars] : [dec]
Explanation A problem with the address table management subsystem has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-4-AT_DEBUG_MAC : [chars]: [chars] : [enet]
Explanation A problem with the address table management subsystem has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-4-AT_DEBUG_TB : [chars]: [chars] : [dec]
Explanation A problem with the address table management subsystem has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-4-AT_VLAN_DEBUG : [chars]: [chars] : [dec]
Explanation A problem with the address table management subsystem has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-4-BIG_CONTROL_FRAME : AAL5 discarded because it is too large to buffer: vpi = [dec], vci = [dec], size = [dec]
Explanation An AAL5 frame destined for Cisco IOS was discarded because it was too large to buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-4-IF_IDB : [chars]: [chars]
Explanation The ATM IDB for this interface could not be detected.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-3-NO_CREATE_VCC : Cannot create VCC [chars].
Explanation The module was unable to create a VCC for the specified service.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-4-NOVCINFO : [chars] discarded because it is not associated with a
VCD: vpi = [dec] vci = [dec]Explanation An OAM cell or an AAL5 frame was discarded because it was not associated with a VCD.
Recommended Action Check the configuration of your ATM switch and make any necessary corrections.
Error Message%C29ATM-3-OUT_BAD_VCD : The module attempted to transmit frame on a closed or non-existent VCD: vcd = [dec]
Explanation The module attempted to transmit a frame on a closed or nonexistent VCD.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C29ATM-3-OUT_OF_VCD : Cannot create VCC for [chars], run out of VCD
Explanation The module was unable to create a VCC for the specified service.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
C2KATM Messages
The following are Catalyst 2820 ATM module messages.
Error Message%C2KATM-4-BIG_CONTROL_FRAME : AAL5 discarded because it is too large to buffer: vpi = [dec], vci = [dec], size = [dec]
Explanation An AAL5 frame destined for Cisco IOS was discarded because it was too large to buffer.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2KATM-3-NO_CREATE_VCC : Cannot create VCC [chars].
Explanation The module was not able to create a VCC for the specified service.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2KATM-4-NOVCINFO : [chars] discarded because it is not associated with a
VCD: vpi = [dec] vci = [dec]Explanation An Operation, Administration, and Maintenance (OAM) cell or an AAL5 frame was discarded because it was not associated with a VCD.
Recommended Action Check the configuration of your ATM switch.
Error Message%C2KATM-3-OUT_BAD_VCD : The module attempted to transmit frame on a closed or non-existent VCD: vcd = [dec]
Explanation The module attempted to transmit a frame on a closed or nonexistent VCD.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C2KATM-3-OUT_OF_VCD : Cannot create VCC for [chars], no free VCDs
Explanation The module was unable to create a VCC for the specified service.
Recommended Action If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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.
C3600 Messages
The following are Cisco 3600 platform messages.
Error Message%C3600-3-BADNV : Detected invalid NVRAM size: [dec] bytes
Explanation The detected size of NVRAM is not one of the supported sizes. The NVRAM may be bad.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C3600-3-BADPLAT : Unknown platform type
Explanation The Cisco IOS software image does not recognize the motherboard revision of this router. This situation could indicate either that a hardware failure has occurred or that the software needs to be upgraded to allow it to recognize newer hardware.
Recommended Action Verify that you are using a recommended revision of the Cisco IOS software for your hardware. Upgrade to a newer software release if necessary. If the error message recurs, copy the message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C3600-3-CHASSIS : Unknown chassis model.
Explanation Data stored in the midplane is bad or incomplete.
Recommended Action Contact your Cisco technical support representative for assistance in updating your system.
Error Message%C3600-4-COOKIE : Corrupt or missing MAC address cookie
using random base [enet]Explanation Data stored in the midplane is bad.
Recommended Action Contact your Cisco technical support representative for assistance in updating your system.
Error Message%C3600-4-MACBLKSIZE : Unknown MAC address block size.
Explanation Data stored in the backplane is bad or incomplete.
Recommended Action Contact your Cisco technical support representative for assistance in updating your system.
Error Message%C3600-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation A MAC address could not be allocated because of an incorrect slot and port combination that exceeds the maximum available hardware.
Recommended Action Verify that the appropriate hardware is installed in the chassis and that the software configuration correctly reflects the slot and port placement.
Error Message%C3600-3-NVERASEFAIL : Failed to erase config due to internal error
Explanation The password protection feature has failed to erase the configuration because an internal error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C3600-3-SLOTS : Number of slots in chassis is undefined.
Explanation Data stored in the midplane is bad or incomplete.
Recommended Action Contact your technical support representative for assistance in updating your system.
Error Message%C3600-4-VERSION_MISMATCH : Midplane data version mismatch.
Explanation Data stored in the midplane is out of date and needs to be updated.
Recommended Action Contact your technical support representative for assistance in updating your system.
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.
C4GWY_DSPRM Messages
The following are digital signal processor (DSP) Resource Manager messages.
Error Message%C4GWY_DSPRM-5-DSPFAIL : DSP [dec] is in the failed state
Explanation The digital signal processor for the specified address has failed because of excessive alarm indications.
Recommended Action Replace the digital signal processor resource.
Error Message%C4GWY_DSPRM-5-DSPNOTPRESENT : DSP [dec] is not present
Explanation All four digital signal processor SIMMs are not available.
Recommended Action Install all four hardware digital signal processor SIMMs and try again.
Error Message%C4GWY_DSPRM-3-INSUFFICIENT : Insufficient DSP resources for timeslot [dec] on port [chars]
Explanation The configuration requires more digital signal processor resources than are available.
Recommended Action Change the configuration to specify fewer used time slots. Install additional digital signal processor resources to allow for more complex configurations.
Error Message%C4GWY_DSPRM-5-KEEPALIVE : DSP [dec] in slot [chars], NOT RESPONDING - auto restart([dec] times)
Explanation The digital signal processor failed the background keepalive test.
Recommended Action This message is informational. No action is required.
Error Message%C4GWY_DSPRM-5-SETCODEC : Configured codec [dec] is not supported with this dsp image.
Explanation The coder-decoder device is unable to negotiate handoffs because it is not supported with the installed digital signal processor image.
Recommended Action Verify that the device and the Cisco IOS software image that is running in this router are compatible.
Error Message%C4GWY_DSPRM-5-UPDOWN : DSP [dec], changed state to [chars]
Explanation A state change has occurred in the digital signal processor resource.
Recommended Action This is an informational message. No action is required.
C542 Messages
The following are Voice over IP driver messages.
Error Message%C542-1-EMPTY : [chars], packet(size [dec]) is empty.
Explanation A packet greater than 256 bytes has been received on this interface.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-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 the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C542-3-ERROR_INIT_BLDR : [chars] Unable to download the Boot loader firmware, ret = [hex]
Explanation An error occurred during an attempt to initialize the digital signal processor with the bootloader firmware.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C542-3-ERROR_INIT_OVERLAY : [chars] Unable to download the Application overlay firmware. Status returned [hex]
Explanation An error occurred during an attempt to initialize the digital signal processor with the application or overlay firmware.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C542-1-ERROR_INTR : [chars] , Error interrupt occured type = [hex].
Explanation The DMA engine cannot gain access to the PCI bus to read descriptors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-3-IDB_CREATE : Error creating an idb for VoIP fastswitching in slot [dec].
Explanation The C542 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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-1-INCORRECT_DSP_ID : VPM at slot [dec]: Incorrect [dec] DSP-ID passed by SPI.
Explanation The DSP ID provided by the SPI for download is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-3-INCORRECT_ID : VPM in slot [dec]: PCI device not supported.
Explanation An interface controller device did not report the correct PCI device ID.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C542-3-INCORRECT_PMID : VPM at slot [dec]: Incorrect [dec] PM-ID device not supported.
Explanation An interface controller device did not have the correct port module ID in its EEPROM cookie.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-1-INSUFFICIENT_DSPS : VNM([dec]), cannot support all voice channels on VICs.
Explanation More voice channels are configured on the VICs than can be supported by this network module. Some channels will be inoperative.
Recommended Action This behavior is normal when a BRI VIC coexists on a VNM with an analog VIC or when a BRI VIC is on a VNM-1. If those conditions do not apply, check the part number on the VIC to determine whether it is supported in the version of Cisco IOS that is operational on the router. If you cannot resolve the discrepancy, contact your technical support representative for assistance.
Error Message%C542-3-NO_BUFFERS : No buffers available for DSP buffer pool
Explanation The C542 driver does not have enough memory to assemble a multiparticle packet.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-1-NO_DAUGHTER_CARD : VNM([dec]), vic card has an no known daughter cards
Explanation The Cisco IOS software does not recognize any of the VICs that are plugged into the port module.
Recommended Action Check the part number on the VIC and verify that it is supported in the version of Cisco IOS that is operational on the router. If you cannot resolve the discrepancy, contact your Cisco technical support representative for assistance.
Error Message%C542-1-NO_RING_DESCRIPTORS : No more ring descriptors on [chars]. Msg id=[hex], Len=[dec]
Explanation The C542 driver cannot queue messages up to the XILINX DMA engine for transmission.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Reset the DSPs on this port module.
Error Message%C542-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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-4-SWVER_NOSUPPORT : VPM at slot [dec]: not supported on this version of IOS software.
Explanation This version of Cisco IOS software does not support the VPM card.
Recommended Action Load a version of Cisco IOS software that supports the card in the slot specified in the error message.
Error Message%C542-1-TOOBIG : [chars], packet(size [dec]) too big.
Explanation A packet greater than 256 bytes was received on this interface.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C542-1-UNKNOWN_VIC : VNM([dec]), vic daughter card has an unknown id of [hex]
Explanation The software does not recognize the type of VIC daughter card that is plugged into the port module.
Recommended Action Check the part number on the VIC to see if it is supported in the version of Cisco IOS software that is operational on the router. If you cannot resolve the discrepancy, contact your technical support representative for assistance.
C5421 Messages
The following are Voice over IP driver messages.
Error Message%C5421-3-ERROR_ANALYZE : Error analyzing the device in slot [dec].
Explanation The port module in the specified slot could not be recognized.
Recommended Action Power down, reinsert the port module, and reboot. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C5421-3-ERROR_FIRMWARE_DNLD : DSP firmware download fails for slot [dec] dsp_id [dec]
Explanation An error has occurred during initialization of the DSP in the specified slot with the application firmware.
Recommended Action Power down, reinsert the port module, and reboot. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information that you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C5421-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 downloading is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C5421-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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C5421-1-NO_RING_DESCRIPTORS : No more ring descriptors available on slot [dec] dsp [dec].
Explanation The C5421 driver cannot queue messages up to the egress queue for the FPGA to transmit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Reset the DSPs on the port module in the specified slot.
Error Message%C5421-4-SWVER_NOSUPPORT : HDA at slot [dec]: not supported on this version of IOS software.
Explanation This version of Cisco IOS software does not support the HDA card.
Recommended Action Load a version of Cisco IOS software that supports the card in the slot specified in the error message.
Error Message%C5421-1-TOOBIG : [chars], packet(size [dec]) too big.
Explanation A packet greater than 264 bytes has been received on this interface.
Recommended Action The system should recover. No action is required. If the problem recurs, it indicates an error that might be related to data traffic patterns. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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.
C54X Messages
The following are Voice over IP (VoIP) driver messages.
Error Message%C54X-3-ERROR_ANALYZE : Error analyzing the device in slot [dec].
Explanation The system does not recognize the port module in the specified slot.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C54X-3-ERROR_INIT_BLDR : [chars] Unable to download the Boot loader firmware, ret = [hex]
Explanation An error occurred during an attempt to initialize the digital signal processor with the bootloader firmware.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C54X-3-ERROR_INIT_OVERLAY : [chars] Unable to download the Application overlay firmware. Status returned [hex]
Explanation An error occurred during an attempt to initialize the digital signal processor with the application or overlay firmware.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-ERROR_INTR : [chars] , Error interrupt occured type = [hex].
Explanation The DMA engine cannot gain access to the PCI bus to read descriptors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-INCORRECT_DSP_ID : VPM at slot [dec]: Incorrect [dec] DSP-ID passed by SPI.
Explanation The digital signal processor ID provided by the SPI for download is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-3-INCORRECT_ID : VPM in slot [dec]: PCI device not supported.
Explanation An interface controller device did not report the correct PCI device ID.
Recommended Action Power down the device, reinsert the port module, and reboot. If this message recurs, contact your technical support representative for assistance.
Error Message%C54X-3-INCORRECT_PMID : VPM at slot [dec]: Incorrect [dec] PM-ID device not supported.
Explanation An interface controller device does not have the correct port module ID in its EEPROM cookie.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-INVALID_CONFIGURATION : vpm([dec]), vic cards has an invalid configuration.
Explanation The software has detected more VIC interface ports than can be supported on this port module.
Recommended Action Check the part number on the VIC and verify that it is supported in the version of Cisco IOS software that is operational on the router. If you cannot resolve the discrepancy, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-NO_DAUGHTER_CARD : vpm([dec]), vic card has an no known daughter cards
Explanation The software does not recognize any of the VICs that are plugged into the port module.
Recommended Action Check the part number on the VIC and verify that it is supported in the version of Cisco IOS software that is operational on the router. If you cannot resolve the discrepancy, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-NOMEMORY : VPM ([dec]/[dec]), memory unavailable.
Explanation The router or access server could not allocate memory for the descriptors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-NO_RING_DESCRIPTORS : No more ring descriptors available on [dec] slot.
Explanation The VoIP digital signal processor driver cannot queue messages for the Xilinx DMA engine to transmit.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. Reset the digital signal processors on this port module.
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 The system should recover. No action is required. If the problem recurs, it indicates an error that might be related to data traffic patterns. If you are unable to resolve the error, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C54X-1-UNKNOWN_VIC : vpm([dec]), vic daughter card has an unknown id of [hex]
Explanation The software does not recognize the type of VIC daughter card that is plugged into the port module.
Recommended Action Check the part number on the VIC to verify that it is supported in the version of Cisco IOS software that is operational on the router. If you cannot resolve the discrepancy, contact your technical support representative for assistance.
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.
C5RSP Messages
The following are Cisco Catalyst 5000 platform messages.
Error Message%C5RSP-6-BRIDGE_AFU : vlan [dec] could/could not be configured for bridging
Explanation A VLAN could not be reset with the proper bridging information.
Recommended Action Try to resolve this problem by configuring the VLAN with bridging. If that does not work, try configuring the VLAN without bridging.
Error Message%C5RSP-3-C5_BADIPC : bad message received from the NMP
Explanation An unsolicited in-band IPC message was received by the router from the NMP.
Recommended Action No action is required.
Error Message%C5RSP-3-C5IP_SLOTFAIL : can't get Catalyst 5000 Slot number of router
Explanation An attempt by the RSP to query the C5IP for the slot it is plugged into has failed.
Recommended Action Reset the router from the NMP console. If the problem persists, contact your Cisco technical support representative for replacement of the C5IP line card.
Error Message%C5RSP-3-C5_MACADRFAIL : can't get C5 Line Card Mac Addr
Explanation An attempt by the RSP to query the C5IP for VLAN 0 IP address has failed.
Recommended Action Reset the router from the NMP console. If problems persist, complete a return materials authorization for the router or the Catalyst 5000 switch. Follow the instructions for returning the equipment.
Error Message%C5RSP-3-C5_NMPMACADRFAIL : can't get NMP Mac Addr
Explanation An attempt by the RSP to query the C5IP for VLAN 0 MAC address has failed.
Recommended Action Reset the router from the NMP console. If problems persist, contact your Cisco technical support representative to arrange for replacement.
Error Message%C5RSP-3-C5_SAGE0FAIL : Length error occurred on dma channel 0
Explanation A hardware error has occurred on DMA channel 0.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C5RSP-3-C5_SAGE1FAIL : Length error occurred on dma channel 1
Explanation A hardware error has occurred on DMA channel 1.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C5RSP-3-CANT_CREATE_VLAN : vlan [dec] can not be created. media not supported
Explanation An attempt to create a VLAN of media that are not supported has failed.
Recommended Action Configure the VLAN with a different media type.
Error Message%C5RSP-3-INVALID_LOVE_LETTER : Invalid loveletter type, [dec], sent by c5ip\n
Explanation Cisco IOS software is receiving erroneous messages from the C5IP controller.
Recommended Action If the error message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C5RSP-3-MAXVLAN_EXCEEDED : can't configure more than 256 VLANS
Explanation An attempt to create more than the maximum allowable number of VLANs has failed. A maximum of 256 VLANs is supported.
Recommended Action Delete unused VLANS before attempting to configure new ones.
Error Message%C5RSP-3-NMP_DELETE_VLAN : having problems deleting vlan [dec] on the NMP
Explanation An attempt to delete a VLAN has failed.
Recommended Action Check the state of VLAN 0. Check the state of the C5IP by looking at the front-panel LED. Check the state of the NMP. Reset the router.
Error Message%C5RSP-3-NMP_INIT_FAIL : can't talk to NMP during initialization
Explanation An attempt to initialize a VLAN has failed.
Recommended Action Check the state of VLAN 0. Check the state of the C5IP by looking at the front-panel LED. Check the state of the NMP. Reset the router.
Error Message%C5RSP-3-NMP_PROG_FAIL : NMP won't allow vlan [dec] configuration
Explanation An attempt to create a VLAN has failed.
Recommended Action Check the state of VLAN 0. Check the state of the C5IP by looking at the front-panel LED. Check the state of the NMP. Reset the router.
Error Message%C5RSP-6-NOSWIDB : vlan [dec] missing IDB
Explanation An internal data structure of the VLAN is missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%C5RSP-3-RSM_NMP_BRIDGE_INVALID : NMP returned invalid bridge id [dec] for [dec]\n
Explanation The NMP has returned an invalid bridge ID to the RSM.
Recommended Action Verify that the VLAN between the token ring and the bridge relay function on the RSM is configured correctly on the NMP.
Error Message%C5RSP-3-RSM_NMP_CONFIG_MISMATCH : RSM NMP mismatch in config for [dec], RSM [dec], NMP [dec]\n
Explanation A discrepancy between the NMP and the RSM has been detected in the configuration for the specified VLAN.
Recommended Action Verify that the parameters for this VLAN are defined the same on the NMP and on the RSM.
Error Message%C5RSP-3-UNKNOWN_NMP_PROG : unknown timer for NMP programming
Explanation An unknown timer event has expired.
Recommended Action This message is informational. No action is required.
Error Message%C5RSP-6-VLAN_INFO_MISSING : vlan [dec] info errant. something very wrong
Explanation Internal information about the VLAN is missing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
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.
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 one 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 indicated component will be powered off. For shared components, the system must be powered off.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information 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%C6KENV-4-MAJORTEMPALARMRECOVER : [chars] has returned to allowed operating temperature range.
Explanation The indicated 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 The normal operating temperature range has been exceeded. This message may indicate a trend for the component, and also 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 determine whether it will eventually exceed the allowed operating temperature range. Verify that air flow to the device is not blocked and that the fan is operational.
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 the indicated power supply has failed. This condition could lead to the overheating and shutdown of the power supply.
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 the indicated power supply is operating as expected and within the normal temperature range.
Recommended Action This message is informational. 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 Automatic shutdown is disabled on this device; 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 or the chassis as soon as possible.
Error Message%C6KENV-0-VTTMAJFAILED : Too many VTT failures to continue system operation
Explanation The Cisco 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 Previously failed VTTs have begun operating again.
Recommended Action This message is informational. No action is required.
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. Using the information provided in the message, troubleshoot and resolve the power problem. If necessary, replace defective components.
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 This message is informational. 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.
