Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Support

Troubleshooting Hardware and Booting Problems

Downloads

Table Of Contents

Troubleshooting Hardware and Booting Problems

Booting the Router

Network Booting Tips

Fault-Tolerant Boot Strategies

Timeouts and Out-of-Order Packets

Information for Technical Support

Troubleshooting Hardware

Cisco 7500 Series Startup

Cisco 7000 Series Startup

Cisco 4000 Series Startup

Cisco 2500 Series Startup

Catalyst 5000 Series Startup

Catalyst 2900 Series Startup

Testing and Verifying Replacement Parts

Troubleshooting Booting Problems

Booting: Router Fails to Boot from Flash Memory

Booting: Vector Error Occurs When Booting from Flash Memory

Booting: Router Partially Boots from Flash and Displays Boot Prompt

Booting: Router Cannot Network Boot from TFTP Server

Booting: Router Cannot Network Boot from Another Router

Booting: Timeouts and Out-of-Order Packets Prevent  Network Booting

Booting: Invalid Routes Prevent Network Booting

Booting: Client ARP Requests Timeout During Network Boot

Booting: Undefined Load Module Error When Network Booting

Booting: Router Hangs After ROM Monitor Initializes

Booting: Router Is Stuck in ROM Monitor Mode

Booting: Scrambled Output When Booting from ROM

Booting: Local Timeouts Occur When Booting from ROM

Booting: Unresponsive Terminal Connection to  Unconfigured Access Server

Catalyst 6000 Series Startup

How to Recover a Catalyst 6000 from a Corrupted or Missing Boot Image (from CCO)

Things to Be Aware of Before You Use the Recovery Procedure

Recovery Procedures

Method 1: Boot Loader Recovery Procedure Using a Cisco 4500/4700 Router

Method 2: OOB Boot Loader Recovery Procedure Using xmodem

Loading the Catalyst IOS Image

Loading the Catalyst OS Image

Cisco 2600 TFTP Download and Startup

Introduction

Troubleshooting the Power and Cooling Systems

Cisco 3600 Startup

Introduction

Troubleshooting

Cisco Catalyst 4000 Startup

Troubleshooting


Troubleshooting Hardware and Booting Problems

This chapter provides procedures for troubleshooting hardware and booting problems. Although it provides specific procedures for some Cisco products, always refer to your hardware installation and maintenance publication for more detailed information about your specific platform, including descriptions of specific LEDs, configuration information, and additional troubleshooting information.

This chapter begins with the following sections on hardware problems:

•Cisco 7500 Series Startup—Describes hardware and boot process troubleshooting for Cisco 7500 series routers

•Cisco 7000 Series Startup—Describes hardware and boot process troubleshooting for Cisco 7000 series routers

•Cisco 4000 Series Startup—Describes hardware and boot process troubleshooting for Cisco 4000 series routers

•Cisco 2500 Series Startup—Describes hardware and boot process troubleshooting for Cisco 2500 series routers

•Catalyst 5000 Series Startup—Describes hardware and boot process troubleshooting for Catalyst 5000 series LAN switches

•Catalyst 2900 Series Startup—Describes hardware and boot process troubleshooting for Catalyst 2900 series LAN switches

•Testing and Verifying Replacement Parts—Provides suggested actions when swapping router hardware

•Catalyst 6000 Series Startup—Describes hardware and boot process troubleshooting for Catalyst 6000 series LAN switches

•Cisco 2600 Series Startup—Describes hardware and boot process troubleshooting for Cisco 2600 series routers

•Cisco 3600 Series Startup—Describes hardware and boot process troubleshooting for Cisco 3600 series routers

•Catalyst 4000 Series Startup—Describes hardware and boot process troubleshooting for Catalyst 4000 series LAN switches

The remaining sections describe symptoms, problems, and solutions for Flash boot, network boot using TFTP, ROM boot, and other bootup problems:

•Booting: Router Fails to Boot from Flash Memory

•Booting: Vector Error Occurs When Booting from Flash Memory

•Booting: Router Partially Boots from Flash and Displays Boot Prompt

•Booting: Router Cannot Network boot from TFTP Server

•Booting: Router Cannot Network boot from Another Router

•Booting: Timeouts and Out-of-Order Packets Prevent Network booting

•Booting: Invalid Routes Prevent Network booting

•Booting: Client ARP Requests Timeout During Network boot

•Booting: Undefined Load Module Error When Network booting

•Booting: Router Hangs After ROM Monitor Initializes

•Booting: Router Is Stuck in ROM Monitor Mode

•Booting: Scrambled Output When Booting from ROM

•Booting: Local Timeouts Occur When Booting from ROM

•Booting: Unresponsive Terminal Connection to Unconfigured Access Server

Booting the Router

Cisco routers can initialize the system (boot) in four ways:

