-
Cisco IOS System Messages, Volume 2 of 2
-
System Messages Overview
-
MBUF through MODEM
-
MODEM_HIST through NSP
-
NSP_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SWITCH_IF
-
SYS through TCPIP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
Volume 2 Glossary
-
Table Of Contents
RPMXF_QUEUE_CFG_GENERAL Messages
RESYNCH Messages
The following are RPM resynchronization process messages.
Error Message%RESYNCH-6-INFO : [chars]
Explanation The system has information to log.
Recommended Action No action is required.
Error Message%RESYNCH-3-INVLD_IN_0 : Invalid input to func [chars]: [chars] = NULL.
Explanation A function has been called with an invalid NULL value for an input parameter.
Recommended Action No action is required.
Error Message%RESYNCH-3-INVLD_IN_D : Invalid input to func [chars]: [chars] = [dec].
Explanation A resynchronization function has been called with an invalid decimal value for an input.
Recommended Action No action is required.
Error Message%RESYNCH-3-MEM_ALLOC_FAIL : Func [chars] could not alloc [dec] bytes for [chars].
Explanation A resynchronization function could not allocate the specified number of bytes for the specified variable.
Recommended Action No action is required.
Error Message%RESYNCH-3-RET_ERROR : Func [chars] is returning an error because [chars].
Explanation A resynchronization function is returning an error because of the reason specified in this message.
Recommended Action No action is required.
Error Message%RESYNCH-6-UPDATE_DELETE : Resynched connection [dec]/[dec] deleted.
Explanation The specified channel was resynched, and it was deleted from the controller.
Recommended Action No action is required.
Error Message%RESYNCH-3-UPDATE_NAKED : Update for channel [dec] was NAKed.
Explanation The controller has sent a NAK in response to an update for the specified channel.
Recommended Action No action is required.
Error Message%RESYNCH-6-UPDATE_OK : Resynched connection [dec]/[dec] re-added.
Explanation The specified channel has been resynched and re-added to the controller.
Recommended Action No action is required.
Error Message%RESYNCH-3-UPD_RESP_UNKNOWN : Unknown update response [dec] for channel [dec].
Explanation The controller has responded with an unknown response for a channel.
Recommended Action No action is required.
Error Message%RESYNCH-4-WARNING : [chars]
Explanation The system will log a warning.
Recommended Action No action is required.
RIP Messages
The following are IP Routing Information Protocol (RIP) messages.
Error Message%RIP-3-NOSOCKET : Unable to open socket
Explanation The requested operation could not be completed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
RLM Messages
The following are RLM messages.
Error Message%RLM-3-INIT : rlm [dec]: [chars][chars].
Explanation The RLM initialization operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RLM-4-LINK : rlm [dec]: [chars][chars].
Explanation A warning has been received for an RLM link. This message provides debugging information only.
Recommended Action No action is required.
Error Message%RLM-4-NOBUF : rlm [dec]: cannot get packet buffer for [chars].
Explanation An RLM link cannot allocate a packet buffer.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
RM Messages
The following are Resource Manager messages.
Error Message%RM-3-BADACCT : Unknown Accounting type ([dec]), flag ([dec]).
Explanation The system has received either an invalid accounting type or a flag.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-BADCALL : Unexpected Call on [chars]. Current state is [dec].
Explanation A call has been received on a line that the software still detects as being active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-BADRG : Bad state rg "[chars]": [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-BOUNDARY : Memory boundary violation
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-NORESP : No response-code from local RM
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-OUTOFBUFFS : Out of buffers in RM event buffer queue
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-RGINFO : [chars]: RG-info conversion failed ([int]).
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-WAVL : Wavl error
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RM-3-ZEROVAL : Uninitialized value being used
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RMON Messages
The following are Remote Monitoring Protocol messages.
Error Message%RMON-5-FALLINGTRAP : Falling trap is generated because the value of [chars] has fallen below the falling-threshold value [dec]
Explanation A falling trap has been generated. The value of the specified MIB object has fallen below the falling-threshold value as configured by the rmon alarm command for the specified object.
Recommended Action Take appropriate action on the specified MIB object.
Error Message%RMON-5-RISINGTRAP : Rising trap is generated because the value of [chars] exceeded the rising-threshold value [dec]
Explanation A rising trap has been generated. The value of the specified MIB object has exceeded the rising-threshold value as configured by the rmon alarm command for the specified object.
Recommended Action Take appropriate action on the specified object.
ROUTEMAP_IPC Messages
The following are route map interprocess communication (IPC) messages.
Error Message%ROUTEMAP_IPC-2-NOMEMORY : Alloc fail for route-map ipc buffer
Explanation The system is unable to allocate a memory buffer to send the route map configuration down to the line cards.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show chunks command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show chunks command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%ROUTEMAP_IPC-2-ROUTEMAPNAMELENEXCEEDED : The length of route map name tag is too long
Explanation The route map name tag length is too long for IPC. The receiver has a 256-character limit for the route map name tag.
Recommended Action Use a route map name tag with a length of 256 or fewer characters.
Error Message%ROUTEMAP_IPC-2-WRONGREQUEST : Invalid request to allocate chunk of size [dec]
Explanation An invalid chunk size allocation has been entered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show chunks command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show chunks command output, contact your Cisco technical support representative and provide the representative with the gathered information.
RP_MLP Messages
The following are distributed PPP Multilink messages.
Error Message%RP_MLP-4-CHANGEQUEUEING : Change the queueing on the distributed multilink interface [chars] to FCFS
Explanation Weighted fair queueing or priority queueing is being used. When multilink interface is used in distributed mode, the queueing should be FCFS.
Recommended Action Shut down the multilink interface and unconfigure weighted fair queueing or priority queueing. Then restart (unshut) the multilink interface.
Error Message%RP_MLP-4-DLFIONELINKSUPPORT : Only ONE link should be configured for dLFI bundle!!
Explanation More than one link was configured for the dLFI bundle interface. More than one link is not supported by dLFIoFR and dLFIoATM.
Recommended Action If the system is using dLFIoFR and dLFIoATM, remove the extra links from the multilink bundle so only one link is in the multilink bundle. Enter the shutdown and no shutdown commands to shut down and restart the dLFI bundle interface and properly restore the links.
Error Message%RP_MLP-4-MISCONFIGLINK : Links spread across VIP OR dCEF not enabled, giving control to RSP
Explanation The system is attempting to add links to a bundle which are spread across VIPs. DMLP cannot support this action. The RSP has been given control of the bundle.
Recommended Action To make the MLPPP bundle interface distributed, check to see if the newly-added link which caused the MLPPP to become non-distributed has distributed switching enabled. If the link is added from another VIP, remove this link from the bundle interface.
Error Message%RP_MLP-4-NODISTMLP : Failure downloading MLP bundle [chars] to the LC [dec]
Explanation An error occurred while MLP information was being downloaded to the line card. The bundle is configured to be a distributed bundle, but the MLP configuration cannot be downloaded to the line card.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RP_MLP-4-PANOTSUPPORTED : Adding Link from unsupported PA, cant add, giving control to RSP
Explanation The system is attempting to add links to a bundle from a PA that is not supported by DMLP. Control of the bundle has been given to the RSP. This condition has resulted in making the MLPPP interface nondistributed.
Recommended Action To make the MLPPP interface distributed, remove the links that were added from the nonsupported PAs.
RPA Messages
The following are Resource Pool Allocation (RPA) messages.
Error Message%RPA-3-FLEXIBLE : [chars]
Explanation This message is displayed for all messages that use ASCII text and do not take any parameters.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPA-3-NO_CAS_ENTRY : CAS Entry does not exist for slot: [dec], ctrl:[dec], channel:[dec]
Explanation The CAS entry did not exist for the given controller and channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPA-3-UNKNOWN_MSG : Unknown message type [dec] enqueued to RPA CAS Process
Explanation A message type that is not known to the RPA CAS process has been placed in the queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPC Messages
The following are Remote Procedure Call (RPC) messages.
Error Message%RPC-2-APPNOTREG : Remote application '[chars]' not registered
Explanation The remote application has not registered itself with the RPC subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-4-BADID : Application ID [dec] is invalid
Explanation The application ID used by the RPC subsystem is invalid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-4-DUPREG : Application '[chars]' is already registered
Explanation The application has already registered itself with the RPC subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-2-FAILED : Failed to send RPC request [chars]
Explanation A communication error has occurred during an RPC request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-2-NOMEM : No memory available for [chars]
Explanation The RPC subsystem could not obtain the memory it required.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-2-NOSUCH : The referenced RPC application ([dec]) does not exist
Explanation A message was received for an RPC application that does not exist.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-2-NOTREADY : The referenced RPC application ([dec],[chars]) is not ready
Explanation A message was received for an RPC application that is not ready.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPC-4-TOOMANY : Too many RPC applications, '[chars]' not registered
Explanation Too many applications are registered with the RPC subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
RPM Messages
The following are Route Processor Module (RPM) messages.
Error Message%RPM-4-CDINFOSNDFAIL : Sending [chars] info to pxm failed.
Explanation The card information could not be successfully sent to the PXM.
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%RPM-4-COOKIE : Corrupt or missing MAC address cookie\n 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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM-4-LVCRECOVER : vcd [int] holds [int] buffers.
Explanation The LVC of the MPLS subinterface is stuck. The system will recover by itself because the auto-SAR recovery and auto-LVC recovery features are enabled.
Recommended Action Check if the system recovers automatically and traffic flows in both directions through the LVC corresponding to the VCD. Otherwise, clear the Switch1 interface using CLI commands and check to see if the LVC recovers. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPM-3-LVCSTUCK : LVC (vcd = [int]) stuck with [int] buffers held.
Explanation The LVC of the MPLS subinterface is stuck. This condition can affect the outgoing traffic through this LVC.
Recommended Action Enable the auto-SAR recovery and auto-LVC recovery features for so that the system will automatically recover from the LVC stuck situation. Otherwise, manually clear the Switch1 interface using CLI commands.
Error Message%RPM-3-MPLSPTR : Error setting MPLS pointers for the interface [chars].
Explanation The congestion pointers for the interface could not be set, because there are two MPLS interfaces already configured.
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%RPM-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from the EEPROM. This condition is probably due to 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%RPM-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation MAC address allocation failed because of an incorrect slot and port combination, which exceeds the maximum available hardware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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-4-PCIVALID : PCI activation failed, bay [dec], [hex]
Explanation The system has received an invalid PCI signal from the port adapter. This error 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%RPM-5-SUBIFNOSHUT : Sub-interface Switch1.[dec], changed state to up.
Explanation The switch subinterface has been activated via user-entered CLI.
Recommended Action No action is required.
Error Message%RPM-5-SUBIFSHUT : Sub-interface Switch1.[dec], changed state to administratively down.
Explanation The switch subinterface has been deactivated via user-entered CLI.
Recommended Action No action is required.
Error Message%RPM-6-SWIFCLR : Clear interface done on interface Switch1
Explanation The user has entered commands to clear the Switch1 interface, and the action has completed successfully.
Recommended Action No action is required.
RPM_BULK Messages
The following are RPM-specific bulk file messages.
Error Message%RPM_BULK-3-ADDERR : Cannot add file [chars]. File Index [hex] Error [dec]
Explanation The bulk file entry could not be added to the MIB table.
Recommended Action Check to see if this error is due to an invalid value being used for setting the object or due to an incorrect row status for setting the object. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPM_BULK-3-ADDOBJECTERR : Cannot add object. File [hex]. Object [dec]. Error [dec]
Explanation The bulk file object entry could not be added to the MIB table.
Recommended Action Check to see if this error is due to an invalid value being used for setting the object or due to an incorrect row status for setting the object. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPM_BULK-3-CREATEABORT : File Index [hex] error state [hex]
Explanation The bulk file could not be created. The error detail is defined in the MIB variable cbfStatusFileState of the CISCO-BULK-FILE-MIB.my MIB.
Recommended Action If file state specified by the MIB object cbfStatusFileState shows an error state (if the state displays a value in the range 4 through 9), copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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_BULK-5-CREATEDONE : [chars]. File Index [hex]
Explanation The bulk file transfer is completed.
Recommended Action No action is required.
Error Message%RPM_BULK-5-CREATESTARTED : File Index [hex]
Explanation The bulk file is opened and the file transfer is started.
Recommended Action No action is required.
Error Message%RPM_BULK-3-DEFSETERR : Cannot set Bulk File definitions. Error [dec]
Explanation An error occurred while bulk file definitions were being set.
Recommended Action Check if this error is due to an invalid value being used for setting the object. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%RPM_BULK-5-GOACTV : Received GO ACTIVE.
Explanation The RPM bulk process received a "GO ACTIVE" event.
Recommended Action No action is required.
Error Message%RPM_BULK-5-GOREADY : Process initialization is done. Wait for Events.
Explanation The RPM bulk process is ready to process events,
Recommended Action No action is required.
Error Message%RPM_BULK-5-GOSTBY : Received GO STANDBY
Explanation The RPM bulk process received a "GO STANDBY" event.
Recommended Action No action is required.
Error Message%RPM_BULK-5-INIT : Initialize process
Explanation The RPM bulk process has entered its initialization phase.
Recommended Action No action is required.
Error Message%RPM_BULK-3-PARTCNFERR : Cannot set partial config. File [hex], Object [hex], size [hex], Error [dec]
Explanation An error occurred while the bulk file partial configuration was being set.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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_BULK-5-POPULATED : Configurations are populated in MIB tables.
Explanation The RPM bulk file configurations have been initialized.
Recommended Action No action is required.
Error Message%RPM_BULK-3-STATSETERR : Cannot set Bulk File stats objects. Error [dec]
Explanation An error occurred while bulk file status objects were being set.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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_BULK-3-TRAPBAD : Bad file index. File Index [hex] state [hex] reason [hex]
Explanation The bulk file trap could not be sent because a file index is corrupt or invalid.
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%RPM_BULK-3-TRAPERR : Cannot generate trap. File Index [hex] state [hex] reason [hex] error [hex]
Explanation The bulk file trap could not be sent. The system message text on the console or in the system log provides additional details on the nature of the error.
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.
RPM_CONFIG_COPY Messages
The following are RPM Config Copy feature messages.
Error Message%RPM_CONFIG_COPY-3-CCOPYFAILED : Snmp Config Copy Set Failed:Index([hex])State([dec])Fail Cause([dec])
Explanation The configuration copy set operation has failed while writing the memory to storage. One possible reason is that there is not enough memory space where the file was to be copied. This condition could be critical.
Recommended Action Enter the following commands on the RPM and copy the output:
–
show flash
–
–
–
–
–
Enter the following commands on the PXM:
–
–
Enter the shellicon command on the PXM, and then enter printAllConfigCopyTable.
–
Error Message%RPM_CONFIG_COPY-3-CCOPYINDEX : Snmp Config Copy Get Request invalid index rcv/sav [dec]/[dec]
Explanation An invalid index has been passed in a configuration copy get request.
Recommended Action This condition is not critical. However, the PXM should not forward this request when the index is invalid. One possible reason for this error is that a debug command has been issued.
Enter the following commands on the RPM and copy the output:
–
–
–
–
–
–
Enter the following commands on the PXM:
–
–
–
–
Error Message%RPM_CONFIG_COPY-3-CCOPYINPROGRESS : Snmp Config Copy Set Request: Config Copy already in Progress.
Explanation The SNMP configuration copy set request has issued an error for a SET operation because one Config Copy operation was already in progress. Only one configuration copy entry is supported at a time on the RPM.
Recommended Action This condition is not critical. However, the PXM should not forward this request when one configuration copy request is already in progress. One possible reason for this error is that a debug command has been issued.
Enter the following commands on the RPM and copy the output:
–
–
–
–
–
–
Enter the following commands on the PXM:
–
–
–
–
Error Message%RPM_CONFIG_COPY-3-CCOPYINVSRC : Snmp Config Copy Set Failed: Invalid Source([dec])or Dest File([dec])
Explanation An invalid source or destination type has been requested. The system can only support a source type of running-configuration (type 4), or a destination type of startup-configuration (type 3).
Recommended Action This condition is not critical. However, the PXM is not supposed to forward this request when the source and destination types are incorrect. One possible reason for this error is that a debug command has been issued.
Enter the following commands on the RPM and copy the output:
–
–
–
–
–
–
Enter the following commands on the PXM:
–
–
–
–
Error Message%RPM_CONFIG_COPY-3-CCOPYNULLDATA : Config Copy Error: received NULL message
Explanation An error has occurred during the copying of the configuration file. A null message has been returned.
Recommended Action This condition is not severe. Check to see if any configuration copy request was made. Enter the dsplog command on the PXM, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPM_RED Messages
The following are Route Processor Module (RPM) redundancy messages.
Error Message%RPM_RED-3-FILE_COPY : [chars] source_file = [chars]. destination_file = [chars]
Explanation The copying of the file to the running configuration (running-config) or the copying of the file to boot flash has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_RED-3-IPCERR : [chars] Error String = [chars]. Error Code = [dec]
Explanation The RCP or IPC request to PXM has failed or has been rejected by the PXM.
Recommended Action The problem could affect service. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_RED-3-REDERR : An unexpected FW error has occured. [chars]. [chars]
Explanation An unexpected firmware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_RED-3-STATE_ERR : [chars] Current State = [dec]
Explanation The PXM has requested the card to go to a new state from the current state and transitions cannot occur. This error should not occur.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPM_VIRTUAL_PORT Messages
The following are Route Processor Module (RPM) virtual port messages.
Error Message%RPM_VIRTUAL_PORT-3-CLRALLCNF_DELETE_FILE : ERROR: clrAllCnf --- Fail to delete clrAllCnf file on PXM C: disk ... Please delete file manually by doing "delete c:auto_config_slot[dec]".
Explanation The reconfiguration request to the PXM has failed, timed out, or been rejected by the PXM.
Recommended Action In the case of failure or timeout, the state of the connection will be set to TIMEOUT, and the resynchronization process will periodically attempt to update the PXM. If the request was rejected by the PXM, the connection state will be set to FAILED until the connection is deleted or reconfigured.
Error Message%RPM_VIRTUAL_PORT-3-CONNDEL : [chars]
Explanation The delete request to the PXM has failed, timed out, or been rejected by the PXM.
Recommended Action In the case of failure or timeout, the state of the connection will be set to TIMEOUT, and the resynchronization process will periodically attempt to update the PXM. If the request was rejected by the PXM, the connection state will be set to FAILED until the connection is deleted or reconfigured. If the request is rejected, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_VIRTUAL_PORT-3-IPCERR : [chars] Error String = [chars]. Error Code = [dec]
Explanation The RPC/IPC request to the PXM has failed or has been rejected by the PXM.
Recommended Action If the error message indicates "rpc-timeout", retry the command that was entered last. For other errors, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_VIRTUAL_PORT-3-IPCPAK : [chars] Message size = [dec]
Explanation The ip_get_pak_message failed. This error was probably caused by insufficient memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_VIRTUAL_PORT-3-IPCSIZE : [chars] Message size = [dec]
Explanation The message that is supposed to be sent to or received from the PXM is too big.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_VIRTUAL_PORT-3-RPCREQERR : [chars] request_type = [dec]
Explanation The RPC request from the Virtual Port or Resync process is not valid.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_VIRTUAL_PORT-3-VRTLERR : An unexpected FW error has occured. [chars]
Explanation An unexpected firewall error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPM_VIRTUAL_PORT-3-VRTLINFO : [chars]
Explanation This is an informational message from the RPM Virtual Port Module.
Recommended Action The message is for informational purposes only. No action is required.
RPMXF Messages
The following are RPMXF 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 specified an out-of-range card interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-2-BADRSRCNUM : Invalid resource number from PXF ([dec]). (PLEASE REPORT THIS!)
Explanation The PXF hardware diversion path specified an invalid resource number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-2-BADSLOT : Out of range card slot index[dec]
Explanation The software specified an out-of-range card slot index.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-2-BADSLOTSUBSLOT : Out of range card slot/subslot pair[dec]/[dec]
Explanation The software specified an out-of-range card slot or subslot pair.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-2-CARDRECUR : Recursive loop while getting the daughtercard info for card type [dec]
Explanation While retrieving the daughter card information for the chassis MIB, the platform SNMP code has gone into an infinite loop.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-CARD_SLOT_MISMATCH : Card type [hex] not allowed in slot [dec]/[dec].
Explanation The card type is not supported in the specified slot.
Recommended Action Remove the card from the slot.
Error Message%RPMXF-4-COOKIE : Corrupt or missing MAC address cookie\n using random base [enet]
Explanation The MAC address information provided by the controller card is invalid. The controller card may not have provided a MAC address. The system is using a random MAC address.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-DEACTIVATED : card in slot [dec] disabled.
Explanation The card is being deactivated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF-1-DISCOVER_ENET : Failed to init Ethernet device [dec]
Explanation The Cisco IOS software could not initialize.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-1-DISCOVER_SAR : Failed to init SAR device [dec]
Explanation The Cisco IOS software could not initialize.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-INTERNAL : RPM-XF internal error, [chars]
Explanation An internal RPM-XF error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-IPC : [chars]: IPC Failure
Explanation An interprocess communication error has occurred. Additional details on the nature of the error are provided in the error message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-4-MACBLKSIZE : Unknown MAC address block size.
Explanation The data stored in the midplane is invalid or incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%RPMXF-3-NOACK : Access to [chars] temperature sensor failed
Explanation An attempt to access to the chassis temperature sensor has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF-4-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from the EEPROM. This condition is probably due to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation An attempt to allocate a MAC address has failed because of an incorrect slot and port combination. The slot and port combination exceeds the maximum configured value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-NOMEM : OUT of Memory: [chars]
Explanation The software was unable to allocate memory for the interface specified in the error message. A possible reason for this condition is that the system has exhausted its memory.
Recommended Action Reload the router to free up memory. Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF-4-PCIVALID : PCI activation failed, slot [dec], [hex]
Explanation the system has received an invalid PCI signal from the port adapter. This condition might be due to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-3-PLUGIN_UNKNOWN : Unknown card type [hex] in slot [dec]/[dec].
Explanation The card in the specified slot is not a known type. This condition might be due to a hardware failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-2-PROCFAILED : Unable to create system process, [chars]
Explanation An internal RPM-XF error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF-4-TEST : Test command no. [dec] executed by user
Explanation The test message command has been executed.
Recommended Action No action is required.
Error Message%RPMXF-3-UNEXP_INTR : Interrupt [chars] not expected, masking off
Explanation An interrupt of a certain type was signaled, but the interrupt handler for this type of interrupt is not yet installed. This error should be self-correcting but can indicate either a hardware or a software problem. If the error is caused by a hardware problem, further problems are to be expected. If the error is caused by a software problem, certain types of error and alarm conditions may be left undetected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPMXF_QOS_GENERAL Messages
The following are RPMXF quality of service (QoS) messages.
Error Message%RPMXF_QOS_GENERAL-3-EREVENT : Error @ [chars]:[dec]
Explanation This message provides general error information that is used for sanity tests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPMXF_QUEUE_CFG_GENERAL Messages
The following are RPMXF PXF Queueing Configuration messages.
Error Message%RPMXF_QUEUE_CFG_GENERAL-3-EREVENT : Error @ [chars]:[dec]
Explanation This message provides general error information that is used for sanity tests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPMXF_TOASTER Messages
The following are RPMXF Toaster messages.
Error Message%RPMXF_TOASTER-5-DNLD_DONE : PXF download complete, PXF operational, time elapsed [time-stamp]
Explanation The PXF microcode has been successfully downloaded and started. The PXF forwarding engine is now configured and operational. The time elapsed begins when the "DNLD_START" message is received.
Recommended Action No action is required. This is a normal activity at Cisco IOS boot time or after a fatal PXF error has occurred.
Error Message%RPMXF_TOASTER-5-DNLD_START : Downloading PXF Microcode [chars], version=[chars], [chars]
Explanation The platform code is starting to download a PXF microcode image.
Recommended Action No action is required. This is a normal activity at Cisco IOS boot time or after a fatal PXF error has occurred.
Error Message%RPMXF_TOASTER-2-DOWNLOAD : [chars]: Toaster microcode image [chars]: could not be downloaded.
Explanation The Toaster microcode could not be downloaded. This condition could be due to an already corrupted image or to a software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-DUMP : RPMXF Toaster has crashed, attempting to write core file(s)....
Explanation The RPMXF Toaster has crashed because of an exception. Depending on the current system configuration, one or more core files will be generated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-DWNLOAD : Could not download the microcode into PXF processor @ column [dec] row [dec].
Explanation A problem has occurred that prevented microcode from being downloaded to the toaster. This condition could be caused by either a software or a hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-0-FP_ERROR : FP Init error: [chars]
Explanation The FP board is not working properly or it is not compatible with the Cisco IOS software image running on the system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-0-FP_REV : FP rev [dec].[dec] is [chars], require at least [dec].[dec]
Explanation This Cisco IOS image is incompatible with the hardware revision of the FP board, or the FP board is supported, but with software workarounds for certain hardware problems. In the first case, the software will not complete the boot process; in the second case, the software will run but may exhibit unexpected behavior.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-0-FP_TYPE : FP type [dec] is [chars]
Explanation This Cisco IOS image is incompatible with the hardware type of the FP board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-HDRCORRUPT : Toaster microcode header of image [chars] has been corrupted, expected [hex], got [hex].
Explanation The Toaster microcode appears to be corrupted. This condition could be due to an already corrupted image or, less likely, a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-IMAGE : Toaster microcode image [chars]: could not be read.
Explanation The Toaster microcode could not be read. This condition could be due to an already corrupted image or, less likely, a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-INCOMPAT : This microcode image is incompatible with this Cisco IOS image.
Explanation The signature in the microcode image does not match the signature in the Cisco IOS software image.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-METADATA : Toaster microcode meta-data [chars]: [chars], in file: [chars].
Explanation The Toaster microcode appears to be corrupted. This condition could be due to an image that is already corrupted or, less likely, a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-OPER : Toasters not operational: [chars]
Explanation The Toaster clients could not be made operational. This condition could be caused by either a software or a hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-5-REDNLD : PXF download requested during PXF download
Explanation A PXF restart and download was requested while the previous download was still in progress. This condition is typically caused by an exception during the restart. Another restart and download will be started as soon as the current one is complete.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-ROW : Toaster microcode header of image [chars] doesn't match block [chars], row [dec] not row [dec].
Explanation The Toaster microcode appears to be corrupt. This problem could be occurring because an image is already corrupted, or less likely, because of software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-STALL : Toaster Stall detected
Explanation The RPMXF toaster driver has detected a toaster stall condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-START : Toasters not started: memory state: [dec], expected [dec].
Explanation The Toaster clients could not be started. This condition could be due to either a software or a hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-TDB : Could not find control block for Toaster image [chars].
Explanation A software error has occurred that prevented the control block representing this Toaster from being located.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RPMXF_TOASTER-2-UNUSABLE : No usable Toaster microcode
Explanation No usable Toaster microcode could be loaded. This condition could be due to an already corrupted image or to a software or hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
RPMXFEVENTMGR Messages
The following are Event Manager subsystem messages.
Error Message%RPMXFEVENTMGR-1-CRITICAL_FAULT : [chars], Restarting IOS
Explanation A critical fault has occurred. The system is now performing a crash dump.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-IRONBUS_FAILURE : [chars], Restart Failed([hex]). Resetting line card.
Explanation An ironbus fault has occurred. The ironbus failed to restart.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-IRONBUS_FAULT : [chars], Restarting Ironbus
Explanation An ironbus fault has occurred. The ironbus is now being restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-IRONBUS_REOCCURRING : [chars], Resetting line card.
Explanation An ironbus fault has reoccurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-IRONBUS_SUCCESS : [chars], Restart Successful
Explanation An IronBus fault has occurred. The IronBus restarted successfully.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-MAJOR_FAULT : [chars], Restarting PXF
Explanation A major fault has occurred. The PXF complex is being restarted.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-MINOR_FAULT : [chars]
Explanation A threshold for a minor event has been reached.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-1-MINOR_REOCCURRING : [chars]
Explanation A minor fault is reoccurring.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-4-PXF_CRASHINFO : Writing PXF debug information to [chars].
Explanation A file containing information useful for diagnosing a PXF restart is being written.
Recommended Action Save the file named "pxf_crashinfo". Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-3-PXF_CRASHINFO_FAIL : Failed to write PXF debug information.
Explanation PXF debugging information could not be written. The device on which the write was attempted is likely out of free space, or the write has encountered some other error.
Recommended Action Free up some space on the device to which the PXF debugging information will be written.
Error Message%RPMXFEVENTMGR-4-SAR_CRASHINFO : Writing SAR debug information to [chars].
Explanation A file containing information useful for diagnosing a SAR restart is being written.
Recommended Action Save the file named "sar_crashinfo". Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPMXFEVENTMGR-3-SAR_CRASHINFO_FAIL : Failed to write SAR debug information.
Explanation PXF debugging information could not be written. The device on which the write was attempted is likely out of free space, or the write has encountered some other error.
Recommended Action Free up some space on the device to which the SAR debugging information will be written.
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 presents debug data for single-bit correctable errors.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
RPS Messages
The following are redundant power system messages.
Error Message%RPS-3-DCOUTPUTVOLTFAIL : System detected Redundant Power System DC Output Voltage failure condition.
Explanation The redundant power system experienced a DC output voltage failure in one of the power supplies.
Recommended Action The redundant power supply has failed for one of the DC outputs. For redundant power supplies in Cisco 2600 and 3600 series routers, the "DC Status" LED on the front of the power supply identifies which DC output has failed. For redundant power supplies in the Cisco AS5300 universal access server, the "DC OK" LED on the front of the power supply identifies which DC output has failed. Replace the redundant power supply that has failed.
Error Message%RPS-3-DCOUTPUTVOLTOK : Redundant Power System DC Output Voltage condition is now normal
Explanation The DC voltage is normal for the redundant power system.
Recommended Action No action is required.
Error Message%RPS-3-FANFAIL : System detected Redundant Power System FAN FAIL condition.
Explanation The redundant power system has experienced a fan failure.
Recommended Action Replace the redundant power supply.
Error Message%RPS-3-FANOK : Redundant Power System FAN condition is now normal.
Explanation The redundant power supply previously detected a fan failure condition that has now returned to a normal condition.
Recommended Action No action is required.
Error Message%RPS-3-INPUTVOLTFAIL : System detected Redundant Power System Input Voltage failure condition.
Explanation The redundant power system has experienced an input voltage failure in one of the power supplies.
Recommended Action One of the AC or DC inputs has failed on the redundant power supply. For the redundant power supplies in the Cisco 2600 and 3600 series routers, the "AC Input" LED on the front of the power supply identifies which AC input has failed. For the redundant power supplies in the Cisco AS5300 universal access server, the "AC OK" LED on the front of the power supply identifies which AC input has failed. For the redundant power supplies in the Cisco AS5800 universal access server, the "DC Input" LED on the front of the power supply identifies which DC input has failed. Ensure that the AC/DC circuit in your building is operational, verify that the power cord is plugged into the redundant power supply, and ensure that the AC/DC power switch on the redundant power supply is on.
Error Message%RPS-3-INPUTVOLTOK : Redundant Power System Input Voltage condition is now normal
Explanation The redundant power system input voltage is normal.
Recommended Action No action is required.
Error Message%RPS-3-MULTFAIL : There is more than one failure with the Redundant Power System; please resolve problems immediately
Explanation The redundant power system has experienced multiple failures. This is a critical condition.
Recommended Action Examine the LEDs on the front of the Redundant Power Supply to find out which failure has occurred. Replace the redundant power supply that has failed.
Error Message%RPS-3-OVERTEMP_OK : System temperature is now normal.
Explanation The system previously detected a high temperature condition that has now returned to a normal temperature condition. This condition might have been caused by high ambient temperature where the router is located.
Recommended Action No action is required.
Error Message%RPS-3-OVERVOLT : Redundant Power System detected OVERVOLTAGE condition.
Explanation The Redundant Power System has detected an over voltage condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RPS-3-RPSOK : Redundant Power System is now normal
Explanation The redundant power system is operating normally.
Recommended Action No action is required.
Error Message%RPS-3-THERMAL : System detected Redundant Power System THERMAL FAIL condition.
Explanation The redundant power system experienced either a fan failure or a high temperature condition.
Recommended Action For the redundant power supplies in the Cisco 2600 and 3600 series routers, look at the "FAN" and "TEMP" LEDs on the front of the power supply. If the "FAN" LED is amber, one of the fans has failed, and you should replace the redundant power supply. If the "TEMP" LED is amber, the ambient temperature is too high. For the redundant power supplies in the Cisco AS5300 universal access server, this error message is displayed when the ambient temperature is too high.
Error Message%RPS-3-THERMOK : Redundant Power System THERMAL condition is now normal.
Explanation The redundant power system thermal condition is now normal. The redundant power supply previously detected a high temperature condition that has now returned to a normal temperature condition. This condition was probably caused by high ambient temperature where the redundant power supply is located. A redundant power system thermal failure can also be caused by a fan failure in the redundant power supply.
Recommended Action If this message recurs, pay close attention to the messages that are displayed and to the LED indicators on the front of the power supply. No immediate action is required.
Error Message%RPS-3-VOLTOK : Redundant Power System VOLTAGE is now normal.
Explanation The redundant power system voltage is now normal.
Recommended Action No action is required.
RS_TDM Messages
The following are router shelf time-division multiplexing (TDM) messages.
Error Message%RS_TDM-3-MALLOC_FAIL : [chars]: Memory allocation failed.
Explanation The system could not allocate memory for the requested function. This error may be due to memory system exhaustion.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RS_TDM-3-TDM_BACKPLANE_CLASH : Clash in usage for TDM backplane DS0 [dec]
Explanation The TDM backplane DS0 to be allocated is already in use.
Recommended Action Check the split dial-shelf settings on both sides of the split for conflicting settings.
Error Message%RS_TDM-3-TDM_BADARG : A TDM function is used with a bad argument: [chars]
Explanation An internal software error has occurred. A TDM function was called with invalid arguments and could not be processed. The invalid arguments are specified at the end of this error message, along with any other useful data.
Recommended Action Enter the debug tdm command. If this problem recurs, copy the error message, the trace message, and surrounding debug text exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RS_TDM-3-TDM_CONFLICT : TDM split user settings are in conflict: my [chars] = [dec], other's [chars] = [dec]
Explanation The user setting for the TDM split on this side of the split is in conflict with the setting on the other side. More backplane DS0s are in use than the backplane supports.
Recommended Action Adjust the split backplane-DS0 of the other side to a nonconflicting setting.
Error Message%RS_TDM-3-TDM_DS0_POOL_CLASH : The two sides of the split in the [chars] pool ([int] DS0s) overlap: this side has [chars] [int], other side has [chars] [int]; overlap of [dec] DS0s
Explanation There is a clash in the given pool whereby both sides claim to own one or more of the DS0s in the pool. This error suggests a software problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RS_TDM-3-TDM_EXTEND_CLASH : TDM extended split on Router shelf Clashes to my [chars] other [chars] extended backplane ds0
Explanation The TDM extended split backplane DS0 for this router conflicts with the extended backplane DS0 of another router shelf.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RS_TDM-4-TDM_FREE_QUEUE_EMPTY : No backplane timeslots are available
Explanation A call was not hairpinned because the call capacity of the system has been exceeded.
Recommended Action Load-balancing may be required to reduce the number of calls handled by this system.
Error Message%RS_TDM-3-TDM_LEG_CLASH : TDM legacy split on Router shelf Clashes to my [dec] other [dec] legacy backplane ds0
Explanation The number of legacy backplane DS0s for the specified router shelf conflicts with the number of legacy backplane DS0s on the other specified router shelf.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RS_TDM-4-TDM_NO_HPM_DEVICE : No hairpin device available
Explanation A call was not hairpinned because all devices capable of hairpinning DS0s were in use.
Recommended Action More modem or voice feature boards may be required to increase hairpinning capacity.
Error Message%RS_TDM-3-TDM_NOT_SPLIT_PAIR : TDM split user setting are not matched pairs; my [chars] = [dec] DS0, expected other's [chars] = [dec] DS0, actual other's [chars] = [dec] DS0
Explanation The user setting for the TDM split on this side of the split is not compatible with the setting on the other side.
Recommended Action Set the split backplane-DS0 of the other side to the setting shown in the error message.
Error Message%RS_TDM-3-TDM_REDUCED_TDM_SPLIT : TDM split on [chars] Router shelf Reduced to [dec] backplane ds0
Explanation The number of backplane DS0s for this router has been forced to a lower number.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RS_TDM-3-TDM_UNKNOWN_DS0_STATE : TDM backplane DS0 [dec] is in an unknown state
Explanation The TDM backplane DS0 specified is in an unknown state.
Recommended Action Check the split dial-shelf settings on both sides of the split for conflicting settings.
%RS_TDM-3-TDM_UNKNOWN_TS_STATE : TDM backplane timeslot [dec] is in an unknown state
Explanation The specified TDM backplane time slot is in an unknown state.
Recommended Action Check the split dial shelf settings on both router shelves for conflicting settings.
RSC Messages
The following are route switch controller (RSC) messages.
Error Message%RSC-2-MAC_ADDRESS_ERROR : mac address not programmed. [chars]
Explanation The MAC address is not programmed on the backplane EEPROM.
Recommended Action Program the MAC address.
RSC_CF Messages
The following are Compact Flash messages.
Error Message%RSC_CF-3-CF_ERROR : Compact flash error on Cmd = [hex], Nsecs = [dec], Sector = [dec], Cylinder Low = [dec], Cylinder High = [dec], Drive Head = [dec], [chars]
Explanation The compact Flash reports an error on a command.
Recommended Action If the compact Flash cannot be read from or written to, reformat disk 0.
Error Message%RSC_CF-3-CF_ERROR_REG : Compact Flash Error Register = [hex], Request Sense = [hex]
Explanation The compact Flash reports an error on a command.
Recommended Action If the compact Flash cannot be read from or written to, reformat disk 0.
RSCPB Messages
The following are RSC Push Button handling messages.
Error Message%RSCPB-6-ACO : Alarm cutoff (ACO) selected from front panel
Explanation The ACO function was selected using the push buttons on the front panel. The front panel alarm LED has been turned off, and the alarm port has been deactivated.
Recommended Action No action is required.
Error Message%RSCPB-6-CLR_HIST : Alarm history LED cleared on front panel
Explanation The Alarm History Clear (CLR HIST) function was selected using the push buttons on the front panel. The front panel Alarm History (HIST) LED has been turned off.
Recommended Action No action is required.
Error Message%RSCPB-6-IDLE : Idle timeout occurred on front panel
Explanation The push buttons on the front panel were used to bring up choices on the front panel display, but no final action was selected before the idle timeout of 2 minutes expired.
Recommended Action No action is required.
Error Message%RSCPB-6-MODE : MODE push button pressed on front panel
Explanation The MODE push button was pressed on the front panel.
Recommended Action No action is required.
Error Message%RSCPB-6-SEL : SEL push button pressed on front panel
Explanation The SEL push button was pressed on the front panel.
Recommended Action No action is required.
Error Message%RSCPB-5-START_RSC : RSC Start selected from front panel
Explanation The RSC Start (RSC STRT) function was selected using the push buttons on the front panel to reverse an earlier RSC STOP command. The RSC is reactivating.
Recommended Action No action is required.
Error Message%RSCPB-5-STOP_RSC : RSC Stop selected from front panel
Explanation The RSC STOP function was selected using the push buttons on the front panel. The RSC is being prepared for removal.
Recommended Action No action is required.
RSP Messages
The following are Route Switch Processor (RSP) messages.
Error Message%RSP-3-ACCERROR : [chars] acc [hex] had bad value [dec]
Explanation An incorrect value has been written on an accumulator.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. A microcode reload can correct the error condition.
Error Message%RSP-3-BADBUFHDR : [chars], address [hex]
Explanation A software or hardware error regarding the MEMD buffers has occurred; for example, a buffer header pointer might be invalid. The exact nature of the problem is described in the error message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-2-BADCACHE : Overrun detected.\n End of MEMD buffer : [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 MTU size, or an illegal buffer header data area was found.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSP-3-BADHWREV : [chars] (slot [int]) has wrong hardware revision [int].[int]
Explanation The hardware in the indicated slot must be upgraded for operation with the RSP.
Recommended Action Upgrade the board.
Error Message%RSP-3-BADTURBOIPCMSG : Bad Turbo IPC msg ([chars]): msg=[hex] lastmsg=[hex] hdrsize=[hex] size=[hex]
Explanation An error has been discovered in an IPC message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-BENGAL : Bengal error. [chars]
Explanation The Bengal system controller has reported an error or event.
Recommended Action Read the error reports. If the error is an SBE, it is generally not a fatal error. If any other error is encountered, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-4-COOKIE : Corrupt or missing MAC address cookie\n using random base [enet]
Explanation The MAC addresses that are allocated to this chassis could not be accessed or were found to be corrupt. This condition was caused by a hardware problem or manufacturing problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-DEVERR : Error accessing the device : Device number = [dec] Error number = [dec]
Explanation An error was detected while the device was being accessed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case 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-3-ERROR : NULL
Explanation An internal software error has occurred. The exact nature of the problem is described in the message text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-FOREVER : cmd [int] to [chars] (slot [int]) took [int] usecs, done [hex]
Explanation A command from the RSP to an IP took longer for the system to process than expected. This condition may be caused by a heavily loaded CPU.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSP-4-HSA_MEM : size mismatch, master [int]MB, slave [int]MB
Explanation The system has detected a memory size mismatch between a master and slave RSP.
Recommended Action Configure both master and slave RSPs to have an equal amount of memory.
Error Message%RSP-4-HSA_MINMEM : [int]MB required for HSA
Explanation HSA requires a minimum of 24 MB of memory.
Recommended Action Upgrade your system to meet minimum memory requirements for HSA.
Error Message%RSP-3-IDPROM : Bad or missing ID EEPROM, controller type [int]
Explanation The ID EEPROM on the RSP is missing or invalid. This condition might be caused by a manufacturing error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-INVQPTR : queue=[hex], bufhdr [hex]: [hex] [hex] [hex] [hex]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-INVRTN : Invalid return queue next=[hex], hwidb=[hex], type=[hex] queue_ptr=[hex], bufhdr_offset=[hex], id=[dec], bcast_id=[dec] bufhdr [hex]: [hex] [hex] [hex] [hex]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-INVRTNBCASTID : Invalid return queue bcast_id=[dec] bufhdr [hex]: [hex] [hex] [hex] [hex]
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-IPC : [chars] [chars]
Explanation An IPC error has occurred. The exact nature of the problem is described in the error message.
Recommended Action Copy the router configuration along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-IP_PANIC : Panic: [chars] [hex] [hex] [hex] [hex]
Explanation The status message handler for the interface processor has detected that the firmware for the interface processor has experienced a critical condition. The name of the affected interface and the first four words of the status message buffer will be displayed, along with the message, for diagnostics.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSP-3-LOVEGIANT : Card [chars] wants [dec] byte love letters, but only got [dec] bytes
Explanation An inconsistency between the microcode and the system code has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-LOVENOTE : [hex] corrupt: [hex] [hex] [hex] [hex]
Explanation The event handler at the RSP has detected a status update message from an interface processor, but the field in the status message that identifies the associated interface processor is not valid. This condition indicates that the status message is corrupted. This error could occur because of a hardware or a software problem. The address of the status message buffer and the first four words of the message will be displayed for diagnostic purposes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSP-3-MSDOG : Master/slave watchdog timed out
Explanation While handling the interrupts from the DBUS FPGA, the RSP has detected that the timeout bit in the interrupt status register has been set. This condition indicates that the master RSP no longer controls the CBus and DBus. The slave may become active during this time, so the rest of the interrupt handler will not be processed. This behavior could be the result of either a hardware or a software problem.
Recommended Action Copy the error message exactly as it appears. If this problem recurs, copy down the router configuration along with any other relevant information, such as the output of show tech-support and show logging commands. Contact your Cisco technical support representative for assistance, and provide the representative with the gathered information.
Error Message%RSP-3-MSFIX : Fixing [chars] by setting to default [chars]
Explanation The characters shown can be either on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform to these specifications. This mismatch has most likely occurred because a new RSP was being installed and booted in an HSA environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message might result from a previous IPC error that occurred while the HSA environment was being reconfigured.
Recommended Action Perform the following steps:
a.
b.
If the slot number obtained in step 1 is the same as the number obtained in step 2, then no further action is required. You have configured HSA in simple hardware backup mode, and both RSPs are identical. However, if the two slot numbers differ, you have configured HSA in software error protection mode, and you will have different images running, depending on which RSP is currently the slave RSP.
If the slot numbers discovered in steps 1 and 2 differ, reload the router image to ensure that the desired system image is running. After the reload, the actual slave RSP will match the default slave RSP in the system configuration file.
For details about various HSA configuration modes, refer to the Cisco IOS Configuration Fundamentals Configuration Guide.
Error Message%RSP-3-MSVERS : Master has m/s version [dec], slave has m/s version [dec]
Explanation The master and slave are running software versions that are incompatible with the master/slave exchange process.
Recommended Action If the slave image global configuration is used to override the default slave image from the bundle, the slave image is incompatible. Update either the master or slave image to ensure that the two are compatible. If the slave is running the image from the bundle, enter and record the output of the show version, show running-config, and show controller cbus commands. Report this information and the error message to your Cisco technical support representative.
Error Message%RSP-3-NOIDB : bad vc [int] on [chars]
Explanation A channelized interface driver received a packet on an unconfigured channel.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSP-3-NOMAC : Can't allocate MAC address for interface [int]/[int]
Explanation No MAC address was available for allocation to the specified interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-2-NOMEMORY : No memory available for [chars]
Explanation An attempt to allocate memory has failed.
Recommended Action Try one or more of the following actions:
–
–
–
–
Error Message%RSP-3-NORESTART : [chars]: unable to schedule restart for output queue
Explanation A software or hardware error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-NOSTART : No microcode for [chars] card, slot [int]
Explanation No microcode is defined or available for the specified card.
Recommended Action Reconfigure the card to specify an existing microcode file.
Error Message%RSP-2-QADIAG : QA Diagnostic [chars] error at [hex]
Explanation An error has occurred during an attempt to access the RSP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSP-2-QAERROR : [chars] error, [chars] at addr [hex] ([chars])
log [hex], data [hex] [hex]Explanation While the system was attempting to process a hardware queue, an error was detected by the QA ASIC. The error could be either a zero link error or a reuse error. A zero link error is caused by an attempt to place in the hardware queue a buffer header with an address of 0x0. A reuse error occurs when the QA ASIC detects or attempts to place in the hardware queue a buffer header that is the same as another buffer header in another hardware queue. Either of these errors can occur because of a software or hardware problem with the RSP or a line card.
Recommended Action Enter the show logging command and view the output to see whether any parity errors were recorded just before the QAERROR error message was received. If any parity error was recorded before the QAERROR error message, a hardware error has occurred. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information. If no parity error was recorded and the problem recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-RESTART : NULL
Explanation The CBus buffer memory has been reset and reallocated. The exact nature of the problem is described in the message text.
Recommended Action Reset the memory manually (by changing the MTU on an interface, for example). If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-4-RSPDRAM : Insufficient DRAM to adequately run this IOS version. [dec]M is recommended.
Explanation The quantity of DRAM for the RSP is lower than the recommended amount.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RSP-3-SLAVE_NVRAM_BUSY : Slave NVRAM is temporarily busy
Explanation Another process is temporarily locking the slave configuration.
Recommended Action Retry the command that caused the error message. If this message recurs, check for other EXEC processes by entering the show users command. If no other users are locking the slave NVRAM, contact your Cisco technical support representative for assistance.
Error Message%RSP-3-SLAVECHANGE : Slave changed state from [chars] to [chars]
Explanation The slave RSP has undergone a hardware state change. Both the old state and new state are shown. Possible state changes indicated by the above message are the following: any to unplugged, unplugged to nonparticipant, slave nonparticipant to slave, or slave to nonparticipant. Any other combination is unexpected.
Recommended Action If the slave RSP has been removed, consider reinstalling the RSP if continued HSA operation is required. If the RSP is present, ensure that the slave RSP is properly seated in the card cage. If a slave RSP was installed, configure the router for HSA. Refer to the chapter "Loading System Images and Configuration Files" (Cisco 7500 series only) in the Cisco IOS Configuration Fundamentals Configuration Guide for more details. In particular, use the slave sync config command to ensure that the new slave RSP is configured consistently with the current master RSP.
Caution
Possibly, a previously crashed slave RSP was reset, or a newly installed slave RSP is in transition from unplugged to nonparticipant, and finally to slave state. In this case, no action is required. The slave RSP image has crashed. Log in to the slave RSP console using the if-console slot command. You will now be connected to the ROM monitor prompt on the slave RSP. Diagnose the slave RSP failure (for example, capture the output from the stack and context ROM monitor commands). Provide that information to your Cisco technical support representative with the router configuration and any other relevant information so that the problem can be investigated. Log out from the slave route RSP console port using a Ctrl-c or Ctrl-z key sequence, and enter the slave reload command in global configuration mode on the master RSP to bring the slave RSP back online. All other state changes indicate a software or hardware error.
Error Message%RSP-3-SLAVECOPYFAILED : Copy of [chars] failed, ([chars]).
Explanation The copy of the file sent to the slave has failed.
Recommended Action Ensure that the corresponding slave device exists and has available memory.
Error Message%RSP-3-SLAVEMASTER : Slave stole mastership
Explanation The master RSP has detected that the slave RSP configuration was changed from slave to master. The old master RSP will reload and become the slave RSP, allowing the new master RSP to take over. This behavior indicates a software or hardware error.
Recommended Action Copy the router configuration, along with any other relevant information. Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-4-SLAVENOTUPDATED : Slave configuration not updated for [chars].
Explanation The configuration on the slave RSP cannot be synchronized with the master RSP.
Recommended Action Ensure that the slave auto-sync config command has been entered to configure the slave RSP and that the slave RSP is active.
Error Message%RSP-4-SLAVETIME : [chars]
Explanation A failure has occurred during an update of the reload time on the slave. Because of this, the slave might show a different reload time and a large bootup time.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-5-SLAVEUP : Slave changed to state Running, Buffer memory state : [chars]
Explanation The slave RSP has started running the slave RSP image. This informational message appears after the router boots or after the slave reload global configuration command is issued on the master RSP.
Recommended Action No action is required.
Error Message%RSP-2-STALL : partially inserted or removed IPs on cyBus[int]
Explanation The RSP has detected a stall condition of the CBus.Most likely a board is not fully seated in the chassis. A less likely possibility is a hardware problem with the RSP or backplane.
Recommended Action Try reseating the boards. If this message persists, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSP-3-XBUFHDR : corrupt bufhdr [hex]: [hex] [hex] [hex] [hex]
Explanation A miscommunication has occurred between the RSP and an IP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
RSRB Messages
The following are remote source-route bridging messages.
Error Message%RSRB-4-BADLEN : Peer [chars], [chars], bad length [dec], trn [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-BADLENIP : Peer [dec]/[IP_address], [chars], bad length [dec], trn [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-3-BADVERSIONFST : FSTin: [chars]: version mismatch, mine [dec], theirs [dec]
Explanation The remote end of a direct serial peer is running the wrong version of the system software. This condition might occur if the local end, the remote end, or both ends are not up to date.
Recommended Action Contact your Cisco technical support representative to obtain an update.
Error Message%RSRB-3-BADVERSIONIF : IFin: [chars]: version mismatch, mine [dec], theirs [dec]
Explanation The remote end of a direct serial peer is running the wrong version of the system software. This condition might occur if the local end, the remote end, or both ends are not current.
Recommended Action Contact your Cisco technical support representative to obtain an update.
Error Message%RSRB-3-BADVERSIONTCP : [chars]: [dec]/[IP_address]: version mismatch, mine [dec], theirs [dec]
Explanation The remote end of a TCP remote peer is running the wrong version of the system software. This condition might occur if the local end, the remote end, or both ends are not up to date.
Recommended Action Contact your Cisco technical support representative to obtain an update.
Error Message%RSRB-4-BADVRE : Bad vre type
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-CONIPST : Peer [dec]/[IP_address], CONN, illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-CONNILLSTATE : Peer [chars], CONN, illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-CONNSTAT : Peer [chars], IFin, bad connection state [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-3-FSTERR : [chars]: [chars]: [IP_address], op [hex], len [dec], trn [dec]
Explanation The remote end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message%RSRB-3-HDRNOVRP : Peer [IP_address], HDR, no vrp
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-HDRRECV : Peer [dec]/[IP_address], HDR, recv state invalid, not empty [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-3-HDRVRP : Peer [dec]/[IP_address], HDR, vrp state wrong, [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-3-IFERR : [chars]: [chars]: [chars], op [hex], len [dec], trn [dec]
Explanation The remote end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration. The destination target ring is denoted by the value of trn.
Error Message%RSRB-4-ILLPEER : Peer [chars] [[hex]], illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-LOCAL : Unit [dec], local/vring set simultaneously, vrn [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-3-NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be completed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RSRB-3-NOTREM : Null idb and not remote
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-OPTNULL : Remopened and t NULL
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-PEERSTAT : Peer [chars], wrong state [dec]
Explanation An internal software error has occurred.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSRB-4-RNGXFAIL : Ring exchange failure, resetting peer: [chars]
Explanation The RSRB peer initiation logic has failed because of a memory shortage or a congestion condition.
Recommended Action No action is required. The problem should clear, and the peers should reopen without operator intervention.
Error Message%RSRB-3-SENDPUNTFST : [chars]: sent [chars] to [chars]
Explanation The local end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
Error Message%RSRB-3-SENDPUNTIF : [chars]: sent [chars] to [chars]
Explanation The local end of a direct serial RSRB connection has detected a configuration problem or traffic that is not recognized by the configuration.
Recommended Action Examine the configuration on both sides of the serial connection for possible problems. Examine the traffic being offered for propagation with respect to the configuration.
RSVP Messages
The following are RSVP protocol messages.
Error Message%RSVP-3-BAD_RMSG_TIMER : Inconsistent rsvp reliable message timer
Explanation The summary refresh timer may be blocked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_COOKIE : [chars] message from [IP_address] discarded - challenge failed for key ID [chars]
Explanation The router sent an RSVP message to an untrusted source. The message was a challenge to the untrusted source to compute a secure hash on a random piece of data and return the hash with the same data. The source did not return the expected data. RSVP discarded the response because the untrusted source might be (unsuccessfully) attempting an RSVP challenge response replay attack.
Recommended Action If you can verify that the source is trusted, it is possible that the source has malfunctioned; in this case, copy the error message exactly as it appears on the console or in the system log, enter the show tech-support rsvp command to gather data which may help identify the nature of the error, contact your Cisco technical support representative, and provide the representative with the gathered information. Otherwise, attempt to find and disable the untrusted source.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DIGEST : [chars] message from [IP_address] discarded - incorrect message digest
Explanation The router received an RSVP message that contained a different secure hash than the one that was computed by the router. RSVP discarded the message because the message may have come from an untrusted source.
Recommended Action Check the configuration on the router and on the sending system to ensure that they are using the correct security key and secure hash algorithm.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_DUP : [chars] message from [IP_address] discarded - authentication seq #[int] is a duplicate
Explanation The router received an RSVP message with an authentication sequence number that has already been seen. RSVP discarded the message because an untrusted source may be unsuccessfully attempting an RSVP message replay attack.
Recommended Action If you can verify that the source is trusted, it is possible that the source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source unsuccessfully attempting an RSVP message replay attack; in this case, attempt to find and disable the untrusted source.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_NO_SA : [chars] message from [IP_address] discarded: no security association for [IP_address] - no RSVP security key configured or no memory left.
Explanation The router received an RSVP message that contained a secure hash but dropped the message because the router was not able to create a security association for the sending system.
Recommended Action Check the configuration on the router to ensure that RSVP has access to a security key for the sending system. If such a key is configured, then check to see if the router has run out of memory.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_AUTH_WIN : [chars] message from [IP_address] discarded - seq #[int] outside authentication window
Explanation The router received an RSVP message whose authentication sequence number is less than the lower limit of the out-of-order window. RSVP discarded the message because an untrusted source may be unsuccessfully attempting an RSVP message replay attack.
Recommended Action It is possible that a trusted source is sending a burst of reordered RSVP messages that is too large for the authentication window size. If you can verify that the source is trusted and its messages are being sent in large reordered bursts, use the ip rsvp authentication window-size command to increase the window size on the receiving router. It is also possible that a trusted source has rebooted and its clock has gone backward in time; in this case, the source should be configured to synchronize its clock with an NTP server. Otherwise, the sender could be an untrusted source unsuccessfully attempting an RSVP message replay attack; in this case, attempt to find and disable the untrusted source.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_CHECKSUM : RSVP Message had a bad checksum: [dec] foo: [dec]
Explanation The router has received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_LEN : RSVP Message had a bad length ip len: [dec] rsvp len: [dec]
Explanation The router has received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_OBJ_LEN : Received a bad RSVP message, num objs: [dec] obj len: [dec] msg_len: [dec]
Explanation The router has received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_TYPE : RSVP Message had a bad type: [dec]
Explanation The router has received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-3-BAD_RSVP_MSG_RCVD_VER : RSVP Message had a bad version: [dec]
Explanation The router has received an incorrect RSVP message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-5-CLEAR_COUNTERS : Clear rsvp message counters by [chars]
Explanation The RSVP message counters have been cleared.
Recommended Action No action is required.
Error Message%RSVP-3-CONSISTENCY : [chars]: [chars] [chars] [chars]
Explanation An action attempted by the RSVP implementation has encountered an unexpected condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support rsvp command to gather data which may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support rsvp command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RSVP-3-IP_HDR : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This message is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy all messages exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSVP-3-MSG_1 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This message is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy all messages exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSVP-3-MSG_2 : [hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation This message is an auxiliary message to several packet-related messages. It provides a raw display of the information in the header of a corrupted data block.
Recommended Action This message provides additional information only. Copy all messages exactly as they appear on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RSVP-3-RSVP_MSG_AUTH_CHALLENGE_TIMEOUT : No response to challenge issued to [IP_address] for key ID [chars]
Explanation The router sent an RSVP message to challenge the untrusted source to compute a secure hash on a random piece of data and to return the hash with the same data, but the source did not reply. The source may have crashed or lost its network connection. However, it is also possible that the source was unsuccessfully attempting to replay an RSVP message before the challenge and gave up when it saw the challenge from the router.
Recommended Action If you can verify that the source is trusted, try to determine if it has crashed or lost its network connection, and then restore network connectivity to it. If the source repeatedly crashes when challenged, a temporary workaround might be to disable challenges on the router by issuing a no ip rsvp authentication challenge command until the problem on the source is resolved. Otherwise, assume that the source is untrusted and attempt to find and disable it.
RTT Messages
The following are round trip time monitor messages.
Error Message%RTT-3-BadLoc : %RTR: should not have reached rttmon_config_entry_command
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RTT-3-BufferInitFailed : RTR: Initialization of buffers failed!
Explanation The RTTMON process could not be started because of a low-memory condition.
Recommended Action Reduce the usage of resources in the configuration to resolve the memory shortage. After the memory shortage is resolved in the configuration, the system must be restarted because this error occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-4-ClockNotSet : 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 is not set.
Recommended Action Ensure that the system clock is functional by using NTP or another mechanism.
Error Message%RTT-4-ConfigFailed : 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-4-DuplicateEvent : RTR [dec]: Duplicate event received. Event number [dec]
Explanation An RTR process has received a duplicate event.
Recommended Action This is only a warning message. If this message recurs, enter the show rtr configuration command and copy the command output. Collect information about the application that is configuring and polling the Service Assurance Agent probes. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RTT-3-GlobalInitFailed : RTR 0: [chars] - Failed to initialize local storage
Explanation The RTTMON process could not be started because of a low-memory condition.
Recommended Action Reduce the usage of resources in the configuration to resolve the memory shortage. After the memory shortage is resolved in the configuration, the system must be restarted because this error occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-3-IcmpCallbackWithNullCntx : %RTR: recv NULL context from ICMP Echo Reply
Explanation An internal software error occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RTT-3-IcmpCallbackWithNullPtr : %RTR: recv NULL echo ptr from ICMP Echo Reply
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RTT-3-IPSLATHRESHOLD : IP SLA Monitor [dec] Threshold [chars] for [chars]
Explanation This informational message logs threshold violations in the Service Assurance Agent probe. This message appears when the rtr logging trap command is entered.
Recommended Action If this message is not necessary, enter the no rtr logging trap command to disable logging. Otherwise, no action is required.
Error Message%RTT-3-MissingEchoStruct : %RTR: failed to get EchoAdmin Struct
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RTT-3-MissingInit : %RTR: required initialization failed, thus cannot configure
Explanation Configuration of the RTTMON has failed because of the previously reported memory shortage.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-3-SAANOPROCESS : RTR: Cannot create a new process
Explanation RTR is unable to start a new process; RTR might not be running.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%RTT-3-SemaphoreBadUnlock : %RTR: Attempt to unlock semaphore by wrong RTR process [dec], locked by [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%RTT-3-SemaphoreInitFailed : RTR: Initialization of rttMonConfigSemaphore failed!
Explanation The RTTMON process could not be started because of a low-memory condition.
Recommended Action Reduce the use of resources in the configuration to resolve the memory shortage. After the memory shortage is resolved in the configuration, the system must be restarted because this error occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
%RTT-3-SemaphoreInUse : %RTR: Could not obtain a lock for RTR. Process [dec]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
RUDP Messages
The following are RUDP messages.
Error Message%RUDP-3-INIT : rudp [dec]: [chars][chars].
Explanation RUDP initialization has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%RUDP-4-LINK : rudp [dec]: [chars][chars].
Explanation A warning has been provided for a specific RUDP link.
Recommended Action This is a debug message only. No action is required.
Error Message%RUDP-4-NOBUF : rudp [dec]: cannot get packet buffer for [chars].
Explanation An RUDP link cannot allocate a packet buffer.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
S4T68360 Messages
The following are four-port synchronous serial adapter based on the 68360 processor messages.
Error Message%S4T68360-1-DWNLDCKSM : Failed for bay [dec], sent = [hex], received = [hex]
Explanation When the internal firmware is downloaded to the S4T68360, a system firmware verification revealed an invalid checksum. This condition might indicate a hardware failure of the S4T68360 or the VIP.
Recommended Action Power down and restart the system. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%S4T68360-1-DWNLDFAIL : Microcode to port adaptor in bay [dec]
Explanation The S4T hardware has failed. It could not download its operational microcode.
Recommended Action Try to reseat the PA properly in the system slots. If this error message recurs, verify for a hardware failure, including the chassis in the case of the Cisco 7200, or the VIP in the case of the RSP and the PA. This error will occur only if there is a hardware failure.
Error Message%S4T68360-1-INITFAIL : Bay [dec]: [chars]
Explanation The S4T port adapter has failed to complete is hardware initialization.
Recommended Action Try to reseat the PA properly in the system slots. If this error message recurs, verify for a hardware failure, including the chassis in the case of the Cisco 7200, or the VIP in the case of the RSP and the PA. This error will occur only if there is a hardware failure.
Error Message%S4T68360-3-MBXREAD : Bay [dec] stale msg [chars]- mbx0:[hex], mbx1:[hex], mbx2:[hex]
Explanation The S4T68360 has not responded to a message from the VIP within a specified time frame.
Recommended Action Perform a microcode reload for the VIP. If this problem recurs, it might indicate that the S4T68360 or VIP hardware has failed.
Error Message%S4T68360-1-NOTCMPLT : Microcode download to bay [dec] failed
Explanation The S4T68360 port adapter hardware has failed. The system was unable to acknowledge the completion of the operational microcode download.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%S4T68360-1-NOTREADY : Bay [dec] for microcode download
Explanation The S4T68360 port adapter hardware has failed. The S4T68360 port adapter could not download the operational microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%S4T68360-3-NOTS4T68360 : Bay [dec] device ID seen as [hex], expected [hex]
Explanation The S4T hardware has failed. A non-S4T device pointed at the software for the S4T.
Recommended Action Check the system configuration for the failure in the bay number that is reported. If the failure is not from an M4T PA, contact the appropriate component to which that PA in that slot belongs. If the failure is from an M4T PA, reseat the PA. If the error recurs, enter the show tech-support and show logging commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%S4T68360-3-OWNERR : [chars] packet buffer, pak=[hex]
Explanation A software or hardware error has occurred. The S4T driver detected that the transmit ring is an inconsistent state.
Recommended Action Enter the shutdown and no shutdown commands to shut down and restart the interface. If this problem recurs, perform an OIR of the PA. If the problem recurs, there might be a hardware failure. Verify for a hardware failure. Copy the error message exactly as it appears on the console or in the system log, enter the show tech and show log commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%S4T68360-3-PANIC : Bay [dec], Exception [dec], trace [dec]
Explanation The S4T68360 firmware has detected an unexpected CPU exception or condition. This condition might be caused by a software error or by a hardware failure.
Recommended Action Perform a microcode reload of the VIP. If the problem persists, it might indicate that the S4T68360 hardware has failed.
Error Message%S4T68360-1-RESTART : Bay [dec] port adaptor
Explanation The S4T68360 port adapter hardware has failed. The periodic check routine detected the failure and restarted it.
Recommended Action No action is required.
Error Message%S4T68360-5-RINGSIZE : [chars] TX packet dropped; particle count ([dec]) exceeds [dec]
Explanation A Tx packet has been dropped because the Tx ring was full. This condition normally occurs when the port adapter is overdriven.
Recommended Action No action is required.
Error Message%S4T68360-1-STARTFAIL : [chars] [chars]
Explanation A software or hardware error has occurred. The S4T interface is not responding to the commands that are used to initialize it. This failure is caused by S4T port initialization or reset failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%S4T68360-1-STOPFAIL : [chars] [chars]
Explanation The S4T port adapter failed to respond to a request to disable an interface. This failure is caused by S4T port initialization or reset failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support and show logging commands to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support and show logging command output, contact your Cisco technical support representative and provide the representative with the gathered information.
SARMGR Messages
The following are SARMGR messages.
Error Message%SARMGR-1-ANALYZE1575FAILED : The 1575 device analysis failed
Explanation The SARMGR has failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SARMGR-3-NOTNRPSARMGRDEV : Device reported [hex]
Explanation The PCI device ID was incorrect.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SBETH Messages
The following are MAC controller messages.
Error Message%SBETH-1-BAD_IDB : Invalid Interface Descriptor Block
Explanation The driver could not fetch the interface IDB. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_MEDIA : Unknown media-type in subblock
Explanation The media type specified in the driver subblock is invalid. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_PARTICLE : Problem getting particle size
Explanation The driver was unable to get the particle size for this interface. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_PLUGIN : Plugin function table incomplete or missing
Explanation The driver could not access the specific function table of the PA. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_POOL : Could not init buffer pools
Explanation The driver failed to get a pool of buffers from the Cisco IOS software. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_SB_NOMEM : [chars] - Cannot create IDB subblock due to insufficient memory
Explanation There was insufficient system memory to create the subblock.
Recommended Action The router requires more main memory.Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_STRUCT : Could not initialize structure
Explanation The driver failed to initialize a structure. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-BAD_SUBBLOCK : [chars] - Could not install or use IDB subblock
Explanation An internal software error prevented the IDB subblock from being installed or used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-3-ERRINT : [chars], error interrupt, mac_status = [hex]
Explanation The MAC controller has signaled an error condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-IDBTYPE_UNK : Unknown IDBTYPE while starting driver
Explanation The IDBTYPE in the interface instance structure is undefined for this driver. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-1-INITFAIL_NOMEM : [chars], initialization failed, no buffer memory
Explanation The Ethernet port initialization failed because of insufficient memory.
Recommended Action The router needs more packet memory. Consider upgrading the router. If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SBETH-1-MODE_INVALID : Unknown or invalid chip mode (MII/TBI)
Explanation The driver subblock contains an invalid or undefined chip operating mode (either MII or TBI mode). This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-2-NOISL : Interface [chars] does not support ISL
Explanation ISL is not supported on the specified interface hardware.
Recommended Action No action is required.
Error Message%SBETH-1-RESET : MAC Still in Reset
Explanation An attempt was made to access the MAC while it was being reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SBETH-3-TOOBIG : [chars], packet too big ([dec]), from [enet]
Explanation The interface has detected that a packet larger than what is defined by MTU has been received.
Recommended Action Check the MTU setting of the other station.
SCB Messages
The following Channel Interface Processor (CIP) messages are related to the storage control block.
Error Message%SCB-6-BADSCB : Request to free SCB 0 ignored
Explanation An attempt has been made to free SCB 0. This is an internal logic error. The request was ignored.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCB-6-RESUME : SCB on port [dec] available, correlator: [dec] task: [chars] [hex]
Explanation A task waiting for a channel SCB woke up. This message is typically preceded by the message, "SCB limit on port [dec] reached." The correlator value in this message and the following message indicate that the two messages form a pair. In most cases, the pair of messages indicates a burst of activity that resulted in an unusually long queue for the channel.
Recommended Action No action is required.
Error Message%SCB-6-WAIT : SCB limit on port [dec] reached, correlator: [dec] task: [chars] [hex]
Recommended Action A task tried to allocate a channel SCB when all blocks were in use. The task is now waiting for a block to become available. This message is typically followed by the message, "SCB on port [dec] available." The correlator value in this message and the following message indicate that the two messages form a pair. In most cases, the pair of messages indicates a burst of activity that resulted in an unusually long queue for the channel.
Recommended Action If this message is followed by any kind of indication that the CIP has stopped working properly, report it to your Cisco technical support representative, along with the output of the show extended channel / subchannel, show extended channel / statistics, show version, show running-config, and show controller cbus commands. In addition, check the MVS syslog and the TCPIP job log (or equivalent for other mainframe operating systems) for unusual channel-related messages. Pay particular attention to anything related to TCP/IP offload.
SCCP Messages
The following are Skinny Client Control Protocol (SCCP) messages.
Error Message%SCCP-1-ALERT : [chars]
Explanation A condition that should be corrected immediately has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCCP-2-CRITICAL : [chars]
Explanation A critical condition has occurred that should be corrected immediately.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCCP-6-DSPFARM_REGISTER_FAILED : Failed to register SCCP Application with DSPFARM\n
Explanation The system failed to register the SCCP Application with DSPFARM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-3-ERROR : [chars]
Explanation During the registration process to CCM, a device name for the Conf, Transcode, or MTP has not been specified or is mismatched in the CCM configuration.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-4-INFO : [chars]
Explanation An informational-level message involving SCCP has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-4-NOTICE : [chars]
Explanation A notice-level message involving SCCP has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-0-PANIC : [chars]
Explanation An unrecoverable internal panic event has occurred that should be resolved immediately.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCCP-6-SESS_REC_DATABASE_FAILED : Failed to create session record database\n
Explanation The system failed to create a session record database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCCP-4-WARNING : [chars]
Explanation An application was attempting to connect to the CCM while another application was attempting to connect to the CCM.
Recommended Action Once the lock has been released by the other application process, retry the operation to connect to the CCM.
SCHED Messages
The following are scheduler messages.
Error Message%SCHED-2-ATTRCMD : Attempt to [chars] attribute [chars] on process [dec].
Explanation An attempt has been made to set or get a private attribute that belongs to another process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-2-ATTRVALUE : Attempt to set bad [chars] value ([hex]) on process [dec]
Explanation An attempt has been made to set the specified attribute for a process to an invalid value.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-0-BADPRIORITY : Task priority of [dec] is not allowed
Explanation A request was made to create a task, but the priority level for the task was not valid. The task was not created.
Recommended Action Tasks get created either at CIP startup time or as a result of a configuration command. If this message was caused by a configuration command, the configuration command was rejected. If the error message was issued at CIP startup time, while system tasks were being created, the CIP may not be fully functional. Note the steps necessary to recreate the problem, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-3-CORRUPT : Scheduler '[chars]' corrupted by process [chars] (expected [hex], found [hex])
Explanation The scheduler has determined that its data structures were corrupted during the execution of the current process.This corruption is the result of a process action (multiple errors reported against the same process) or an interrupt driver (multiple errors reported against different processes).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-2-EDISMSCRIT : Critical/high priority process [chars] may not dismiss.
Explanation Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, although lower priority processes can use primitives from either the new or old scheduler. A higher priority process attempted to use an old scheduler primitive.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-INTSETWAKEUP : Invalid scheduler action ([chars]) at interrupt level
Explanation A process_set_wakeup_reasons has been attempted from an interrupt handler.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-0-INVLOCK1 : Invalied lock word of [dec] used in lock request
Explanation An attempt has been made to request a lock, but the lock word contained invalid data. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-INVLOCK2 : Invalied lock word of [dec] used in unlock request
Explanation An attempt has been made to unlock a lock, but the data in the lock word was not valid. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-3-LOSTWAKEUP : Wakeup information for process [chars] lost (maj [hex], min [hex]).
Explanation A process can register to be notified when various events occur in the router. An event for the specified process has been lost, and the router might not be functioning correctly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-2-MESSAGE : Key ([chars]) does not match key ([chars]) of process ([dec]) in process_send_message request
Explanation An attempt has been made to send a message to a process. The key associated with the process did not match the key in the message. This condition occurs when an incorrect process id is used in the send message request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-0-NMLDATA : tcb_addr = [hex] current_tcb = [hex] lock_value = [dec]
Explanation This message contains data that relates to the SCHED-0-NOTMYLOCK message.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-2-NOATTR : Attempt to [chars] unknown process attribute [dec].
Explanation An attempt has been made to set or get a nonexistent process attribute.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-0-NOLOCK : Attempt was made to unlock resource that wasn't locked
Explanation An attempt was made to unlock a lock that was not held. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-NOPROCID : No process id available for process creation
Explanation An attempt has been made to create one more task than the CIP is designed to allow. The task was not created.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, issue the show tech-support command, and provide the information to your Cisco technical support representative. If your running configuration shows that you are trying to use a supported number of configuration commands, the limit on the number of tasks on the CIP has to be increased.
Error Message%SCHED-0-NOSTACK : Could not allocate [dec] bytes for stack from memory
Explanation An attempt has been made to create a task, but sufficient memory was not available to contain the stack for the task. The task was not created.
Recommended Action If this message was caused by a configuration command, it is an indication that the CIP does not have enough memory to run it. Install more memory for the CIP, or configure fewer devices. If this message occurred at CIP startup time, it is an indication that the version of CIP microcode you are running is not supported on a CIP with the amount of memory you have installed. Install more memory for the CIP in this case.
Error Message%SCHED-0-NOTCB : Could not allocate [dec] bytes for tcb from memory
Explanation An attempt has been made to create a task, but sufficient memory was not available to contain the control block for the task. The task was not created.
Recommended Action If this message was caused by a configuration command, it is an indication that the CIP does not have enough memory to run it. Install more memory for the CIP, or configure fewer devices. If this message occurred at CIP startup time, it is an indication that the version of CIP microcode you are running is not supported on a CIP with the amount of memory you have installed. In this case, install more memory for the CIP.
Error Message%SCHED-0-NOTMYLOCK : Attempt was made to unlock another task's resource
Explanation An attempt has been made to unlock a lock that was set by another task. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-0-NOTPROCES : Attempt was made to lock while not at process level
Explanation An attempt has been made to lock a resource while not at the process level. This is a fatal internal logic error.
Recommended Action This error message is typically followed by a fatal error dump with code 37. Capture all the messages and issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCHED-2-NOTWATCHTIMER : [chars] timer [hex] not being watched.
Explanation A process can register to be notified when various events occur in the router. An attempt has been made to deregister a timer expiration event that is not currently registered.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-PAGEZERO : Low memory modified by [chars] ([hex] = [hex])
Explanation In all Cisco products, the first 256 bytes of memory are not used, and this area of memory is off limits. Newer platforms have hardware to immediately trap reads or writes to this area. Older platforms periodically check this memory. This message appears only on older platforms and indicates that this off-limits memory area has been modified.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-PRIORITY : Illegal priority ([dec]) specified for process [chars].
Explanation Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, although lower priority processes can use primitives from either the new or old scheduler. An attempt has been made to set the specified process to a priority level that is not allowed for the type of scheduler primitives being used.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-4-PROCESSTIME : Invalid argument ([dec] msec) for process_set_schedtime
Explanation An attempt was made to change the maximum time a process can run scheduling to an invalid value. The value should range between 20 ms and 200 ms.
Recommended Action Copy the error message exactly as it appears; include the stack trace; and report it to your technical support representative. If this message recurs, revert to a Cisco IOS software image that did not exhibit this behavior.
Error Message%SCHED-2-QUEUENOTEMPTY : Attempt to delete non-empty watched queue [chars] (address [hex]).
Explanation A process can register to be notified when various events occur in the router. An attempt has been made to destroy a queue that still contained items. These items are lost and not returned to free memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-2-SEMNOTLOCKED : [chars] attempted to unlock an unlocked semaphore
Explanation Some sections of code use semaphores to protect critical sections of software. An attempt was made to unlock a semaphore that was not locked.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-2-SEMUNLOCK : [chars] attempted to unlock semaphore owned by [chars].
Explanation Some sections of code use semaphores to protect critical sections of software. An attempt has been made to unlock a semaphore that was not owned by the process attempting to unlock it.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-2-SETHIGHORCRIT : Attempt to set [chars] priority on process [dec] ([chars])
Explanation Each process executes at a specified priority level. Higher priority processes must use the new scheduler primitives, although lower priority processes can use primitives from either the new or old scheduler. An attempt has been made to set the specified priority too high for a process using old scheduler primitives.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-STACKSIZE : Illegal stack size ([dec]) specified for process [chars].
Explanation Each process has its own stack space that must be one of several predefined sizes. An attempt has been made to specify an illegal stack size.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-STILLWATCHING : Process still watching [chars] [chars]
Explanation A process can register to be notified when various events occur in the router. A process destroyed a set of events without first individually removing each event in the set.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-STILLWATCHINGT : Process still watching [chars] timer [hex]
Explanation A process can register to be notified when various events occur in the router. A process destroyed a set of events without first individually removing each event in the set.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-STUCKMTMR : Sleep with expired managed timer [hex], time [time-stamp] ([time-stamp] ago).
Explanation A process can register to be notified when various events occur in the router. A registered timer has expired, and the timer value has remained unchanged after the process has been executed two successive times. This message indicates a software failure that does not impact the functionality of the router.
Recommended Action No action is required; however, to take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train.
Error Message%SCHED-3-STUCKTMR : Sleep with expired timer [hex], time [time-stamp] ([time-stamp] ago).
Explanation A process can register to be notified when various events occur in the router. A registered timer has expired, and the timer value has remained unchanged after the process has been executed two successive times. This message indicates a software failure that does not impact the functionality of the router.
Recommended Action No action is required; however, to take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train.
Error Message%SCHED-3-THRASHING : Process thrashing on watched [chars].
Explanation A process can register to be notified when various events occur in the router. The process has taken and released control of the processor 50 consecutive times, and not all outstanding events were processed. The systems will recover, and the functionality of the router is not affected.
Recommended Action If this message recurs, this error may be caused by a software failure. Note that these messages are not always caused by software failures but may be issued in response to either instantaneous or sustained demand on the router. Increased or persistent messages might indicate that the traffic load should be reviewed. If the router does not seem to be overloaded, consider upgrading your system to the latest Cisco IOS software release in your release train to take advantage of recent fixes. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show log, show tech-support, and show proc cpu commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-UNEXPECTEDEVENT : Process received unknown event (maj [hex], min [hex]).
Explanation A process can register to be notified when various events occur in the router. A process has received an event that it did not know how to handle. This message may be caused by a problem with the process receiving the event or with another process that has passed event numbers to the wrong process. This message indicates a software failure.
Recommended Action To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show tech-support, show log and show process commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-UNEXPECTEDMESSAGE : Unknown message [hex] received (ptr arg [hex], num arg [hex]).
Explanation A process can register to be notified when various events occur in the router. A process has received a message from another process that the process was unable to handle. This message may be caused by a problem with the process receiving this message, or with the other process passing a message to the wrong process. This message indicates a software failure.
Recommended Action To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If this problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show tech-support, show log, and show process commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-UNEXPECTEDQUEUE : Queue event for unknown queue (index [dec]).
Explanation A process can register to be notified when various events occur in the router. A process has received a queueing event for an unknown queue. This message indicates a software failure.
Recommended Action To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show tech-support, show log, and show process commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-3-UNEXPECTEDTIMER : Unknown timer expiration, timer = [hex], type [dec].
Explanation A process can register to be notified when various events occur in the router. A process has received a timer expiration event for an unknown timer. This message indicates a software failure.
Recommended Action To take advantage of recent fixes, upgrade your system to the latest Cisco IOS software release in your release train. If the problem persists, copy the error message text exactly as it appears on the console or in the system log, enter the show tech-support, show log, and show process commands, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SCHED-7-WATCH : Attempt to [chars] uninitialized watched [chars] (address [hex]).
Explanation A processes can register to be notified when various events occur. This message indicates that an attempt was made to register for an event without first creating the data structure for that event.
Recommended Action If this message recurs, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
SCP Messages
The following are downstream physical unit (DSPU) 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 did not receive SCP delivery acknowledgment from the SP after two retries.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCP-3-NOPROC : Cannot create SCP process.
Explanation The system does not have sufficient internal resources available to create the queue.
Recommended Action Check available memory capacity on the router. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SCP-3-NOQUEUE : Cannot create SCP Rx/Tx queue.
Explanation The system does not have sufficient internal resources available to create the queue.
Recommended Action Check available memory capacity on router. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%SCP-2-NOTREG : Process [dec]([chars]) not registered for SCP
Explanation The SCP application cannot send an SCP message because the application has not registered for a SAP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%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 error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%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. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SCP-3-UNKMSG : Unknown SCP message (opcode [hex]) received.
Explanation The remote peer has sent an unknown SCP message.
Recommended Action Check software compatibility between the peers.
SCP-SP
Error Message%SCP-SP-2-NOMEM : No memory available for [chars]
Explanation The SCP protocol system could not obtain the memory it needed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.SDLC Messages
The following are Synchronous Data Link Control (SDLC) messages.
Error Message%SDLC-4-BADFRAME : [chars], Received bad SDLC [chars]frame, address [hex], control [hex]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SDLC-3-CONFIGERR : [chars], addr [hex], Sent SNRM, received SNRM. Check link station roles.
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SDLC-4-CTRLBAD : Interface [chars], Invalid control field
Explanation A bad SDLC frame has been received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to the line.
Error Message%SDLC-3-DLU_ERROR : [chars], DLU failed to close station [hex] before re-opening, [chars]/[chars]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SDLC-4-DROPPED : Dropped SDLC packet from SDLC hold queue
Explanation An SDLC frame had to be dropped from the output hold queue. This condition can occur when there is excessive congestion on the output link.
Recommended Action If this message occurs frequently, determine why the SDLC link is being overloaded with data and resolve the cause. This condition can usually be resolved either by increasing bandwidth to the SDLC line or reducing the load on the link.
Error Message%SDLC-4-FRAMEERR : Interface [chars], Frame error: CF [hex], VS [dec] [char] VR [dec], Reason [hex]
Explanation A FRMR frame has been received. This error can be caused by a noisy serial line, an overloaded SDLC device, or corrupted data.
Recommended Action If this message recurs, service the serial line and the devices attached to the line.
Error Message%SDLC-2-ILLEGSTATE : [chars], illegal state for addr [hex], [chars]([dec])
Explanation An internal SDLC state violation has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SDLC-4-INFOBAD : Interface [chars], Info field not permitted
Explanation An invalid SDLC frame has been received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to the line.
Error Message%SDLC-4-INVLDGRPCFG : Interface [chars], ignoring group-poll mismatch, UPOLL [hex]
Explanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SDLC-5-INVLDGRPPOLL : Interface [chars], not configured for group-poll frame, received [hex]
Explanation A UP was received with the wrong group poll address.
Recommended Action Ensure that the group poll address that is configured on the router matches the group poll address that is configured in the PU macro (GP3174=XX) in the NCP generate file.
Error Message%SDLC-4-INVNR : Interface [chars], Invalid NR value
Explanation An invalid SDLC frame has been received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to the line.
Error Message%SDLC-4-N1TOOBIG : Interface [chars], N1 too large
Explanation An information frame has been received from the remote end of the SDLC link that was larger than the N1 parameter on this link allowed.
Recommended Action Either increase the value of the N1 parameter for this interface on the router or reduce the size of the maximum information frame that is sent by the remote end of the link.
Error Message%SDLC-3-NOINPIDB : Input idb not set
Explanation A frame has been given to the SDLC handler to process, but the interface on which the frame arrived is not known.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SDLC-2-NOPOINTER : AW_SDLC_SEC with no sdllc_llc pointer.
Explanation An error condition has occurred during an SDLLC initiation.
Recommended Action No action is required. The SDLLC session will restart without operator intervention.
Error Message%SDLC-4-NOUA : [chars], addr [hex] received command [hex] in response to SNRM, expected UA
Explanation The router has received a frame other than a UA in response to a SNRM.
Recommended Action Check the end station to see if the SNA stack is up and running.
Error Message%SDLC-3-NULLPAK : Interface [chars], NULL packet ptr, rvr [dec], vs [dec], vr [dec]
Explanation An internal software error has occurred in the SDLC processing system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that might help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%SDLC-4-SDLC_ERR : SDLC_ERROR with no poll
Explanation A protocol error has been detected on a secondary station, but FRMR could not be sent because the station did not own the poll bit. This condition might occur because of poor line conditions or a faulty SDLC implementation.
Recommended Action If this message recurs, run traces on the SDLC line. Copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the gathered information.
Error Message%SDLC-6-XID_DISPLAY : sa [enet] da [enet] ss [hex] ds [hex] [[hex][hex][hex][hex]]
Explanation This message supplies the information for the received and rejected XID.
Recommended Action This is a security feature. The additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
Error Message%SDLC-6-XID_FORMAT : Unsupported XID format received, format [dec]
Explanation An inappropriate XID format has been received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to ensure that they are supported.
Recommended Action This is a security feature. The additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
Error Message%SDLC-4-XID_NOMATCH : [chars], XID mismatch for [hex]. CONNECTION REJECTED
Explanation An inbound XID from a PU 2.0/PU 2.1 node has been rejected. The targeted SDLC address is displayed. The targeted SDLC address and the XID information is displayed in one of the following messages: "SDLLC-6-XID_DISPLAY" or "SDLLC-6-FORMAT."
Recommended Action This is a security feature. The additional information is displayed to help trace the source of the rejected XID. If the message is undesirable, simply remove the XID statement from the router configuration.
