Cisco Systems RSP8 manual Verifying System Startup Sequence

Page 66

Troubleshooting the Installation

Verifying System Startup Sequence

By checking the state of the LEDs, you can determine when and where the system failed in the startup sequence. Because you turn on the system power with the on/off switches on each power supply, it is easiest to observe the startup behavior from the rear of the router. Use the following descriptions of the normal startup sequence to isolate the problem, and then use the troubleshooting procedures wherever the system fails to operate as expected. If you are able to isolate the problem to a faulty hardware component, or if you are unable to successfully restart the system, see the “Obtaining Technical Assistance” section on page 89 for instructions on contacting a service representative.

Note The time required for the system to initialize (boot) might vary with different router configurations and the amount of memory that must be initialized. During the system startup sequence, the time required to initialize the memory (not necessarily the entire boot sequence) in a system that contains 256 MB of DRAM might be longer than in a system that contains less DRAM.

During the boot sequence, the system banner display pauses while it initializes the memory. Because your RSP8 has more than 32 MB of DRAM, you might notice an increase in the amount of time required to initialize the memory. The pause in the banner display occurs after the copyright line and before the system displays the list of installed hardware, as shown in the following display:

%SYS-5-RELOAD: Reload requested System Bootstrap, Version 11.1

Copyright (c) 1986-1999 by cisco Systems, Inc.

[System initializes memory at this point in the display]

Note The procedures in this section are based on the assumption that your system was operating correctly until you removed (or replaced) the RSP8. If the following sequence uncovers a new problem with the power subsystem or one of the interface processors, refer to the Cisco 7500 Series Installation and Configuration Guide for system startup troubleshooting procedures.

Use the following startup sequences and troubleshooting procedures to isolate system problems:

Step 1 When you restart the system, the system power and AC (DC) OK LEDs should go on.

If the system power LED remains off, the RSP8 is probably not fully inserted and connected to the backplane. Loosen the captive installation screws on the RSP8, and then use the ejector levers to release the RSP8 and reseat it in the backplane. (For a description and illustration of the ejector levers, see the “Removing the RSP8” section on page 16 .) Tighten both captive installation screws.

If the system power LED still fails to go on as expected, a power supply or input power failure could be the problem. Before contacting a service representative, refer to the Cisco 7500 Series Installation and Configuration Guide for power subsystem troubleshooting procedures.

If the system power LED goes on, the power source is good, and the power supply is functional. When the system power LED indicates normal operation, proceed to the next step.

Step 2 Listen for the system blower and observe the fan OK LED. You should hear the system blower start operating immediately after you turn on the system power. If you determine that the power supply is functioning normally and that an internal fan (or the system blower) is faulty, contact a service representative. If the blower or a power supply fan does not function properly at initial startup, you cannot make any installation adjustments.

Route Switch Processor (RSP8) Installation and Configuration Guide

66

OL-4920-02

 

 