•Network boot—Routers can boot from a server using the Trivial File Transfer Protocol (TFTP), the DEC Maintenance Operation Protocol (MOP), or the Remote Copy Protocol (RCP) across any of the supported media types (such as Ethernet, Token Ring, Fiber Distributed Data Interface [FDDI], High-Speed Serial Interface [HSSI], and serial lines).

•Flash memory—Routers can boot from Flash memory, a nonvolatile storage medium that can be electrically erased and reprogrammed.

•ROM—Routers can boot a system from built-in read-only memory (ROM).

•PC Flash memory card—Routers can boot from a removable Flash memory card.

This section provides general information about router booting.

Network Booting Tips

During network booting sessions, routers behave like hosts. They route via proxy Address Resolution Protocol (ARP), Serial Line Address Resolution Protocol (SLARP) information, Internet Control Message Protocol (ICMP) redirects, or a default gateway. When network booting, routers ignore dynamic routing information, static IP routes, and bridging information. As a result, intermediate routers are responsible for handling ARP and User Datagram Protocol (UDP) requests correctly. For serial and HSSI media, ARP is not used.

Before network booting from a server, you should ping the server from the ROM software. If you cannot ping the server, follow the procedures described in the section "Booting: Router Cannot Network boot from TFTP Server," later in this chapter. If you still cannot ping the server, there is probably a server configuration or hardware problem. Refer to your TFTP server documentation, or contact your technical support representative for assistance.

Fault-Tolerant Boot Strategies

Although network booting is useful, network or server failures can make network booting impossible. After you have installed and configured the router's Flash memory, configure the boot sequence for the router to reduce the impact of a server or network failure. The following order is recommended:

1. Boot an image from Flash memory.

2. Boot an image using a network boot.

3. Boot from a ROM image.

The following is an example of how to configure a router with a fault-tolerant boot sequence. 

goriot# configure terminal

Enter configuration commands, one per line.  End with CNTL/Z.

goriot(config)# boot system flash gsxx

goriot(config)# boot system gsxx 131.108.1.101

goriot(config)# boot system rom

goriot(config)# ^Z

goriot#

%SYS-5-CONFIG_I: Configured from console by console

goriot# copy running-config startup-config

[ok]

goriot#

Using this strategy, a router has three sources from which to boot: Flash memory, network boot, and ROM. Providing alternative sources can help to mitigate any failure of the TFTP server or the network.

Note The configuration register must be set to allow ROM image booting after failed network booting attempts. For more information, refer to the hardware configuration manual for your platform.

Timeouts and Out-of-Order Packets

When network booting, a client might need to retransmit requests before receiving a response to an ARP request. These retransmissions can result in timeouts and out-of-order packets.

