-
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
RPM_CONN_MGMT Messages
The following are RPM Connection Management-related messages.
Error Message%RPM_CONN_MGMT-6-CONN_STATUS : Number of connections in inSynch: [dec], failed: [dec], timed out: [dec], mismatch: [dec], Only on RPM: [dec], Not on RPM: [dec]
Explanation This message provides information on the synchronization status of all the switch connections that are configured on the system.
Recommended Action No action is required.
Error Message%RPM_CONN_MGMT-4-MASTERSHIP : Cannot modify the mastership on the connection with vpi/vci: [dec]/[dec]
Explanation An attempt to reconfigure the active or standby switch connection has failed.
Recommended Action Delete the existing switch connection and reconfigure it as either an active or a standby switch connection.
Error Message%RPM_CONN_MGMT-4-NO_ATMPVP : Failed to add a switched virtual path connection with vpi:[dec]
Explanation PVP has not been configured. A VPC must be configured before the switched PVP connection can be configured.
Recommended Action Before configuring the switched PVP connection, create a PVP by entering the atm pvp vpi command in interface configuration mode, with vpi being the ATM network virtual path identifier of the VC to multiplex on the permanent virtual path.
Error Message%RPM_CONN_MGMT-3-NO_MEM : Failed to add connection with vpi/vci: [dec]/[dec]
Explanation System memory has been exhausted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPM_CONN_MGMT-4-NO_VPIVCI : Failed to add connection with vpi/vci: [dec]/[dec]
Explanation There is no PVC configuration. Before configuring the switch connection, a PVC is required for the subinterface.
Recommended Action Create a PVC using the pvc vpi/vci command in interface or subinterface configuration mode, with vpi/vci being the virtual path identifier and virtual channel identifier, on the switch interface.
Error Message%RPM_CONN_MGMT-4-OUTOFRSRCPART : Configured swconn with vpi/vci: [dec]/[dec] is out of resource partition
Explanation The VPI and VCI pair that was used to configure the switch connection is not within the VPI and VCI range that is configured on the resource partition.
Recommended Action Either choose the VPI and VCI pair to create a connection from the RSRC range that has been configured on the switch partition or modify the VPI and VCI range on the switch partition.
Error Message%RPM_CONN_MGMT-4-REMATMADDR : Cannot change the remote atm address of the existing swconn withvpi/vci: [dec]/[dec]
Explanation An attempt was made to change the remote ATM address that is configured on an existing switch connection. This operation is not allowed.
Recommended Action Delete the existing switch connection and reconfigure the switch connection with the desired remote ATM address.
RPMXF Messages
The following are Route Processor Module, express forwarding (RPM-XF) card level messages.
Error Message%RPMXF-6-ACTIVATED : card in slot [dec] enabled.
Explanation The card is being activated.
Recommended Action No action is required.
Error Message%RPMXF-2-BADINTERFACE : Out of range Card interface, [dec] on slot [dec]
Explanation The software has specified a card interface that is not within the specified range.
Recommended Action Check the product user guide and software specifications for the valid interface range. 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%RPMXF-2-BADRSRCNUM : Invalid resource number from PXF ([dec]). (PLEASE REPORT THIS!)
Explanation The PXF hardware diversion path has specified an invalid resource number.
Recommended Action Enter the show ip interface brief command to identify the resource that was allocated and attempt to determine the cause of 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%RPMXF-2-BADSLOT : Out of range card slot index[dec]
Explanation The Cisco IOS software detected an out-of-range card slot index.
Recommended Action Check to see if the line card is inserted in the correct slot. 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%RPMXF-3-CARD_SLOT_MISMATCH : Card type [hex] not allowed in slot [dec]/[dec].
Explanation The card type in the specified slot is not supported.
Recommended Action Remove the card from the slot. 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%RPMXF-3-CONFIG : Recommended port adapter configuration exceeded
Explanation The total bandwidth of fast- and medium-bandwidth port adapters has exceeded the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed high- and medium-bandwidth port adapters for the system.
Error Message%RPMXF-4-COOKIE : Corrupt or missing MAC address cookie using random base [enet]
Explanation The contents of the MAC address EEPROM are invalid. The system is providing random MAC addresses.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF-3-DEACTIVATED : card in slot [dec] disabled.
Explanation The card is being deactivated.
Recommended Action If the deactivation was requested by the user, no action is required. If the deactivation was not requested by the user, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF-2-INITFAIL : Platform initialization failure: [chars]
Explanation A failure has occurred during initialization of the platform. This condition will likely result in the platform failing to boot correctly.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF-3-INTERNAL : RPM-XF internal software error, [chars]
Explanation An internal software error involving RPM-XF 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%RPMXF-3-IPC : [chars]: IPC Failure
Explanation An Interprocess Communication process failure has occurred.
Recommended Action Enter the show ipc ports, show ipc stats, and show ipc seats commands to attempt to determine the location of the errors. 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, show tech-support, show ipc ports, show ipc stats, and show ipc seats commands and your pertinent troubleshooting logs.
Error Message%RPMXF-3-NOACK : Access to [chars] temperature sensor failed
Explanation An attempt to access the chassis temperature sensor has failed. This internal error indicates that a component in the system could not be accessed and generally indicates a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from EEPROM. This condition is probably caused by a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF-3-NOMAC : System was not able to allocate MAC address for interface [int]/[int]
Explanation A MAC address could not be allocated because of an incorrect slot and port combination. This combination exceeds the maximum number of available hardware ports and slots.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF-3-NOMEM : OUT of Memory: [chars]
Explanation Memory could not be allocated during system initialization.
Recommended Action A reboot may be necessary. 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%RPMXF-3-PCIERR : RPM-XF pci error, [chars]
Explanation An internal RPMXF 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%RPMXF-2-PROCFAILED : Unable to create system process, [chars]
Explanation An internal software error involving RPM-XF 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%RPMXF-4-STR_TRUNCATED : [chars] too long: Truncated to [int] characters
Explanation The Cisco IOS software image version or bootloader version cannot be displayed in its entirety and has been truncated.
Recommended Action Enter the show version command to view the entire Cisco IOS software image version or bootloader version.
Error Message%RPMXF-6-SWIFCLR : Clear interface done on interface Switch1
Explanation The clear interface command has been entered on the Switch1 interface.
Recommended Action No action is required.
Error Message%RPMXF-4-TEST : Test command no. [dec] executed by user.
Explanation A test command has been entered.
Recommended Action No action is required.
Error Message%RPMXF-3-UNEXP_INTR : Interrupt [chars] not expected, masking off
Explanation An interrupt was signaled, but the interrupt handler for this type of interrupt has not yet been installed. This problem should be self-correcting but indicates either a hardware or a software problem. If the problem is caused by a hardware error, further problems are to be expected. If the problem is caused by a software error, certain types of error and alarm conditions may be undetected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show registry rpmxf 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, show tech-support, and show registry rpmxf commands and your pertinent troubleshooting logs.
RPMXFEVENTMGR Messages
The following are Route Processor Module, express forwarding (RPM-XF) event manager messages.
Error Message%RPMXFEVENTMGR-1-CRITICAL_FAULT : [chars], Restarting IOS
Explanation A critical error involving the Cobalt ASIC has occurred. The system is performing a crash dump.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-IRONBUS_FAILURE : [chars], Restart of Ironbus Failed([hex]) - timing out. Resetting line card.
Explanation The Ironbus component could not restart in the allocated time.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-IRONBUS_FAULT : [chars], Restarting Ironbus
Explanation A fault involving the Ironbus component has occurred. Ironbus is being restarted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-IRONBUS_REOCCURRING : [chars], Resetting line card.
Explanation A fault involving the Ironbus component has reoccurred. The line card must be reset.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-IRONBUS_SUCCESS : [chars], Restart Successful
Explanation A fault involving the Ironbus component has occurred. Even though Ironbus was restarted successfully, data connectivity has been lost.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-MAJOR_FAULT : [chars], Restarting PXF
Explanation A major error involving the Cobalt ASIC has occurred. The PXF complex is being restarted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-MINOR_FAULT : [chars]
Explanation The threshold for a minor event has been reached.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-1-MINOR_REOCCURRING : [chars]
Explanation A minor fault has reoccurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-4-PXF_CRASHINFO : Writing PXF debug information to [chars].
Explanation A file containing information useful to diagnose a PXF restart is being written.
Recommended Action Save the "pxf_crashinfo" file. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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 contents of the "pxf_crashinfo" file, and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-3-PXF_CRASHINFO_FAIL : Failed to write PXF debug information.
Explanation PXF debugging information could not be written to the target device. The device on which the write operation was attempted is likely out of free space, or the write operation has encountered some other error.
Recommended Action Enter the show bootflash: command to determine the amount of free space that is available on the device. 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%RPMXFEVENTMGR-4-SAR_CRASHINFO : Writing SAR debug information to [chars].
Explanation The system is saving information that will be useful to diagnose the cause of the SAR restart error.
Recommended Action Wait for the system to save the crash information file. After it has completed, save the crash information file and open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-3-SAR_CRASHINFO_FAIL : Failed to write SAR debug information.
Explanation SAR debugging information could not be written to the target device.
Recommended Action Enter the show bootflash: command to see if there is enough free space to save the debugging information to the target device. 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%RPMXFEVENTMGR-4-SAR_RESETINFO : Writing SAR debug information to [chars].
Explanation A file containing information useful for diagnosing a SAR restart is being written.
Recommended Action Save the "sar_info" file. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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 contents of the "sar_info" file, and your pertinent troubleshooting logs.
Error Message%RPMXFEVENTMGR-3-SAR_RESETINFO_FAIL : Failed to write SAR debug information.
Explanation SAR debugging information could not be written to the target device. The device on which the write operation was attempted is likely out of free space, or the write operation has encountered some other error.
Recommended Action Enter the show bootflash: command to determine the amount of free space that is available on the device. 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%RPMXFEVENTMGR-1-SBE_DEBUG : Address: [hex], Who: [hex], Data With ECC: [hex] [hex] [hex] [hex], Data w/o ECC: [hex] [hex] [hex] [hex]
Explanation This message provides debug data for single-bit correctable errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPMXF_QOS_GENERAL Messages
The following are Route Processor Module, express forwarding (RPM-XF) Quality of Service (QoS) messages.
Error Message%RPMXF_QOS_GENERAL-3-ERSHAPE : Traffic shape not allowed with sar_based_cbwfq.Installation of policy [chars] failed on interface [chars]
Explanation A policy map could not be attached.
Recommended Action No action is required.
Error Message%RPMXF_QOS_GENERAL-4-NOTEVENT : Interface bandwidth should be atleast 8000 bps for policing to happen. Skipping police parameter update on interface: [chars]
Explanation The RPMXF Toaster requires the bandwidth of the interface to be at least 8 kbps for policing to happen. However, because of dynamic bandwidth feedback, the interface bandwidth can be adjusted to 4 kbps.
Recommended Action No action is required.
RPMXF_QUEUE_CFG_STR Messages
The following are Route Processor Module, express forwarding (RPM-XF) queuing configuration messages.
Error Message%RPMXF_QUEUE_CFG_STR-3-EREVENT : [chars] [chars]
Explanation This message is a general error condition used for sanity tests.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RPMXF_TOASTER Messages
The following are Route Processor Module, express forwarding (RPM-XF) queuing configuration messages.
Error Message%RPMXF_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 is operational. The time elapsed is measured from the time that the %RPMXF_TOASTER-5-DNLD_START message was received. This situation is a normal system activity when the Cisco IOS software is being booted or after a fatal PXF error has occurred.
Recommended Action No action is required.
Error Message%RPMXF_TOASTER-5-DNLD_START : Downloading PXF Microcode [chars], version=[chars], [chars]
Explanation The platform code is starting to download the PXF microcode image. This situation is a normal system activity when the Cisco IOS software is being booted or after a fatal PXF error has occurred.
Recommended Action No action is required.
Error Message%RPMXF_TOASTER-2-DOWNLOAD : [chars]: PXF microcode image [chars]: could not be downloaded.
Explanation The PXF microcode could not be downloaded. This condition could be caused by a corrupted image or 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%RPMXF_TOASTER-2-DWNLOAD : Could not download the PXF microcode into PXF processor @ column [dec] row [dec].
Explanation Microcode could not be downloaded to the PXF processor. This condition could be caused by either a hardware or software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF_TOASTER-2-HDRCORRUPT : PXF microcode header of image [chars] has been corrupted, expected [hex], got [hex].
Explanation The PXF microcode appears to be corrupted. This condition could be caused by a 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%RPMXF_TOASTER-2-IMAGE : PXF microcode image [chars]: could not be read.
Explanation The PXF microcode could not be read. This condition could be caused by a 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%RPMXF_TOASTER-2-INCOMPAT : This PXF microcode image is incompatible with this Cisco IOS image.
Explanation The signature in the 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%RPMXF_TOASTER-2-METADATA : PXF microcode meta-data [chars]: [chars], in file: [chars].
Explanation The PXF microcode appears to have been corrupted. This condition could be caused by a 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%RPMXF_TOASTER-2-OPER : PXF not operational: [chars]
Explanation The PXF clients could not be made operational. This condition could be due to either a software or a hardware problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF_TOASTER-5-REDNLD : PXF download requested during PXF download
Explanation A PXF restart and download operation was requested while the previous download was still in progress. This condition is typically caused by an exception while the restart operation was being performed. Another restart and download operation will be started as soon as the current one is complete.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPMXF_TOASTER-2-ROW : PXF microcode header of image [chars] doesn't match block [chars], row [dec] not row [dec].
Explanation The PXF microcode appears to have been corrupted. This condition could be caused by a 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%RPMXF_TOASTER-2-START : PXF not started: memory state: [dec], expected [dec].
Explanation The PXF clients could not be started. This condition could be due to either 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%RPMXF_TOASTER-2-TDB : Could not find control block for PXF image [chars].
Explanation A software error occurred that prevented the control block representing this PXF 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.
RSCMSM Messages
The following are Resource Measurement messages.
Error Message%RSCMSM-3-NO_LIST_CREATED : [chars]: Cannot create interface-based rsc list.
Explanation An error occurred during the "list create" operation.
Recommended Action Check available system memory.
Error Message%RSCMSM-3-NO_SUCH_INTERFACE : [chars]: The interface doesn't exist
Explanation The interface for resource measurement does not exist at during the time that the operation was requested.
Recommended Action Check the configuration to ensure that the interface is present.
Error Message%RSCMSM-5-TEST_ALREADY_RUNNING : One test is already running.
Explanation A test is already running while another test was requested.
Recommended Action Wait for the currently running test to complete before starting another test.
RS_TDM Messages
The following are router shelf time-division multiplexing (TDM) messages.
Error Message%RS_TDM-3-TDM_BP_INIT_FAILED : Initialisation of the Backplane object failed; TDM function partially or fully inhibited
Explanation Initialization of the software that controls the TDM backplane has failed. The TDM subsystem can function only partially, if at all.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RS_TDM-3-TDM_FB_INIT_FAILED : TDM-specific initialisation of the [chars] FB in slot [dec] failed
Explanation Initialization of TDM-related hardware or software on the indicated FB has failed. The FB is unusable.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RSC Messages
The following are route switch controller (RSC) messages.
Error Message%RSC-6-CPU_LATENCY_REPORT : CPU latency for [chars] priority process is [dec] msec. The latency report threshold is set at [dec] msec.
Explanation The CPU latency has exceeded the maximum allowed value. CPU latency is determined by calculating how much time it takes for a process to be rescheduled at a specified priority level. If the CPU latency test does not recover, (the CPU latency does not drop below the threshold value), a process at the priority level specified in the error message might be slow to respond to requests.
Recommended Action This is a report message only. No action is required. The CPU latency test threshold may be fine tuned by changing the "cpu-latency [priority]-latency-threshold" value in diagnostic-monitor configuration mode.
Error Message%RSC-6-CPU_UTILISATION_REPORT : Process '[chars]' with assigned PID=[dec] utilised [dec].[dec]% worth of CPU in the last 5 seconds. The CPU utilisation report threshold is set at [dec]%.
Explanation The indicated processes have exceeded the maximum allowed CPU utilization level during the last five seconds. If the CPU utilization test does not recover (the CPU utilization value does not drop below the threshold value), a process might be consuming excessive CPU, especially if a CPU latency is reported at the same process priority level as the process specified in the error message.
Recommended Action This is an informational message only. No action is required. The CPU utilization test threshold can be fine tuned by changing the cpu-utilization-threshold value in the diagnostic-monitor configuration mode.
Error Message%RSC-4-DATADESCR_DECODE_ERROR : Failed to find [chars] corresponding to if_index [dec]
Explanation Data descriptors are used to compactly encode an interface index for transfer to another RSC. An interface corresponding to the if_index was not found on the standby RSC. The HA synchronization will fail for that interface.
Recommended Action This is a debug message only. No action is required.
Error Message%RSC-3-FB_MIL_PATH_PING_INTERNAL_ERROR : Feature board MIL path ping test internal error: [chars]
Explanation The RSC-to-feature-board path-test through the MIL layer has an internal software error. Common software errors that cause this condition are as follows:
–
The internal process received an unexpected major event.
–
–
–
The Diagnostic monitor cannot detect MIL path-related errors until this condition is corrected.
Recommended Action If the test does not recover within the next few scheduled tests, reload the RSC reporting the error during the nearest convenient maintenance window. If this error 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%RSC-3-FB_MIL_PATH_PING_NO_RSP : RSC did not receive a ping response from the feature board in slot [dec] through the MIL layer.
Explanation The feature board is not responding to the ping test from the RSC through the MIL. The RSC might not be able to communicate with the feature board.
Recommended Action If the test does not recover within the next few scheduled tests, reload the feature board reported in the error to reestablish communications with the RSC. If the error recurs, replace the feature board with a spare. If this error 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%RSC-3-FB_MIL_PATH_PING_NO_XMIT : RSC cannot ping the feature board in slot [dec] through the MIL layer.
Explanation The RSC cannot transmit a ping packet from the RSC to the feature board in the specified slot through the MIL. The RSC might not be able to communicate with the feature board.
Recommended Action If the test does not recover within the next few scheduled tests, reload the feature board reported in the error to reestablish communication with the RSC. If the error recurs, replace the feature board with a spare. If this error 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%RSC-3-FPGA_INCORRECT_ID : IO FPGA version [hex] is incorrect (expected [hex] or higher)
Explanation The I/O FPGA has an incorrect hardware version. The I/O FPGA hardware could be faulty, or the RSC could have a wrong hardware version for the I/O FPGA.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC-2-MAC_ADDRESS_PORT_ERROR : Port number ([dec]) out of range for interface [chars]
Explanation The port number is not valid for generating a MAC address.
Recommended Action Specify port numbers that are within the allowed range.
Error Message%RSC-2-ROMMON_MEMSIZE_INVALID : Memory size [dec]K read from ROMMON is different from IOS total memory region size [dec]K
Explanation The RSC ROMmon has a possible read error. The system could malfunction because of an unreliable data read from ROMmon. The system might not function properly the next time the RSC reloads.
Recommended Action During the nearest convenient maintenance window, reload the RSC reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC-3-SWITCH_FAB_ID_FAILED : MMC switching fabric [dec] version cannot be checked.
Explanation The MMC switching fabric for the NP5400 version check has failed. The switching fabric could be faulty, or the wrong hardware version could be incorrect.
Recommended Action During the nearest convenient maintenance window, reload the RSC reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC-3-TEST_PROCESS_ERROR : Process '[chars]' has encountered an internal error: [chars]
Explanation An internal software error has occurred for the process specified in the error message. Common software errors that cause this condition are as follows:
–
–
–
–
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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.
RSC_CF Messages
The following are Compact Flash messages.
Error Message%RSC_CF-3-IOSDIAGS_OP_FAILED : Compact Flash function [chars] failed using path = [chars]
Explanation The specified compact flash function failed during the Cisco IOS diagnostic test. The disk might be faulty.
Recommended Action Remove and reinsert the compact flash disk. If the error persists, replace the compact flash disk.
RSC_FPFE_IOSDIAGS Messages
The following are route switch controller (RSC) front panel Fast Ethernet (FPFE) IOS diagnostic messages.
Error Message%RSC_FPFE_IOSDIAGS-3-STUCK_IN_LOOPBACK : Cannot restore FPFE Control/Config registers after loopback test.
Explanation The front panel FE control or configuration registers are set in loopback mode and cannot be restored to the previous values. The front panel FE control could be faulty. The system cannot use the front panel FE interface for any communication until the error is corrected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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.
RSC_MBUS Messages
The following are MBus messages on RSC.
Error Message%RSC_MBUS-3-EEPROM_DATA_INVALID : EEPROM diagnostics test failed to validate EEPROM data in slot [dec] (read [hex]; expected [hex])
Explanation The system was unable to validate data from the RSC MBus EEPROM. The system might not function as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_MBUS-3-EEPROM_READ_FAILED : EEPROM diagnostics test failed to read EEPROM data at offset [hex] in slot [dec]
Explanation The system was unable to read data from the RSC MBus EEPROM. The system might not function as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_MBUS-3-INVALID_SLOT : No MBUS structrue found for slot [dec]
Explanation The system could not find an internal MBus data structure for the referenced slot. Either the slot number is out of range or the structures have not been 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%RSC_MBUS-4-LOCK_CANCEL : Canceled download lock request for slot [dec] not matched to lock request
Explanation A mismatched cancel request can lead to the client's not being notified of the cancel acknowledgment. This condition can prevent that client or others from downloading code to the slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RSC_MBUS-4-LOCK_OUTSTANDING : Lock granted to slot [dec], but already have an existing grant for slot [dec]
Explanation The peer RSC granted a download lock while a grant was already in effect. This condition could prevent a grant from being made and a slot from being booted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RSC_MBUS-4-LOCK_RECONCILE : Lock reconcile failed for slot [dec], lock is already granted to slot [dec]
Explanation The specified RSC has just come up and owns the lock. The peer RSC held the previous lock. The peer RSC has an existing download lock outstanding that needs to be reconciled. However, the lock is already allocated elsewhere, causing two downloads to proceed. This condition can lead to download failures on one or both of these RSCs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RSC_MBUS-3-NO_EVENT : No more events on free queue, event discarded
Explanation The free queue is empty. The state machine that initializes the MBus agents on each card uses an event queue. If this queue exhausts all free events, messages cannot be sent to the state machine. This error condition can prevent the MBus agent for the card in question from being initialized and running the appropriate firmware. Running old firmware can cause loss of function and spurious errors because the MBus agent is not running from RAM and therefore is slower.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RSC_MBUS-3-NO_QUEUE : Could not create event queue.
Explanation The system could not create or initialize the event queue, or the events on that queue, for the RSC MBus agent state machine. The system cannot download new MBus firmware to the cards. Running old firmware can cause loss of function and spurious errors because the MBus agent is not running from RAM and therefore is slower.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RSC_PIF_IOSDIAGS Messages
The following messages are for Cisco IOS diagnostic test error conditions in RSC processors.
Error Message%RSC_PIF_IOSDIAGS-3-GMAC_READ_ERROR : [chars] failed to read from [chars] (addr [hex])
Explanation Gigabit Ethernet GMAC failed to read a value from the specified address register. Gigabit Ethernet GMAC hardware could be faulty. The corresponding Gigabit Ethernet interface might not be operating as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_PIF_IOSDIAGS-3-GMAC_RW_ERROR : [chars] data invalid at [chars] (addr [hex]) writing [hex] but actually read [hex]
Explanation The Gigabit Ethernet GMAC failed to validate a test value after writing to the specified address register. The corresponding Gigabit Ethernet interface might not be operating as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_PIF_IOSDIAGS-3-GMAC_WRITE_ERROR : [chars] failed to write at [chars] (addr [hex]) with value [hex]
Explanation The Gigabit Ethernet GMAC failed to write a value at the specified address register. The Gigabit Ethernet GMAC hardware could be faulty. The corresponding Gigabit Ethernet interface might not be operating as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_PIF_IOSDIAGS-3-IMEM_READ_ERROR : PIF [dec] [chars] failed to read data from PIF Internal Memory address [hex]
Explanation The specified PIF could not read data from the PIF internal memory address. The PIF internal memory might be faulty. Traffic flow on the port could be disrupted.
Recommended Action If the test does not recover within the next few scheduled tests, reload the RSC reported in the error. If this error 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%RSC_PIF_IOSDIAGS-3-MMC_INVALID : MMC switching fabric [dec] is not valid
Explanation The specified MMC switching fabric is invalid. The software might be faulty. The specified fabric might not switch traffic.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_PIF_IOSDIAGS-3-MMC_PORT_READ_FAIL : MMC switching fabric [dec] failed to read data from port [dec] [chars] reg [hex]
Explanation The MMC switching fabric in the specified slot failed to read data from the specified register in the specified port. The port connected to the switching fabric might be faulty. Traffic flow on the port can be disrupted.
Recommended Action If the test does not recover within the next few scheduled tests, reload the RSC that is reporting in the error. If this error 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%RSC_PIF_IOSDIAGS-3-PHY_READ_ERROR : PIF [dec] [chars] failed to read data from port [dec] PHY [dec] Reg [dec]
Explanation The specified PIF PHY could not read data from the specified port. The PIF PHY hardware could be faulty. Traffic flow on the port could be disrupted.
Recommended Action If the test does not recover within the next few scheduled tests, reload the RSC that is reporting in the error. If this error 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%RSC_PIF_IOSDIAGS-3-PHY_WRITE_ERROR : PIF [dec] [chars] failed to write data to port [dec] PHY [dec] Reg [dec]
Explanation The specified PIF PHY could not write data to the specified PIF PHY register. The PIF PHY hardware could be faulty. Traffic flow on the port could be disrupted.
Recommended Action If the test does not recover within the next few scheduled tests, reload the RSC that is reporting in the error. If this error 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%RSC_PIF_IOSDIAGS-3-PIF_IDB_ERROR : PIF [dec] HWIDB not valid
Explanation No valid PIF HWIDB is available to read the PIF PHY register because of possible software corruption. The specified port is not available to handle any communication.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error persists, If the test does not recover within the next few scheduled tests, reload the RSC that is reporting in the error. If this error 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%RSC_PIF_IOSDIAGS-2-PIF_PC_LOCKED : [chars] is now locked at [hex]
Explanation XPIF PC is locked at an address that is not idle. Traffic flow on the port is stopping.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_PIF_IOSDIAGS-3-PIF_PORT_NON_EXISTS : MMC [dec] PIF [dec]'s first switch local port does not exist
Explanation The specified MMC switching fabric is missing a local port. Software might be corrupted. Traffic flow on the port could be disrupted.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%RSC_PIF_IOSDIAGS-3-PIF_VER_WRONG : MMC switching fabric [dec] port [dec] [chars] has an unexpected version [dec] (expected version between [dec] and [dec])
Explanation The specified port connected to the specified MMC switching fabric has an unexpected PIF version. The port has either the wrong version or faulty hardware. Traffic flow on the port could be disrupted.
Recommended Action If the test does not recover within the next few scheduled tests, reload the RSC that is reporting in the error. If this error 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%RSC_PIF_IOSDIAGS-3-WRONG_PIF : MMC switching [dec] PIF [dec] is not an [chars]
Explanation The PIF port type is incorrect. The software might be corrupted. Traffic flow on the port could be disrupted.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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.
RSCPB Messages
The following are RSC Push Button handling messages.
Error Message%RSCPB-5-START_TDMC : Start TDM Clocking selected from front panel
Explanation The STRT TDMC (Start TDM Clocking) function was selected using the front panel. TDM clocking on this RSC is starting.
Recommended Action No action is required.
Error Message%RSCPB-5-STOP_TDMC : Stop TDM Clocking selected from front panel
Explanation The STOP TDMC (Stop TDM Clocking) function was selected using the front panel. TDM clocking on this RSC is stopping.
Recommended Action No action is required.
Error Message%RSCPB-5-STOP_TDMC_REJECTED : Stop TDM Clocking selected from front panel; rejected because no peer exists to take over
Explanation The STOP TDMC (Stop TDM Clocking) function was selected using the front panel. However, TDM Clocking on this RSC cannot be stopped because there is no peer RSC present that can take over the TDM clock mastership role. As a result, the command has been rejected.
Recommended Action No action is required.
RSP Messages
The following are Route Switch Processor (RSP) messages.
Error Message%RSP-2-BADCACHE : Overrun detected.\n Buffer ptr addr : [hex]\n End of MEMD buffer : [hex]\n Start of datagram : [hex]\n End of datagram : [hex]\n bufhdr [hex]: [hex] [hex] [hex] [hex]\n Flushing Processor Cache
Explanation A packet was processed that was greater in size than the maximum possible MTU size, or an illegal buffer header data area was found.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RSP-4-EMPTY_VIPBAYS : VIP in slot [dec] was empty and was disabled
Explanation The VIP in the specified slot does not contain any port adapters. Because this configuration is unsupported, the VIP has been disabled.
Recommended Action Remove the VIP and reinsert it with one or more port adapters in its bay or bays.
Error Message%RSP-3-PROCCREATEFAIL : Failed to create [chars] process
Explanation The RSP failed to create a process that is necessary for proper functioning of the RSP. If the process displayed is the "LC stats update" process, you might not see the input and output rate and bytes being incremented in the output of the show interface command for VIP nonchannelized interfaces; however, the statistics can still be obtained by entering the show interfaces accounting or show interface stats command. If the process displayed is the "RSP Background" process, this message indicates that the system could be very unstable.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RSP-6-TXSTUCK : Txacc of Interface [chars] is at [dec]% of its txlimit
Explanation The specified interface has a low value for the transmit queue accumulator (txacc). This might be a transient condition and harmless if it occurs during periods of high packet traffic. If it occurs more than once in periods of relatively moderate traffic, it could indicate a problem with the system. Distributed packet switching might be disrupted as a result of this condition. If the message recurs during periods of relatively moderate traffic, this might indicate a disruption in distributed packet switching.
Recommended Action If a disruption in packet switching occurs, enter the microcode reload command to recover. Open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
RTT Messages
The following are round-trip time monitor messages.
Error Message%RTT-4-SAACLOCKNOTSET : RTR Probe(s) could not be scheduled because clock is not set.
Explanation One or more RTR probes could not be scheduled because the system clock has not been set.
Recommended Action Ensure that the system clock is functional by using the Network Time Protocol feature or another mechanism.
Error Message%RTT-3-SAAINITIALIZEFAIL : RTR: Failed to initialize, SAA functionality will not work
Explanation The RTR failed to initialize. This condition is caused by either a timer wheel process that could not be initialized or a process that could not be created. A likely cause of this condition is that sufficient memory is not available to complete the task.
Recommended Action Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-3-SAANEGATIVEVALUE : RTR([dec]): Negative Value for [chars]
Explanation RTR statistics generated an error 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%RTT-3-SAAPROBENOTFOUND : RTR: Error deleting the probe
Explanation The system attempted to delete a probe that does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RTT-3-SAARESPTWINITFAIL : IP SLA Monitor responder initialzation failed
Explanation The IP SLA Monitor responder initialization failed to initialize the timer wheel. Because of this failure the IP SLA Monitor probes on other routers, for which this router acts as responder, will not work.
Recommended Action Contact your Cisco technical support representative.
Error Message%RTT-4-SAASCHEDCONFIGFAIL : RTR Probe [dec]: [chars]
Explanation The RTR probe could not be scheduled. Either the configured starting time has already occurred, or the starting time is invalid.
Recommended Action Reschedule the failed probe with a valid start time.
Error Message%RTT-3-SAATHRESHOLD : RTR([dec]): Threshold [chars] for [chars]
Explanation This informational message logs threshold violations in the Service Assurance Agent probes. This messages appears when the rtr logging trap command is entered
Recommended Action If this message is not required, enter the no rtr logging trap command to disable logging. Otherwise, no action is required
Error Message%RTT-3-SAATWINITFAIL : RTR: Generic Timer wheel timer functionality failed to initialize
Explanation The RTR could not initialize the timer wheel.
Recommended Action Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
RW_TOO_LONG Messages
The following are Windstar MPLS rewrite messages.
Error Message%RW_TOO_LONG-3-WSEVENT : [chars] [dec] [chars]
Explanation The PXF MPLS rewrite operation for the Cisco 7300 platform is taking longer than expected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SBETH Messages
The following are MAC controller messages.
Error Message%SBETH-3-BAD_GBIC_EEPROM : [chars] - GBIC contains a bad EEPROM
Explanation The interface contains a GBIC with an invalid EEPROM. This condition causes the link to become inactive.
Recommended Action Ensure that the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or from a supported vendor.
Error Message%SBETH-1-IOSDIAGS_READ_ERROR : MAC Read to the [chars] has failed,expected = [hex] read = [hex]
Explanation The SiByte MAC register read test has failed to read the expected data from the specified register. The system might not operate as expected.
Recommended Action During the next convenient maintenance window, reload the RSC that is reporting the error. If the error recurs, replace the RSC with a spare. If this error 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%SBETH-6-SFP_IN : Interface [chars] [chars] SFP has been inserted.
Explanation An SFP has been inserted.
Recommended Action No action is required.
Error Message%SBETH-6-SFP_OUT : Interface [chars] SFP has been removed.
Explanation An SFP has been removed.
Recommended Action No action is required.
Error Message%SBETH-3-UNKNOWN_GBIC : [chars] - Unknown GBIC type
Explanation The interface contains a GBIC of an unknown type. This condition causes the link to become inactive.
Recommended Action Ensure that the GBIC type is compatible with the interface. Verify that the GBIC was obtained from Cisco or from a supported vendor.
SBFIFO Messages
The following are packet first-in, first-out (FIFO) MAC controller messages.
Error Message%SBFIFO-1-BAD_IDB : Allocation of an Interface Descriptor Block failed
Explanation The packet FIFO MAC driver failed to obtain an IDB for the packet FIFO MAC interface. This condition indicates 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%SBFIFO-1-BAD_POOL : Could not initialize [chars]
Explanation The packet FIFO MAC driver failed to obtain a pool of buffers from the Cisco IOS software. This condition indicates 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%SBFIFO-1-BAD_STRUCT : Could not allocate memory for [chars]
Explanation The packet FIFO MAC driver failed to allocate memory for the specified component. This condition indicates 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%SBFIFO-3-ERRINT : [chars], error interrupt, mac_status = [hex]
Explanation The packet FIFO MAC controller has signaled an error 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%SBFIFO-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The packet FIFO MAC port failed to initialize because of insufficient memory. This condition most likely indicates a software problem.
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%SBFIFO-3-NOINT : Packet FIFO interface not created
Explanation A packet FIFO interface could not be created.
Recommended Action Gather previous messages sent to the console, They should contain the exact reason for the failure. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SBFIFO-3-TOOBIG : [chars], packet too big ([dec])
Explanation The packet FIFO interface has detected a packet that was larger than the predefined MTU. This condition most likely indicates 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.
SCCP Messages
The following are Signaling connection control part messages.
Error Message%SCCP-3-ERROR : [chars]
Explanation An internal error involving the SCCP facility 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%SCCP-6-INFO : [chars]
Explanation This is an informational message involving the SCCP facility.
Recommended Action No action is required.
Error Message%SCCP-5-NOTICE : [chars]
Explanation This is a notice-level message involving the SCCP facility.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCCP-4-WARNING : [chars]
Explanation This is a warning-level message involving the SCCP facility.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SCHED Messages
The following are scheduler messages.
Error Message%SCHED-0-ISRWATCHDOG : Interrupt of level [dec] running for a long time.[chars]
Explanation The indicated interrupt service routine ran for more than 2 minutes without handing over control of the system. This condition caused the system to reset.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the stack trace, output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCHED-3-SEMLOCKED : [chars] attempted to lock a semaphore, already locked by itself
Explanation Some sections of code use semaphores to protect critical sections of software. This message indicates that an attempt was made to lock a semaphore that was already locked.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the stack trace, output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SCHED-0-WATCHDOG : Scheduler running for a long time, more than the maximum configured ([dec]) secs.[chars]
Explanation The scheduler was running for a long time and has caused the system to reset.
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.
SCP Messages
The following are System Control Protocol messages.
Error Message%SCP-3-BADVLAN : Rx'd VLAN [dec] (opcode [hex]) from the NMP which is not configured.
Explanation The NMP sent a configuration command for an unconfigured VLAN interface.
Recommended Action Configure the VLAN interface.
Error Message%SCP-4-DACK_TIMEOUT_MSG : SCP delivery ack timeout for opcode=[hex]
Explanation The RP didn't receive SCP delivery ACKs from the SP, even after 2 retries.
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.
Error Message%SCP-4-GET_PAK_MSG : Failed for message size=[dec]
Explanation The system is out of pak type buffers of the required size.
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.
Error Message%SCP-2-NOMEM : No memory available for [chars]
Explanation The SCP protocol subsystem could not obtain the memory it needed.
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.
Error Message%SCP-3-NOPROC : Cannot create SCP process.
Explanation There are insufficient internal resources available to create a queue.
Recommended Action Check available memory capacity on the router.
Error Message%SCP-3-NOQUEUE : Cannot create SCP Rx/Tx queue.
Explanation There are insufficient internal resources available to create a queue.
Recommended Action Check available memory capacity on the router.
Error Message%SCP-2-NOTREG : Process [dec]([chars]) not registered for SCP
Explanation The SCP application cannot send an SCP message because it has not registered for a SAP.
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.
Error Message%SCP-5-ONLINE : Module online [chars]
Explanation The router has received online indication from the supervisor.
Recommended Action No action is required.
Error Message%SCP-3-PROCEXIT : The SCP process is terminating. signal: [dec]. subcode; [dec]. addr: [hex].
Explanation The SCP process has been terminated.
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%SCP-2-TOO_MANY_SAP : Not enough space to register process [dec]([chars]) for SCP
Explanation The SCP application cannot register for a SAP because all possible numbers have been assigned.
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.
Error Message%SCP-3-UNKMSG : Unknown SCP message (opcode [hex]) received.
Explanation The remote peer sent an unknown SCP message.
Recommended Action Check software compatibility between peers.
SDEE Messages
The following are SDEE subsystem messages.
Error Message%SDEE-4-BUFFER_SIZE : SDEE: Reduced maximum events stored to [int]
Explanation An SDEE buffer size could not be allocated on account of memory limitations.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SDEE-4-HTTP_ERROR : SDEE: HTTP returned error [dec] when registering
Explanation While the SDEE subsystem was being initialized, it received an error message from HTTP. This message indicates that SDEE was not able to register successfully with the HTTP server.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
SDSPFARM Messages
The following are SDSP FARM register and unregister messages.
Error Message%SDSPFARM-6-REGISTER : mtp-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has registered.
Explanation The configured DSP farm has been registered.
Recommended Action No action is required.
Error Message%SDSPFARM-6-REGISTER_NEW : mtp-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has registered.
Explanation A DSP farm has registered. The DSP farm is not yet in current running configuration.
Recommended Action No action is required.
Error Message%SDSPFARM-6-UNREGISTER_ABNORMAL : mtp-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has unregistered abnormally. \n
Explanation A DSP farm has been unregistered without sending an unregister message.
Recommended Action No action is required.
Error Message%SDSPFARM-6-UNREGISTER_NORMAL : mtp-[dec]:[chars] IP:[IP_address] Socket:[dec] DeviceType:[chars] has unregistered normally.
Explanation A DSP farm has been successfully unregistered.
Recommended Action No action is required.
SEC Messages
The following are IP security messages.
Error Message%SEC-6-IPACCESSLOGSP : list [chars] [chars] [chars] [IP_address] [chars]-> [IP_address] ([dec]), [dec] packet[chars] [chars]
Explanation A packet matching the log criteria for the given access list was detected.
Recommended Action No action is required.
SEC_LOGIN Messages
The following are secure login messages.
Error Message%SEC_LOGIN-4-25 : Login failed [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] at [chars]
Explanation An invalid username or password has been entered from the terminal.
Recommended Action Specify a valid username or password.
Error Message%SEC_LOGIN-3-INIT_FAILED : Secure Login Initialization failed. [chars]
Explanation Initialization of the secure login subsystem has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%SEC_LOGIN-5-LOGIN_SUCCESS : Login Success [user: [chars]] [Source: [IP_address]] [localport: [int]] at [chars]
Explanation Login has succeeded.
Recommended Action No action is required.
Error Message%SEC_LOGIN-5-QUIET_MODE_OFF : Quiet Mode is OFF, because [chars] at [chars]
Explanation Quiet mode has been set to off. The router is now operating in normal connection processing mode. The reason for the state change is specified in the message text.
Recommended Action No action is required.
Error Message%SEC_LOGIN-1-QUIET_MODE_ON : Still timeleft for watching failures is [int] secs, [user: [chars]] [Source: [IP_address]] [localport: [int]] [Reason: [chars]] [ACL: [chars]] at [chars]
Explanation Quiet mode has been set to on. No request for a connection will be accepted unless allowed by an ACL if one is configured for the blocking period. An implicit "deny all" of any logins will be in effect.
Recommended Action Because all the requests from other sources are blocked, check ACL and add any source addresses, if required.