Image 66
Contents Document Contents Related Documentation Cisco.com, Obtaining Documentation,Product Description Topics discussed in this section areMonitoring interface and environmental status RSP8-Horizontal Front-Panel ViewFlash Eprom ROMmon Bus connectors Auxiliary port U12Memory Components Shows the memory components on the RSP8Type Size Quantity Description Location LEDs There are no user-configurable jumpers on the RSP8Jumpers Flash Memory Cards and Flash DisksPC Card Slots Serial PortsLED Label Color State Indication Specifications SpecificationsLists the physical specifications for the RSP8 System SoftwareInstallation Prerequisites Safety GuidelinesSafety Warnings Installation Prerequisites Telephone Wiring Guidelines Electrical Equipment GuidelinesPreventing Electrostatic Discharge Damage Compatibility Requirements Chassis Slot and Dram RequirementsMemory Requirements Software Prerequisites Hardware PrerequisitesList of Parts and Tools Microcode RequirementsInstalling the RSP8 Removing the RSP8Ejector Levers and Captive Installation Screw Replacing the RSP8 Handling the RSP8 During Removal and Installation Connecting a Console Terminal Connecting to the Auxiliary PortUsing the Y-Cables for Console and Auxiliary Connections Restarting the System Shows the console Y-cable and shows the auxiliary Y-cableInstalling the RSP8 Router show version Configuring the Router for a Single RSP8 Using the Exec Command InterpreterConfiguring High System Availability HSA Active and Standby OperationHSA Implementation Methods HSA Configuration Task List HSA System RequirementsRouter# configure terminal Specifying the Default Standby RSPCommand Purpose Router# copy system running-config nvramstartup-configEnsuring that Both RSPs Contain the Same System Image Ensuring that Both RSPs Contain the Same Microcode Image Router# show controller cbusRouter# dir slavebootflash slaveslot0 slaveslot1 Router# copy bootflashfilename slot0filenameSlot1filename slavebootslotfilename Router# copy source bootflash slot0 slot1 Determines whether the standby RSP contains the sameCopies a different system image to the active RSP Upgrading to a New Software Version Example Bootflash Now view the standby software image location and versionRouter# copy tftp slot0rsp-pv-mz.120-22.3.S1 Routerconfig# boot system tftp rsp-pv-mz.120-23.S Routerconfig# config-register 0x010FBacking Up with an Older Software Version Example ANB Router# show bootflash Delete the rsp-pv-mz.120-22.3.S1image from the standby RSPRouter# delete slaveslot0rsp-pv-mz.120-22.3.S1 Manually Setting Environment Variables on the Standby RSP Router# copy system running-config startup-configRouter# copy running-config startup-config Routerconfig# slave sync configInformation under that RSP’s ROM monitor control Routerconfig# hw-module slot imageMonitoring and Maintaining HSA Operation Specifies which image the standby runsEnabling High Availability Features High Availability Feature OverviewRouter# slave sync config Enabling High Availability Features Installation Procedures Hardware and Software PrerequisitesThis completes the procedure to enable the router Enabling the RouterCopying an Image onto an RSP Router# copy tftp slot slot-number Router# copy tftp slaveslot slot-numberRouterconfig# boot system flash Setting the Config-Register Boot VariableConfiguring RPR and RPR+ Router# show versionRouterconfig# hw-module slot slot-numberimage file-spec Router# hw-module sec-cpu resetConfiguring RPR and RPR+ Example Verifying RPR and RPR+Router# show redundancy Configuring a Stateful Switchover SSO Saves the configuration changes to the startup Configuration fileVerifying SSO Router# show redundancy states my state = 13 -ACTIVE Router# show redundancy clientConfiguring Nonstop Forwarding NSF Configuring CEF NSFConfiguring BGP NSF As-number Configuring Ospf NSFConfiguring IS-IS NSF Graceful-restartVerifying CEF NSF Seconds adjacencyVerifying BGP NSF Router# show ip bgp neighborsVerifying Ospf NSF Running-config commandThis example, note the presence of NSF restart enabled Verifying IS-IS NSFNetworking device Troubleshooting NSF Features NSF Troubleshooting TipsOspf NSF Configuration Example BGP NSF Configuration ExampleBGP NSF Neighbor Device Configuration Example IS-IS NSF Configuration ExamplePerforming a Fast Software Upgrade Routerconfig# hw-module slot slot-number image Specifies the image to be used by the standby RSP atName of the image of the standby RSP Router# redundancy force-switchover Configuring SlcrFast Software Upgrade Example Routerconfig# service single-slot-reload-enable Slcr Troubleshooting Tips RPR, RPR+, SSO, and FSU Troubleshooting Tips Slcr Configuration Example Disabling SlcrMonitoring and Maintaining the Active and Standby RSPs Troubleshooting the InstallationSystem Power LEDs Verifying LEDsRSP8 LEDs NormalVerifying System Startup Sequence Troubleshooting the Installation Troubleshooting a Router That is Failing to Boot Troubleshooting a Failed RSP8Reloading a Failed RSP Maintenance InformationSaving and Retrieving a Configuration File Displaying a Stack Trace of an RSPUsing the ping Command to Ensure Connectivity Router# pingMight include the name or address of a default file server Copying the Configuration FileSection on page 24 to enable the privileged level Copy to this fileRouter# show startup-config Retrieving the Configuration File Replacing and Upgrading Dram DIMMs Product Numbers Quantity Dram Sockets Totals Sdram DimmRemoving DIMMs Polarization notchInstalling New DIMMs Inserting the DimmRecovering a Lost Password Checking the RSP Memory UpgradeInitialize the router using the i command as follows Console Port Signals Pin Signal Direction DescriptionReference Information Auxiliary Port Signals Female DB-25 Pins Male DB-25 Pins Signal DescriptionConsole and Auxiliary Y-Cable Pinouts P1-5 J1-5 and J2-5 Software Configuration Register SettingsMale DB-25 Pins Female DB-25 Pins Signal Description P1-7 J1-7 and J2-7 Ground P1-8 J1-8 and J2-8Boots the first system image in onboard Flash memory Boot Field MeaningStays at the system bootstrap prompt Bit Number Hexadecimal MeaningBit Meanings Changing SettingsRouterconfig# config-register 0xvalue Tftp flash filenameAction/Filename Bit Bit Address net host Enabling a Boot from Flash MemoryRouterconfig# boot system flash devicefilename Baud BitEnabling a Boot from the Flash Disk Obtaining Documentation Using Flash MemorySystem# copy running-config startup-config Cisco.comOrdering Documentation Obtaining Technical AssistanceDocumentation CD-ROM Documentation FeedbackCisco TAC Website Opening a TAC Case TAC Case Priority DefinitionsObtaining Additional Publications and Information Copyright 2004 Cisco Systems, Inc. All rights reserved