Timeouts (shown as periods in a network booting display) and out-of-order packets (shown as uppercase O's) do not necessarily prevent a successful network boot. It is acceptable to have either or both timeouts or out-of-order packets occur during the network boot process.

The following examples show console output from network booting sessions that were successful even though timeouts and out-of-order packets occurred (exclamation points represent successfully received packets):

Booting gs3-bfx from 131.108.1.123: !.!!!!!!!!!!!!!!!!!!!!!!

Booting gs3-bfx from 131.108.1.123: !O.O!!!!!!!!!!!!!!!!!!!!!!

If a network boot generates excessive out-of-order packets and timeouts, problems might result. These problems are discussed later in this chapter, in the section "Booting: Timeouts and Out-of-Order Packets Prevent Network booting."

Information for Technical Support

If you cannot resolve your booting problem using the procedures outlined in this chapter, collect the following information for your technical support representative:

•ROM images. (Use the show version exec command.)

•Programmable ROM labels. (This information is printed on the physical chip, and an example is shown in Figure 3-1.)

Figure 3-1 An Example of a Boot ROM Label—Boot ROM Version 11.1(2)

•NVRAM configurations for client and adjacent routers.

•Debugging output from adjacent routers using the following privileged exec commands:

–debug ip packet

–debug arp

–debug ip udp

–debug tftp

For more information about these debug commands, refer to the Debug Command Reference.

Troubleshooting Hardware

This section discusses procedures for connectivity problems related to booting. It describes specific booting symptoms, the problems that are likely to cause each symptom, and the solutions to those problems.

Cisco 7500 Series Startup

When you start up a Cisco 7500 series router, the following should occur:

•The AC (or DC) OK LED should go on immediately and should remain on as long as the system is receiving power.

•The blower should be operating.

•The Route Switch Processor (RSP) and front-panel Normal LEDs should go on (to indicate normal system operation) and should remain on during system operation; the CPU Halt LED should remain off.

•The Enabled LED on each interface processor should go on (to indicate that the RSP has completed initialization of the interface processor).

When the 7500 series system has initialized successfully, the system banner should be displayed on the console screen. If it is not displayed, make sure that the console terminal is properly connected to the RSP console port and that the terminal is set correctly. The system banner should look similar to the following: 

System Bootstrap, Version 4.6(5), SOFTWARE

Copyright (c) 1986-1995 by cisco Systems

RSP2 processor with 16384 Kbytes of memory

### [...] ###

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 (RSP-K), Version 10.3(571) [fc3], RELEASE SOFTWARE

Copyright (c) 1986-1995 by cisco Systems, Inc.

[...]

Press RETURN to get started!

If a problem occurs, try to isolate the problem to a specific subsystem. The Cisco 7500 series routers have the following subsystems:

•Power subsystem—Includes power supplies, external power cable, and backplane

•Cooling subsystem—Depending on your system, includes the following:

–Cisco 7505—Fan tray, fan tray spare with six individual fans, and fan control board

–Cisco 7507—Chassis blower

–Cisco 7513—Blower module, including blower, blower-speed control board, front-panel LEDs, and the module itself

•Processor subsystem—Depending on your system, includes all interface processors and either the RSP1 or the RSP2

Table 3-1 outlines the areas where Cisco 7500 series startup problems may occur and describes solutions to those problems.

Table 3-1 Hardware: Cisco 7500 Series Startup Problems and Solutions 

Possible Problem Area
Solution

Power subsystem

1. Check to see whether the blower is operating and that LEDs on the processor modules are on. If the blower and LEDs are on but the Power Supply LED is off, there is probably a faulty Power Supply LED.

2. Make sure that the power switch is set correctly to the on position.

3. Make sure that the power source, power cable, and power supply are functioning correctly. Swap parts to see whether one of the components is faulty.

4. Ensure that the blower module is seated properly. Make sure that the blower control board edge connector is inserted fully in the backplane socket.

Cooling subsystem

1. Check to see whether the blower is operating when you start up the system. If the blower is not operating, there might be a problem with the blower or the +24 V DC power:

•If the Output Fail LED is on, there might be a problem with the +24V DC supply to the blower or fan tray at either the power supply or the blower control board.

•If the blower is not operating and the Output Fail LED is off, ensure that the blower module is seated properly. Ensure that the blower control board edge connector is inserted fully in the backplane socket.

2. If the system and blower start up but shut down after about 2 minutes, one or more fans might have failed or might be operating out of tolerance. You will probably see an error message similar to the following:

%ENVM-2-FAN: Fan has failed, shutdown in 2 minutes

If the blower or the blower control board fails, you must replace the blower module.

3. If you see the following message at startup, the system has detected an overtemperature condition or out-of-tolerance power inside the chassis:

Queued messages:

%ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdown

If an environmental shutdown results from an out-of-tolerance power condition, the Output Fail LED goes on before the system shuts down.

This shutdown message might also indicate a faulty component or temperature sensor. Before the system shuts down, use the show environment or show environment table commands to display the internal chassis environment.

4. Ensure that heated exhaust air from other equipment is not entering the inlet vents and that there is sufficient clearance around the chassis to allow cooling air to flow.

Processor subsystem

1. Check the RSP1 LEDs. If no LEDs come on, ensure that the power supplies and blower are functioning properly.

2. Check the seating of the RSP. If the RSP is not seated properly, it will hang the system.

3. If the RSP CPU Halt LED is on, the system has detected a processor hardware failure. Contact a technical support representative for instructions.

4. Check to see whether the RSP Normal LED is on, indicating that the system software has initialized successfully and that the system is operational.

5. Check the Enabled LED on each interface processor. This LED should go on when the RSP has initialized the interface processor.

6. If the Enabled LED on an individual interface processor is off, the interface processor might have pulled away from the backplane. If the interface processors are not seated properly, they will hang the system.

1 RSP = Route Switch Processor


Cisco 7000 Series Startup

When you start up a Cisco 7000 series router, the following should occur:

•The DC OK LED should go on and should remain on as long as the system is receiving source power.

•The fans should be operating.

•The Route Processor (RP) Normal LED should go on and stay on to indicate normal system operation; the Halt CPU LED should remain off.

•The Enabled LED on the Switch Processor (SP) or Silicon Switch Processor (SSP) and each interface processor should go on when the RP has completed initialization of the interface processor or SP (or SSP) for operation.

When the system has initialized successfully, the system banner should be displayed on the console screen. If it is not displayed, make sure that the console terminal is properly connected to the RP console port and that the terminal is set correctly. The system banner should look similar to the following: 

System Bootstrap, Version 4.6(5), SOFTWARE

Copyright (c) 1986-1995 by cisco Systems

RP1 processor with 16384 Kbytes of memory

### [...] ###

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 West Tasman Drive

              San Jose, California 95134-1706


GS Software (GS7), Version 10.3(1) [fc3], RELEASE SOFTWARE

Copyright (c) 1986-1995 by cisco Systems, Inc.


RP1 (68040) processor with 16384K bytes of memory.

[...]


Press RETURN to get started!

If problems occur, try to isolate the problem to a specific subsystem. The Cisco 7000 series routers have the following subsystems:

•Power subsystem—Includes power supplies, fans, external power cable, and internal power harness that connects to the backplane

•Cooling subsystem—Depending on your system, includes the following:

–Cisco 7000—Chassis blower

–Cisco 7010—Fan tray assembly, including six individual fans, the fan control board, and the tray itself

•Processor subsystem—Includes the RP, SP (or SSP), and all interface processors

Table 3-2 outlines the areas where Cisco 7000 series startup problems may occur and describes solutions to those problems.

Table 3-2 Hardware: Cisco 7000 Series Startup Problems and Solutions 

Possible Problem Area
Solution

Power subsystem

1. Check to see whether the DC OK LED is on.

2. If the LED is not on but the fans are operating and LEDs on the processor modules are on, the Power Supply LED might be faulty.

3. If the LED is not on and there is no other activity, make sure that the power switch is fully in the on position.

4. Make sure that the power source, power cable, and power supply are functioning correctly. Swap parts to see whether one of the components is faulty.

5. Ensure that the fan tray is seated properly. Make sure that the fan control board edge connector is inserted fully in the backplane socket.

Cooling subsystem

1. Check to see whether the fans are operating.

2. If the fans are not operating and the DC OK LED is off, there might be a problem with the +24V DC power.

3. Ensure that the fan tray is seated properly. Make sure that the fan control board edge connector is inserted fully in the backplane socket.

4. If the system and the fans start up but shut down after about 2 minutes, one or more fans has failed or is operating out of tolerance. You will see an error message similar to the following:

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

5. If you see the following error message, the system has detected an overtemperature condition or out-of-tolerance power inside the chassis:

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.

Cooling subsystem (continued)

This shutdown message could also indicate a faulty component or temperature sensor. Use the show environment or show environment table command to display the internal chassis environment.

6. Make sure that heated exhaust air from other equipment is not entering the inlet vents, and that there is sufficient clearance around the chassis to allow cooling air to flow.

Processor subsystem

1. Check to see whether the RP1 LEDs come on when system power is turned on.

2. If none of the RP LEDs come on, make sure that both the fan and the power supply are functioning properly.

3. If the power supply and fans appear operational but none of the RP LEDs are on, an improperly connected RP, SP 2 (or SSP3 ), or interface processor might have hung the bus.

4. If the SP (or SSP) Enabled LED is off but any of the RP LEDs are on, make sure that the SP (or SSP) is seated in its slot properly.

5. Check to see whether the Boot Error LED is on. If the LED is on, the system software is incapable of starting up. If you have a spare RP with the system software ROMs installed, replace the installed RP with the spare to see whether the system will boot.

6. Check to see whether the RP CPU Halt LED is on. If it is, the system has detected a processor hardware failure. Contact a technical support representative for more information.

7. Check to see whether all interface processor Enabled LEDs are on.

8. If the Enabled LED on an individual interface processor is off, make sure that the interface processor has not pulled away from the backplane.

1 RP = Route Processor

2 SP = Switch Processor

3 SSP = Silicon Switch Processor


Cisco 4000 Series Startup

When you start up a Cisco 4000 series router, the following should occur:

•The System OK LED should come on and stay on as long as power is supplied.

•The fans should be operating.

When the system has initialized successfully, the system banner should be displayed on the console screen. The system banner should look similar to the following: 

System Bootstrap, Version 4.14(9), SOFTWARE

Copyright (c) 1986-1994 by cisco Systems

4000 processor with 16384 Kbytes of main memory


Loading xx-j-mz.112-0.15 at 0x4A790, size = 3496424 bytes [OK]

F3: 8988+3487404+165008 at 0x12000

Self decompressing the image : ###[...]#### [OK]


              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 West Tasman Drive

           San Jose, California 95134-1706




Cisco Internetwork Operating System Software

IOS (tm) 4000 Software (XX-J-M), Version 11.2(0.15), BETA TEST SOFTWARE

Copyright (c) 1986-1996 by cisco Systems, Inc.

Compiled Wed 03-Jul-96 01:21 by susingh

Image text-base: 0x00012000, data-base: 0x006F6494



cisco 4000 (68030) processor (revision 0xA0) with 16384K/4096K bytes of memory.

Processor board ID 5007155

G.703/E1 software, Version 1.0.

Bridging software.

SuperLAT software copyright 1990 by Meridian Technology Corp).

