Cisco Systems CISCO7201 Problem Solving Using a Subsystems Approach, Identifying Startup Problems

Models: CISCO7201

1 166
Download 166 pages 19.06 Kb
Page 115
Image 115

Chapter 5 Troubleshooting Initial Startup Problems

Problem Solving Using a Subsystems Approach

Problem Solving Using a Subsystems Approach

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:

Power subsystem—This subsystem comprises the power supply, the external power cable, and the system board.

Cooling subsystem—The fans should be operating whenever system power is on. Contact your customer service representative if you determine a fan is not functioning properly.

Processor subsystem—This subsystem includes the processing and input/output functions, the port adapter or service adapter, and system memory and management functions. The ENABLE LED on the port adapter indicates if the port adapter is initialized. A port adapter that is partially installed can cause the system to pause indefinitely and reload.

The following sections 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 port adapter or service adapter that is dislodged from the system board. 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 router for the first time, you should observe the startup sequence described in the “Starting the System and Observing Initial Conditions” section on page 3-8in Chapter 3, “Starting and Configuring 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.

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, and 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:

You should immediately hear the fans operating. If not, proceed to the “Troubleshooting the Cooling Subsystem” section on page 5-6. If you determine that the power supply is functioning normally and that a fan is faulty, contact a customer service representative. If a fan does not function properly at initial startup, there are no installation adjustments that you should make.

The STATUS LED should come on. As the system boots to the ROM monitor state, the STATUS LED blinks amber. The STATUS LED turns green when the system boots to the Cisco IOS state. If the system does not boot properly, call your local service representative.

The EN (Enable) LED comes on and indicates that a RJ-45 port (0/0 and 0/1) is initialized and enabled for operation by the system. This LED comes on during a successful router boot and remains on during normal operation of the router. If this LED remains off when you start the router, it is probably a problem with the RJ-45 port. Consult Step 6 in the troubleshooting table on page 5-2.

The native LINK/ACTV LED is solid green when a Gigabit Ethernet SFP port (0/0, 0/1, 0/2, or 0/3) is up with no activity. When it is receiving a carrier signal from the network, it flashes green.

Cisco 7201 Installation and Configuration Guide

 

OL-11364-04

5-3

 

 

 

Page 115
Image 115
Cisco Systems CISCO7201 manual Problem Solving Using a Subsystems Approach, Identifying Startup Problems