Cisco RSP2 - Route Switch Processor 2 Installation And Configuration Manual page 64

If the RSP2 LEDs previously indicated a successful system boot, but none of the enabled LEDs on
•
the interface processors go on, suspect that one of the interface processors has shifted out of its
backplane connector and halted the system. Use the ejector levers to release the interface processor
and reseat it in the backplane. (For an illustration of the ejector levers, see
Tighten both captive installation screws.
If the enabled LED on a single interface processor remains off, suspect that the interface processor
•
has shifted out of its slot. Use the ejector levers to release the interface processor and reseat it in the
backplane. (For an illustration of the ejector levers, see
installation screws. After the system reinitializes the interfaces, the enabled LED on the interface
processor should go on.
• If an enabled LED still fails to go on after you perform these steps, suspect that the specific interface
processor has failed.
Step 6 When the system boot is complete and all interface processors have been initialized, the active RSP2's
console screen displays a script and a system banner similar to the following:
System Bootstrap, Version 11.1, RELEASED SOFTWARE
Copyright (c) 1986-1999 by cisco Systems, Inc.
SLOT 6 RSP2 is system master (SLOT 2 for a Cisco 7507)
SLOT 7 RSP2 is system slave (SLOT 3 for a Cisco 7507, if installed)
RSP2 processor with 128 Mbytes of main memory
ROM: System Bootstrap, Version 11.1 [biff 2], RELEASE SOFTWARE (fc1)
ROM: GS Bootstrap Software (RSP-BOOT-M), Version 10.3(7), RELEASE SOFTWARE
Warning: monitor nvram area is corrupt... using default values
SLOT 6 RSP2 is system master
SLOT 7 RSP2 is system slave
RSP2 processor with 128 Mbytes of main memory
[additional displayed text omitted from this example]
• If all the previous conditions are met and this banner is displayed, the system startup was successful
and your installation is complete.
• If an error message is displayed on the terminal, refer to the appropriate software publication for
error message definitions.
If the console screen is blank, check the terminal to ensure that it is turned on and that the console
•
cable is correctly connected between the terminal and the console port on the RSP2.
Check the terminal settings to ensure that the terminal is set for 9600 baud, 8 data bits, no parity,
•
and 2 stop bits.
If the terminal is set correctly and still fails to operate, suspect that the terminal is faulty. Connect
•
a different terminal and restart the system.
If the system still fails to start up or operate properly, or if you isolate the cause of the problem to a failed
component, contact a service representative for further assistance.
This completes the procedure for verifying system startup.
64
Figure 3 on page
Figure 3 on page 16.) Tighten both captive
16.)
OL-4923-01 B0