|
|
The following are Route Processor Module (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] = NULLExplanation A function has been called with an invalid NULL value for an input parameter. The error message will display specific information about this message.
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. The error message will display specific information about this message.
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. The error message will display specific information about this message.
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 specified reason. The error message will display specific information about this message.
Recommended Action No action is required.
Error Message
%RESYNCH-6-UPDATE_DELETE: Resynched connection [dec]/[dec] deletedExplanation The specified channel was resynched, and it was deleted from controller. The error message will display specific information about this message.
Recommended Action No action is required.
Error Message
%RESYNCH-3-UPDATE_NAKED: Update for channel [dec] was NAKedExplanation The controller has sent a negative acknowledgement (NAK) in response to an update for the specified channel. The error message will display specific information about this message.
Recommended Action No action is required.
Error Message
%RESYNCH-6-UPDATE_OK: Resynched connection [dec]/[dec] re-addedExplanation The specified channel has been resynched and re-added to the controller. The error message will display specific information about this message.
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. The error message will display specific information about this message.
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.
The following are IP Routing Information Protocol error messages.
Error Message
%RIP-3-NOSOCKET: Unable to open socketExplanation 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.
The following are Redundant Link Manager (RLM) messages.
Error Message
%RLM-3-INIT: rlm [dec]: [chars][chars]Explanation The Redundant Link Manager (RLM) initialization operation has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 a Redundant Link Manager (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 A Redundant Link Manager (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.
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, call 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 active.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RM-3-BOUNDARY: Memory boundary violationExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RM-3-NORESP: No response-code from local RMExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 queueExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RM-3-WAVL: Wavl errorExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RM-3-ZEROVAL: Uninitialized value being usedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are route map interprocess communication (IPC) error messages.
Error Message
%ROUTEMAP_IPC-2-NOMEMORY: Alloc fail for route-map ipc bufferExplanation The system is unable to allocate a memory buffer to send the route map configuration down to the line cards.
Recommended Action Enter the show chunks command, and report the command output and this error message to your Cisco technical support representative.
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 provide information to determine 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, call your Cisco technical support representative, and provide the representative with the gathered information.
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. The message will describe the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 channel associated signalling (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, call 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 ProcessExplanation A message type has been placed in the queue that is not known to the Resource Pool Allocation (RPA) channel associated signalling (CAS) process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Route Processor Module (RPM) error messages.
Error Message
%RPM-4-COOKIE: Corrupt or missing MAC address cookie using random base [sci_notation]Explanation The contents of the Media Access Control (MAC) address electrically erasable programmable read-only memory (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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RPM-4-NOCPUVER: Invalid CPU ID, assuming revision 1Explanation The CPU ID could not be read from the electrically erasable programmable read-only memory (EEPROM). This condition 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, call 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 Media Access Control (MAC) address allocation failed because of an incorrect slot and port combination that exceeded the maximum available hardware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RPM-4-PCIVALID: PCI activation failed, bay [dec], 0x[hex]Explanation The system has received an invalid protocol control information (PCI) signal from the port adapter. This condition 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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Route Processor Module (RPM) virtual port error messages.
Error Message
%RPM_VIRTUAL_PORT-3-CONNDEL: [chars]Explanation The delete request to the Processor/Switching Module (PXM) has failed, timed out, or been rejected by the PXM.
Recommended Action For a failure or time-out, the state of the connection is set to TIMEOUT, and the resynchronization process will periodically attempt to update the PXM. A request should not be rejected by the PXM. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RPM_VIRTUAL_PORT-3-CONNUPDATE: [chars]Explanation The reconfiguration request to the Processor/Switching Module (PXM) has failed, timed out, or been rejected by PXM.
Recommended Action For a failure or time-out, the state of the connection is set to the TIMEOUT state, and the resynchronization process will periodically attempt to update PXM. When a request is rejected by PXM, the connection state will be set to the FAILED state until the connection is deleted or reconfigured.
Error Message
%RPM_VIRTUAL_PORT-3-IPCERR: [chars] Error String = [chars]. Error Code = [dec]Explanation The remote call procedure (RPC) interprocess communication (IPC) request to the Processor/Switching Module (PXM) has failed or been rejected by the PXM.
Recommended Action If the error message indicates RPC-TIMEOUT, the last command entered must be retried later. For other error messages, copy the error message exactly as it appears on the console or in the system log, call 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 ipc_get_pak message failed. This condition might be caused by insufficient memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 size of the message that has been sent to or received from the Processor/Switching Module (PXM) is too large.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 remote procedure call (RPC) request from a Virtual-Port or Resync process is not valid. This error should never occur.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 FW error has occured.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are redundant power system error messages.
Error Message
%RPS-3-DCOUTPUTVOLTFAIL: System detected Redundant Power System DC Output Voltage failure conditionExplanation 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 normalExplanation 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 conditionExplanation The redundant power system experienced a fan failure.
Recommended Action The redundant power supply should be replaced.
Error Message
%RPS-3-FANOK: Redundant Power System FAN condition is now normalExplanation The redundant power supply previously detected a fan failure condition that has now returned to normal conditions.
Recommended Action The redundant power system fan is now normal. No action is required.
Error Message
%RPS-3-INPUTVOLTFAIL: System detected Redundant Power System Input Voltage failure conditionExplanation The redundant power system 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.
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 normalExplanation 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 immediatelyExplanation 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 normalExplanation The system previously detected a high temperature condition that has now returned to normal temperature condition. This might be caused by high ambient temperature where the router is located.
Recommended Action The system is operating at a normal temperature. No action is required.
Error Message
%RPS-3-OVERVOLT: Redundant Power System detected OVERVOLTAGE conditionExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RPS-3-RPSOK: Redundant Power System is now normalExplanation 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 conditionExplanation 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 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 a normal temperature condition. This is most likely 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 normalExplanation The redundant power system voltage is now normal.
Recommended Action The redundant power system previously detected an over voltage condition that has now cleared.
The following are Routing with Resource Reservation (RRR) path calculation error messages.
Error Message
%RRR_PCALC-2-PCALC_DUP_IP_ADDRESS: [chars] [int] [chars]Explanation Two nodes share the same IP address.
Recommended Action Find the system that has the duplicate IP address and configure a different IP address.
Error Message
%RRR_PCALC-2-PCALC_DUP_RRR_ID: [chars] [int] [chars]Explanation Two nodes share the same router ID.
Recommended Action Find the system that has the duplicate router ID and configure a different router ID.
Error Message
%RRR_PCALC-3-PCALC_INIT: [chars]: rrr_pcalc_system_id_size == 0Explanation An internal inconsistency has been detected when an attempt was made to initialize the Routing with Resource Reservation (RRR) path calculation system ID before the system_id_size was known.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RRR_PCALC-3-PCALC_LSA: [chars] [chars]Explanation An internal inconsistency has been detected during an attempt to establish a link-state advertisement (LSA) for the Routing with Resource Reservation (RRR) topology database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RRR_PCALC-2-PCALC_MEM: [chars] [dec]Explanation A failure has been detected during an attempt to allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RRR_PCALC-3-PCALC_PATH: [chars]Explanation An internal inconsistency has been detected during an attempt to establish an Routing with Resource Reservation (RRR) tunnel using the RRR path calculation subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
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, call 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 has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-2-BADCACHE: Overrun detected. End of MEMD buffer : 0x[hex] End of datagram : 0x[hex] bufhdr [hex]: [hex] [hex] [hex] [hex] Flushing Processor CacheExplanation A packet was processed that was greater in size than the maximum transmission unit 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, call 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 Route Switch Processor (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 interprocess communication (IPC) message.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-4-COOKIE: Corrupt or missing MAC address cookieExplanation The Media Access Control (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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-3-ERROR: NULLExplanation An internal software error has occurred. This message will provide information about the software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 Route Switch Processor (RSP) to an IP took longer than expected.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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]MBExplanation The system has detected a memory size mismatch between a master and slave Route Switch Processor (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 HSAExplanation High system availability (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 electrically erasable programmable read-only memory (EEPROM) on the Route Switch Processor (RSP) is missing or bad. This condition might be caused by a manufacturing error.
Recommended Action Report this error to your Cisco technical support representative.
Error Message
%RSP-3-INVQPTR: queue=[hex], bufhdr [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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-3-INVRTN: Invalid return queueExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-3-INVRTNBCASTID: Invalid return queue bcast_id=[dec]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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-3-IPC: [chars] [chars]Explanation An interprocess communication (IPC) error has occurred. This message will provide information about the error.
Recommended Action Copy the error message exactly as it appears. Copy down the router configuration along with any other relevant information. Contact your Cisco technical support representative for assistance.
Error Message
%RSP-3-IP_PANIC: Panic: [chars] [hex] [hex] [hex] [hex]Explanation Firmware for the interface processor 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 might provide information to determine the nature of the error. 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] bytesExplanation 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, call 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 error indicates miscommunication between the Route Switch Processor (RSP) and an IP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-3-MSDOG: Master/slave watchdog timed outExplanation 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 error message exactly as it appears. Copy down the router configuration along with any other relevant information. Contact your Cisco technical support representative for assistance.
Error Message
%RSP-3-MSFIX: Fixing [chars] by setting to default [chars]Explanation The characters shown can be either on the slave Route Switch Processor (RSP) setting or on the master RSP setting. The read-only memory (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. This0 mismatch has most likely occurred because a new RSP was being installed and booted in a high system availability (HSA) environment (dual RSPs) for the first time. Alternatively, in established HSA configurations, this message might result from a previous interprocess communication (IPC) error that occurred while the HSA environment was being reconfigured.
Recommended Action Follow these steps:
Step 1 Determine which slot contains the current slave RSP by entering the show version or show boot command.
Step 2 Determine which slot has been specified as the default slave RSP by entering the show configuration command. If there is no slave default-slot n command in the configuration file, the value defaults to the highest numbered CPU slot (slot 3 on a Cisco 7507 RSP, and slot 7 on a Cisco 7513 RSP).
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 of various HSA configuration modes, consult the Cisco IOS Configuration Fundamentals Configuration Guide. See the "Loading System Images and Configuration Files" chapter (Cisco 7500 series only).
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, then 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 might provide information to determine the nature of the error. Contact your Cisco technical support representative and provide the representative with the gathered d information.
Error Message
%RSP-3-NOMAC: Can't allocate MAC address for interface [int]/[int]Explanation No Media Access Control (MAC) address was available for allocation to the specified interface.
Recommended Action Report this error to your Cisco technical support representative.
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 queueExplanation 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, call 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 occured while accessing the Route Switch Processor (RSP).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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])Explanation A software error was detected during packet switching.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSP-3-RESTART: NULLExplanation The cBus buffer memory has been reset and reallocated.
Recommended Action Report this error to your Cisco technical support representative if memory is not reset manually (for example, by changing the maximum transmission unit 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 Route Switch Processor (RSP) is lower than the recommended amount.
Recommended Action If conditions warrant, upgrade to a larger memory configuration.
Error Message
%RSP-3-SLAVECHANGE: Slave changed state from [chars] to [chars]Explanation The slave Route Switch Processor (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: 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 high system availability (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. See 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 Failure to ensure a consistent configuration on a freshly installed slave RSP might result in undefined behavior if the router reloads. |
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. Provide the router configuration and any other relevant information to your Cisco technical support representative so that the problem can be investigated.
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 mastershipExplanation The master Route Switch Processor (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 to take over. This behavior indicates a software or hardware error.
Recommended Action Copy the error message exactly as it appears. Copy down the router configuration along with any other relevant information. Contact your Cisco technical support representative for assistance.
Error Message
%RSP-4-SLAVENOTUPDATED: Slave configuration not updated for [chars].Explanation The configuration on the slave Route Switch Processor (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-5-SLAVEUP: Slave changed to state RunningExplanation The slave Route Switch Processor (RSP) has started running the slave RSP. 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 required.
Error Message
%RSP-3-SLAVE_NVRAM_BUSY: Slave NVRAM is temporarily busyExplanation Another process is temporarily locking the slave configuration.
Recommended Action Retry the command that caused the error message. If the error message recurs, check for other EXEC processes by entering the show users command. If you know that there are no other users locking the slave NVRAM, contact your Cisco technical support representative for assistance.
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 Route Switch Processor (RSP) or backplane. The second condition is unlikely to occur.
Recommended Action Try reseating the boards. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 Route Switch Processor (RSP) and an IP.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are remote source-route bridging (RSRB) 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSRB-4-BADLENIP: Peer [dec]/[int], [chars], bad length [dec], trn [dec]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 receive an update.
Error Message
%RSRB-3-BADVERSIONTCP: [chars]: [dec]/[int]: version mismatch, mine [dec], theirs [dec]Explanation The remote end of a TCP remote peer is running the wrong version of the system software. Either the local end, the remote end, or both are not current.
Recommended Action Contact your Cisco technical support representative to receive an update.
Error Message
%RSRB-4-BADVRE: Bad vre typeExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSRB-4-CONIPST: Peer [dec]/[int], CONN, illegal state [dec]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSRB-3-FSTERR: [chars]: [chars]: [int], op [hex], len [dec], trn [dec]Explanation The remote end of a direct serial remote source-route bridging (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 [int], HDR, no vrpExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSRB-4-HDRRECV: Peer [dec]/[int], HDR, recv state invalid, not empty [dec]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSRB-3-HDRVRP: Peer [dec]/[int], HDR, vrp state wrong, [dec]Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 remote source-route bridging (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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 remoteExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%RSRB-4-OPTNULL: Remopened and t NULLExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 remote source-route bridging (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 re-open without operator intervention.
Error Message
%RSRB-3-SENDPUNTFST: [chars]: sent [chars] to [chars]Explanation The local end of a direct serial remote source-route bridging (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 remote source-route bridging (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 following are round trip time (RTT) monitor error messages.
Error Message
%RTT-3-BadLoc: %%RTR: should not have reached rttmon_config_entry_commandExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might help determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%RTT-3-BufferInitFailed: RTR: Initialization of buffers failed!Explanation The Round Trip Time Monitor (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. Once the memory shortage is resolved in the configuration, the system must be restarted because this error has 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 storageExplanation The Round Trip Time Monitor (RTTMON) process could not be started because of a low-memory condition.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage. Once the memory shortage is resolved in the configuration, the system must be restarted because this error has 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 StructExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%RTT-3-MissingInit: %%RTR: required initialization failed, thus cannot configureExplanation Configuration of the Round Trip Time Monitor (RTTMON) has failed because of the previously-reported memory shortage.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message
%RTT-3-SemaphoreInitFailed: RTR: Initialization of rttMonConfigSemaphore failed!Explanation The Round Trip Time Monitor (RTTMON) process could not be started because of a low-memory condition.
Recommended Action Reduce usage of resources in the configuration to resolve the memory shortage. Once the memory shortage is resolved in the configuration, the system must be restarted because this error has occurred during system initialization. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
The following error messages are for the four-port synchronous serial adapter based on the 68360 processor.
Error Message
%S4T68360-1-DWNLDCKSM: Failed for bay [dec], sent = 0x[hex], received = 0x[hex]Explanation When downloading the internal firmware to the S4T68360, a system firmware verification revealed an invalid checksum. This condition might indicate a hardware failure of the S4T68360 or the Versatile Interface Processor (VIP).
Recommended Action Power down and restart the system. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 S4T68360 hardware has failed. It could not download the operational microcode.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%S4T68360-1-INITFAIL: Bay [dec]: [chars]Explanation The S4T68360 port adapter has failed to complete the hardware initialization.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%S4T68360-3-MBXREAD: Bay [dec] stale msg [chars]- mbx0:%lx, mbx1:%lx, mbx2:%lxExplanation The S4T68360 has not responded to a message from the Versatile Interface Processor (VIP) within a specified time frame.
Recommended Action Perform a microcode reload for the VIP. If the problem recurs, it might indicate that the S4T68360 or VIP hardware failed.
Error Message
%S4T68360-1-NOTCMPLT: Microcode download to bay [dec] failedExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%S4T68360-1-NOTREADY: Bay [dec] for microcode downloadExplanation 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, call 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 S4T68360 hardware failed. A non-S4T68360 device pointed at S4T68360 software.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%S4T68360-3-OWNERR: [chars] packet buffer, pak=0x[hex]Explanation A software or hardware error has occurred. The S4T68360 driver detected that the transmit ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 Versatile Interface Processor (VIP). If the problem persists, it might indicate that the S4T68360 hardware failed.
Error Message
%S4T68360-1-RESTART: Bay [dec] port adaptorExplanation The S4T68360 port adapter hardware has failed. The periodic check routine detected the failure and restarted.
Recommended Action No action is required.
Error Message
%S4T68360-5-RINGSIZE: [chars] TX packet dropped; particle count ([dec]) exceeds [dec]Explanation A transmit (TX) packet has been dropped because the TX ring was full. This condition normally occurs when the port adapter is over driven.
Recommended Action No action is required.
Error Message
%S4T68360-1-STARTFAIL: [chars] [chars]Explanation A software or hardware error has occurred. The S4T68360 interface is not responding to initialization commands.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%S4T68360-1-STOPFAIL: [chars] [chars]Explanation The S4T68360 port adapter has failed to respond to a request to disable an interface.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are segmentation and reassembly manager (SARMGR) error messages.
Error Message
%SARMGR-1-ANALYZE1575FAILED: The 1575 device analysis failedExplanation The segmentation and reassembly manager (SARMGR) has failed to initialize.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SARMGR-3-NOTNRPSARMGRDEV: Device reported [hex]Explanation The protocol control information (PCI) device ID was not correct.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are scheduler error 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, call 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, call 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, call 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, while 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SCHED-3-INTSETWAKEUP: Invalid scheduler action ([chars]) at interrupt levelExplanation A process_set_wakeup_reasons has been attempted from an interrupt handler.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call 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 properly.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 requestExplanation 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, call 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, call 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 was 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, call 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, call 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, while lower priority processes can use primitives from either the new or the 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, call your Cisco technical support representative, and provide the representative with the gathered information.
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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SCHED-2-SEMNOTLOCKED: [chars] attempted to unlock an unlocked semaphoreExplanation Some sections of code use semaphores to protect critical sections of software. An attempt has been 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, call 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, call 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, while lower priority processes can use primitives from either the new or the 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, call 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, call 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, call 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, call 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 %#Ta (%TE ago)Explanation A process can register to be notified when various events occur in the router. A registered timer is expired, and the timer value is unchanged after the process was executed two successive times.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SCHED-3-STUCKTMR: Sleep with expired timer [hex], time %#Ta (%TE 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 is unchanged after the process was executed two successive times.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
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 relinquished the processor 50 consecutive times, and there were still outstanding events to be processed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 received an event that it did not know how to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 first process is unable to handle.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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 received a queueing event for an unknown queue.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call 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.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SCHED-2-WATCH: Attempt to [chars] uninitialized watched [chars] (address [hex]).Explanation A process can register to be notified when various events occur in the router. An attempt has been made to register for an event without first creating the data structure for that event.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are downstream physical unit (DSPU) error messages.
Error Message
%SCP-3-BADVLAN: Rx'd VLAN [dec] (opcode 0x[hex]) from the NMP which is not configuredExplanation The Network Management Processor (NMP) sent a configuration command for an unconfigured virtual local area network (VLAN) interface.
Recommended Action Configure the VLAN interface.
Error Message
%SCP-3-NOPROC: Cannot create SCP processExplanation 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 queueExplanation 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-PROCEXIT: The SCP process is terminating. signal: [dec]. subcode; [dec]. addr: [hex]Explanation The Service Control Point (SCP) process has been terminated.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SCP-3-UNKMSG: Unknown SCP message (opcode 0x[hex]) receivedExplanation The remote peer has sent an unknown Service Control Point (SCP) message.
Recommended Action Check software compatibility between peers.
The following are Synchronous Data Link Control (SDLC) error 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, call 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 rolesExplanation 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SDLC-4-CTRLBAD: Interface [chars], Invalid control fieldExplanation A bad Synchronous Data Link Control (SDLC) frame has been received.
Recommended Action If this message recurs, check the SDLC serial line and the devices attached to that 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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SDLC-4-DROPPED: Dropped SDLC packet from SDLC hold queueExplanation A Synchronous Data Link Control (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 your SDLC link is being overloaded with data and resolve the cause. This condition can usually be resolved by either increasing bandwidth to your SDLC line or reducing the load on your link.
Error Message
%SDLC-4-FRAMEERR: Interface [chars], Frame error: CF [hex], VS [dec] [char] VR [dec], Reason [hex]Explanation A Frame Reject (FRMR) frame has been received. This error can be caused by a noisy serial line, an overloaded Synchronous Data Link Control (SDLC) device, or corrupted data.
Recommended Action If this message recurs, service the serial line and the devices attached to it.
Error Message
%SDLC-2-ILLEGSTATE: [chars], illegal state for addr [hex], [chars]([dec])Explanation An internal Synchronous Data Link Control (SDLC) state violation has been detected.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%SDLC-4-INFOBAD: Interface [chars], Info field not permittedExplanation A bad Synchronous Data Link Control (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-NOINPIDB: Input idb not setExplanation A frame has been given to the Synchronous Data Link Control (SDLC) handler to process, but the frame arrived on an interface that was not recognized. This condition indicates a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
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, call 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 An unnumbered poll (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 Physical Unit (PU) macro (GP3174=XX) in the Network Control Program (NCP) generate file.
Error Message
%SDLC-4-INVNR: Interface [chars], Invalid NR valueExplanation A bad Synchronous Data Link Control (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-2-NOMEMORY: No memory available: [chars]Explanation The requested operation has failed 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
%SDLC-2-NOPOINTER: AW_SDLC_SEC with no sdllc_llc pointerExplanation An error condition has occurred during a Synchronous Data Logical Link Control (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 UAExplanation The router has received a frame other than an unnumbered acknowledgement (UA) in response to a Set Normal Response (SNRM).
Recommended Action Check the end station to see if the Systems Network Architecture (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 Synchronous Data Link Control (SDLC) processing system.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%SDLC-4-N1TOOBIG: Interface [chars], N1 too largeExplanation An information frame has been received from the other end of the Synchronous Data Link Control (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 other end of the link.
Error Message
%SDLC-4-SDLC_ERR: SDLC_ERROR with no pollExplanation A protocol error has been detected on a secondary station, but Frame Reject (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 Synchronous Data Link Control (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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SDLC-6-XID_DISPLAY: sa [sci_notation] da [sci_notation] ss [hex] ds [hex] [[hex][hex][hex][hex]]Explanation This message supplies the information for the received and rejected exchange identification (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 exchange identification (XID) format has been received for this mode of SDLLC operation. Review the type of devices you are connecting with SDLLC to that ensure 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 REJECTEDExplanation An inbound exchange identification (XID) from a Physical Unit 2.0 (PU 2.0)/Physical Unit type 2.1 (PU 2.1) node was rejected. The targeted Synchronous Data Link Control (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.
The following are Synchronous Data Logical Link Control (SDLLC) logical link control type 2 (LLC2) translation error messages.
Error Message
%SDLLC-5-ACT_LINK: SDLLC: [chars] LINK address [hex] ACTIVATED: [chars]Explanation A Synchronous Data Logical Link Control (SDLLC) media conversion session has been activated.
Recommended Action No action is required.
Error Message
%SDLLC-5-DACT_LINK: SDLLC: [chars] LINK address [hex] DEACTIVATED: [chars]Explanation A Synchronous Data Logical Link Control (SDLLC) media conversion session has been deactivated. If the deactivation was a result of an error condition, this message will include a reason.
Recommended Action If the message does not include a description of an error, the deactivation was normal, and the message is for information only. If the message does include a description of an error, begin problem analysis. Determine whether the session loss is related to logical link control type 2 (LLC2) timers by entering the debug llc2-err command. If the problem is related to LLC2 timers, consider using SDLLC with the local acknowledgment feature. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are IP security error messages.
Error Message
%SEC-6-IPACCESSLOGDP: list [chars] [chars] [chars] [int] [chars]-> [int] ([dec]/[dec]), [dec] packet[chars]Explanation A packet matching the log criteria for the given access list has been detected.
Recommended Action No action is required.
Error Message
%SEC-6-IPACCESSLOGNP: list [chars] [chars] [dec] [int] [chars]-> [int], [dec] packet[chars]Explanation A packet matching the log criteria for the given access list has been detected.
Recommended Action No action is required.
Error Message
%SEC-6-IPACCESSLOGP: list [chars] [chars] [chars] [int]([dec]) [chars]-> [int]([dec]), [dec] packet[chars]Explanation A packet matching the log criteria for the given access list has been detected.
Recommended Action No action is required.
Error Message
%SEC-6-IPACCESSLOGRP: list [chars] [chars] [chars] [int] [chars]-> [int], [dec] packet[chars]Explanation A packet matching the log criteria for the given access list has been detected.
Recommended Action No action is required.
Error Message
%SEC-6-IPACCESSLOGS: list [chars] [chars] [int] [dec] packet[chars]Explanation A packet matching the log criteria for the given access list has been detected.
Recommended Action No action is required.
Error Message
%SEC-3-NOMAX: No default for NLESO definedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SEC-2-NOOPT: Box secured, no option on internal packetExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SEC-2-NOTSEC: First opt in tcb not BASIC securityExplanation An internal software error has occurred.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SEC-2-SECINS: Security opt in tcb not SECINSERTExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SEC-4-TOOMANY: Box secured, too many options on internal packetExplanation The system was not able to process the packet because there was not enough room for all of the desired IP header options. The packet has been discarded.
Recommended Action Change the system configuration to process fewer IP header options.
The following are service module error messages.
Error Message
%SERVICE_MODULE-4-ACCESSERROR: Unit [chars] reports register access error - [chars]Explanation The T1 module supplied an invalid register address. This error might be caused if a new version of the module is using an old Cisco IOS software image.
Recommended Action Update the Cisco IOS software image on the system. If updating the software does not adequately resolve the problem, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-ALARMFAILURE: Unit [chars] - Could not access alarm status - disabling alarm processingExplanation The system issued an alarm interrupt but could not read the alarm status register from the module. This condition caused the system to disable alarm processing.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-BADTYPE: Unit [chars] - reports incompatible module type [dec] against router hw detectExplanation A register read request returned an identity for a module that was different from the identity that was reported by the router hardware pinout.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-COMMANDFAILED: Unit [chars] not ready/responding after register [dec] access command issuedExplanation The system did not receive a ready signal within the allotted time after writing to the command register.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-0-INITFAILURE: Unit [chars] - failed to create data structures used for module-accessExplanation The channel service unit (CSU) /data service unit (DSU) driver failed to allocate memory for its data structures. This is a catastrophic error, and the system has crashed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-0-INITWICFAILURE: Unit [chars] - failed to download properlyExplanation The channel service unit (CSU) /data service unit (DSU) driver detected a checksum error while downloading WIC firmware.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-INTERBYTETIMEOUT: Unit [chars] - timed out while [chars] byte [dec] of [dec] length register [dec]Explanation The module took more than two seconds to respond between bytes.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-3-LOOPDOWNFAILED: Unit [chars] - WARNING - Loopdown of remote unit failedExplanation A remote channel service unit (CSU) is looping pings and test patterns back to the system. This error could be triggered if the user disabled loopbacks on the remote CSU after placing the remote CSU into remote loopback mode.
Recommended Action Execute a clear command on the remote CSU.
Error Message
%SERVICE_MODULE-5-LOOPDOWNREMOTE: Unit [chars] - Remote loopback test cancelledExplanation A hardware or software error has occurred.
Recommended Action Copy the error message exactly as it appears and report it to your Cisco technical support representative for assistance.
Error Message
%SERVICE_MODULE-5-LOOPUPFAILED: Unit [chars] - Loopup of remote unit failedExplanation The loopback on the remote unit has failed. The failure might indicate that the network connection is broken or that loopbacks are disabled at the other side.
Recommended Action Check that the router is connected to the network and enable loopbacks on the remote unit. If this process does not adequately resolve the problem, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-5-LOOPUPREMOTE: Unit [chars] - Remote unit placed in loopbackExplanation The user executed a loopback command on the remote unit. The remote unit is now in loopback mode.
Recommended Action No action is required.
Error Message
%SERVICE_MODULE-4-NOTREADY: Unit [chars] not ready for register accessExplanation The module has been waiting for a ready status before executing a read/write request. The system reported a not ready status for 5 seconds. This condition caused the module to terminate the read/write request.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-OLDIMAGE: Unit [chars] - router image older than module version - access errors may be seenExplanation The Cisco IOS software image does not recognize the programmable read-only memory (PROM) software version number on the module. In this situation, the system displays this message if the PROM was upgraded to a new version when the Cisco IOS software image has not been upgraded.
Recommended Action Upgrade the Cisco IOS software image.
Error Message
%SERVICE_MODULE-4-REPEATEDRESET: Unit [chars] - giving up after [dec] repeated resets couldn't bring module up againExplanation The software issued several clear service-module requests to the module, but the module did not respond to these requests.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-REQUESTOVERLOAD: Unit [chars] - module request overload - lock access timeoutExplanation The system employs a Cisco IOS scheduler semaphore object to ensure mutually exclusive access across software threads to the channel service unit (CSU) /data service unit (DSU). In this situation, a thread had to wait for more than 5 seconds on this semaphore.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-5-RESET: Reset of Unit [chars] issuedExplanation The module has been reset.
Recommended Action No action is required.
Error Message
%SERVICE_MODULE-4-RESETFAILURE: Unit [chars] - failed to create reset process - non-default module configuration may be lostExplanation To execute a reset, the Cisco IOS software must initiate a separate process. The Cisco IOS software did not have sufficient memory to create this separate process. The module came up in an initialized state with the default configuration. The user-defined configuration might have been lost.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-UNKNOWNALARM: Unit [chars] reports unknown network alarms - alarm status reg = [hex]Explanation A recent version of the module is operating with an old Cisco IOS software image. The module did not recognize an alarm condition.
Recommended Action Update the Cisco IOS software image on the system. If updating the software does not adequately resolve the problem, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SERVICE_MODULE-4-WICNOTREADY: Unit [chars] not ready for next commandExplanation The module has been waiting for the current request to be processed before sending the next request. The current request was in progress for more than 3 seconds.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Stack Group Bidding Protocol (SGBP) error messages.
Error Message
%SGBP-7-ACTIVE: Member [chars] State -> ActiveExplanation This message is generated only when Stack Group Bidding Protocol (SGBP) errors or events debugging is enabled. This message indicates that a link to another SGBP member has completed the interactions to set up the link and is now entering the active state.
Recommended Action No action is required.
Error Message
%SGBP-5-ARRIVING: New peer event for member [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) event debugging is enabled. This message indicates that a SGBP peer joined the group.
Recommended Action No action is required.
Error Message
%SGBP-1-AUTHFAILED: Member [chars] failed authenticationExplanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos or errors is enabled. This message indicates that an attempted peer connection ended in authentication failure. A peer might be misconfigured. This condition could also indicate an attempted security breach.
Recommended Action Check if the peer is correctly configured. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-7-AUTHOK: Member [chars] State -> AuthOKExplanation This message is generated only when Stack Group Bidding Protocol (SGBP) errors or events debugging is enabled. A message has been received from another SGBP member indicating that an authentication attempt to that member succeeded.
Recommended Action No action is required.
Error Message
%SGBP-7-CANCEL: Local query #[dec]:[dec] for bundle [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) query debugging is enabled. This message provides information about queries in progress.
Recommended Action No action is required.
Error Message
%SGBP-7-CHALLENGE: Send Hello Challenge to [chars] group [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This condition indicates that an authentication challenge has been sent to a peer.
Recommended Action No action is required.
Error Message
%SGBP-7-CHALLENGED: Rcv Hello Challenge message from member [chars] using [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This condition indicates that an authentication challenge has been received from a peer.
Recommended Action No action is required.
Error Message
%SGBP-7-CLOSE: Closing pipe for member [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) event debugging is enabled. An interprocess communication link has been closed.
Recommended Action No action is required.
Error Message
%SGBP-1-DIFFERENT: Rcv [chars]'s addr [int] is different from the hello's addr [int]Explanation The internally configured address for an Stack Group Bidding Protocol (SGBP) member does not match the address of the host that tried to authenticate as that member. The configuration is incorrect on either this system or the other member; they must agree.
Recommended Action Determine which configuration is in error and fix it.
Error Message
%SGBP-7-DONE: Query #[dec] for bundle [chars], count [dec], master is [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) query debugging is enabled. This message provides information about queries in progress.
Recommended Action No action is required.
Error Message
%SGBP-7-DUPL: Duplicate local query #[dec] for [chars], count [dec], ourbid [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) query debugging is enabled. This message provides information about queries in progress.
Recommended Action No action is required.
Error Message
%SGBP-1-DUPLICATE: Rcv Duplicate bundle [chars] is found on member [chars]Explanation This message is generated only when SGBP debugging for hellos or errors is enabled and indicates that a duplicate bundle has been received from the same peer more than once. The duplicate bundle was discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-7-EQUAL: [dec] equal highest bids, randomly select bid# [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) query debugging is enabled. This message provides information about queries in progress.
Recommended Action No action is required.
Error Message
%SGBP-7-HANGUP: I am a forward-only member, can't forward bundle [chars], hangupExplanation This message is generated only when Stack Group Bidding Protocol (SGBP) query, event, and error debugging is enabled. This message indicates a routine change of role for the router in SGBP interactions with peers.
Recommended Action No action is required.
Error Message
%SGBP-3-INVALID: MQ message with [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos or errors is enabled. An invalid message has been received and discarded.
Recommended Action This condition probably indicates that an error occurred in the network media or a peer and that erroneous packets are being generated.
Error Message
%SGBP-3-INVALIDADDR: Stack group [chars] IP address [int]Explanation The current configuration does not allow a local IP address to be configured using the sgbp member address command. Any local address is automatically removed from the Stack Group Bidding Protocol (SGBP) group.
Recommended Action Do not configure sgbp member address using a local IP address.
Error Message
%SGBP-3-INVALIDB: [chars] for bundle '[chars]' -- [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-3-INVFIELD: [chars] field type [hex] has [chars] [dec] (expected [dec])Explanation A Stack Group Bidding Protocol (SGBP) request from a peer contained invalid or corrupt data.
Recommended Action Check the peer equipment or network media for any problems.
Error Message
%SGBP-7-KEEPALIVE: Sending Keepalive to [chars], retry=[dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This message indicates that a keepalive message has been sent to an SGBP member.
Recommended Action No action is required.
Error Message
%SGBP-7-KEEPALIVE_TIMEOUT: Keepalive timeout on [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. Keepalive messages have not been answered, so the pipe to an SGBP member was closed.
Recommended Action No action is required.
Error Message
%SGBP-5-LEAVING: Member [chars] leaving group [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) event debugging is enabled. An SGBP peer has left the group.
Recommended Action No action is required.
Error Message
%SGBP-1-MISSCONF: Possible misconfigured member [chars] using [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos or errors is enabled and indicates a configuration error. Either this router has an incorrect IP address listed for the peer or the peer is using an incorrect IP address.
Recommended Action Find and correct the configuration error.
Error Message
%SGBP-7-MQ: [chars] ([hex]) for query [dec]:[dec], bundle [chars], bid [dec], len [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) error debugging is enabled. An SGBP query has been received.
Recommended Action No action is required.
Error Message
%SGBP-7-MQB: Bundle: [chars] State: [chars] OurBid: %03dExplanation This message is part of a list of debug states that are displayed at the request of the operator.
Recommended Action No action is required.
Error Message
%SGBP-7-NEWL: Local query #[dec] for [chars], count [dec], ourbid [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) query debugging is enabled. It provides information about queries in progress.
Recommended Action This message provides debugging information only. No action is required.
Error Message
%SGBP-7-NEWP: Peer query #[dec] for [chars], count [dec], peerbid [dec], ourbid [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) query debugging is enabled. This message provides information about queries in progress.
Recommended Action This message provides debugging information only. No action is required.
Error Message
%SGBP-7-NORESP: Failed to respond to [chars] group [chars], may not have passwordExplanation An authentication challenge has been received, but there was no information available to respond to the authentication challenge. This condition probably indicates a configuration error or a missing password.
Recommended Action Refer to the documentation to configure a username with the same name as the Stack Group Bidding Protocol (SGBP) group.
Error Message
%SGBP-7-PB: [int] State: [chars] Bid: %03d Retry: [dec]Explanation This message is part of a list of debug states that are displayed at the request of the operator.
Recommended Action No action is required.
Error Message
%SGBP-3-PEERERROR: Peer [int] [chars] during 'PB [chars]' state for bundle [chars]Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-7-RCVD: MQ [chars] from [int] for query [dec]:[dec], bundle [chars], bid [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) message debugging is enabled. This message indicates that an SGBP packet has been received.
Recommended Action No action is required.
Error Message
%SGBP-7-RCVINFO: Received Info Addr = [int] Reference = [hex]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This message indicates that data has been received by a listener process.
Recommended Action No action is required.
Error Message
%SGBP-7-RESPONSE: Send Hello Response to [chars] group [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This message indicates that a response to an authentication challenge has been sent to a peer.
Recommended Action No action is required.
Error Message
%SGBP-7-RESPONSED: Rcv Hello Response message from member [chars] using [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This message indicates that a response to an authentication challenge has been received from a peer.
Recommended Action No action is required.
Error Message
%SGBP-7-SENDAUTHOK: Send Hello Authentication OK to member [chars] using [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. A message has been sent or re-sent to another SGBP member that indicates that an authentication attempt from that member has succeeded.
Recommended Action No action is required.
Error Message
%SGBP-7-SENDINFO: Send Info Addr to [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos is enabled. This message indicates that data has been sent by the listener process in response to received data.
Recommended Action No action is required.
Error Message
%SGBP-7-SENT: MQ [chars] to [int] for query [dec]:[dec], bundle [chars], bid [dec], len [dec]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) message debugging is enabled. This message indicates that an SGBP packet has been sent.
Recommended Action No action is required.\
Error Message
%SGBP-5-SHUTDOWN: [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) event debugging is enabled. A process involved in SGBP has been terminated upon completion.
Recommended Action No action is required.
Error Message
%SGBP-5-STARTUP: [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) event debugging is enabled. A process involved in SGBP has been started.
Recommended Action No action is required.
Error Message
%SGBP-3-TIMEOUT: Peer [int] bidding; state 'PB [chars]' deletedExplanation This message is generated only when Stack Group Bidding Protocol (SGBP) event debugging is enabled and indicates that a peer timed out while closing a query. The connection was dropped.
Recommended Action Check the peer equipment and network media for problems.
Error Message
%SGBP-3-UNEXP: MQ [chars] from [int] for query [dec]:[dec], bundle [chars], bid [dec], state [chars]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) error debugging is enabled. The SGBP connection has entered an unexpected state, possibly caused by a software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-3-UNKNOWN: [int] not knownExplanation This message is generated only when Stack Group Bidding Protocol (SGBP) error debugging is enabled. An SGBP connection has been attempted by a host that was not recognized as a peer, and the connection was not accepted.
Recommended Action Depending on the network topology and firewall configuration, SGBP connection attempts from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-3-UNKNOWNEVENT: Event [hex] from peer at [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) error debugging is enabled. An invalid event occurred, possibly caused by an an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SGBP-1-UNKNOWNHELLO: Rcv Hello message from non-group member using [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) debugging for hellos or errors is enabled. An SGBP Hello message has been received from a host. The host is not a member of the SGBP group, and the message was discarded.
Recommended Action This is a configuration error. The host is not a member of the SGBP group, and the host should be listed in the configuration of this router as a member (unless the other host is misconfigured to attempt to join this group.)
Error Message
%SGBP-3-UNKNOWNPEER: Event [hex] from peer at [int]Explanation This message is generated only when Stack Group Bidding Protocol (SGBP) error debugging is enabled. An SGBP event came from a network host that was not recognizable as an SGBP peer, and the event was discarded.
Recommended Action Check if a network media error could have corrupted the address, or if peer equipment is malfunctioning to generate corrupted packets. Depending on the network topology and firewall configuration, SGBP packets from a non-peer host could indicate probing and attempts to breach security. If there is a chance your network is under attack, obtain knowledgeable assistance. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Simple Gateway Control Protocol (SGCP) protocol-related error messages.
Error Message
%SGCP-2-INTERNAL_CRITICAL: [chars]Explanation The Simple Gateway Control Protocol (SGCP) subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%SGCP-3-INTERNAL_ERROR: [chars]Explanation The Simple Gateway Control Protocol (SGCP) subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%SGCP-4-INTERNAL_WARNING: [chars]Explanation The Simple Gateway Control Protocol (SGCP) subsystem encountered an internal software error. The error message contains text that can be used to help identify the nature of the problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that might provide information to determine 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, then call your Cisco technical support representative, and provide the representative with the information.
Error Message
%SGCP_APP-6-CALL_REC_DATABASE_FAILED: Failed to create call record databaseExplanation The system failed to create an endpoint database.
Recommended Action Check the amount of free memory to ensure that there is enough memory.
Error Message
%SGCP_APP-6-DNS_QUEUE_FAILED: Failed to create DNS message watched queueExplanation The system failed to create a Domain Name System (DNS) message watched queue.
Recommended Action Check the amount of free memory to ensure that there is enough memory.
Error Message
%SGCP_APP-6-PROCESS_CREATION_FAILED: Cannot create SGCP application processExplanation The system failed to create the Simple Gateway Control Protocol (SGCP) application process.
Recommended Action Check the size of free memory to ensure that there is enough memory.
Error Message
%SGCP_APP-6-SOCKET_OPEN_FAILED: Failed to open UDP port for SGCP.Explanation The system failed to open a User Datagram Protocol (UDP) port for the Simple Gateway Control Protocol (SGCP) process. An IP address has not been configured, or the UDP port (2427) was already in use.
Recommended Action Check if an IP address is configured and if any other applications use the same UDP port number (2427).
The following are router shelf (RS) error messages.
Error Message
%SHELF-5-AUTH_FAILED: MD5 digest does not match, SDP packet received from, [int] rejectedExplanation A Shelf Discovery Protocol (SDP) hello packet has been received from a shelf that the system does not trust.
Recommended Action Either specify the correct SDP password or destination on the shelf from which this message was received
Error Message
%SHELF-3-DISCOVER_SOCKET_OPEN: socket open failedExplanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SHELF-6-HELLO_PROCESS_START: Shelf hello process has started.Explanation This is an informational message only. An internal system controller process has been started.
Recommended Action Informational messages can be disabled by changing logging level.
Error Message
%SHELF-6-HELLO_PROCESS_STOP: Shelf hello process was stopped.Explanation An internal system controller process completed its work. This is an informational message only. Informational messages can be disabled by changing the logging level.
Recommended Action No action is required.
Error Message
%SHELF-6-SYSCTLR_ESTABLISHED: Configured via system controller located at [int]Explanation Configuration information has been received from a system controller. This is an informational message only. Informational messages can be disabled by changing logging level.
Recommended Action No action is required.
The following are Serial Line Internet Protocol (SLIP) error messages.
Error Message
%SLIP-2-BADQUOTE: Impossible quoted character [hex]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, call your Cisco technical support representative, and provide the representative with the gathered information.
Error Message
%SLIP-2-BADSTATE: Impossible input state [hex]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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are slot dump error messages.
Error Message
%SLOTDUMP-3-CORE_DUMP_ERROR: Core dump error slot [dec]: [chars]Explanation An error occured during a core dump of a slot.
Recommended Action No action is required.
The following are Software MAC Filter error messages.
Error Message
%SMF-4-INVALID_ACTION: failed to create SMF entry for [sci_notation] on [chars] with result [hex]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, call your Cisco technical support representative, and provide the representative with the gathered information.
The following are Simple Multicast Routing Protocol (SMRP) error messages.
Error Message
%SMRP-2-ASSERTFAILED: SMRP assertion failed: [chars]Explanation The software has detected an inconsistency. This condition is considered a serious error. The router attempts to continue, but Simple Multicast Routing Protocol (SMRP) processing might be impaired.
Recommended Action Copy the error message exactly as it appears, noting any SMRP problems that you are experiencing, and report it to your Cisco technical support representative.
Error Message
%SMRP-7-DEBUGMSG: SMRP Debug: [chars]Explanation This message is generated by some debug commands to provide additional information about conditions in Simple Multicast Routing Protocol (SMRP).
Recommended Action If you are experiencing problems in SMRP, these messages should be provided, along with any other information, in a report to your Cisco technical support representative.
Error Message
%SMRP-5-NEIGHBORDOWN: [chars]: SMRP neighbor down - [chars]Explanation A neighboring Simple Multicast Routing Protocol (SMRP) router is now down. This is an informational message only.
Recommended Action No action required.
Error Message
%SMRP-6-NEIGHBORUP: [chars]: SMRP neighbor up - [chars]Explanation A neighboring Simple Multicast Routing Protocol (SMRP) router has appeared.
Recommended Action This is an informational message. No action required.
Error Message
%SMRP-3-NOFDDICOMPAT: SMRP port [chars] disabled; pre-fdditalk not supportedExplanation Simple Multicast Routing Protocol (SMRP) cannot be started on an interface running pre-FDDITalk.
Recommended Action Use FDDITalk on the Fiber Distributed Data Interface (FDDI) ring if possible.
Error Message
%SMRP-5-PORTDOWN: [chars]: SMRP port down - [chars]Explanation A Simple Multicast Routing Protocol (SMRP) port is down and is no longer operational.
Recommended Action This is an informational message. No action required.
Error Message
%SMRP-6-PORTUP: [chars]: SMRP port up - [chars]Explanation A Simple Multicast Routing Protocol (SMRP) port has come up.
Recommended Action This is an informational message. No action required.
The following are Snapshot dial-on-demand routing (DDR) error messages.
Error Message
%SNAPSHOT-2-BADSTATE: Bad state for Snapshot block [chars][[dec]], location [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, call your Cisco technical support representative, and provide the representative with. the gathered information.
Error Message
%SNAPSHOT-2-TOOMANYDIALERS: Exceeded maximum dialer interfaces to watch. Ignoring [chars]Explanation Snapshot is being used on more than 100 dial-on-demand routing (DDR) interfaces.
Recommended Action Do not use Snapshot over more than 100 DDR interfaces.
Posted: Fri Jun 16 11:53:31 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.