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 you encounter 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 the source power or an interface processor that has become dislodged from the backplane. Although an overtemperature condition is unlikely at initial startup, the environmental monitoring functions are included because they also monitor internal voltages.


Note The procedures in this chapter assume that you are troubleshooting the initial system startup, and that the router is in the original factory configuration. If you have removed or replaced components or changed any default settings, the recommendations in this section might not apply.

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 appropriate software documentation to configure the system and the individual 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:

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

h2819.gif


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


Problem Solving with Subsystems

The key to problem solving 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. Because 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 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 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 section "Starting the Router" 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.

By checking the state of the LEDs on the power supply and processor modules (the RSP1 and interface processors), 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 main system power switch on the interface processor end of the power supply, the following should occur:

The green DC OK LED indicates the status of the power supply and internal DC voltages. The DC OK LED stays on when all of the following conditions are met:

If the AC or DC source power or any of the internal DC voltages exceeds allowable tolerances, the DC OK LED will not go on, or will go off shortly after you turn on the power. Because both the RSP1 (which uses +5, +12, --12 VDC), and the fan tray (which uses +24 VDC) are required for operation, a problem with any of the internal DC lines can prevent the system from starting up or continuing operation.

For example, if there is a problem with the +24 VDC line that supplies the fan tray, the system will start up but also recognize that the fans are not operating. The system will initiate a fan failure shutdown sequence, display the appropriate warning messages, then shut down after two minutes. If there is a problem with any of the other DC lines, the RSP1 will not be able to initialize the system software, so the system might attempt to start up and fail during the boot sequence.

Depending on when the DC OK LED goes off, proceed as follows:
%ENVM-2-FAN: Fan array has failed, shutdown in 2 minutes        

If the normal LED on the RSP1 does not go on, or if the CPU halt LED goes on and stays on, proceed to the section "Troubleshooting the Cooling Subsystem" in this chapter.

Note While the system is starting up and initializing the individual interface processors, the status LEDs on the interface processors will flash on and off or light intermittently; this is normal behavior. The LEDs do not indicate the true status of the interfaces until the system has initialized the interface processors and you have enabled the individual interfaces.

When the LEDs indicate that the system has initialized successfully, the system banner (similar to the following example) should be displayed on the console screen. If it is not displayed, refer to the section "Connecting the Console Terminal," in the chapter "Installing the Router," to verify that the terminal is set correctly and that it is properly connected to the RSP1 console port.

System Bootstrap, Version 4.6(5), SOFTWARE        
Copyright (c) 1986-1995 by cisco Systems
RSP1 processor with 16384 Kbytes of memory
(display text omitted)
F3: 2012356+47852+194864 at 0x1000
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
              cisco Systems, Inc.
              170 Tasman Drive
              San Jose, CA 95134
GS Software (GS7), Version 10.3(3) [fc3], RELEASE SOFTWARE
Copyright (c) 1986-1995 by cisco Systems, Inc.
(display text omitted)
Press RETURN to get started!


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 the power supply or power cable is faulty, contact a service representative for instructions.


Troubleshooting the Cooling Subsystem

Check the following to help isolate the problem:

To determine whether the fans are operating, listen for the fan motors. In noisy environments, place your hand next to the left side of the chassis (when facing the interface processor end of the router) to feel for air being forced out the side vents.
%ENVM-2-FAN: Fan array has failed, shutdown in 2 minutes        

If one or more fans or the fan control board fails, you must replace the fan tray.
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 guidelines 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 RSP1 and interface processors. The RSP1 is a required system component. The system cannot operate unless the RSP1 is installed properly; however, because the CyBus interface processors support OIR, the system can operate without any interface processors installed if none of their connectors 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 RSP1 is installed properly and the system software has initialized successfully. Then, if necessary, you can troubleshoot individual interface processors.


Troubleshooting the RSP1

These procedures assume that the RSP1 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 RSP1," in the chapter "Maintaining the Router," to ensure that the software configuration register is set to the factory defaults. For example, the software configuration register boot field should be set to boot from ROM.

If the RSP1 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. 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.