Cisco Systems RSP8 manual Troubleshooting the Installation

Page 67

Troubleshooting the Installation

Step 3 When you have verified that the power supply is functioning properly, observe the LEDs on the RSP8. The CPU halt LED always turns on during initial power-up of an RSP8 and remains on for approximately one-half second, then turns off. If it remains on during the startup sequence, the system has encountered a processor hardware error.

Use the show version command to check the current configuration register settings.

If the CPU halt LED remains on during a second startup attempt, suspect a processor hardware error and contact a service representative.

Step 4 During the boot process, the LEDs on most of the interfaces light in irregular sequence; this does not indicate either correct system startup or failure.

Step 5 When the system boot is complete, the RSP8 begins to initialize the interface processors. During this initialization, the LEDs on each interface processor behave differently (most flash on and off). The enabled LED on each interface processor goes on when initialization has been completed.

If the enabled LEDs on the interface processors go on, the system has booted successfully and is now functional.

If the RSP8 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 Figure 3 on page 17.) 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 Figure 3 on page 17.) Tighten both captive 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 RSP8’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 RSP8 is system master (SLOT 2 for a Cisco 7507)

SLOT 7 RSP8 is system slave (SLOT 3 for a Cisco 7507, if installed)

RSP8 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 RSP8 is system master

SLOT 7 RSP8 is system slave

RSP8 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 RSP8.

Route Switch Processor (RSP8) Installation and Configuration Guide

 

OL-4920-02

67

 

 

 

