Table of Contents
Troubleshooting the Installation
Your router went through extensive testing and burn-in before leaving the factory; however, if your system appears to have problems starting up, use the information in this chapter to help isolate the cause. Problems with the initial startup will most likely be caused by an interface processor or power supply that has become dislodged from the backplane or chassis power connector. Although overtemperature conditions rarely occur at initial startup, the environmental monitoring functions are included because they also monitor DC line voltages.
This manual covers the system hardware installation only. At the initial system boot, you should verify the following:
- The power supplies are installed properly and are supplying power to the system.
- The system blower is operating.
- The system software boots successfully.
- The RP, SP (or SSP), and all interface processors are properly installed in their slots and each is initialized without problems.
When each of these conditions is met, the hardware installation is complete, and you should proceed to the Router Products Getting Started Guide on UniverCD or in the printed manual to configure the interfaces. If the startup sequence fails before these conditions are met, use the procedures in this chapter to isolate and, if possible, resolve the problem.
If you are unable to easily solve the problem, contact a customer service representative for assistance and further instructions. Before you call, have the following information ready to help your service provider assist you as quickly as possible:
This section describes the troubleshooting methods used in this chapter and defines how the router is divided into subsystems for more efficient problem solving. A description of a normal startup sequence contains pointers to sections in this chapter that contain troubleshooting procedures for specific components so that you can determine where your system is having trouble and then troubleshoot that specific component or subsystem.
The key to problem solving the system is to try to isolate the problem to a specific subsystem. The first step in solving startup problems is to compare what the system is doing to what it should be doing. Since a startup problem is usually attributable to a single component, it is more efficient to first isolate the problem to a subsystem rather than troubleshoot each separate component in the system. For these troubleshooting procedures, consider the following subsystems:
The following sections will help you isolate a problem to one of these subsystems and will direct you to the appropriate troubleshooting section.
When you start up the router for the first time, you should observe the startup sequence described in the chapter "Installing the Router."
This section contains a more detailed description of the normal startup sequence and describes the steps to take if the system does not perform that sequence as expected.
With the exception of the system blower, LEDs indicate all system states in the startup sequence. By checking the state of the LEDs, you can determine when and where the system failed in the startup sequence. Use the following descriptions to isolate the problem to a subsystem, then proceed to the appropriate sections (indicated in each description) to try to resolve the problem.
When you start up the system by turning on the power supply switches, the following should occur:
- If the AC power (or input power), upper power, or lower power LEDs do not come on, or if the DC fail (or out fail) LED on any power supply does come on, proceed to the next section, "Troubleshooting the Power Subsystem."
- If the normal LEDs on the RP and chassis front panel do not come on, or if either the boot error or CPU halt LED comes on and remains on, proceed to the section "Troubleshooting the RP Subsystem" later in this chapter.
Check the following to help isolate the problem:
- On the lower power supply, is the AC power or input power LED on?
- If yes, the power source is good, and the power supply is functional.
- If no, first suspect the power/interlock switch. Loosen the captive installation screw, turn the power switch fully counterclockwise to the off (O) position, pull the supply out of the bay a few inches, then push it firmly back into the bay, and ensure that the front of the power supply is flush with the back of the chassis.
- Tighten the captive installation screw, then turn the power switch clockwise until it is completely turned to the on (|) position, and the interlock tab is fully extended into the interlock slot in the chassis. (Refer to the section "Installing Power Supplies" in the chapter "Installing the Router.")
- If the AC power (or input power) and DC fail (or out fail) LEDs both remain off, and the switch is correctly set, suspect the power source or the power cable. Turn the switch off, connect the power cable to another power source if available, and turn the switch back on. If the LED then comes on, the problem is the first power source.
- If the LED fails to come on after you connect the power supply to a new power source, replace the power cord, and turn the switch back on. If the AC power (or input power) LED then comes on, return the first power cable for replacement.
- If the LED still fails to come on when connected to a different power source with a new power cable, the power supply is probably faulty. If a second power supply is available, install it in the lower power supply bay and contact a service representative for further instructions.
- On the lower power supply, is the DC fail (or out fail) LED on?
- Is the AC power (input power) LED on for the second (redundant) power supply?
- If not, repeat each of the above procedures for the second power supply.
If you are unable to resolve the problem, or if you determine that either a power supply or chassis connector is faulty, contact a service representative for instructions.
Check the following items to help isolate the problem:
- Did any LEDs on the RP come on?
- If no, first refer to the section "Troubleshooting the Power Subsystem" earlier in this chapter to determine whether the power subsystem is functioning properly.
- If no, suspect that an improperly connected RP, SP (or SSP), or interface processor has hung the bus. Turn all power supply switches off, then use the ejector levers to ensure that each board is seated properly. On each ejector lever pair, push the top lever down while pushing the bottom lever up until both levers are at a 90-degree orientation to the rear of the chassis. (For a description and illustration of the ejector levers, refer to the section "Ejector Levers" in the chapter "Maintenance.") Tighten all captive installation screws, then restart the system.
- Are both the RP normal and front panel normal LEDs on?
- If yes, the system software has initialized successfully, and the system is operational.
- If only one of the normal LEDs is on but the other is not, suspect an LED failure. Try proceeding with the installation and configuring the interfaces, but contact a service representative for replacement instructions.
- Is the boot error LED on?
- If yes, the system software is unable to start up. Turn the system power off and on again.
- If you have a spare RP with the system software EPROMs installed, turn the system power off and replace the installed RP with the spare.
- If after several attempts the boot error LED continues to come on, try to estimate the amount of time that elapses between power on and when the LED comes on, and contact a service representative.
- Is the RP CPU halt LED on?
- If yes, the system has detected a processor hardware failure. Contact a service representative for instructions.
Check the following to help isolate the problem:
- Are the enabled LEDs on the SP (or SSP) and all interface processors on?
- If yes, the system is operational. Proceed to the Router Products Getting Started Guide or the Router Product Configuration Guide to configure the interfaces.
- Are any enabled LEDs on the SP (or SSP) and all interface processors on?
If you experience trouble with the startup that is not resolved with these procedures, contact a service representative for assistance.
Posted: Thu Nov 1 12:50:42 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.