X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.

TN3270 Emulation software (copyright 1994 by TGV Inc).

Basic Rate ISDN software, Version 1.0.

2 Ethernet/IEEE 802.3 interfaces.

4 Serial network interfaces.

8 ISDN Basic Rate interfaces.

128K bytes of non-volatile configuration memory.

4096K bytes of processor board System flash (Read/Write)


Press RETURN to get started!

If problems occur, try to isolate the problem to a specific subsystem. The Cisco 4000 series routers have the following subsystems:

•Power subsystem—This subsystem includes the power supply and the wiring.

•Cooling subsystem—This subsystem includes the blower assembly, which should come on when power is applied.

•Network processor modules (NPMs)—This subsystem includes all NPMs installed in the router chassis.

•System cables—This subsystem includes all the external cables that connect the router to the network.

Table 3-3 outlines the areas where Cisco 4000 series startup problems may occur and describes solutions to those problems.

Table 3-3 Hardware: Cisco 4000 Series Startup Problems and Solutions

Possible Problem Area
Solution

Power and cooling subsystems

1. Check to see whether the blower is operating. If it is not, check the AC power input, AC power source, router circuit breaker, and power supply cable.

2. If the system shuts down after being on a short time, check the power supply. If the power supply appears operational, the router might have shut down due to overheating. Check the console for error messages similar to the following:

