-
Cisco IOS Release 12.0S System Message Guide
-
System Messages Overview
-
AAAA through AUDIT messages
-
AUTORP through C10KSDCC messages
-
C10K_TOASTER through CBUS messages
-
CE3 through CPUIF messages
-
CRYPTO through ECC messages
-
EDGE through EE192 messages
-
EELC through ENV_MON messages
-
ESMP through FM messages
-
FR through GLCSPA messages
-
GRP through GRPSPA messages
-
GRP_CHOCX through GT96K_FE messages
-
HA through I82543 messages
-
ICC through IPV6FIB messages
-
IP_VRF through LC_CHOCX messages
-
LCCOREDUMP through LCINFO messages
-
LCLOG through MBUSFLASH messages
-
MCC192 through MPLS_TE_LM messages
-
MPLS_TE_PCALC through PM3386 messages
-
PM622 through PRP2 messages
-
PS through RSP messages
-
RSVP through SW_MGR messages
-
SYS through TCAM_MGR messages
-
TCATM through XCPA messages
-
Glossary of Acronyms
-
Table Of Contents
CRYPTO Messages
The following are encryption feature messages.
Error Message%CRYPTO-6-CERTFAIL : Certificate enrollment failed.
Explanation A fatal error occurred during an attempt to enroll a certificate.
Recommended Action Contact the CA administrator.
Error Message%CRYPTO-6-CERT_FATAL_ERR : [chars]
Explanation A fatal error has occurred during an attempt to enroll a certificate. The enrollment process is terminated.
Recommended Action Contact the CA administrator.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_ADDR_MATCH : ID of [IP_address] (type [dec]) and certificate addr with [IP_address]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the IP address of the peer's certificate.
Recommended Action Contact the administrator of the remote peer if this situation persists.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_DN_MATCH : ID of [chars] (type [dec]) and certificate DN with [chars]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the distinguished name of the peer's certificate.
Recommended Action Contact the administrator of the remote peer if this situation persists.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_FQDN_MATCH : ID of [chars] (type [dec]) and certificate fqdn with [chars]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the FQDN of the peer's certificate.
Recommended Action Contact the administrator of the remote peer if this situation persists.
Error Message%CRYPTO-6-IKMP_NO_ID_CERT_USER_FQDN_MATCH : ID of [chars] (type [Dec.]) and certificate user FADM with [chars]
Explanation ISAKMP entities assume an identity to inform the peer of who or what they are. The claimed identity did not match the information gleaned from the user FQDN of the peer's certificate.
Recommended Action Contact the administrator of the remote peer if this situation persists.
Error Message%CRYPTO-3-POLLCACERT : Polling CA certificate.....
Explanation The system is attempting to poll a CA certificate.
Recommended Action Ensure that the CA or LDAP server is online.
Error Message%CRYPTO-3-POLLRACERT : Polling RA certificate.....
Explanation The system is attempting to poll an RA certificate.
Recommended Action Ensure that the CA or LDAP server is online.
Error Message%CRYPTO-3-POLLROUTERCERT : Polling Router certificate.....
Explanation The system is attempting to poll a router certificate.
Recommended Action Ensure that the CA or LDAP server is online.
Error Message%CRYPTO-3-QUERYRACERT : Failed to query RA certificate.
Explanation An attempt to get RA certificates has failed.
Recommended Action Ensure that the CA or LDAP server is online.
Error Message%CRYPTO-3-QUERYROUTERCERT : Failed to query router certificate.
Explanation An attempt to query a router certificate has failed.
Recommended Action Ensure that the CA or LDAP server is online.
CT3 Messages
The following are Channelized T3 port adapter messages.
Error Message%CT3-3-BADMSG : Received unexpected mailbox message (id = [dec])
Explanation An unexpected message was received from the CT3 firmware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-2-CT3FWCRASHED : CT3 F/W crashed in bay [dec]: [hex] - reset
Explanation The CT3 firmware was not able to update the software watchdog.
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%CT3-2-CT3FWCRASHEDINFO : [hex] [hex] [hex] [hex]
Explanation This message displays information about a CT3 firmware crash.
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%CT3-1-DISCOVER : Found [dec] interfaces in bay [dec], shutting down bay
Explanation The CT3 hardware has failed. Some components on the board failed to initialize.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-1-DWNLDFAIL : Microcode to slot [dec]
Explanation A firmware download to the CT3 port adapter has failed.
Recommended Action If possible, perform an OIR. Refer to Cisco documentation for OIR information for your platform. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-3-LOVEFAIL : [chars]: failed to send [chars] love letter
Explanation A "love letter" (operating status or configuration message) was not sent to the RSP.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-3-MBOXRECV : Failed to receive reply [dec] from bay [dec] firmware
Explanation A message was not received from the CT3 firmware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-3-MBOXSENDP : Failed to send msg [dec] to [chars] driver firmware
Explanation A port-related message was not sent to the CT3 firmware.
Recommended Action If possible, perform an OIR. Refer to Cisco documentation for OIR information for your platform. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-2-NOVC : [chars]: packet received for unknown VC [dec]
Explanation The virtual channel encapsulation is corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The CT3 driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-1-RESTARTFAIL : [chars] could not be reset by [chars]
Explanation The restart failed to reset the interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CT3-1-STARTFAIL : [chars] could not be enabled by [chars]
Explanation The restart failed to enable the interface.
Recommended Action If possible, perform an online insertion and removal (OIR). Refer to Cisco documentation for OIR information for your platform. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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%CT3-1-STOPFAIL : [chars] could not be disabled by [chars]
Explanation The shutdown failed to disable the interface.
Recommended Action If possible, do an online insertion and removal (OIR). Refer to Cisco documentation for OIR information for your platform. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CTMGR Messages
The following are TCAM Manager handler messages.
Error Message%CTMGR-3-UNSUPP : [chars]:[dec]
Explanation The TCAM Manager handler received unsupported messages from the Feature Manager or QoS Manager from the RP.
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.
DBUS Messages
The following are data bus messages.
Error Message%DBUS-3-DBUSDISABLED : Slot [dec] disabled, will be restarted.
Explanation A processor was disabled due to an error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. 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%DBUS-3-DBUSINTERRSWSET : Slot [dec], Internal Error due to VIP crash
Explanation A processor reported an error. The processor will be reset and not used until the next OIR event or microcode download, when it will be retested.
Recommended Action Reinstall the processor or download the microcode. 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%DBUS-3-MSGOVERFLOW : Slot [dec], too many DBUS messages
Explanation A board in the slot identified in the error message tried to send too many logger messages.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DBUS-3-PERMANENT_WEDGED : Line card in slot [dec] is permanently wedged
Explanation Two successive attempts to restart and analyze the line card have failed.
Recommended Action Reinstall the line card. This condition could be caused by bad VIP hardware. If this message recurs, 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 might help identify the nature of the message. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.DEC21140 Messages
The following are DEC21140 Fast Ethernet controller messages.
Error Message%DEC21140-5-REMOVE_HWADDR_FAIL : Interface [chars] failed to remove Addr:=[enet] from HWAF\n
Explanation Removal of hardware address from the HWAF has failed. The failure occurred due to a a search in the HWAF table failed for the requested address. This failure should not occur when the interface is not operating in promiscuous mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DIAG Messages
The following are diagnostic messages.
Error Message%DIAG-3-ALWAYS_ENABLE_TEST : [chars]: The users are not allow to disable monitoring for Test #[dec]
Explanation An attempt to disable the health monitoring test has failed. The specified health monitoring test cannot be disabled by design. This condition indicates that the system is working properly.
Recommended Action No action is required.
Error Message%DIAG-6-BYPASS : [chars]: Diagnostics is bypassed
Explanation Diagnostics testing was not performed on the card because diagnostic testing was disabled in the system configuration. This behavior is consistent with the system configuration.
Recommended Action This is an informational message only. No action is required. If bootup diagnostics should be performed, enable bootup diagnostics by entering the diagnostic bootup command.
Error Message%DIAG-3-CARD_ABSENT : [chars] is not detected
Explanation A line card could not be located in a slot where a diagnostic action was requested.
Recommended Action Ensure that the targeted line card is properly seated in the specified slot. If the line card is properly seated, ensure that the correct slot was indicated in the command-line interface. If the line card is well seated and the correct slot was specified, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support and show controllers vip slot-number tech-support commands, with slot-number being the slot number of the port adapter from where the message came, and your pertinent troubleshooting logs.
Error Message%DIAG-3-CREATE_PROCESS_FAIL : Create process [chars] failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG-6-DIAG_OK : [chars]: Passed [chars]
Explanation The line card passed the diagnostic tests. No errors were detected on the line card.
Recommended Action No action is required.
Error Message%DIAG-3-DIAG_RUNNING : [chars]: Diagnostic is currently running
Explanation A diagnostic test is currently being run on the specified card, and additional tests cannot be run until the previously requested tests have been completed.
Recommended Action The system is working properly. No action is required. To run the specified diagnostic test, either wait for the current diagnostic test to finish and then run the test, or stop the current test and run the new test.
Error Message%DIAG-6-DIAG_STOPPED : [chars]: Diagnostic is stopped.
Explanation The diagnostic test has stopped.
Recommended Action No action is required. To run to the test to its completion, restart the test.
Error Message%DIAG-3-ENQUEUE_FAIL : [chars]: process_enqueue() failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG-3-FIXED_INTERVAL_TEST : [chars]: The users are not allow to change monitoring interval of Test #[dec]
Explanation The specified health monitoring test interval cannot be configured by the user and therefore cannot be changed.
Recommended Action No action is required.
Error Message%DIAG-3-GET_ARGU_FAIL : Get argument failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG-3-INVALID_DEVICE : Invalid device number : [chars]
Explanation A diagnostic request is being made on a device that does not exist.
Recommended Action Ensure that the specified device number (numeral-based) exists and is valid.
Error Message%DIAG-3-INVALID_MONITORING_INTERVAL : [chars]: The [chars][ID=[dec]] monitoring interval must be at least [dec] millisec
Explanation The specified test monitoring interval is too short. The message text provides the lowest possible configurable number in milliseconds for the specified monitoring interval.
Recommended Action The system is working properly, and no user action is required.
Error Message%DIAG-3-INVALID_PORT : Invalid port number : [chars]
Explanation A diagnostic request is being made on a port that does not exist.
Recommended Action Ensure that the specified port number exists and that the correct port number is being specified.
Error Message%DIAG-3-INVALID_TEST : Invalid test IDs : [chars]
Explanation A diagnostic test ID that does not exist was requested.
Recommended Action Ensure that the specified test ID number is supported by the line card. The list of available tests and their associated test IDs can be retrieved by entering the show diagnostic content command.
Error Message%DIAG-3-MAJOR : [chars]: [chars] detected a Major Error. Please use 'show diagnostic result <target>' to see test results.
Explanation A major error was detected during diagnostic testing.
Recommended Action Reseat the card and retry the test. If the same result occurs after the card is reseated and the test is retried, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG-3-MINOR : [chars]: [chars] detected a Minor Error. Please use 'show diagnostic result <target>' to see test results.
Explanation A minor error was detected during diagnostic testing.
Recommended Action Re-seat the card and retry the test. If the same result occurs after the card is reseated and the test is retried, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG-3-MONITOR_DISABLE : [chars]: The monitoring test:[dec] is disable since default interval is Zero
Explanation The specified test is no longer a health monitoring test because health monitoring has been disabled.
Recommended Action The system is working properly and no user action is required. To change the specified test to a health monitoring test, enable the health monitoring feature and ensure that your test is enabled as a health monitoring test.
Error Message%DIAG-3-MONITOR_INTERVAL_ZERO : [chars]: Monitoring interval is 0. Cannot enable monitoring for Test #[dec]
Explanation Health monitoring cannot be enabled for the specified test because the interval for the test has been set to zero.
Recommended Action If this condition was intended, no action is required. In order to enable the specified test for health monitoring, reset the interval to a number other than zero.
Error Message%DIAG-3-NO_DIAG_RUNNING : [chars]: Diagnostic is not running
Explanation An attempt was made to stop a diagnostic test that was not running.
Recommended Action No action is required.
Error Message%DIAG-3-NO_TEST : [chars]: No test to run
Explanation The diagnostic test cannot find tests to run.
Recommended Action In some cases on some platforms, a field diagnostic image must be loaded onto the line card before diagnostic testing can be run. If applicable, download a field diagnostic image onto the line card. In other cases, the test is not available and no action is required.
Error Message%DIAG-3-NOT_MONITORING_TEST : [chars]: The test:[dec] cannot be used as health monitoring test
Explanation The specified test number cannot be used as a health monitoring test.
Recommended Action No action is required.
Error Message%DIAG-6-RUN_COMPLETE : [chars]: Running Complete Diagnostics...
Explanation A complete diagnostic test is running on the card.
Recommended Action No action is required.
Error Message%DIAG-6-RUN_MINIMUM : [chars]: Running Minimum Diagnostics...
Explanation A minimum diagnostic test is running on the card.
Recommended Action No action is required.
Error Message%DIAG-6-SCHED_COMPLETE : [chars]: Scheduled Online Diagnostic is completed
Explanation The scheduled diagnostic test has completed.
Recommended Action Check the results, and proceed accordingly. No other action is required.
Error Message%DIAG-6-SCHED_RUNNING : [chars]: Performing Scheduled Online Diagnostic...
Explanation The scheduled diagnostic test is running.
Recommended Action No action is required.
Error Message%DIAG-6-SCHED_STOPPED : [chars]: Scheduled Online Diagnostic is stopped
Explanation The scheduled diagnostic test has been stopped.
Recommended Action If this condition was intended, no action is required. To run the diagnostic test, schedule the test or run the test manually.
Error Message%DIAG-6-SCHEDULE_IS_REMOVED : [chars]: Schedule Diagnostic for [[chars] [chars] [dec]:[dec].] is removed
Explanation The scheduled online diagnostic tests are no longer configured. This message usually appears after a scheduled test is removed by the user or a card is removed from the chassis.
Recommended Action If you want the scheduling tests to be removed, no action is required. If you want the scheduled tests to still be run, reconfigure the scheduled tests.
Error Message%DIAG-3-SET_ARGU_FAIL : Set argument failed
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG-6-SKIP_ONDEMAND_ACTIVE_TO_STANDBY_TEST : [chars]: [chars] cannot be executed.
Explanation The specified test can be run only from the active supervisor to test the standby supervisor.
Recommended Action Run the test from the active supervisor to test the standby supervisor.
Error Message%DIAG-6-SKIP_ONDEMAND_STANDBY_CARD_TEST : [chars]: [chars] cannot be executed.
Explanation The specified test can only be from a standby supervisor to test a standby supervisor.
Recommended Action Run the test from the standby supervisor to test the standby supervisor.
Error Message%DIAG-3-TEST_FAIL : [chars]: [chars]{ID=[dec]} has failed. Error code = [hex]
Explanation A diagnostic test has found an error on the line card.
Recommended Action Ensure that the line card is firmly in the slot, reseat the line card if necessary, and attempt to run the test again. If this error recurs after the card is reseated and the test is retried, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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%DIAG-3-TEST_NOT_SUPPORT : [chars]: [chars]{ID=[dec]} is not supported
Explanation The diagnostic test is not supported by the current chassis configuration. The test cannot be run. This condition does not indicate a problem with the system.
Recommended Action No action is required.
Error Message%DIAG-6-TEST_OK : [chars]: [chars]{ID=[dec]} has completed successfully
Explanation Diagnostic testing was completed, and no errors were found on the line card.
Recommended Action No action is required.
Error Message%DIAG-6-TEST_RUNNING : [chars]: Running [chars]{ID=[dec]} ...
Explanation The diagnostic testing function is running a test on the card.
Recommended Action No action is required.
Error Message%DIAG-3-TEST_SKIPPED : [chars]: [chars]{ID=[dec]} is skipped
Explanation The specified diagnostic test cannot be run. This condition does not indicate a problem with the system.
Recommended Action No action is required.
Error Message%DIAG-3-UNKNOWN_OPCODE : [chars]: Unknown opcode ([dec]) is received
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
DIAG_C10K Messages
The following are Online Offline Diagnostics (OOD) C10K subsystem messages.
Error Message%DIAG_C10K-2-CREATE_FAIL : Couldn't create [chars].
Explanation An internal software error has occurred. This error often occurs when heavy traffic loads are consuming large amounts of memory on the system.
Recommended Action If possible, retry the process that caused the error at a time when less traffic is being passed on the system. Alternatively, upgrade the SDRAM on the system. If this message recurs or neither of these options are viable, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to 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%DIAG_C10K-5-EXIT_ON_ERR : Field Diagnostics is stopped for card in slot [chars] due to test failure.
Explanation Diagnostic testing was previously configured to stop when a test failure occurred. A test failure has been detected, and diagnostic testing has been stopped.
Recommended Action The system is performing according to its configuration. No action is required. For diagnostic testing to continue after a test failure has been detected, enter the diagnostic ondemand action-on-failure command and change the failure count setting.
Error Message%DIAG_C10K-5-EXIT_ON_FAIL_LIMIT : Field Diagnostics is stopped for card in slot [chars] as failure limit is reached.
Explanation Diagnostic testing has been stopped because the test failure limit has been reached.
Recommended Action The system is performing according to its configuration. No action is required. For diagnostic testing to continue after more failures have been detected, enter the diagnostic ondemand action-on-failure command and change the failure count setting.
Error Message%DIAG_C10K-3-FD_BAD_IMAGE : Field Diagnostics image is corrupted.
Explanation The field diagnostics image has been corrupted.
Recommended Action Ensure that the correct field diagnostics image for the line card has been downloaded. If required, download a new field diagnostic image from http://www.cisco.com. Retry the download.
Error Message%DIAG_C10K-3-FD_BOOT_FAIL : Failed to boot Field Diagnostics image for card in slot [chars] after [dec] seconds.
Explanation The field diagnostic image failed in its attempt to initialize on the target line card.
Recommended Action Retry the image loading process by entering the diagnostic load command. If the message recurs while the field diagnostics loading process is being reloaded, download a new field diagnostic image from http://www.cisco.com. If the 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%DIAG_C10K-3-FD_CHECKSUM_ERR : Invalid checksum. Please make sure that you have indicated a valid Field Diagnostics image.
Explanation The indicated image is not a valid field diagnostics image.
Recommended Action Ensure that you are indicating a field diagnostics image and not another file (for example, a Cisco IOS software image, although this message will be triggered by any image that is not a field diagnostics image) in the CLI.
Error Message%DIAG_C10K-3-FD_CRASH : Crash of Field Diagnostics image detected for card in slot [chars]
Explanation The field diagnostics image has crashed, and the line card is attempting to reload the run-time image in place of the field diagnostics image. This field diagnostics image crash can occur when a test is not running, while a test is running, or while the line card is booting the field diagnostics image. If this message is received, the line card run-time image will be restored in place of the field diagnostics image.
Recommended Action Note when the message occurred and perform one of the following actions:
–
If this message occurred because the hw-module slot slot-number reset command, with slot-number being the slot number of the line card, was entered while the field diagnostics image was being loaded onto the line card, no action is required. This is normal router behavior.
–
–
Error Message%DIAG_C10K-4-FD_EXIT : Unexpected exit of Field Diagnostics image detected for card in slot [chars].
Explanation The field diagnostic operation was interrupted by the hw-module slot slot-number reset command, with slot-number being the slot number of the line card, and the original run-time image has been restored on the line card.
Recommended Action No action is required. To ensure the run-time image has been properly restored on the line card, enter the show diagnostic status command. To reload the field diagnostics image onto the line card, enter the diagnostic load command.
Error Message%DIAG_C10K-3-FD_INVALID_URL : Invalid URL for Field Diagnostics image.
Explanation An invalid path was provided for the field diagnostics image, and the field diagnostics image could not be found.
Recommended Action Ensure that the correct path and image name were specified.
Error Message%DIAG_C10K-3-FD_LENGTH_ERR : Length error detected for the extracted image.
Explanation An internal software error occurred while the field diagnostics image was being downloaded to the line card.
Recommended Action Attempt to download of the field diagnostics image to the line card again. 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%DIAG_C10K-3-FD_LOAD_FAIL : Failed to load Field Diagnostics image for card in slot [chars].
Explanation The image loading process failed to load the field diagnostics image onto the target line card.
Recommended Action Attempt to reload the field diagnostics image onto the line card. If the problem persists, reattempt the download at a time when system traffic is lower. 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%DIAG_C10K-3-FD_NO_SPACE : Can not allocate space for the extracted image.
Explanation The PRE does not contain enough memory to download the field diagnostics image.
Recommended Action Upgrade the SDRAM memory. If this message recurs, or this solution is not viable, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-FD_NOT_SUPPORT : Target line card is not supported by this Field Diagnostics image.
Explanation The indicated field diagnostics image does not support the targeted line card.
Recommended Action Check the system documentation to ensure that the line card is supported. If the line card is supported, download the correct field diagnostics image from http://www.cisco.com.
Error Message%DIAG_C10K-3-FD_TIMEOUT : Timeout waiting for a response from card in slot [chars].
Explanation The field diagnostics image is not responding.
Recommended Action Attempt to reload the image. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-GET_IPC_MSG_BUF_FAIL : Unable to get an IPC msg buffer: slot [int]/[int]
Explanation The PRE does not contain enough memory for a field diagnostics operation.
Recommended Action Retry the process at a time when system traffic is lower or upgrade the SDRAM memory. If this message recurs, or neither of the solutions are viable, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-GET_TSTAT_FAIL : Failed to get detail statistic information for test ID [int].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-INVALID_TID_MSG : Invalid test ID [int] in [chars] message.
Explanation An internal software error occurred, and the line card software (LCDOS) image automatically replaced the field diagnostics image on the line card. This error often occurs at times when heavy traffic loads are consuming large amounts of memory on the system.
Recommended Action Retry the process at a time when system traffic is lower or upgrade the SDRAM memory for the system. If this message recurs, or neither of the solutions are viable, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-INVSLOT : Invalid slot [int]/[int].
Explanation An internal software error has occurred.
Recommended Action Enter the hw-module slot slot-number reset command, with slot-number being the slot number of the line card, to reset the line card. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-IPC_OPEN_FAIL : Failed to open IPC port [hex]: [chars].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-4-IPC_PORT_EXIST : IPC handle already exists for card in slot [chars].
Explanation The line card in the indicated slot is attempting to establish communication with the PRE.
Recommended Action In most cases, this is an informational message and no action is required. The PRE will accept the request to set up the new communication channel, and the router will function normally. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-IPC_REMOVE_FAIL : Failed to remove IPC port [hex]: [chars].
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%DIAG_C10K-3-IPC_SEND_FAIL : Failed to send [chars] to card in slot [chars]: [chars].
Explanation An internal software error has occurred.
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