Banner
HomeTOCPrevNextGlossSearchHelp

PDF

Table of Contents

Troubleshooting the Installation


Troubleshooting the Installation

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:

When each of these conditions is met, the hardware installation is complete, and you should proceed to the Router Products Getting Started Guide 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:


Troubleshooting Overview

This section describes the troubleshooting methods used in this chapter and defines how the router is divided into subsystems for more efficient problem solving.

Figure 4-1 shows the general troubleshooting strategy described in this chapter. Refer to this chart as necessary to follow the steps to isolate problems to a specific subsystem, and resolve the problem if possible.

Figure 4-1 Troubleshooting Strategy for Startup Problems

h3885.gif


Problem Solving with Subsystems

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.


Identifying Startup Problems

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 LEDs for AC power (or input power), upper power, or lower power do not come on, or if the DC fail (or out fail) LED on any power supply does come on, proceed to the section "Troubleshooting the Power Subsystem" following.

If the normal LEDs on the RSP and chassis front panel do not come on, or if the CPU halt LED comes on and remains on, proceed to the section "Troubleshooting the RSP2" later in this chapter.


Troubleshooting the Power Subsystem

Check the following to help isolate the problem:

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.


Troubleshooting the Cooling Subsystem

Check the following to help isolate the problem:

To determine whether the blower is operating, listen for the motor. In noisy environments, place your hand above and to each side of the processor slots on the rear of the chassis (when facing the interface processor end of the router) to feel for air being forced out the vents.
Queued messages:        
%ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdown

If an environmental shutdown results from an out-of-tolerance power condition, the DC OK LED will go off before the system shuts down. (Refer to the section "Troubleshooting the Power Subsystem" in this chapter.) Although an overtemperature condition is unlikely at initial startup, ensure that heated exhaust air from other equipment is not entering the inlet vents, and that there is sufficient clearance around the sides of the chassis to allow cooling air to flow. Refer to the section "Preventive Site Configuration: Maintaining Normal Operation" in the chapter "Preparing for Installation" for preventive site configurations.

This message could also indicate a faulty component or temperature sensor. Before the system shuts down, use the show environment or show environment table command to display the internal chassis environment. (Refer to the chapter "Product Overview" for detailed descriptions.)

If you are still unable to resolve the problem, contact a service representative for further instructions.


Troubleshooting the Processor Subsystem

The processor subsystem comprises the RSP and interface processors. The RSP is a required system component. The system cannot operate unless the RSP is installed properly; however, because the CyBus interface processors support OIR, the system can operate without any interface processors installed as long as none are in partial contact with the backplane pins; an interface processor that is partially connected to the backplane will send incomplete signals to the processor, which will fault the bus and cause the system to hang. Therefore, first ensure that the RSP2 is installed properly and the system software has initialized successfully. Then, if necessary, you can troubleshoot individual interface processors.


Troubleshooting the RSP2

These procedures assume that the RSP2 and router are in the original factory configuration, and that you have not changed any configuration register settings or made changes to your configuration file. If you have made such changes, refer to the section "Configuring the RSP2" in the chapter "Maintaining the Router" to reselect default values.

If the RSP2 LEDs do not go on as expected, check the following items to help isolate the problem.

If yes, the system software has initialized successfully, and the system is operational.

If yes, the system has detected a processor hardware failure. (This LED should be off in normal operation.) Contact a service representative for instructions.


Troubleshooting the Interface Processors

Check the following to help isolate the problem:

If yes, the system is operational. Proceed to the instructions for configuring the interfaces in the appropriate software documentation.

If you experience trouble with the startup that is not resolved with these procedures, contact a service representative for assistance and further instructions.

 

HomeTOCPrevNextGlossSearchHelp
-

Copyright 1988-1995 © Cisco Systems Inc.