%SYS-1-OVERTEMP: System detected OVERTEMPERATURE condition. Please resolve cooling problem immediately!

Make sure that the fans are working and that there is no air blockage to cooling vents.

3. If the system partially boots but LEDs do not light, contact your technical support representative.

NPMs1 and cables

1. Make sure that NPMs are properly connected to the motherboard connector.

2. Check the external cables.

3. Check the processor or software for proper configuration.

4. Check the external console connection and verify that the console baud rate is correct.

1 NPMs = network processor modules


Cisco 2500 Series Startup

When you start up a Cisco 2500 series router, the following should occur:

•The System OK LED should come on and stay on as long as power is supplied.

•The fans should be operating.

When the system has initialized successfully, the system banner should be displayed on the console screen. The system banner should look similar to the following: 

System Bootstrap, Version (3.3), SOFTWARE

Copyright (c) 1986-1993 by cisco Systems

2500 processor with 16384 Kbytes of main memory


Unknown or ambiguous service arg - udp-small-servers

Unknown or ambiguous service arg - tcp-small-servers

Booting igs-in-l.110-9 from Flash address space

F3: 3844616+90320+228904 at 0x3000060


              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 West Tasman Drive

           San Jose, California 95134-1706




Cisco Internetwork Operating System Software

IOS (tm) 3000 Software (IGS-IN-L), Version 11.0(9), RELEASE SOFTWARE (fc1)

Copyright (c) 1986-1996 by cisco Systems, Inc.

Compiled Tue 11-Jun-96 01:15 by loreilly

Image text-base: 0x03020F8C, data-base: 0x00001000


cisco 2500 (68030) processor (revision A) with 16384K/2048K bytes of memory.

Processor board ID 01062462, with hardware revision 00000000

Bridging software.

X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.

Basic Rate ISDN software, Version 1.0.

1 Ethernet/IEEE 802.3 interface.

2 Serial network interfaces.

1 ISDN Basic Rate interface.

32K bytes of non-volatile configuration memory.

4096K bytes of processor board System flash (Read ONLY)



Press RETURN to get started!

If problems occur, try to isolate the problem to a specific subsystem. The Cisco 2500 series routers have the following subsystems:

•Power subsystem—This subsystem includes the power supply and the wiring.

•Cooling subsystem—This subsystem includes the fan, which should go on when power is applied.

•Network interfaces—This subsystem includes all network interfaces, such as Ethernet, Token Ring, serial, or ISDN Basic Rate Interface (BRI).

•System cables—This subsystem includes all the external cables that connect the router to the network.

Table 3-4 outlines the areas where Cisco 2500 series startup problems may occur and describes solutions to those problems.

Table 3-4 Hardware: Cisco 2500 Series Startup Problems and Solutions

Possible Problem Area
Solution

Power and cooling subsystems

1. If the Power LED is off, make sure that the power supply is plugged in to the wall receptacle and that the cable from the power supply to the router is connected.

2. If the system shuts down after being on a short time, there might have been a thermal-induced shutdown caused by a faulty fan, or the power to the system might have been lost. Ensure that the system is receiving power and that the chassis intake and exhaust vents are clear.

3. If the system does not boot up but LEDs are on, check the 12V power supply.

4. If the system partially boots but LEDs are not on, check the 5V power supply.

Network interfaces and cables

1. If a network interface is not recognized by the system, check the interface cable connection and the LED on the network interface.

2. If a network interface is recognized but will not initialize, check the interface cable connection.

3. If the system will not boot properly or constantly, or if it intermittently reboots, there might be a processor or software problem. Make sure that DRAM SIMM modules are seated properly.