Image 67
Contents Document Contents Cisco.com, Obtaining Documentation, Related DocumentationTopics discussed in this section are Product DescriptionRSP8-Horizontal Front-Panel View Monitoring interface and environmental statusU12 Flash Eprom ROMmon Bus connectors Auxiliary portShows the memory components on the RSP8 Memory ComponentsType Size Quantity Description Location Flash Memory Cards and Flash Disks There are no user-configurable jumpers on the RSP8Jumpers LEDsSerial Ports PC Card SlotsLED Label Color State Indication System Software SpecificationsLists the physical specifications for the RSP8 SpecificationsSafety Guidelines Installation PrerequisitesSafety Warnings Installation Prerequisites Electrical Equipment Guidelines Telephone Wiring GuidelinesPreventing Electrostatic Discharge Damage Chassis Slot and Dram Requirements Compatibility RequirementsMemory Requirements Hardware Prerequisites Software PrerequisitesMicrocode Requirements List of Parts and ToolsRemoving the RSP8 Installing the RSP8Ejector Levers and Captive Installation Screw Replacing the RSP8 Handling the RSP8 During Removal and Installation Connecting to the Auxiliary Port Connecting a Console TerminalUsing the Y-Cables for Console and Auxiliary Connections Shows the console Y-cable and shows the auxiliary Y-cable Restarting the SystemInstalling the RSP8 Router show version Using the Exec Command Interpreter Configuring the Router for a Single RSP8HSA Active and Standby Operation Configuring High System AvailabilityHSA Implementation Methods HSA System Requirements HSA Configuration Task ListRouter# copy system running-config nvramstartup-config Specifying the Default Standby RSPCommand Purpose Router# configure terminalEnsuring that Both RSPs Contain the Same System Image Router# show controller cbus Ensuring that Both RSPs Contain the Same Microcode ImageRouter# copy bootflashfilename slot0filename Router# dir slavebootflash slaveslot0 slaveslot1Slot1filename slavebootslotfilename Determines whether the standby RSP contains the same Router# copy source bootflash slot0 slot1Copies a different system image to the active RSP Upgrading to a New Software Version Example Now view the standby software image location and version BootflashRouter# copy tftp slot0rsp-pv-mz.120-22.3.S1 Routerconfig# config-register 0x010F Routerconfig# boot system tftp rsp-pv-mz.120-23.SBacking Up with an Older Software Version Example ANB Delete the rsp-pv-mz.120-22.3.S1image from the standby RSP Router# show bootflashRouter# delete slaveslot0rsp-pv-mz.120-22.3.S1 Router# copy system running-config startup-config Manually Setting Environment Variables on the Standby RSPRouterconfig# slave sync config Router# copy running-config startup-configSpecifies which image the standby runs Routerconfig# hw-module slot imageMonitoring and Maintaining HSA Operation Information under that RSP’s ROM monitor controlHigh Availability Feature Overview Enabling High Availability FeaturesRouter# slave sync config Enabling High Availability Features Hardware and Software Prerequisites Installation ProceduresEnabling the Router This completes the procedure to enable the routerCopying an Image onto an RSP Router# copy tftp slaveslot slot-number Router# copy tftp slot slot-numberRouter# show version Setting the Config-Register Boot VariableConfiguring RPR and RPR+ Routerconfig# boot system flashRouter# hw-module sec-cpu reset Routerconfig# hw-module slot slot-numberimage file-specVerifying RPR and RPR+ Configuring RPR and RPR+ ExampleRouter# show redundancy Configuring a Stateful Switchover SSO Configuration file Saves the configuration changes to the startupVerifying SSO Router# show redundancy client Router# show redundancy states my state = 13 -ACTIVEConfiguring CEF NSF Configuring Nonstop Forwarding NSFConfiguring BGP NSF Graceful-restart Configuring Ospf NSFConfiguring IS-IS NSF As-numberSeconds adjacency Verifying CEF NSFRouter# show ip bgp neighbors Verifying BGP NSFVerifying IS-IS NSF Running-config commandThis example, note the presence of NSF restart enabled Verifying Ospf NSFNetworking device NSF Troubleshooting Tips Troubleshooting NSF FeaturesIS-IS NSF Configuration Example BGP NSF Configuration ExampleBGP NSF Neighbor Device Configuration Example Ospf NSF Configuration ExamplePerforming a Fast Software Upgrade Specifies the image to be used by the standby RSP at Routerconfig# hw-module slot slot-number imageName of the image of the standby RSP Routerconfig# service single-slot-reload-enable Configuring SlcrFast Software Upgrade Example Router# redundancy force-switchoverDisabling Slcr RPR, RPR+, SSO, and FSU Troubleshooting TipsSlcr Configuration Example Slcr Troubleshooting Tips Verifying LEDs Troubleshooting the Installation System Power LEDs Monitoring and Maintaining the Active and Standby RSPsNormal RSP8 LEDsVerifying System Startup Sequence Troubleshooting the Installation Troubleshooting a Failed RSP8 Troubleshooting a Router That is Failing to BootDisplaying a Stack Trace of an RSP Maintenance InformationSaving and Retrieving a Configuration File Reloading a Failed RSPRouter# ping Using the ping Command to Ensure ConnectivityCopy to this file Copying the Configuration FileSection on page 24 to enable the privileged level Might include the name or address of a default file serverRouter# show startup-config Retrieving the Configuration File Replacing and Upgrading Dram DIMMs Sdram Dimm Product Numbers Quantity Dram Sockets TotalsPolarization notch Removing DIMMsInserting the Dimm Installing New DIMMsChecking the RSP Memory Upgrade Recovering a Lost PasswordInitialize the router using the i command as follows Pin Signal Direction Description Console Port SignalsReference Information Female DB-25 Pins Male DB-25 Pins Signal Description Auxiliary Port SignalsConsole and Auxiliary Y-Cable Pinouts P1-7 J1-7 and J2-7 Ground P1-8 J1-8 and J2-8 Software Configuration Register SettingsMale DB-25 Pins Female DB-25 Pins Signal Description P1-5 J1-5 and J2-5Bit Number Hexadecimal Meaning Boot Field MeaningStays at the system bootstrap prompt Boots the first system image in onboard Flash memoryTftp flash filename Changing SettingsRouterconfig# config-register 0xvalue Bit MeaningsAction/Filename Bit Baud Bit Enabling a Boot from Flash MemoryRouterconfig# boot system flash devicefilename Bit Address net hostEnabling a Boot from the Flash Disk Cisco.com Using Flash MemorySystem# copy running-config startup-config Obtaining DocumentationDocumentation Feedback Obtaining Technical AssistanceDocumentation CD-ROM Ordering DocumentationTAC Case Priority Definitions Cisco TAC Website Opening a TAC CaseObtaining Additional Publications and Information Copyright 2004 Cisco Systems, Inc. All rights reserved