Login | Sign Up
ErrorKey - Search engine for Error codes and messages     
  RSP  [ 139 result(s) ]
CISCO 6400 CISCO IOS MICROSOFT 
  - %RSP-3-SLAVECHANGE: Slave changed state from [chars] to [chars] CISCO 6400
The slave RSP has undergone a hardware state change. Both the old and new states are shown. Possible states are nonparticipant, slave, master, and unplugged. Possible state changes indicated by the message: *unplugged to nonparticipant or slave *nonparticipant to slave *slave to nonparticipant Any other combination is unexpected.
Depending on the cause of the alarm, do one of the following: The slave RSP has been removed. – Consider reinstalling it if continued high system availability (HSA) operation is required. If the slave RSP is present, ensure that it is properly seated in the card cage. A slave RSP has been installed. – Configure the router for HSA. See the Configuration Fundamentals Configuration Guide in the "Loading System Images and Configuration Files" chapter 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. A previously crashed slave RSP has been reset, or a newly installed slave RSP is in transition from unplugged to nonparticipant, and finally to slave state. – 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 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, the router configuration, and all other relevant information to your technical support representative. Log out from the slave RSP console port using Ctrl-c or Ctrl-z, and enter the slave reload global configuration command on the master RSP to bring the s
RSP
Comments
 
  - %RSP-3-MSFIX: Fixing [chars] by setting to default [chars] CISCO 6400
The characters shown can be on the slave RSP setting or on the master RSP setting. The ROM monitor default slave RSP setting is not synchronized with the system configuration file specifications. During bootup, the system image detects the mismatch and modifies the ROM monitor setting to conform with these specifications. This mismatch 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 may result from a previous Interprocess Communication (IPC) error occurring while the HSA environment is reconfigured.
Using the show version or show boot command, determine which slot contains the current slave RSP. Using the show config command, determine which slot has been specified as the default slave RSP. 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, and slot 7 on a Cisco 7513). 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 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 your router to ensure that the desired system image is running. After the reload, the slave RSP will match the default slave RSP specified in (or inferred from) the system configuration file. For details of various HSA configuration modes, refer to the Cisco IOS Configuration Fundamentals Configuration Guide. See the "Loading System Images and Configuration Files" chapter (Cisco 7500 series only).
RSP
Comments
 
  - %RSP-4-HSA_MEM: size mismatch, master [int]MB, slave [int]MB CISCO 6400
Memory size mismatch between master and slave RSP.
Configure both master and slave RSPs to have an equal amount of memory.
RSP
Comments
 
  - %RSP-5-SLAVEUP: Slave changed to state Running CISCO 6400
This is an informational message to indicate that the slave RSP has started running the slave RSP image. This message appears after the router boots or after the slave reload global configuration command is issued on the master RSP.
No action required.
RSP
Comments
 
  - %RSP-4-RSPDRAM: Insufficient DRAM to adequately run this IOS version. [dec]M is recommended CISCO 6400
 The quantity of RSP DRAM is below the recommended amount.
Add DRAM.
RSP
Comments
 
  - %RSP-3-LOVENOTE: [hex] corrupt: [hex] [hex] [hex] [hex] CISCO 6400
This message indicates miscommunication between the RSP and an IP.
Contact your technical support representative.
RSP
Comments
 
  - %RSP-3-XBUFHDR: corrupt bufhdr [hex]: [hex] [hex] [hex] [hex] CISCO 6400
Miscommunication occurred between the RSP and an IP.
Report this error to your technical support representative.
RSP
Comments
 
  - %RSP-3-SLAVEMASTER: Slave stole mastership CISCO 6400
The master RSP detected that the slave RSP had taken mastership of the router. The old master RSP will reload and become the slave RSP, letting the new master RSP have control. This behavior indicates a software or hardware error.
Copy the error message exactly as it appears, the router configuration, and all other relevant information and report it to your technical support representative.
RSP
Comments
 
  - %RSP-2-STALL: partially inserted or removed IPs on cyBus[int] CISCO 6400
A board is not fully seated in the chassis or there is a hardware problem with the RSP or backplane.
Reseat the boards. If this message persists, call your technical support representative for assistance.
RSP
Comments
 
  - %RSP-3-BADHWREV: [chars] (slot [int]) has wrong hardware revision [int].[int] CISCO 6400
The hardware in the indicated slot needs to be upgraded for operation with the RSP.
Upgrade the board.
RSP
Comments
 
 

 
RSP  (35)
Cisco IOS (93)
C# .Net Compiler Errors and Warnings (1)
Visual Basic .Net Compiler Messages (2)
 (1)
ATM Signaling  (1)
IPC  (6)
 
  Prev   1  2  3  4  5  6  7  8  9  10  Next