4. If the system boots but the console screen is frozen, check the external console connection and verify that the console baud rate is correct.

5. If the system powers on and boots with a particular interface disconnected, check the network interface connection.


Catalyst 5000 Series Startup

When you start up a Catalyst 5000 series LAN switch, the following should occur:

•The PS1 and PS2 LEDs on the supervisor engine module faceplate should be green.

•The system fan assembly should be operating, and the Fan LED on the supervisor engine module should come on.

•The Status LED on the supervisor engine module and all interfaces should be orange until the boot is complete.

When the system boot is complete, the supervisor engine module should initialize the switching modules. The status LED on each switching module goes on when initialization has been completed, and the console screen displays a script and system banner similar to the following: 

        ATE0

ATS0=1

Catalyst 5000 Power Up Diagnostics

Init NVRAM Log

LED Test

ROM CHKSUM

DUAL PORT RAM r/w

RAM r/w

RAM address test

Byte/Word Enable test

RAM r/w 55aa

RAM r/w aa55

EARL test

BOOTROM Version 1.4, Dated Dec  5 1995 16:49:40

BOOT date: 00/00/00 BOOT time: 03:18:57

SIMM RAM address test

SIMM Ram r/w 55aa

SIMM Ram r/w aa55

Start to Uncompress Image ...

IP address for Catalyst not configured

BOOTP will commence after the ports are online

Ports are coming online ...

Cisco Systems Console

If problems occur, try to isolate the problem to a specific subsystem. The Catalyst 5000 series LAN switches have the following subsystems:

•Power subsystem—This subsystem includes the power supplies and power supply fans.

•Cooling subsystem—This subsystem includes the chassis fan assembly, which should be operating when the system power is on.

•Processor and interface subsystem—This subsystem includes the supervisor engine module (which contains the system operating software), the network interfaces, and all associated cabling.

Table 3-5 outlines the areas where Catalyst 5000 series startup problems may occur and describes solutions to those problems.

Table 3-5 Hardware: Catalyst 5000 Series Startup Problems and Solutions 

Possible Problem Area
Solution

Power subsystem

1. Check to see whether the PS1 LED is on. If it is not, ensure that the power supply is connected properly and is flush with the back of the chassis. Make sure that captive installation screws are tight.

2. Check the AC source and the power cable. Connect the power cord to another power source, if one is available, and turn the power back on. If the LED fails to go on after you connect the power supply to a new power source, replace the power cord.

3. If the LED fails to go on when the switch is connected to a different power source with a new power cord, the power supply is probably faulty. If a second power supply is available, install it in the second power supply bay, and contact a customer service representative for further instructions.

4. Repeat these steps for the second power supply, if present.

Cooling subsystem

1. Check to see whether the Fan LED on the supervisor engine module is green. If it is not, check the power subsystem to see whether it is operational.

2. If the Fan LED is red, the fan assembly might not be seated properly in the backplane.

To ensure that the fan assembly is seated properly, loosen the captive installation screws, remove the fan assembly, and reinstall it. Tighten all captive installation screws, and restart the system.

3. If the Fan LED is still red, the system has probably detected a fan assembly failure. Contact a technical support representative for assistance.

Processor and interface subsystem

1. Check the supervisor engine module Status and Link LEDs. These should both be green if all diagnostic and self-tests were successful and ports are operational. For more information about interpreting the supervisor engine module LEDs, refer to the user guide for your switch.

2. Check the LEDs on individual interface modules. In most cases, these should be green (or should flicker green, in the case of Transmit and Receive LEDs) if the interface is functioning correctly. For detailed information on interpreting interface module LEDs, refer to the user guide for your switch.

3. Check all cabling and connections. Replace any faulty cabling.


Catalyst 2900 Series Startup

When you start up a Catalyst 2900 series LAN switch, the following should occur:

•The PS LED on the supervisor engine module faceplate should come on and stay green while power is applied to the system.

•The system fan assembly and Fan LED should come on and stay on while power is applied to the system.

•The Status LED on the supervisor engine module and on each interface should be orange until the boot is complete.

When the system boot is complete, the supervisor engine module initializes the switching modules. The status LED on each switching module goes on when initialization has been completed, and the console screen displays a script and system banner similar to the following: 

BOOTROM Version 2.1, Dated May 22 1996 15:17:09


Boot date: 05/22/96 BOOT time: 15:17:09


Executing from RAM



Cisco Systems Console



Sending RARP request with address 00:40:0b:a0:05:b8


Sending bootp request with address 00:40:0b:a0:05:b8


Sending RARP request with address 00:40:0b:a0:05:b8


Sending bootp request with address 00:40:0b:a0:05:b8


No bootp or rarp response received


Enter password:

