-
Cisco IOS System Error Messages, Volume 2 of 2
-
About Cisco IOS Software
-
System Error Messages Overview
-
NPS_APS through POSDW
-
POSLC through PQUICC_ETHER
-
PQUICC_ETHERNET through RESOURCE_MON
-
RESYNCH through SDLC
-
SDLLC through SNAPSHOT
-
SNASW
-
SNMP through SW_VLAN
-
SYS through TCP
-
TDM through TXCONN
-
UBR7200 through VPD
-
VPDN through XTAGATM
-
CMCC System Error Messages
-
CMCC-ADAPTER
-
CMCC-BSQ through CMCC-DEBUGGER
-
CMCC-DIAG through CMCC-NEVADA
-
CMCC-OFFL through CMCC-XCPA
-
System Failure Messages
-
Glossary of Acronyms
-
Index
-
Table Of Contents
RESYNCH Messages
The following are RPM resynchronization process error 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 IP Routing Information Protocol (RIP) error 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 error 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 error 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.
ROUTEMAP_IPC Messages
The following are route map interprocess communication (IPC) error 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-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.
RPA Messages
The following are Resource Pool Allocation (RPA) error messages.
Error Message%RPA-3-FLEXIBLE : [chars]
Explanation This message is displayed for all error 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) error 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 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%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 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%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 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%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 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%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 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%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 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%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 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%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 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.
RPM Messages
The following are Route Processor Module (RPM) error messages.
Error Message%RPM-4-COOKIE : Corrupt or missing MAC address cookie using random base [enet]
Explanation The contents of the MAC address EEPROM are invalid. The system is providing random MAC addresses.
Recommended Action Copy the 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-NOCPUVER : Invalid CPU ID, assuming revision 1
Explanation The CPU ID could not be read from the EEPROM. This error is probably caused by 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%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 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-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 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.
RP_MLP Messages
The following are Distributed Point-to-Point Protocol (PPP) Multilink error messages.
Error Message%RP_MLP-4-MISCONFIGLINK : Links spread across VIPs, cant add, giving control to RSP
Explanation DMLP is giving control of a bundle to the RSP because DMLP cannot support the attempt to add links to this bundle, which has been spread across VIPs.
Recommended Action No action is required.
Error Message%RP_MLP-4-NODISTMLP : Failure downloading MLP bundle [chars] to the LC [dec]
Explanation The bundle is configured to be distributed, but the MLP configuration cannot be downloaded to the line card.
Recommended Action No action is required.
Error Message%RP_MLP-4-PANOTSUPPORTED : Adding Link from unsupported PA, cant add, giving control to RSP
Explanation An attempt to add links to a bundle from a port adapter that is not supported by DMLP has been made. DMLP is passing control of the bundle to the RSP.
Recommended Action No action is required.
RPM_VIRTUAL_PORT Messages
The following are Route Processor Module (RPM) virtual port error 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.
RPS Messages
The following are redundant power system error 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 error 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.
RSP Messages
The following are Route Switch Processor (RSP) error 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. End of MEMD buffer : [hex] End of datagram : [hex] bufhdr [hex]: [hex] [hex] [hex] [hex] Flushing Processor Cache
Explanation A packet was processed that was greater in size than the MTU size possible, 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, 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-4-COOKIE : Corrupt or missing MAC address cookie
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 : [chars]
Explanation An internal software error has occurred. 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-3-FOREVER : cmd [int] to [chars] (slot [int]) took [int] usecs, done [hex]
Explanation A command from the RSP to an IP took longer than expected.
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-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 Firmware for the interface processor has experienced a critical 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%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 This message indicates miscommunication between the RSP and an IP.
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-MSDOG : Master/slave watchdog timed out
Explanation The system software failed to reset the master/slave watchdog timer, which caused the timer to time out. This condition might indicate a software problem or a hardware problem.
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-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:
1.
Determine which slot contains the current slave RSP by entering the show version or show boot command.
2.
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 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, 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 A hardware error has occurred. The message will specify the buffer header address and queue pointer that were the cause of the failure. The most likely cause of this problem is a defective RSP (either master or slave), or a defective card.
Recommended Action If you have spare parts, try to swap the RSP or the cards to identify the faulty board. If you do not have any spare parts, or if you could not locate the defective card, contact your Cisco technical support representative with the detailed QAERROR diagnostic messages. This present message will be followed a list of QADIAG messages that give the number of elements in each hardware queue and duplicate buffer headers. A block of DMPMEM messages follow, which dump the buffer contents. Then another list of QADIAG messages will give information about the various queues of the interfaces present in the router. Provide all this information, along with the output of the show tech-support command, to your Cisco technical support representative.
Error Message%RSP-3-RESTART : [chars]
Explanation The cBus buffer memory has been reset and reallocated. The exact nature of the problem is described in the error message.
Recommended Action Report this error to your Cisco technical support representative if memory is not reset manually (for example, by changing the MTU on an interface).
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-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 has been changed from slave to master. The old master RSP will reload and become the slave RSP, which allows the new master RSP 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, 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-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-5-SLAVEUP : Slave changed to state Running
Explanation The slave RSP has started running the slave RSP image. This message appears after the user enters the router boots or slave reload commands in global configuration mode on the master RSP.
Recommended Action No action is required.
Error Message%RSP-2-STALL : partially inserted or removed IPs on cyBus[int]
Explanation This condition might occur if a board is not correctly seated in the chassis. This condition could also be caused by a hardware problem with the RSP or backplane. The second condition is unlikely to occur.
Recommended Action Try reseating the boards. 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-3-XBUFHDR : corrupt bufhdr [hex]: [hex] [hex] [hex] [hex]
Explanation A miscommunication 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, contact your Cisco technical support representative, and provide the representative with the gathered information.
RSRB Messages
The following are remote source-route bridging error 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.
RS_TDM Messages
The following are router shelf time-division multiplexing (TDM) error messages.
Error Message%RS_TDM-3-TDM_BACKPLANE_CLASH : Clash in usage for TDM backplane timeslot [dec]
Explanation The TDM backplane time slot to be allocated is already in use.
Recommended Action Check the split dial shelf settings on both router shelves for conflicting settings.
Error Message%RS_TDM-3-TDM_CONFLICT : TDM split user setting are in conflict: my RS [chars] = [dec], other RS [chars] = [dec]
Explanation The user setting for the TDM split on this router shelf is in conflict with the setting on the other router. More backplane DS0 settings are in use than the allowed maximum of 2048 DS0s.
Recommended Action Set the other router dial shelf split backplane DS0 to another setting within the range.
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-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-3-TDM_NOT_SPLIT_PAIR : TDM split user setting are not matched pairs my RS [chars] = [dec] ds0, expected other RS [chars] = [dec] ds0, actual other RS [chars] = [dec] ds0
Explanation The user setting for the TDM split on the specified router shelf is not compatible with the TDM split setting on the other specified router shelf.
Recommended Action Set the other router dial shelf split backplane DS0 to the same setting.
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_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.
RTT Messages
The following are Round Trip Time monitor error 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 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%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-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-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 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
