Banner
HomeTOCPrevNextGlossSearchHelp

PDF

Table of Contents

Troubleshooting the Installation

Troubleshooting the Installation

Troubleshooting the Installation

Your Cisco 7206 router went through extensive testing before leaving the factory. However, if you encounter problems starting the router, use the information in this chapter to help isolate the cause of the problems. This chapter contains the following sections:

The procedures in this chapter assume that you are troubleshooting the initial system startup, and that the Cisco 7206 is in the original factory configuration. If you have removed or replaced components or changed any default settings, the recommendations in this chapter might not apply. Make sure to review the safety warnings listed in the appendix "Translated Safety Warnings" before using the troubleshooting procedures in this chapter.

If you are unable to easily solve the problem, contact a customer service representative for assistance and further instructions. Provide the representative with the following information:

Figure 5-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; then resolve the problem if possible.

Figure 5-1 : Troubleshooting Strategy for Startup Problems

h6595.gif


Troubleshooting Overview

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


Problem Solving with Subsystems

The key to solving problems with the system is isolating 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 caused by 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

Startup problems are commonly due to the source power or to a board (network processing engine, I/O controller, or port adapter) that is dislodged from the midplane. Although an overtemperature condition is unlikely at initial startup, the environmental monitoring functions are included in this chapter because they also monitor internal voltages.

When you start up the Cisco 7206 for the first time, you should observe the startup sequence described in the section "Starting the Cisco 7206" in the chapter "Installing the Cisco 7206." 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 fan tray and network processing engine, 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 to try to resolve the problem.

When you start up the system by turning on the power supply switch, the following should occur:

If the green Power OK LED does not come on, proceed to the section "Troubleshooting the Power Subsystem."


Troubleshooting the Power Subsystem

Check the following to help isolate a problem with the power subsystem:

If you are unable to resolve the problem or you determine that either a power supply or chassis connector is faulty, contact a service representative for instructions.


Troubleshooting the Processor Subsystem

The processor subsystem comprises the I/O controller, network processing engine, and all port adapters. The I/O controller and network processing engine are required system components. The system cannot operate unless the I/O controller and network processing engine are installed properly; however, the system can operate without any port adapters installed as long as none are in partial contact with the midplane pins. A port adapter that is partially connected to the midplane will send incomplete signals to the processor, which will fault the PCI bus and cause the system to hang. Therefore, first ensure that the I/O controller and the network processing engine are installed properly and the system software has initialized successfully. Then, if necessary, you can troubleshoot individual port adapters.


Troubleshooting the I/O Controller

These procedures assume that the I/O controller, network processing engine, and router itself are in the original factory configuration, and that you have not made changes to your configuration file.

If the I/O controller LEDs do not go on as expected (refer to the section "Identifying Startup Problems" in this chapter), check the following items to help isolate the problem.


Troubleshooting the Network Processing Engine

These procedures assume that the I/O controller, network processing engine, and router itself are in the original factory configuration, and that you have not made changes to your configuration file.

If the I/O controller enabled LED does not go on as expected, make sure the power to the router is turned off, reseat the network processing engine in its slot, and restart the router.

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


Troubleshooting the Port Adapters

Check the following to help isolate a problem with the port adapters:

If yes, the system is operational.


Troubleshooting the Cooling Subsystem

Check the following to help isolate a problem with the cooling system:

To determine if the fans are operating, listen for them. In noisy environments, place your hand on the left side of the chassis (when viewing the chassis from the front) 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 power OK LED will go off and 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 router's inlet vent, 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.

The above 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 section "Functional Overview" in the chapter "Product Overview" for descriptions of the show environment and show environment table commands.)

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-1996 © Cisco Systems Inc.