If problems occur, try to isolate the problem to a specific subsystem. The Catalyst 2900 series LAN switches have the following subsystems:

•Power subsystem—This subsystem includes the power supplies and power supply fans.

•Cooling subsystem—This subsystem includes the chassis fan assembly, which should be operating when the system power is on.

•Processor and interface subsystem—This subsystem includes the supervisor engine module (which contains the system operating software), the network interfaces, and all associated cabling.

Table 3-6 outlines the areas where Catalyst 2900 series startup problems may occur and describes solutions to those problems.

Table 3-6 Hardware: Catalyst 2900 Series Startup Problems and Solutions

Possible Problem Area
Solution

Power subsystem

1. Check the Power LED. If it is off, ensure that the power supply cord is not damaged and that it is properly attached to the power supply and to an AC receptacle.

2. If the LED is red, the power supply has detected an anomaly or voltage outage and needs to be serviced. Contact your technical support representative for instructions.

Cooling subsystem

1. Check to see whether the Fan LED on the supervisor engine module is green. If it is not, check the power subsystem to see whether it is operational.

2. If the Fan LED is red, contact a technical support representative for assistance.

Series processor and interface subsystem

1. Check the supervisor engine module Status and Link LEDs. These should both be green if all diagnostic and self-tests were successful and ports are operational. For more information about interpreting the supervisor engine module LEDs, refer to the user guide for your switch.

2. Check the LEDs on individual interface modules. In most cases, these should be green (or should flicker green, in the case of transmit and receive LEDs) if the interface is functioning correctly. For detailed information on interpreting interface module LEDs, refer to the user guide for your switch.

3. Check all cabling and connections. Replace any faulty cabling.


Testing and Verifying Replacement Parts

If you are replacing a part or card to remedy a suspected problem, make only one change at a time.

To test a system, start with a simple hardware configuration and add one card at a time until a failed interface appears or is isolated. Use a simple software configuration, and test connectivity using a ping test.

If you determine that a part or card replacement is required, contact your sales or technical support representative. Specific instructions concerning part or card installation are outlined in the configuration note provided with the replacement.

For modular routers, make sure that you seat all cards correctly. Check the seating of cards if the system is not booting properly. Use the ejector levers to reseat all processor modules, and then reboot.

Caution Before accessing the chassis interior and removing any cards, turn off power to the chassis. Use extreme caution around the chassis. Potentially harmful voltages are present.
Caution To prevent damage to components that are sensitive to electrostatic discharge (ESD), attach ESD protection before opening a chassis. Make certain that the power cord is connected but that power is off. ESD damage prevention guidelines are provided in the hardware installation and maintenance publication for your router.

If a part replacement appears to solve a problem, reinstall the suspect part to verify the failure. Always double-check a repair.

Troubleshooting Booting Problems

This section discusses troubleshooting procedures for connectivity problems related to booting. It describes specific booting symptoms, the problems that are likely to cause each symptom, and the solutions to those problems.

Booting: Router Fails to Boot from Flash Memory

Symptom: When a user is booting a router from Flash memory, the boot process appears to complete, but the router does not route traffic or communicate with neighbors. In addition, exec commands might or might not appear to function.

Table 3-7 outlines the problems that might cause this symptom and describes solutions to those problems.

Table 3-7 Booting: Router Fails to Boot from Flash Memory 

Possible Problem
Solution

Incorrect or corrupted image (exec does not function)

1. Check the configuration register using the show version exec command. Set the register to boot from Flash memory. For information about configuration register settings, refer to your hardware installation and maintenance documentation.

2. Power-cycle the router.

3. Within the first 60 seconds of booting, press the Break key to access the ROM monitor.

4. At the ROM monitor prompt (>), enter o/r 0x1 to set the configuration register to boot from ROM.

5. Enter i to reinitialize the router, which causes the router to enter setup mode.

6. Obtain the correct system image. If necessary, contact your technical support representative to determine which image is correct.

7. After the correct image is identified, use the copy tftp flash privileged exec command at the router to retrieve the image.

8. Check the configuration register using the show version exec command. Set the register to boot from Flash memory.

9. Use the show running-config privileged exec command to see whether the router configuration contains the boot system flash global configuration command.

Note: Issuing the copy running-config startup-config command at this point on a Cisco 2500, Cisco 3000, Cisco 4000, or Cisco 7000 series will overwrite the configuration. Make sure that you have a backup of your configuration file.

10. Include the boot system flash command, if it is not in the configuration. Be sure to use the copy running-config startup-config command after this change.

11. Enter the reload privileged exec command to restart the router.

Syntax:

The following is the syntax for the reload command:

reload [text] | [in [hh:]mm [text]] | [at hh:mm [month day | day month] [text]] | [cancel]

Incorrect or corrupted image (exec does not function) (continued)

Examples:

The following example illustrates how to use the reload command to immediately reload the software on the router:

