-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
SENSOR Messages
The following are voltage and temperature sensor messages.
Error Message%SENSOR-3-TEMP_CRITICAL : System sensor [dec] has exceeded CRITCAL temperature thresholds
Explanation One of the measured environmental test points has exceeded the extreme threshold. This condition could cause the system to fail to operate properly.
Recommended Action Correct the specified condition, or the system may shut itself down as a preventive measure. Enter the show environment all command to help determine if this problem is due to a temperature or voltage condition. If this is a critical temperature warning, ensure that the router fans are operating and that the room cooling and air conditioning are functioning.
Error Message%SENSOR-3-TEMP_NORMAL : [chars] temperature sensor is now normal
Explanation One of the measured environmental test points is now within the normal operating temperature range.
Recommended Action No action is required.
Error Message%SENSOR-3-TEMP_SHUTDOWN : Shuting down the system because of dangerously HIGH temperature \n at sensor [dec].
Explanation One of the measured environmental test points has exceeded the operating temperature environment of the router. The system has been shut down.
Recommended Action Unavailable.
Error Message%SENSOR-3-TEMP_WARNING : [chars] temparature sensor [dec] has exceeded WARNING temperature thresholds
Explanation One of the measured environmental test points has exceeded the warning threshold.
Recommended Action Closely monitor the condition and, if possible, correct by cooling the system environment.
Error Message%SENSOR-3-VOLT_CRITICAL : System sensor [dec] has exceeded CRITCAL voltage thresholds
Explanation One of the measured environmental test points has exceeds the extreme voltage threshold. This condition could cause the system to fail to operate properly.
Recommended Action Correct the specified condition, or the system may shut itself down as a preventive measure. Enter the show environment all command to help determine if this problem is due to voltage condition.
Error Message%SENSOR-3-VOLT_NORMAL : System sensor [dec]([dec]) is now operating under NORMAL voltage
Explanation One of the measured environmental test points is now within the normal operating voltage range.
Recommended Action No action is required.
Error Message%SENSOR-3-VOLT_SHUTDOWN : Shuting down the system because of dangerously HIGH voltage \n at sensor [dec].
Explanation One of the measured environmental test points has exceeded the configured operating voltage environment range of the router.
Recommended Action Unavailable.
Error Message%SENSOR-3-VOLT_WARNING : Voltage monitor [dec]([dec]) has exceeded voltage thresholds
Explanation One of the measured voltage test points has indicated that the voltage is not within the normal range.
Recommended Action Check the power supplies or open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SERIAL Messages
The following are WS serial line card messages.
Error Message%SERIAL-0-860_BOOT_NOTOK : [chars] Linecard local processor at slot [dec] failed to boot
Explanation The boot code for the DS3 line card local processor did not initialize properly. The line card will be deactivated. This error indicates a line card hardware failure.
Recommended Action Attempt to reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, and see if the line card recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with 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 hw-module slot slot-number start commands and your pertinent troubleshooting logs.
Error Message%SERIAL-1-ALLOCFAIL : [chars] (slot [dec]) [chars] Allocation failure.
Explanation The DS3 driver data structure could not be allocated while the line card was being initialized. This condition occurs because of low system memory, because of a misconfiguration, or because the memory installed in the system is not large enough to meet the demands of different applications in high-traffic conditions. The line card has been deactivated as a result of this error.
Recommended Action Attempt to reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card. If the error recurs, check the system configuration for the amount of Route Processor-switched traffic. Reconfigure the system for less Route Processor-switched traffic, if possible, because a large amount of Route Processor-switched traffic can cause this error. If the amount of installed memory can be upgraded, consider upgrading main memory by removing and replacing the SDRAM SO-DIMM. If this problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SERIAL-0-BADPORT : [chars] (slot [dec]) [chars] [dec]
Explanation Invalid packets were received at a very high rate on the specified port. This condition can occur as a result of a port misconfiguration, especially mismatched DSU subrates, with the most common problems coming from Kentrox DSUs. The port has been shut down so that the line card is not overwhelmed with these invalid packets.
Recommended Action Verify that the configuration is correct and matching on both ends of the connection. Configuration parameters include clock source (one end line, other internal), DSU (mode and subrate), and encapsulation. Also verify the physical condition on the line by running BERT or a similar test. Check the signal strength and cable length.
Error Message%SERIAL-5-BERT : Interface [chars], BERT [chars]
Explanation The DS3 driver has processed a BERT task. This message is a notification of completion.
Recommended Action No action is required.
Error Message%SERIAL-3-BMAENG : [chars] (slot [dec]) [chars] HDLC, [chars] [chars][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation A hardware race condition has occurred. This condition occurs when access to shared memory is not properly synchronized. The line card is deactivated and an automatic recovery is initiated. If the error occurs more than five times within an hour, the line card is not reactivated.
Recommended Action The line card can be reactivated manually using the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, if it has been deactivated after five failures. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, to gather data that may help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-BMAPAR : [chars] (slot [dec]) [chars] HDLC, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error has occurred on the High-Level Data Link Control Broadcast Multi-Access engine data bus. The line card is deactivated and subsequently reactivated. If the error occurs more than five times within an hour, the line card is not reactivated. This message is probably caused by a hardware failure.
Recommended Action If the line card is deactivated, copy the error message exactly as it appears on the console or in the system log. Enter the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, to gather additional data that might help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-BOOTCODE_CRASHED : [chars] linecard boot code in slot [dec] crashed, reason: [chars] ([hex])
Explanation The DS3 line card local processor boot code has crashed. This error message indicates a line card hardware failure. The line card will be deactivated.
Recommended Action Attempt to initialize the line card by manually entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, and see if the line card recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, to gather data that may help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-BOOTCODE_NOT_READY : [chars] linecard boot code in slot [dec] not ready for firmware download, boot code status [hex]
Explanation The DS3 line card boot code did not initialize properly. This error message indicates a line card hardware failure. The line card will be deactivated.
Recommended Action Attempt to initialize the line card by manually entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, and see if the line card recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, to gather data that may help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-CORRUPT : [chars] Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The running configuration for the DS3 line card is corrupted. The DS3 driver data structures that store snapshots of interface configurations are corrupted or are not correctly updated with the corresponding interface configurations in NVRAM. This problem is caused by a software error.
Recommended Action Attempt a graceful OIR of the line card by removing and reinserting the line card into the same slot or into another slot. A graceful OIR can also be performed by entering the hw-module slot slot-number stop command, with slot-number being the slot number of the affected card followed by the hw-module slot slot-number start command. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-DAUGHTER_CARD : [chars] Slot [dec]: [chars]
Explanation A daughter card was detected in the line card in the specified slot. The line card has been disabled because the daughter card is not supported. If this message appears even though no daughter card is present on the line card, an I2C bus access failure has occurred on the line card.
Recommended Action Remove the line card and inspect it for any daughter cards. If a daughter card is present, dismount it from the line card. After removing the daughter card, or if no daughter card was found, reinsert the line card. If the error persists, 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%SERIAL-0-DLL_OUTOFLOCK : [chars] HW DLLS failed to lock in linecard at slot [dec]
Explanation The DS3 line card could not initialize. The line card has been deactivated.
Recommended Action Attempt to reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, and see if the line card recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, to gather data that may help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with 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, hw-module slot slot-number start, and show diag slot-number commands and your pertinent troubleshooting logs.
Error Message%SERIAL-5-FAREND_EVENT : [chars] Interface [chars] [chars] far end request of type ([chars])
Explanation The DS3 driver has received and processed a known far-end request. The purpose of this message is to provide a notification that a known request was received from the far end of the link and that it has been processed successfully.
Recommended Action No action is required.
Error Message%SERIAL-3-FAREND_UNKNOWN : [chars] Interface [chars] received an unknown far end request ([int])
Explanation The DS3 driver has received an unknown FEAC code from the far end of the link. The request has been ignored. This condition is not a catastrophic error.
Recommended Action Check the configurations at both ends of the connection. If the configuration appears correct, copy the error message exactly as it appears on the console or in the system log. Enter the show controller serial slot-number/port-number command, with slot-number/port-number being the slot number and port number of the affected card, to gather additional 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 controller serial slot-number/port-number command, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with 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 controller serial slot-number/port-number commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-FW_CHECKSUM_FAILED : [chars] linecard in slot [dec] firmware integrity check failed.(section: [dec], expected checksum: [hex], calculated checksum: [hex])
Explanation The DS3 line card local processor firmware has crashed. The line card is restarted after the firmware crash. If the firmware crashes more than five times consecutively, the line card is not reactivated.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, 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, show tech-support and show diag slot-number commands and your pertinent troubleshooting logs.
Error Message%SERIAL-1-FW_CRASHED : [chars] line card firmware in slot [dec] crashed
Explanation The DS3 line card firmware has crashed.
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%SERIAL-3-FW_DOWNLOAD_FAILED : [chars] linecard in slot [dec] firmware download failed
Explanation The DS3 firmware download from the system main processor on the NSE to the line card local processor memory has failed. This error indicates a software failure, unless it is preceded by a firmware checksum failed error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, 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, show tech-support and show diag slot-number commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-FW_IPC_INIT_FAILED : [chars] linecard in slot [dec] firmware ipc initialization failed
Explanation The Cisco IPC module in the DS3 line card local processor firmware has failed to complete a successful initialization. The source of the problem could be a line card hardware failure or a software failure. The line card is deactivated and automatically reactivated. If this error occurs more than five times in an hour, the automatic reactivation does not occur and the line card remains deactivated.
Recommended Action If the line card is not automatically reactivated, copy the error message exactly as it appears on the console or in the system log and enter the show version, show ipc status, and show ipc port and show diag slot-number commands, with slot-number being the slot number of the affected card, to gather additional 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, show tech-support, show version, show diag slot-number, show ipc status, and show ipc port commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-FW_MSG : [chars] DS3 LC(slot [dec]), [chars]
Explanation An informational message has been sent from the DS3 line card firmware to the system main processor on the NSE.
Recommended Action No action is required.
Error Message%SERIAL-3-HDLCENG : [chars] (slot [dec]) [chars] HDLC, [chars]. [chars], port [dec] (src=[hex], det1=[hex], det2=[hex])
Explanation The HDLC engine inside the HDLC ASIC on the line card has detected unrecoverable errors. The line card is deactivated and an automatic recovery starts. The line card reinitializes after this error, unless the error occurs five times in one hour. If a line card encounters five such errors in one hour, the line card is deactivated without further attempts at recovery.
Recommended Action If the line card is not automatically reactivated, copy the error message exactly as it appears on the console or in the system log, and enter the show version and show diag slot-number commands, with slot-number being the slot number of the affected card. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative to determine whether to replace the line card or upgrade the Cisco IOS software. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show version, and show diag slot-number commands and your pertinent troubleshooting logs to determine whether to replace the line card or to upgrade the Cisco IOS version.
Error Message%SERIAL-0-INITFAIL : [chars] initialization failure for slot [dec], [chars]
Explanation The DS3 line card driver has failed to initialize properly. This error indicates a software initialization issue. The line card has been deactivated.
Recommended Action Attempt to reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, and see if the line card recovers from the error. If the error persists, copy the error message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, to gather data that may help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with 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, hw-module slot slot-number start, and show diag slot-number commands and your pertinent troubleshooting logs.
Error Message%SERIAL-3-KEEPALIVE_LOSS : [chars] Loss of keepalives from linecard in slot [dec]
Explanation The system main processor is not receiving keepalive messages from the line card local processor. The source of the problem could be a line card hardware failure or a software failure. The line card is deactivated and an automatic recovery starts. The line card reinitializes after this error, unless the error occurs five times in one hour. If a line card encounters five such errors in one hour, the line card is deactivated without further attempts at recovery.
Recommended Action If the line card is not automatically reactivated, copy the error message exactly as it appears on the console or in the system log, and enter the show version and show diag slot-number commands, with slot-number being the slot number of the affected card, to gather data that may help identify the nature of the error. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show version and show diag slot-number commands and your pertinent troubleshooting logs to determine whether to replace the line card or to upgrade the Cisco IOS version.
Error Message%SERIAL-3-NOHWIDB : [chars] [dec]/[dec][chars] hardware IDB is missing
Explanation The IDB for the DS3 port hardware is missing.
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%SERIAL-3-SRAMPAR : [chars] (slot [dec]) [chars] HDLC, [chars]. [chars]=[hex][chars]. (src=[hex], det1=[hex], det2=[hex])
Explanation A parity error occurred in the HDLC engine SRAM memory. The source of the problem is a hardware failure. The line card is deactivated and an automatic recovery starts. The line card reinitializes after this error, unless the error occurs five times in one hour. If a line card encounters five such errors in one hour, the line card is deactivated without further attempts at recovery.
Recommended Action If the line card is not automatically reactivated, copy the error message exactly as it appears on the console or in the system log, and enter the show version and show diag slot-number commands, with slot-number being the slot number of the affected card. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative to determine whether to replace the line card or upgrade the Cisco IOS software. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show version, and show diag slot-number commands and your pertinent troubleshooting logs to determine whether to replace the line card or to upgrade the Cisco IOS version.
Error Message%SERIAL-4-UNKNOWNPARAM : [chars] [dec]/[dec][chars] parameter value is unknown
Explanation The IPC command parameter is unknown, and the corresponding IPC message has been dropped. This is an informational message only.
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.
SERVICEMODULE Messages
The following are Service Module monitor messages.
Error Message%SERVICEMODULE-4-BADILPALLOCATE : Service module [chars] Received ILP allocate failed ack.
Explanation The platform information of the service module was not received correctly.
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 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%SERVICEMODULE-4-BADILPDEALLOCATE : Service module [chars] Received ILP deallocate failed ack.
Explanation The platform information of the service module was not received correctly.
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 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%SERVICEMODULE-4-BADILPOPERATION : Service module [chars] Received invalid ILP operationt
Explanation The platform information of the service module was not received correctly.
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 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%SERVICEMODULE-5-SHUTDOWN1 : Service module [chars] shutdown not complete: removing the module may currupt the hard-disk
Explanation The service module did not respond to the shutdown request.
Recommended Action No action is required.
Error Message%SERVICEMODULE-5-SHUTDOWN2 : Service module [chars] shutdown complete
Explanation The shutdown of the service module was completed.
Recommended Action No action is required.
Error Message%SERVICEMODULE-5-SHUTDOWN3 : Service module [chars] shutdown not complete: removing the module may loose unsaved configuration
Explanation The service module did not respond to the shutdown request.
Recommended Action No action is required.
SFP Messages
The following are SFP messages.
Error Message%SFP-4-EEPROM_CRC_ERR : EEPROM checksum error for SFP in [chars]
Explanation The SFP in the port specified in the error message contains invalid EEPROM data.
Recommended Action Remove the SFP from the specified port.
Error Message%SFP-3-EEPROM_DUP_ERR : SFP on ports [chars] and [chars] have duplicate serial numbers
Explanation The GBIC or SFP was identified as a Cisco GBIC, but its vendor ID and serial number match those of another GBIC on the system.
Recommended Action Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SFP-4-EEPROM_READ_ERR : Error in reading SFP serial ID in [chars]
Explanation An error occurred when the SFP type was being read from the EEPROM.
Recommended Action Remove the SFP from this port.
Error Message%SFP-4-EEPROM_SECURITY_ERR : SFP in [chars] failed security check
Explanation The SFP in the port specified in the error message contains invalid EEPROM data.
Recommended Action Remove the SFP from the specified port.
Error Message%SIGNATURE-3-ABORT_OPER : %ERROR: Aborting [chars].
Explanation The system is aborting the specified operation because it failed to verify a valid signature in the image file.
Recommended Action Attempt to restart the operation by using an image file with a valid signature. A valid signature ensures the integrity of the image.
SGPRSWARNING Messages
The following are SGPRS warning messages.
Error Message%SGPRSWARNING-2-SGPRS_WARNING_RATE : Use a lower rate value or else loose accuracy
Explanation The average burst time is longer than the configured rate.
Recommended Action If this message recurs, decrease the rate.
SIGNATURE Messages
The following are server load balancing (SLB) Dynamic Feedback Protocol (DFP) agent messages.
Error Message%SIGNATURE-3-CONTINUE_OPER : %ERROR: Continuing Operation [chars] in spite of failure.
Explanation Although the system failed to verify a valid signature in the image file, the user decided to continue the specified operation. A valid signature ensures the integrity of the image.
Recommended Action If you decide to continue the operation without a valid signature in the image file, no action is required. If you would prefer to cancel the operation after choosing to continue it, perform one of the following:
–
If the copy command was used, delete the copied file by entering the delete command.
–
Error Message%SIGNATURE-3-DELETE_FAILED : %ERROR: Unable to auto delete file [chars]. Remove file manually
Explanation The specified Cisco IOS Software image file contains an invalid signature, but the file could not be automatically deleted. A valid signature ensures the integrity of the image.
Recommended Action Delete the file by entering the delete command.
Error Message%SIGNATURE-3-NOT_ABLE_TO_PROCESS : %ERROR: Not able to process Signature in [chars].
Explanation An unknown error occurred when the system attempted to process the signature in the specified image file. A valid signature ensures the integrity of the image.
Recommended Action Do not use this file. The file might be corrupted or modified. Attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it. If this message recurs, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SIGNATURE-4-NOT_PRESENT : %WARNING: Signature not found in file [chars].
Explanation The specified image file does not have a signature. Only Cisco IOS software images in executable and linkable format are signed. Releases that do not support the image verification feature do not contain a signature in the image file. If you enter the verify, copy, or reload command, and the specified file is not a Cisco IOS Software image in executable and linkable format or of an earlier release, the system displays this warning message because the file does not have a signature. A valid signature ensures the integrity of the image.
Recommended Action If the specified file is a Cisco IOS software image in executable and linkable format, exercise caution when deciding whether to use this file. Check the release notes, or check the Feature Navigator at http://www.cisco.com/go/fn and search for "Image Verification," to check if the image that you are using supports the image verification feature.
Error Message%SIGNATURE-3-NOT_VALID : %ERROR: Signature not valid for file [chars].
Explanation The specified Cisco IOS software image contains an invalid signature. A valid signature ensures the integrity of the image.
Recommended Action Do not use this file. The file might be corrupted or modified. Attempt to copy the file again, or download the file again from the http://www.cisco.com page before copying it. If this message recurs, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SIGNATURE-4-UNKNOWN : %WARNING: Found unknown signature type [hex], in file [chars]\n Skipping the signature.
Explanation An unknown signature type was found. If the requested image belongs to a later release than the running image, the requested image might have a newer signature type. A valid signature ensures the integrity of the image.
Recommended Action If the specified file is a Cisco IOS software image in executable and linkable format, exercise caution when deciding whether to use this file. Check the release notes, or check the Feature Navigator at http://www.cisco.com/go/fn and search for "Image Verification," to check if the image that you are using supports the image verification feature.
SIP Messages
The following are Session Initiation Protocol messages.
Error Message%SIP-3-LIST_ERROR : Unable to create list for [chars]
Explanation A list could not be created. Failure to create a list generally indicates that the router is out of memory, because of either a memory leak or insufficient memory. If the error was generated soon after a reload, it is more likely that the router does not have enough memory. If the router has been running for a while, then a memory leak is more likely. The SIP component could not be properly initialized, and SIP calls may not be completed properly.
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%SIP-3-QUEUE_ERROR : Unable to enqueue event [chars] ([dec]) to a process watched queue. Current size: [dec], max size: [dec]
Explanation An internal or external event was dropped because it could not be added to the queue, probably because the queue is full. The result may be minor (an SIP message was retransmitted) or major (a call was dropped), depending on the event that was lost. This error may indicate that the call rate is exceeding the capacity of the gateway. If this is the case, the CPU utilization will be excessively high, probably above 75%.
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%SIP-3-UNSUPPORTED : [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. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Enter the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://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.
SKINNYSECURESERVER Messages
The following are skinny secure server messages.
Error Message%SKINNYSECURESERVER-3-NOINIT : Can't initialize Secure Skinny server
Explanation Ports could not be initialized for the secure skinny server.
Recommended Action Ensure that the skinny secure server port is available on the local machine.
Error Message%SKINNYSECURESERVER-3-NOMEM : Can't initialize memory for Secure Skinny server
Explanation Insufficient memory was available to initialize the secure skinny server.
Recommended Action Increase the amount of available memory.
Error Message%SKINNYSECURESERVER-3-NOPROC : Could not start Skinny Secure Server
Explanation An internal problem was encountered while a process was being created.
Recommended Action No action is required.
Error Message%SKINNYSECURESERVER-3-NOSOCKETS : Max Number of Skinny Secure Server sockets exceeded: too many IP phones
Explanation Too many skinny secure server clients are requesting service.
Recommended Action Reduce the number of secure IP phones that are requesting service.
SKINNYSECURESERVICE Messages
The following are skinny secure service messages.
Recommended Action support representative and provide the representative with the gathered information.
Error Message%SKINNYSECURESERVICE-3-NOINIT : Can't initialize Secure Skinny server
Explanation There are internal problems with initializing ports for the Secure Skinny server.
Recommended Action Make sure the Skinny secure server port is available on the local machine.
Error Message%SKINNYSECURESERVICE-3-NOMEM : Can't initialize memory for Secure Skinny server
Explanation There is insufficient memory for the Secure Skinny server.
Recommended Action Increase the amount of available memory.
Error Message%SKINNYSECURESERVICE-3-NOPROC : Could not start Skinny Secure Server
Explanation There is an internal problem in process creation.
Recommended Action No action is required.
Error Message%SKINNYSECURESERVICE-3-NOSOCKETS : Max Number of Skinny Secure Server sockets exceeded: too many IP phones
Explanation There are too many skinny Secure server clients requesting service.
Recommended Action Reduce number of Secure IP phones requesting service.
SLB_DFP Messages
The following are server load balancing (SLB) Dynamic Feedback Protocol (DFP) agent messages.
Error Message%SLB_DFP-4-SOCK_ERR : Agent [IP_address]:[int] - Socket_recv error [dec]
Explanation A message involving a socket error has been received from the SLB DFP agent.
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.
SLICE_TOASTER Messages
The following are slice messages.
Error Message%SLICE_TOASTER-5-DNLD_DONE : PXF download complete, PXF operational, time elapsed [time-stamp]
Explanation The PXF microcode was successfully downloaded and started. The PXF forwarding engine is now configured and operational. The time elapsed is measured from the time the "%SLICE_TOASTER-5-DNLD_START" message was received. This is a normal activity when the Cisco IOS software is being booted after a fatal PXF error has occurred.
Recommended Action No action is required.
Error Message%SLICE_TOASTER-5-DNLD_START : Downloading PXF Microcode [chars], version=[chars], [chars]
Explanation The platform code has started to download a specific PXF microcode image. This is a normal activity when the Cisco IOS software is being booted after a fatal PXF error has occurred.
Recommended Action No action is required.
Error Message%SLICE_TOASTER-2-DOWNLOAD : [chars]: Slice (PXF) microcode image [chars]: could not be downloaded.
Explanation The slice (PXF) microcode could not be downloaded. This condition could be due to an already corrupted image or to a software or 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%SLICE_TOASTER-2-DUMP : Slice (PXF) has crashed, attempting to write core file(s)....
Explanation The slice (PXF) hardware 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%SLICE_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%SLICE_TOASTER-3-FATALPXF : Fatal Slice (PXF) interrupt, reg=[hex], mask=[hex], config=[hex] - [chars]
Explanation The slice (PXF) facility has issued a fatal interruption. This condition may be caused by a hardware or a software 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%SLICE_TOASTER-0-FP_ERROR : Topflite Init error: [chars]
Explanation The Topflite board is not working properly or is not compatible with the Cisco IOS software image that is operational on the system.
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%SLICE_TOASTER-0-FP_REV : Topflite rev [dec].[dec] is [chars], require at least [dec].[dec]
Explanation The Cisco IOS software image that is operational on the system is incompatible with the hardware revision of the Topflite board, or the Topflite board is supported but with software workarounds for certain hardware problems. If the first condition is present, the Cisco IOS software has not completed the boot process. If the second condition is present, 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%SLICE_TOASTER-0-FP_TYPE : Topflite type [dec] is [chars]
Explanation This Cisco IOS software image is incompatible with the hardware type of the Topflite 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%SLICE_TOASTER-2-HDRCORRUPT : Slice (PXF) microcode header of image [chars] has been corrupted, expected [hex], got [hex].
Explanation The slice (PXF) microcode appears to be corrupted. This condition could be due to an already corrupted image or, less likely, to a software 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%SLICE_TOASTER-2-IMAGE : Slice (PXF) microcode image [chars]: could not be read.
Explanation The slice (PXF) microcode could not be read. This condition could be due to an already corrupted image or, less likely, a software 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%SLICE_TOASTER-2-INCOMPAT : This Slice (PXF) microcode image is incompatible with this Cisco IOS image.
Explanation The signature in the slice (PXF) 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%SLICE_TOASTER-3-INV_TT2RP_CMD : Invalid TT2RP Cmd ([dec]) received from PXF (Msg: [hex][hex])
Explanation The slice (PXF) facility has sent a TT2RP command to the RP that contains an invalid TT2RP command ID. This condition typically indicates that a PXF microcode 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%SLICE_TOASTER-2-METADATA : Slice (PXF) microcode meta-data [chars]: [chars], in file: [chars].
Explanation The slice (PXF) microcode appears to be corrupted. This condition could be due to an already corrupted image or, less likely, to a software 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%SLICE_TOASTER-3-NOMEM : OUT of Memory: [chars]
Explanation Unavailable.
Explanation Unavailable.
Error Message%SLICE_TOASTER-2-OPER : Slice (PXF) not operational: [chars]
Explanation The slice (PXF) clients could not be made operational. This condition could be due to a software or 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%SLICE_TOASTER-4-PXF_CRASHINFO : Writing Slice (PXF) debug information to [chars].
Explanation A file containing information useful for diagnosing a slice (PXF) restart operation is being written.
Recommended Action Save the "pxf_crashinfo" file. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the "pxf_crashinfo" file, and your pertinent troubleshooting logs.
Error Message%SLICE_TOASTER-3-PXF_CRASHINFO_FAIL : Failed to write Slice (PXF) debug information.
Explanation Slice (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 Attempt to free up space on the device to which the debugging information was addressed. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the "pxf_crashinfo" file, and your pertinent troubleshooting logs.
Error Message%SLICE_TOASTER-2-ROW : Slice (PXF) microcode header of image [chars] doesn't match block [chars], row [dec] not row [dec].
Explanation The slice (PXF) microcode appears to be corrupted. This condition could be due to an already corrupted image or, less likely, a software 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%SLICE_TOASTER-2-STALL : Slice (PXF) Stall detected
Explanation The slice (PXF) driver has detected a slice 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%SLICE_TOASTER-2-START : Slice (PXF) not started: memory state: [dec], expected [dec].
Explanation The slice (PXF) clients could not be started. This condition could be due to a software or 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%SLICE_TOASTER-2-TDB : Could not find control block for Slice (PXF) image [chars].
Explanation A software error occurred that prevented the control block that represents this slice (PXF) image 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%SLICE_TOASTER-2-UNUSABLE : No usable Slice (PXF) microcode
Explanation No usable slice (PXF) microcode could be loaded. This condition could be due to an already corrupted image or to a software or 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.
SLOT Messages
The following messages are for the AS5850 slot state machine and OIR-related events.
Error Message%SLOT-3-CHKPT_INTERNAL : Internal OIR checkpointing error [[chars]]
Explanation An internal error has occurred within the OIR checkpoint code.
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%SLOT-3-DISC_FAIL : Could not start board discovery process.
Explanation The system could not start the feature board discovery process. In this error condition, feature boards cannot be discovered either at boot time or if inserted into the system.
Recommended Action The likely cause of the condition is low memory during boot, which points to a fault in the Cisco IOS version being run. Try installing a different Cisco IOS software version.
Error Message%SLOT-4-FB_NOT_DISC : Timed out waiting for discovery of boards ([dec] seconds), [dec] missing
Explanation A time out occurred while waiting for the discovery of the FBs. The system reads the redundancy mode at boot time and suspends the boot until all FBs have been discovered. If they are not discovered within the allotted period, booting continues. When booting continues without all FBs being discovered, the system can reject the configuration that is specific to the missing cards.
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%SLOT-4-FB_RESET : Resetting feature board [dec], [chars]
Explanation The feature board is being reset for the reason specified in the message.
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%SLOT-3-INCOMPAT : Board in slot [dec] ignored, it is a [chars] board which is incompatible with the system.
Explanation This message is displayed when T1 and E1 boards are owned by an RSC. Each RSC can only own boards of either T1 or E1 types; the types cannot be mixed. It is possible to have an E1 card on one side of the chassis and a T1 on the other, but only if they are owned by different RSCs with the system in chassis-split mode.
Recommended Action Change one of the card types, or change ownership of one type of boards to another RSC.
Error Message%SLOT-4-RSC_RESET : Resetting RSC [dec], [chars]
Explanation The RSC is being reset for the reason specified.
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%SLOT-3-SLOT_INTERNAL : Slot state machine error for slot [dec] [[chars]]
Explanation An internal error has occurred within the slot state machine code.
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.
SLOT_HM Messages
The following are RSC slot health monitor messages.
Error Message%SLOT_HM-4-FB_POWERDOWN : Powering down feature board [dec], [chars]
Explanation The feature board is being powered off for the reason specified. To reenable the FB, use the hw-module slot reset command.
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%SLOT_HM-3-HM_REGISTRATION_FAILED : The rsc_slot subsystem failed to register with the Health-Monitor
Explanation The rsc_slot subsystem has failed to register with the health monitor. The health monitor rules associated with the subsystem are not operational. This error condition does not have an adverse impact on the CEF or on the health monitor.
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%SLOT_HM-3-RULE_OPERATION_FAILED : Failed to [chars] [chars] for Repeat FB [dec] Reboot Rule.
Explanation The RSC slot subsystem failed to create or delete a health monitor rule, or its component conditions or actions. The health monitor rule is not operational. This error condition does not have an adverse impact on the RSC slot subsystem or on the health monitor.
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%SLOT_HM-3-SUBSYS_HEALTH_CHANGE_FAIL : Attempt to [chars] rsc slot HM subsystem health (for slot [dec]) by [dec] failed.
Explanation An attempt to update the RSC slot in the HM subsystem health has failed. The RSC slot subsystem health is incorrect, causing the system health also to be incorrect. The impact on the system health is negligible, because the weighting of the RSC slot subsystem is low. This error is usually considered a minor 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.
SMIC Messages
The following are 2FE2W, 1FE2W, 1FE1R2W, 2W network module-related messages.
Error Message%SMIC-3-BSCHUNT : BSC HUNT cmd for int [dec]/[dec] failed
Explanation An 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%SMIC-1-DISCOVER : NM slot [dec]: only [dec] PCI dev found
Explanation Some of the interface controller devices on MRC did not initialize properly.
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%SMIC-3-DSCC4 : DSCC4 chip init slot [dec] failed
Explanation An 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%SMIC-4-FPGA_UPDATE : FECPM FPGA (slot [dec]) updated, all EADI sessions terminated
Explanation The Cisco IOS software image contains updated FECPM FPGA firmware, which must be downloaded to the FPGA regardless of EADI sessions.
Recommended Action Verify the status of EADI sessions once the router is operational.
Error Message%SMIC-1-INITFAIL : NM slot [dec]: PCI dev [dec] init failed
Explanation A PCI device on MRC has failed to perform a successful hardware initialization.
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%SMIC-3-INVALID_CLOCKRATE : Unsupported clock rate req on int [dec]/[dec] - index [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SMIC-3-INVALID_SCC : Config req for invalid SCC via int [dec]/[dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SMIC-3-NOMEMORY : No memory for [chars] of unit [dec]
Explanation The router does not have enough memory to perform the function specified in the message text.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SMIC-3-OWNERR : Buffer owner ship error on int [dec]/[dec], pak=[hex]
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%SMIC-2-SCCFAIL : For SMIC interface:[dec]/[dec] failed to do [chars]
Explanation The software failed to initialize or restart the SCC of a serial interface on the SMIC.
Recommended Action Clear the serial 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%SMIC-3-SCCRESET : SCC reset for int [dec]/[dec] at [chars] failed
Explanation An 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%SMIC-3-SPI_OP_FAILED : NM base addr - [hex], WIC slot - [dec], SPI op 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%SMIC-5-SPURINT : Spurious [chars] int on SCC [dec] in slot [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SMIC-3-TDMSW : TDM switch init in slot [dec] failed
Explanation An 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%SMIC-5-TOOBIG : On int [dec]/[dec], tx pak is [dec] bytes
Explanation A packet greater than the assigned MTU of this serial interface was queued up for transmission.
Recommended Action The system should recover. 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%SMIC-5-TOOSMALL : On int [dec]/[dec], tx pak size is [dec] bytes
Explanation A small packet (shorter than 2 bytes) was queued up for transmission. The interface cannot process such small packets for transmission.
Recommended Action The system should recover. 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%SMIC-3-TXCOMPNOTIFY : On int [dec]/[dec], tx_comp_notify vector is not set
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%SMIC-3-UFHANDLE : UnderFlow handling on int [dec]/[dec] failed.
Explanation An 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%SMIC-5-UNDERFLOW : Transmit underflow on int [dec]/[dec]
Explanation While transmitting a frame, the local buffer of the serial 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 problem is temporary, depending on transient peak loads within the system.
Recommended Action The system should recover. No action is required.
Error Message%SMIC-1-UNKNOWN_WIC : NM slot [dec], wic card has an unknown id [hex]
Explanation The software does not recognize the type of WIC that is plugged into the port module.
Recommended Action Check the part number on the WIC to verify that it is supported in the Cisco IOS software release that is operational on the router. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SNASW Messages
The following are Systems Network Architecture (SNA) Switching Services messages.
Error Message%SNASW-3-ASM_LOG_7 : PROBLEM - [int] - BIND received with the next hop in the RSCV set to the local node again [chars]
Explanation The SNA switch has received a BIND request with an incorrectly formatted RSCV. The CP name for the next hop in the RSCV is in the local node. The session will not be activated.
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%SNASW-3-CLS_LOG_0 : PROBLEM - [int] - Could not validate process handle [chars]
Explanation CLS has passed a DLC packet to the SNA Switch , butthe SNA Switch does not have a valid handle to invoke the correct SNA process. The CLS message has been discarded.
Recommended Action Dump traces and contact the Cisco TAC.
Error Message%SNASW-3-CS2_LOG_31 : PROBLEM - [int] - Unable to activate port as the IP DLC does not support IP hostnames [chars]
Explanation Unable to activate port because the IP DLC does not support IP hostnames. The START_PORT verb will fail and the port will not restart successfully.
Recommended Action Either choose a different IP DLC that does support IP hostnames or, if IPv4 is being used, specify the local port by IP address instead of IP hostname.
Error Message%SNASW-3-CS2_LOG_32 : PROBLEM - [int] - Unable to start link station as the IP DLC does not support IP hostnames [chars]
Explanation Unable to activate link station because the IP DLC does not support IP hostnames. The START_LS verb will fail and the link station will not restart successfully.
Recommended Action Either choose a different IP DLC that does support IP hostnames or, if IPv4 is being used, specify the link station by IP address instead of IP hostname.
Error Message%SNASW-3-CS2_LOG_33 : PROBLEM - [int] - Unable to start dynamic link as the IP DLC does not support IP hostnames [chars]
Explanation Unable to activate dynamic link station as the IP DLC does not support IP hostnames. Link activation will fail and the link station will not start successfully.
Recommended Action Either choose a different IP DLC that does support IP hostnames or, if IPv4 is being used, specify the link station by IP address instead of IP hostname.
Error Message%SNASW-3-HPR_LOG_20 : PROBLEM - [int] - Remote node supplied a corrupted RSCV: the next hop is the local CP [chars]
Explanation An HPR Route Setup RU has been received with an RSCV that gives the local node as the next ANR hop. This is invalid. Therefore the remote node is sending invalid protocol data.
Recommended Action Report error to remote end.
Error Message%SNASW-4-LDLC_IP_LOG_13 : EXCEPTION - [int] - The UDP stub failed to resolve a host name into an IP address. [chars]
Explanation The UDP stub failed to resolve a host name into an IP address. Port activation will fail.
Recommended Action Check that the host name is configured in the DNS server or in your local hosts file. If this machine uses a DNS server, check that it has the correct IP address for the server, and that the server is reachable. Also check surrounding logs for problems that may be related.
Error Message%SNASW-4-LDLC_IP_LOG_14 : EXCEPTION - [int] - A link activation was attempted for an address that matches an existing link. [chars]
Explanation A link activation was attempted for an address that matches an existing link. The link will fail to start. The existing link is unaffected.
Recommended Action Correct the configuration. These settings are supplied in the address information passed to SNAP APPN on the verb DEFINE_LS.
Error Message%SNASW-4-LDLC_IP_LOG_15 : EXCEPTION - [int] - The UDP stub has detected an error. [chars]
Explanation The UDP Stub has detected an error.
Recommended Action Investigate the logs to help identify the error.
Error Message%SNASW-3-LDLC_IP_LOG_20 : PROBLEM - [int] - Failed to activate LDLC link using IPv4 numerical address from remote host. [chars]
Explanation Failed to resolve remote hostname. Attempt to activate HPR/IP link using IPv4 numerical address supplied by remote host has also failed. The link will fail to start.
Recommended Action Check the DNS configuration.
Error Message%SNASW-4-RTP_LOG_10 : EXCEPTION - [int] - LFSID in use, moving on to next one. [chars]
Explanation An LFSID was found to be in use. The SNA switch is using a different LFSID.
Recommended Action If this log appears frequently, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SNMP Messages
The following are SNMP messages.
Error Message%SNMP-3-AUTHFAILIPV6 : Authentication failure for SNMP request from host [ipv6_addr]
Explanation An SNMP request sent by this host was not properly authenticated.
Recommended Action Make sure that the community or user name used in the SNMP request has been configured on the router.
Error Message%SNMP-4-NOENGINEIDV6 : Remote snmpEngineID for [ipv6_addr] not found when creating user: [chars]
Explanation An attempt to create a user failed. This condition is likely due to the engine ID of the remote agent or SNMP manager not being configured.
Recommended Action Configure the remote SNMP engine ID and reconfigure the user. 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.
SNMP_BULKSTAT Messages
The following are SNMP bulk-data collection messages.
Error Message%SNMP_BULKSTAT-4-BUFFER_OVERFLOW : Buffer size too small to accomodate data for one collection \n interval for [chars]
Explanation The bulk data file is too large for the configured buffer size within a single transfer interval. Data collection continues in another new buffer of the configured size, and the collected buffer is transferred to the configured destination.
Recommended Action Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size.
Error Message%SNMP_BULKSTAT-3-NO_MEMORY : Memory not available for [chars] for [chars]
Explanation Data collection or transfer has failed because of lack of memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SNMP_BULKSTAT-4-PRI_URL_UNREACHABLE : Primary network management station is unreachable for [chars]
Explanation The collected bulk data file was not successfully transferred to the primary network management station address specified in the message. This condition can occur because the primary network management address is not configured, or the configured primary network management station address is unreachable. If a secondary network management station address is configured, the collected bulk data file is sent to the secondary network management station address.
Recommended Action Ensure that the primary network management station address is configured. If the primary network management station address is configured, check the connectivity to the destination indicated by the primary network management station address specified in the message.
Error Message%SNMP_BULKSTAT-3-REMOTE_FILE_WRITE_ERR : File Write failed for the remote file [chars]
Explanation The username or password specified in the message might not have the required privileges to write a file to the network management station. It is also possible that the destination directory specified in the message is invalid.
Recommended Action Change the username and password in the network management station address to have the necessary privileges to write to the destination directory.
Error Message%SNMP_BULKSTAT-4-SEC_URL_UNREACHABLE : Secondary network management station is unreachable for [chars]
Explanation The collected bulk data file could not be successfully transferred to the secondary network management station address destination specified in the error message. This condition can occur because the secondary network management station address is not configured or the configured secondary network management station address is unreachable. If a retention interval is not configured, the bulk data file is deleted immediately. If a retention interval is configured, retries are attempted for the configured number of times.
Recommended Action Check the connectivity to the destination indicated by the secondary network management station address shown in the message.
Error Message%SNMP_BULKSTAT-3-TOOSMALL_BUFFER : Buffer size is insufficient to accommodate even the \n header part for [chars]
Explanation The buffer size is insufficient to accommodate the header for the bulk data file. The header contains the schema definitions of all the configured schemas.
Recommended Action Increase the maximum buffer size using the buffer-size size-of-buffer command, where size-of-buffer is the increased buffer size.
SNMP_MGR Messages
The following are Simple Network Management Protocol (SNMP) proxy messages.
Error Message%SNMP_MGR-3-MISSINGHOSTIPV6 : Cannot locate information on SNMP informs host: [ipv6_addr]
Explanation A table entry for the specified SNMP destination for inform notifications cannot be found. As a result, inform notifications will not be sent to this destination.
Recommended Action Deleting and re-adding the informs destination via the snmp-server host command in global configuration mode may clear the condition. Otherwise, reloading the system may be necessary. Enter the show snmp host and show snmp commands. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SOI Messages
The following are Simple Network Management Protocol (SNMP) over interprocess communication (IPC) messages.
Error Message%SOI-2-ACTIVEREGFAIL : Unable to add function to GOACTIVE registry.
Explanation A function could not be added to the "GOACTIVE" registry.
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%SOI-2-BADPXMCOMMUNITY : PXM's community string (length [dec]) was invalid. Limits are [dec] to [dec].
Explanation An invalid PXM community string was received.
Recommended Action Ensure that the length of the community string that is configured on PXM is within the configured limits. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SOI-2-DELAYREGFAIL : Unable to add function to delayed func registry.
Explanation A function could not be added to the "delayed func" registry.
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%SOI-2-EVENTHOOKADDFAIL : Unable to add callback routine for switchover event for SNMP over IPC.
Explanation A callback routine for switchover events for the SNMP over IPC function could not be added.
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.
SONICT Messages
The following are SONIC Ethernet driver messages.
Error Message%SONICT-1-INITFAIL : Unit [dec], initialization timeout failure, csr[dec]=[hex]
Explanation The SONICT chip failed its initialization sequence.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show cont e0/0/x 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.
SPA Messages
The following are Shared Port Adapter (SPA) messages.
Error Message%SPA-3-RESOURCE_ERROR : [chars] ([hex], [hex], [hex], [hex]) [chars]
Explanation A required resource could not be allocated.
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%SPA-3-SOFTWARE_ERROR : [chars] ([hex], [hex], [hex], [hex]) [chars]
Explanation A specified software error has been detected. More details are available in the message text.
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.
SPA_OIR Messages
The following are Shared Port Adapter (SPA) online insertion and removal (OIR) messages.
Error Message%SPA_OIR-1-EVENTDATAERROR : SPA OIR event data error - [chars]([int])
Explanation An error involving an SPA OIR operation 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%SPA_OIR-1-INITFAIL : SPA OIR init ([chars])
Explanation An SPA OIR initialization failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SPA_OIR-1-MESSAGEERROR : [chars]: SPA OIR message error - [chars]([int])
Explanation An SPA OIR message 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%SPA_OIR-1-PLUGINCREATEFAIL : [chars]: SPA PLUGIN create failure. ([chars])
Explanation An SPA OIR plug-in could not be created.
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%SPA_OIR-1-POST_EVENT_ERROR : [chars]: event [hex]
Explanation A post event error occurred in the SPA OIR state machine.
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%SPA_OIR-1-SOFTWARE_ERROR : [chars]: [chars][hex]
Explanation A 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%SPA_OIR-1-SPANOTSUPPORTED : [chars]: SPA TYPE [hex] NOT SUPPORTED
Explanation An SPA OIR subslot initialization failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SPA_OIR-1-SUBSLOTINITFAIL : [chars]: SPA OIR init ([chars])
Explanation An SPA OIR subslot initialization failure has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SPA_OIR-1-UNEXPECTEDEVENT : [chars]: SPA OIR unexpected event([int])
Explanation An SPA OIR message 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%SPA_OIR-1-UNEXPECTED_RECOVERY_ACTION : [chars]: unexpected recovery action([int]) for fail code [hex]
Explanation A 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.
SPE Messages
The following are Service Processing Element (SPE) messages.
Error Message%SPE-6-FM_VERSION_MISSING : Could not get a version from the firmware file [chars]
Explanation The requested firmware image is missing the version information.
Recommended Action No action is required.
SSG Messages
The following are service selection gateway messages.
Error Message%SSG-5-SSG_TAL_AUTH_PENDING : SSG TAL : Authorization requests pending, AAA server might be down
Explanation Pending authorization requests have exceeded the configured maximum value. The AAA server may either be responding very slow may be inactive.
Recommended Action Check to see if the server is active, then increase the maximum number of allowable pending requests in the system configuration.
Error Message%SSG-5-SSG_TAL_AUTH_RATE : SSG TAL : Attempting to send more authorization requests/sec than the configured rate-limit value
Explanation The number of attempted authorization requests per second is greater than the configured maximum rate-limited value.
Recommended Action If the AAA server is capable of handling more requests per second, you may increase the rate-limited value.
Error Message%SSG-5-SSG_TAL_NR : SSG TAL : No response from AAA server. AAA server might be down or overloaded.
Explanation No response has been received from the AAA server for the authorization requests. The AAA server may be inactive, or the load on the AAA server may be very high.
Recommended Action If the AAA server is down, restart the AAA server. If the load on the AAA server is high, configure the SSG authorization rate limit to be smaller than the currently-configured rate.
Error Message%SSG-2-SSG_TAL_SP_MAX : SSG TAL : Suspect users count reached maximum configured value. New suspect user entries will not be added to the TAL list
Explanation The number of suspect users is now greater than the configured value. This condition might signify that a a DoS attack is underway.
Recommended Action Check the network to see if any DoS attacks have been attempted. If you do not detect any problem, free the spurious user entries, or increase the configured limit for the maximum number of spurious users.
SSH Messages
The following are Secure Shell protocol messages.
Error Message%SSH-5-SSH2_CLOSE : SSH2 Session from [chars] (tty = [dec]) for user '[chars]' using crypto cipher '[chars]', hmac '[chars]' closed
Explanation Displays the SSH Session closure information.
Recommended Action No action is required.
Error Message%SSH-5-SSH2_SESSION : SSH2 Session request from [chars] (tty = [dec]) using crypto cipher '[chars]', hmac '[chars]' [chars]
Explanation Displays the SSH session request information.
Recommended Action No action is required.
Error Message%SSH-5-SSH2_USERAUTH : User '[chars]' authentication for SSH2 Session from [chars] (tty = [dec]) using crypto cipher '[chars]', hmac '[chars]' [chars]
Explanation Displays the SSH user authentication status information.
Recommended Action No action is required.
Error Message%SSH-5-SSH_CLOSE : SSH Session from [chars] (tty = [dec]) for user '[chars]' using crypto cipher '[chars]' closed
Explanation Displays the SSH Session closure information.
Recommended Action No action is required.
Error Message%SSH-5-SSH_SESSION : SSH Session request from [chars] (tty = [dec]) using crypto cipher '[chars]' [chars]
Explanation Displays the SSH session request information.
Recommended Action No action is required.
Error Message%SSH-5-SSH_USERAUTH : User '[chars]' authentication for SSH Session from [chars] (tty = [dec]) using crypto cipher '[chars]' [chars]
Explanation Displays the SSH user authentication status information.
Recommended Action No action is required.
SSRP Messages
The following are SONET/SDH based SRP Double Wide PCI port adapter driver messages.
Error Message%SSRP-1-INITFAIL : SRP([dec]/[dec]), initialization timeout failure
Explanation The SRP port adapter has failed to initialize.
Recommended Action Check the seating of the card and reseat the card, if required. 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%SSRP-3-OWNERR : SRP([dec]/[dec]), buffer ownership error, pak=[hex]
Explanation A software or hardware error has occurred. The SRP port adapter driver has 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%SSRP-2-TXERROR : SRP([dec]/[dec]), TX_ERROR Interrupt has occured. Error Register=[hex]
Explanation A fatal error has occurred in the Tx PCI.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support and test srp tx srp slot/port commands, with slot/port being the slot and port of the affected line card, 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, show tech-support, and test srp tx srp slot/port commands and your pertinent troubleshooting logs.
Error Message%SSRP-2-TXERRORCAUSE : SRP([dec]/[dec]), TX_ERROR Interrupt cause :[chars]
Explanation This message provides the cause of the fatal error that occurred in the Tx PCI.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support and test srp tx srp slot/port commands, with slot/port being the slot and port of the affected line card, 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, show tech-support, and test srp tx srp slot/port commands and your pertinent troubleshooting logs.
SSSMGR Messages
The following are Subscriber Service Switching (SSS) Manager messages.
Error Message%SSSMGR-3-NULL_INFO_STRING : Received a NULL info string value.
Explanation An internal SSS manager 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.
STORM_CONTROL Messages
The following are storm control messages.
Error Message%STORM_CONTROL-2-SHUTDOWN : Storm control shut down [chars]
Explanation Excessive traffic has been detected on a port that has been configured to be shut down if a storm event is detected.
Recommended Action Once the source of the packet storm has been fixed, reenable the port using the command for port configuration.
SWEPA Messages
The following are software encryption and key management messages.
Error Message%SWEPA-6-EPA_EXP_RUNNING : Exp Running ....
Explanation Unavailable.
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%SWEPA-6-EPA_EXP_TIMER_EXPIRED : Exp Timer Expired!
Explanation Unavailable.
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%SWEPA-6-FAILED_TO_ALLOCATE_ENCRYPT_QUE : Failed to allocate the encrypt queue.
Explanation Unavailable.
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%SWEPA-6-FAILED_TO_START_DES_PROCESS : Failed to start DES process
Explanation Unavailable.
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%SWEPA-6-FAILED_TO_START_EXP_PROCESS : Failed to start EXP process
Explanation Unavailable.
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%SWEPA-6-INIT_SW_EPA_IDB : Init swepa idb start ...
Explanation Unavailable.
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%SWEPA-6-START_DES_PROCESS : DES process start ...
Explanation Unavailable.
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%SWEPA-6-START_EXP_PROCESS : EXP process start ...
Explanation Unavailable.
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.
SWITCH_IF Messages
The following are Switch Interface subsystem messages.
Error Message%SWITCH_IF-3-CBCINITFAIL : CBC Initialization Failed
Explanation The CBC could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-5-CONFIGNOT : The Switch Control Interface is not configurable
Explanation The switch control interface is for system use only.
Recommended Action Do not attempt to configure the switch control interface.
Error Message%SWITCH_IF-4-CONFIG_WARN : Configuration warning on i/f [chars]. Reason: [chars]
Explanation An error in the configuration has occurred.
Recommended Action Verify the configuration on the indicated interface. Consult Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide for more details. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-5-DATAPATHINFO : [chars]
Explanation This message provide general information regarding the SWITCH_IF system.
Recommended Action No action is required.
Error Message%SWITCH_IF-3-ESYSFAIL : Portmaker ESYS failure, device [chars] command [chars]
Explanation A failure involving PortMaker ESYS 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%SWITCH_IF-3-FPGADWNLDFAIL : FPGA download failed: [chars]:
Explanation The firmware could not be downloaded to the FPGA.
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%SWITCH_IF-3-HUMVEESENDFAIL : Unable to send data to Humvee
Explanation A failure occurred while data was being sent to the fabric interface framer.
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%SWITCH_IF-3-INITFAIL : [chars] initialization failed
Explanation The device specified in the message text could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-3-INTERNAL : Switch Interface internal error, [chars] [chars] [dec]
Explanation An internal switch interface could not be initialized.
Recommended Action Enter the show ip interface brief command to determine the resources allocated and determine the error. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-3-INTERRUPT : Received interrupt from [chars] - OCTRAP register = [hex]
Explanation The RP has received an interrupt from the data path SAR. Relevant information has been collected in the SAR information file. The SAR has been reset to recover from this situation.
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%SWITCH_IF-5-LOGINFO : [chars]
Explanation This message provides the general status of the VC.
Recommended Action No action is required.
Error Message%SWITCH_IF-6-MPLS_PART : Bandwidths for MPLS partition (id=[dec]) have been adjusted
Explanation The minimum and maximum bandwidths are equally set in the MPLS partition.
Recommended Action No action is required.
Error Message%SWITCH_IF-3-NULLHWIDB : Hwidb ptr on the Sub-interface is NULL: [chars]
Explanation The hardware IDB is of a null value switch subinterface that is being configured.
Recommended Action Verify the configuration on the specified interface. Consult the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide for more details. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-3-NULLVCINFO : vc_info ptr is NULL in: [chars]
Explanation Configuration information for the ATM PVC cannot be found.
Recommended Action Verify the configuration on the specified interface. Consult the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide for more details. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-3-SAR_FATAL_SYSERR : [chars] fatal system error[chars], status [hex]
Explanation SAR fatal system error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SWITCH_IF-4-SAR_NONFATAL_SYSERR : [chars] non-fatal system error, status [hex]
Explanation There was a non-fatal SAR system error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SWITCH_IF-4-SAR_SB_ECCERR : [chars] single-bit ECC error, count [int], address [hex], syndrome [hex]
Explanation A SAR single-bit ECC error has occurred and has been corrected.
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 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%SWITCH_IF-3-SARCMDFAIL : SAR command failed, [chars], t/f: [dec], Id: [hex], cmd: [chars], status: [hex]
Explanation SAR command processing for the switch interface 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%SWITCH_IF-3-SARCMDTIMEOUT : SAR command timeout, device [chars], command [chars]
Explanation A SAR command could not be processed for the switch interface before the timeout period expired.
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%SWITCH_IF-3-SARCONFIGFAIL : Configuration of the [chars] failed ([dec])
Explanation An attempt at SAR configuration 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%SWITCH_IF-3-SARCONFIGFAIL : Configuration of the [chars] failed ([dec])
Explanation Configuration of the SAR 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%SWITCH_IF-3-SARDEVMISMATCH : [chars], device [chars], expected [hex] or [hex], actual [hex]
Explanation The system has detected a mismatch in SAR device versions.
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%SWITCH_IF-3-SARINITFAIL : SAR initialization failed, device [chars] [chars] stats [hex]
Explanation SAR initialization for the switch interface 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%SWITCH_IF-3-SARLOADFAIL : Loading the [chars] failed ([dec])
Explanation SAR could not be 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%SWITCH_IF-6-SARLOADOK : Loading [chars] with [chars]: [OK - [int] bytes]
Explanation SAR has been loaded successfully.
Recommended Action No action is required.
Error Message%SWITCH_IF-3-SARMISMATCH : [chars], device [chars], expected [hex], actual [hex]
Explanation A device or microcode mismatch has occurred in the SAR for the specified device.
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%SWITCH_IF-6-SARSIG : Signature returned for [chars]: [hex].[hex].[hex] Level [hex]
Explanation This message provides information regarding the SAR signature.
Recommended Action No action is required.
Error Message%SWITCH_IF-4-SARVCVPMISMATCH : SAR: VC, VP path info mismatch, handle [hex], vpi [int]
Explanation SAR information regarding a VC or VP path did not match the state that was expected.
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%SWITCH_IF-4-SUBIFNOSHUT : Sub-interface Switch1.[dec], changed state to up.
Explanation The subinterface specified in the message text has changed its administrative state to active (up).
Recommended Action If the subinterface was deliberately put into the administrative up state, then no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-4-SUBIFSHUT : Sub-interface Switch1.[dec], changed state to administratively down.
Explanation The subinterface specified in the message text has changed its administrative state to inactive (down).
Recommended Action If the subinterface was deliberately put into the administrative down state, then no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-3-SW_ERROR : [chars] [dec], [dec], [dec], [dec], [dec], [dec]
Explanation An error has occurred in the VC configuration.The SCR, PCR, or cell time might have been configured to a value of zero.
Recommended Action Verify the configuration on the specified interface. Consult the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide for more details. If you require further assistance, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SWITCH_IF-3-UDFCAMERR : UDF fields modification or CAM entry problems
Explanation An attempt to program the UDF fields and the CAM entries for a VPI and VCI combination 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%SWITCH_IF-4-UNSUP : Interface ([chars]): unsupported feature: [chars]
Explanation The specified feature is not supported by RPM-XF. The feature is not supported by the current 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.