Router# reload

The following example illustrates how to use the reload command to reload the software on the router in 10 minutes:

Router# reload in 10

Router# Reload scheduled for 11:57:08 PDT Fri Apr 21 1996 (in 10 minutes)

Proceed with reload? [confirm]

Router#

Incorrect or corrupted image (exec functions)

1. Obtain the correct system image. If necessary, contact your technical support representative to determine which image is appropriate.

2. Use the copy tftp flash privileged exec command to retrieve the image.

3. Check the configuration register using the show version exec command. Set the register to boot from Flash memory. For information about configuration register settings, refer to your hardware installation and maintenance documentation.

4. Use the show running-config privileged exec command to determine whether the active configuration contains the boot system flash global configuration command. Use the show startup-config privileged exec command to determine whether the boot system flash command is included in the configuration stored in NVRAM1 .

5. Include the boot system flash command, if it is not in the configuration. Be sure to use the copy running-config startup-config privileged exec command to save your modification after this change.

6. Enter the reload privileged exec command to restart the router.

Syntax:

The following is the syntax for the reload command:

reload [text] | [in [hh:]mm [text]] | [at hh:mm [month day | day month] [text]] | [cancel]

Examples:

The following example illustrates how to use the reload command to immediately reload the software on the router:

Router# reload

Incorrect or corrupted image (exec functions) (continued)

The following example illustrates how to use the reload command to reload the software on the router in 10 minutes:

Router# reload in 10

Router# Reload scheduled for 11:57:08 PDT Fri Apr 21 1996 (in 10 minutes)

Proceed with reload? [confirm]

Router#

1 NVRAM = nonvolatile random-access memory


Booting: Vector Error Occurs When Booting from Flash Memory

Symptom: Vector errors occur when a user is booting a router from Flash memory.

Table 3-8 outlines the problems that might cause this symptom and describes solutions to those problems.

Table 3-8 Booting: Vector Error Occurs When Booting from Flash Memory 

Possible Problem
Solution

Compressed system image

1. Power-cycle the router.

2. Within the first 60 seconds of booting, press the Break key to access the ROM monitor.

3. At the ROM monitor prompt (>), enter o/r to set the configuration register to boot from ROM.

4. Enter b to boot the router. The router enters setup mode.

5. Press Ctrl-C to bypass the setup.

6. Enter the configure memory privileged exec command.

7. Obtain an uncompressed system image. From the router prompt, use the privileged exec command copy flash tftp to send the compressed image back to the TFTP1 server.

Decompress the image at the TFTP server. This cannot be done at the router.

8. Use the copy tftp flash privileged exec command at the router to retrieve the uncompressed image. The following is an example of the use of the copy tftp flash command:

router# copy flash tftp filename

Compressed system image (continued)

The router asks you for the IP address of the TFTP server and the name of the image file that you are copying to the server. A sample of the output for this command using IP address 131.108.10.6 and filename ic92130n follows:

IP address of remote host [255.255.255.255]? 131.108.10.6

Name of file to copy []? ic92130n

writing ic92130n !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

router#

9. Check the configuration register using the show version exec command. Set the router to boot from Flash memory.

10. Use the show running-config privileged exec command to determine whether the router configuration includes the boot system flash global configuration command in the correct order with respect to the other boot system commands.

Note: The boot system global configuration commands are saved in the order in which they were entered. The most recent entry goes to the bottom of the list. For the recommended ordering, refer to the section "Fault-Tolerant Boot Strategies," earlier in this chapter.

11. Configure the boot system flash command, if it is missing. Confirm that the order of boot system commands is correct. Use the copy running-config startup-config command to save this change. The required syntax is as follows:

copy running-config {rcp | startup-config | tftp | file-id} (Cisco 7000, Cisco 7200, and Cisco 7500 series only)

Syntax description:

rcp—Specifies a copy operation to a network server using RCP.

startup-config—Specifies the configuration used for initialization as the destination of the copy operation. The Cisco 4500 series cannot use this keyword.

tftp—Specifies a TFTP server as the destination of the copy operation.

file-id—Specifies device:filename as the destination of the copy operation. The device argument is optional, but when it is used, the colon (:) is required.

12. Enter the reload privileged exec command to restart the router.

Router hardware problem

Troubleshoot router hardware as discussed earlier in this chapter.

1 TFTP = Trivial File Transfer Protocol


Booting: Router Partially Boots from Flash and Displays Boot Prompt

Symptom: When a user is booting a Cisco 2000, Cisco 2500, Cisco 3000, or Cisco 4000 series router from Flash memory, the boot process halts and the console displays the boot prompt [router(boot)>]. In addition, the router does not route, although exec commands might appear to be operational.

Table 3-9 outlines the problems that might cause this symptom and describes solutions to those problems.