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

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

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

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.

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:

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

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.

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.

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.

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 tftpfilename

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:

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.

1. Use the show flash exec command to determine whether an image exists in Flash memory.

2. If no image exists, use the copy tftp flash privileged exec command to copy the system image from your TFTP1 server to the router's Flash memory. The following is an example of the use of the copy tftp flash command:

router# copy flash tftpfilename

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:

1. Use the show running-config privileged exec command to determine whether the configuration includes a boot system flash global configuration command entry. Use the show startup-config privileged exec command to determine whether the boot system flash command is included in the configuration stored in NVRAM.2

2. Check the order of the boot system commands. For the recommended ordering, refer to the section "Fault-Tolerant Boot Strategies," earlier in this chapter.

3. Add the boot system flash command or reorder the boot system commands, if necessary.

4. Save the configuration change to NVRAM using the copy running-config startup-config privileged exec command. The required syntax is as follows:

•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 a device:filename as the destination of the copy operation. The device argument is optional, but when it is used, the colon (:) is required.

Misconfigured configuration register

Use the show version exec command to check the configuration register setting. Make sure that it is set to boot from Flash memory. Refer to your hardware installation and maintenance publication for details regarding configuration register settings.

Booting: Router Cannot Network Boot from TFTP Server

Symptom: Router cannot boot from a TFTP server. The router tries to obtain its system image over the network but fails.

The following output is an example of a failed network boot session:

Booting gs3-bfx..........[failed]

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

Table 3-10 Booting: Router Cannot Network Boot from TFTP Server

Possible Problem

Solution

Network is disconnected or isolated

1. Boot the router from ROM or Flash memory, if possible.

2. Use the ping exec command to send a message to the broadcast address (255.255.255.255).

3. If there is no response from the server, use the show arp exec command to look for an entry in the ARP table that is associated with the server.

4. Use the show ip route exec command to view the IP routing table. Look for an entry in the table for the network or subnet of the server.

Sample display:

The following is sample output from the show ip route command when entered without an address:

Router# show ip route

Codes: I - IGRP derived, R - RIP derived, O - OSPF
derived

C - connected, S - static, E - EGP derived, B - BGP
derived

candidate default route, IA - OSPF inter area route

Gateway of last resort is 131.119.254.240 to network
129.140.0.0

O E2 150.150.0.0 [160/5] via 131.119.254.6, 0:01:00,
Ethernet2

E 192.67.131.0 [200/128] via 131.119.254.244,
0:02:22, Ethernet2

O E2 192.68.132.0 [160/5] via 131.119.254.6, 0:00:59,
Ethernet2

O E2 130.130.0.0 [160/5] via 131.119.254.6, 0:00:59,
Ethernet2

E 128.128.0.0 [200/128] via 131.119.254.244, 0:02:22,
Ethernet2

E 129.129.0.0 [200/129] via 131.119.254.240, 0:02:22,
Ethernet2

E 192.65.129.0 [200/128] via 131.119.254.244,
0:02:22, Ethernet2

If a path to a boot server exists, a disconnected network is not the problem. If no path exists, make sure that a path is available before again attempting to network boot.

TFTP server is down

1. Check the TFTP server to determine whether it is up and running. You can do this by attempting to make a TFTP connection from the boot server to itself. The connection will be successful if the TFTP server is running.

2. If the TFTP server is not running, initialize it. The initialization process will vary depending on the type of boot server.

For a BSD UNIX server, check the /etc/inetd.conf file. If the TFTP server is not included in this file, add the appropriate line and cause inetd to reload its configuration.

Router image is in the wrong directory

1. Look at the server configuration file to see whether it points to the directory in which the router image is located.

2. Move the router image to the correct directory, if necessary.

3. Make sure that the /tftpboot directory is reachable over the network.

Router system image file permissions are incorrect

1. Check the permissions of the system image file.

2. If necessary, change the permissions for the file. On a UNIX boot server, set the permissions for the file to owner read/write, group read, and global read (the UNIX command for setting these permissions is chmod 644 filename).

Protocol address is bad

1. Check the server configuration file to make sure that the IP address of the host is correct.

2. Change the configuration, if it is incorrect.

Default gateway specification is missing or has been misconfigured

1. Use the show running-config privileged exec command to view the router configuration. Check for the ip default-gateway global configuration command, which defines a default gateway.

Syntax:

ip default-gatewayip-address

Syntax description:

ip-address—IP address of the router.

2. If the command is missing, add it to the configuration. If the command is present, make sure that it specifies the correct IP address.

Boot system command has been misconfigured

1. Use the show running-config privileged exec command to view the router configuration. Check the boot server address (IP address of a TFTP server or MAC1 address of a MOP2 server) that is configured on the router.

2. If the address is specified incorrectly, specify the correct boot server address using the boot system global configuration command.

Wrong filename is specified

1. Use the show running-config privileged exec command to view the router configuration. Check the boot filename that is configured on the router.

2. Make sure that the filename is specified correctly. Change the filename, if necessary. Check the host documentation for details about setting the name of the system image on the TFTP server.

3. Some versions of the ROM are case-sensitive. Try changing the case of the filename. Contact your technical support representative for more information.

Configuration register setting is incorrect

To network boot from a server, you must set the configuration register properly. The specific configuration for network booting depends on the platform that is being booted.

1. Check the configuration register setting for your system.

2. Determine whether you want to manually or automatically network boot from a TFTP server.

To manually network boot, the configuration register must be set to 0x0; otherwise, you will be network booting using the default system image name or the image specified by the boot system global configuration command.

Refer to the Cisco IOS configuration guides and command references, and your hardware installation and maintenance publications, for more details about setting the configuration register.

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

The following example shows a network booting session that contains excessive timeouts and out-of-order packets:

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

The client router might boot in this situation. However, when excessive timeouts and out-of-order packets occur, there is probably a network problem, and network booting (as well as network service availability) might be inconsistent.

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

2. Check local network concentrators for excessive collisions on the same network. If there are excessive collisions, reorganizing your network topology might help reduce collisions.

3. Use the show interfaces exec command on routers in the path, or place a network analyzer between the router and server. Look for dropped packets and output errors.

4. If approximately 15 percent or more of the traffic is being dropped, or if any output errors occur, congestion might be the problem.

5. Wait until the traffic subsides before attempting to network boot the router. If the problem is chronic, increase bandwidth or move the server closer to the router being booted.

Link is down

1. Check the continuity of the path from the booting router to the boot server using ping or trace exec commands.

2. If a break is found, restore the link and attempt to network boot again.

Booting: Invalid Routes Prevent Network Booting

Symptom: Invalid routes prevent successful network booting. If the router is sending packets over an invalid path, a message similar to one of the following is displayed on the console:

Booting gs3-bfx!OOOO..........[timed out]

Booting gs3-bfx!.O.O.O.O..........[timed out]

Booting gs3-bfx!!!!!!!!!!OOOOOOOOOO..........[timed out]

In some cases, there might be an initial response from a server, but the network boot sequence still fails. The boot message would be similar to the following:

Booting gs3-bfx!..........[failed]

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

Table 3-13 Booting: Invalid Routes Prevent Network Booting

Possible Problem

Solution

Bad routing paths on neighbor routers

1. Verify that neighbor routers can ping the server.

2. Use the trace exec command to determine the path to the server.

3. Use the show arp1 privileged exec command to examine the ARP tables, or the show ip route privileged exec command to view the IP routing table. Verify that the server is listed and that the routing table entries are appropriate.

4. Use the clear arp-cache and clear ip-route privileged exec commands to force the router to repopulate its ARP and routing tables.

5. Try to network boot the router again.

Problems caused by multiple paths

1. Shut down all extra interfaces except the one over which you intend to network boot the router.

2. Use the no ip proxy-arp interface configuration command on all neighboring routers to disable their capability to provide proxy ARP responses.

Make this change with care because it can cause problems for other network traffic.

If you do not want to disable proxy ARP, boot the router from ROM and configure the ip default-gateway global configuration command.

Caution: Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.

6. If the neighbor is not sending proxy ARP responses and its configuration contains the noip proxy-arp interface configuration command, disable ARP filtering by removing the entry.

Note that proxy ARP is enabled by default.

7. If you need to have a no ip proxy-arp entry in the neighbor router configurations, use the ip default-gateway global configuration command on the router to specify a default gateway.

IP helper address on intermediate router is missing or has been misconfigured

1. Check the configurations of all routers in the path. Make sure that all intermediate routers have an IP helper address specified that points to the TFTP server.

Syntax:

ip helper-addressaddress

Syntax description:

address—Destination broadcast or host address to be used when forwarding UDP1 broadcasts. You can have more than one helper address per interface.

2. Include helper addresses as required using the ip helper-address interface configuration command.

If you are unicasting to your server, you do not need to use the IP helper address, but if you are broadcasting to 255.255.255.255 (by omitting the IP address of the server), add the ip helper-address command on the neighboring router interface used in the network booting broadcast.

Booting: Undefined Load Module Error When Network Booting

Symptom: An undefined load module error occurs during a network boot. The console display indicates an "undefined load module" error, and the router is incapable of booting.

Table 3-15 outlines the problem that might cause this symptom and describes solutions to that problem.

Table 3-15 Booting: Undefined Load Module Error When Network Booting

Possible Problem

Solution

Filename mismatch

1. If you are booting manually, refer to the user guide for your router to see the proper command-line format.

2. Check the router configuration file. Compare the filename specified in the boot systemfilename [address] global configuration command entry with the actual router image filename. Make sure that they match.

3. If the filenames differ, change the name in the configuration file.

Remember to use the router image filename in the boot system global configuration command specification and the configuration filename with the boot host and boot network global configuration commands.

Booting: Router Hangs After ROM Monitor Initializes

Symptom: When a user is booting a Cisco 7000 series, AGS+, AGS, ASM-CS, MGS, IGS, or CGS router from ROM, the system hangs after the ROM monitor initializes.

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

1. Check your configuration settings (boot ROM jumpers and software configuration). If no jumper is set at bit 0, and no other boot field is defined, you must reconfigure your system so that it can boot properly.

2. To enable your router to boot properly, do one of the following:

•Configure the software configuration register of the router using the config-register value global configuration command. (This applies to the IGS, Cisco 2500, Cisco 3000, and Cisco 7000 platforms running Cisco IOS Release 10.0 or later in the EPROM.)

•Set the boot ROM jumper to permit booting.

•Include the correct boot system global configuration commands to boot the system.

•Set bit 0 to a value of 1 to force booting from ROM.

Refer to the Cisco IOS configuration guides and command references, as well as your hardware installation and maintenance publications, for more information about configuring your router for the various booting options.

Booting: Router Is Stuck in ROM Monitor Mode

Symptom: Router is stuck in ROM monitor mode. When a user is booting a router from ROM, the system boots into ROM monitor mode but does not boot the complete system image.

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

Table 3-17 Booting: Router Is Stuck in ROM Monitor Mode

Possible Problem

Solution

Configuration register setting is incorrect

1. At the ROM monitor prompt (>), enter b to boot the system.

2. If a configuration exists in NVRAM, the system displays the vacant message. Press the Enter key to continue.

If a configuration does not exist in NVRAM, the setup menu appears. Skip the setup process.

3. Use the show version exec command to determine the configuration register setting.

Configuration register setting is incorrect (continued)

4. Look for an invalid configuration register setting. The default is 0x101, which disables the Break key and forces the router to boot from ROM. A typical "bad" setting has a 0 in the least significant bit (for example, 0x100).

For details about setting the configuration register, refer to your hardware installation and maintenance publication.

Break key was pressed during boot process

At the ROM monitor prompt, enter c to allow the router to continue booting.

Console cable was inserted or removed during boot process, or console was power-cycled during boot process

1. Press the Enter key and wait for the ROM monitor prompt (>).

2. If the ROM monitor prompt appears, enter c at the prompt to continue the booting process.

Booting: Scrambled Output When Booting from ROM

Symptom: When a user is booting from ROM, the router displays indecipherable text output on the console.

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

Table 3-18 Booting: Scrambled Output When Booting from ROM

Possible Problem

Solution

Wrong terminal speed setting

1. Use the monitor setup menu to check the terminal line speed setting for the monitor.

2. Check the terminal speed configured on the router as specified in the configuration register setting (default is 9600 baud, 8 data bits, 2 stop bits, and no parity).

3. If the terminal speed of the monitor and the router do not match, modify as necessary.

Refer to your hardware installation and maintenance documentation for details about setting up the monitor.

Router hardware problem

Check all hardware for damage, including cabling (broken wire), adapters (loose pin), router ports, and so forth. For more information, refer to the information in the "Troubleshooting "Hardware section found earlier in this chapter.

Booting: Local Timeouts Occur When Booting from ROM

Symptom: "Local timeout" error messages are generated when a user is booting from ROM. The router is incapable of completing its boot process and will not start the ROM monitor.

Table 3-19 outlines the problem that might cause this symptom and describes solutions to that problem.

Table 3-19 Booting: Local Timeouts Occur When Booting from ROM

Possible Problem

Solution

EPROM problem

Generally, this problem occurs only if you have just replaced your system EPROMs.

1. Power down the system.

2. Inspect each EPROM. Make sure that each EPROM is correctly positioned in the socket (with notches properly aligned) in the correct socket.

3. If a pin is bent, straighten it carefully. Reinstall the EPROM and power up the system. If a pin breaks off, the EPROM must be replaced.

4. If an EPROM has been installed backward and power has been applied to it, the EPROM has been damaged and must be replaced.

5. If local timeouts persist, contact your technical support representative.

Symptom: A terminal connected to an unconfigured access server is unresponsive. The terminal, attached to the console port of an unconfigured Cisco access server, displays bootup banners and begins the setup routine, but the user cannot input commands from the terminal keyboard.

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

Flow control configured on the terminal conflicts with the EIA/TIA-232 control signals supported by the access server console port (RJ-45 to DB-25)

1. Check whether flow control is configured on your terminal.

2. Disable all flow control on the terminal. With flow control enabled, the terminal will wait indefinitely for a CTS signal because the RJ-45 console port on the access server does not assert CTS.

For information on how to check for and disable flow control on your specific terminal, consult the documentation provided by your terminal manufacturer.

3. Alternatively, you can "strap," or short, CTS high by providing the proper voltage on the CTS signal lead to make the signal active. Find an unused signal that is known to be active and strap CTS to it. The terminal sees CTS being asserted (indicating that the access server is ready to receive data) and allows input to be entered.

4. On an already configured access server, another solution is to connect your terminal to the auxiliary port of the access server. The auxiliary port, unlike the console port, asserts CTS, and the terminal will therefore allow input. However, on a new access server with no configuration, this is not an alternative because the bootup banners and setup routine are seen only on the console port.

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

This Tech Note explains how to recover a Catalyst 6000 family switch from either a corrupted or missing boot loader image.

Catalyst 6000 switches running Cisco IOS have two boot Flash areas. The boot Flash area at the supervisor holds the IOS image, and the area at the Multilayer Switch Feature Card (MSFC) holds the boot loader image. To run IOS on the Catalyst 6000, you need to have both images installed.

Note The boot loader image must reside in the MSFC boot Flash. The IOS image can reside in either the supervisor boot Flash, a Flash card, or a TFTP server.

If the boot loader image either is corrupted or has been deleted from the MSFC boot Flash, the next reload causes the switch to go into ROMMON, and you will be unable to boot the switch to run IOS software on it.

Things to Be Aware of Before You Use the Recovery Procedure

To save time, it's important to understand the terminology, as well as constraints you may encounter when using the procedure.

1. The IOS on the Catalyst 6000 family switch is the single IOS image that runs the Catalyst 6000 family switch, also known as native IOS on the Catalyst 6000. We refer to it as Catalyst 6000 IOS, or Cat IOS. Catalyst 6000 OS software is the image that runs the supervisor and all the L2 switch functions, also known as the hybrid image when used in conjunction with IOS software on the MSFC. We refer to it as Catalyst 6000 OS, or Cat OS.

2. Two CPUs are involved, the supervisor CPU or switch processor (SP), and the MSFC CPU or route processor (RP).

3. When the boot loader image is missing or corrupted, the very next reload or power cycle brings the switch to SP ROMMON mode.

4. Each CPU has its own ROMMON Command Language Interpreter (CLI).

5. From the SP ROMMON, you can load either the Catalyst 6000 IOS or the Catalyst 6000 OS from either slot 0 or boot Flash. Loading the Cat OS version on a system previously running Cat IOS causes the switch configuration to be reset.

6. After you load the Cat IOS image, you get the RP ROMMON prompt. On the other hand, if you load the Cat OS image, you can switch to the RP ROMMON console using the switch console command.

7. From the RP ROMMON CLI, you can't access the supervisor boot Flash or slot 0.

8. There are two ways of loading the boot loader image into the MSFC boot Flash: using a Cisco 4500 or 4700 router, or using xmodem. We'll explain both methods in detail in this tech note.

9. When you're running the boot loader image in the MSFC, you get the MSFC Router(boot) prompt in boot mode.

10. You must format the MSFC boot Flash from the MSFC Router(boot) prompt.

11. After you format the MSFC boot Flash, you must copy the boot loader into it. Be aware of the caveats discussed in the following section when attempting to copy the boot loader image.

Recovery Procedures

•Method 2—Use xmodem with the Modem Out-of-Band (OOB) Protocol to load the boot loader image to the MSFC boot Flash. This procedure requires the Catalyst 6000 Supervisor (CAT OS) image if using boot loader version c6msfc-boot-mz.120-7.XE, or the Catalyst IOS image if using version c6msfc-boot-mz.120-7.XE1, to be running on the Supervisor module. The MSFC boot loader image is approximately 1.8 MB and takes about 45 minutes to load.

You should use this second method only as a disaster recovery procedure, and the following caveats apply:

•The xmodem procedure doesn't save the current switch configuration if you run the Cat OS image on the supervisor, and you were previously running Cat IOS on the switch.

•The xmodem procedure loads and runs the boot loader in the MFSC, and it puts it in boot mode.

–From boot mode, the MSFC boot Flash must be formatted before you copy the boot loader image into it.

–You must place the boot loader image that you want to load in supervisor's slot 0.

Note The xmodem procedure has been verified to work with Microsoft Windows Hypertrm program, and minicom under Linux.

If these methods are not successful, contact the Cisco Technical Assistance Center (TAC), and request an RMA for a new boot Flash SIMM with the desired image in it.

Note As it was mentioned earlier, you could use either the Cat OS or Cat IOS image. Which one to use depends on the boot loader version that you are trying to load.

If you are using version c6msfc-boot-mz.120-7.XE, you need to use Cat OS image. If you use boot loader version c6msfc-boot-mz.120-7.XE1 or later, you may use the Cat IOS image. Using release c6msfc-boot-mz.120-7.XE1 or later has major advantages and should be used whenever possible. First, the switch configuration will not be lost by having to load Cat OS in the switch; second, a few extra steps are not necessary, making the process less time-consuming.

The major difference between the releases is the capability to access the supervisor's slot 0 from boot mode. If you load Cat IOS in the supervisor, you will not be able to access slot 0 until you get to release c6msfc-boot-mz.120-7.XE1 or later.

Note The MSFC in ROMMON mode is capable of reading a 4500/4700 router Flash SIMM. However when Cat IOS is running, the MSFC cannot read a 4500/4700 flash SIMM format. Make sure that you format the MSFC boot Flash from boot mode before the boot loader image is put back on it. The following are the typical messages when attempting to read the MSFC's boot Flash when running Cat IOS.

MSFC in ROMMON:

rommon 1 > dir bootflash:

File size Checksum File name

1597884 bytes (0x1861bc) 0x8334 c6msfc-boot-mz.120-7T.XE1.0.95.bin

MSFC in boot mode:

Router(boot)# dir bootflash:

Directory of bootflash:/

1 -rw- 1877456 Jan 01 2000 00:08:25 c6msfc-bootdbg-mz

15990784 bytes total (14113200 bytes free)

Router(boot)#

MSFC running Cat IOS:

IOS4C6K# dir bootflash:

%Error opening bootflash:/ (Bad device info block)

The following is the recovery procedure utilizing a 4500/4700 router.

Step 1 Remove the boot Flash from the Catalyst 6000, and put it into the 4500/4700 router. Ensure that the Flash SIMM from the slot you have selected does not contain the IOS software running the 4500/4700 router.

Important: After booting up the 4500/4700, you'll need to partition the Flash, realizing that the boot Flash in the Catalyst 6000 is 16 M.

4500Router(config)# partition flash 2 8 16

4500Router(config)# end

4500Router#

00:07:30: %SYS-5-CONFIG_I: Configured from console by console

4500Router# show flash

System flash directory, partition 1:

File Length Name/status

1 4512036 c4500-js-mz.112-17.P

2 3838296 c4500-j-mz.111-20

[8350460 bytes used, 38148 available, 8388608 total]

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

System flash directory, partition 2:

No files in System flash

[0 bytes used, 16777216 available, 16777216 total]

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

Step 2 Copy the boot loader image into the appropriate system partition.

4500Router# copy tftp flash

Partition Size Used Free Bank-Size State Copy Mode

1 8192K 8154K 37K 8192K Read/Write Direct

2 16384K 0K 16384K 8192K Read/Write Direct

[Type ?<NO> for partition directory; ? for full directory; q to
abort]

Step 3 When you finish copying the image, take the SIMM back to the same slot in the Catalyst 6000.

Before the system failing, the bootvar in the Catalyst 6000 may have had the following information:

C6000-IOS# sh bootvar

BOOT variable = sup-bootflash:c6sup-jsdbg-mz.120-6.5T.XE1.0.90.bin,1;

CONFIG_FILE variable does not exist

BOOTLDR variable = bootflash:c6msfc-boot-mz.120-6.5T.XE1.0.90.bin

Configuration register is 0x2

If you did not have the bootldr variable set. you will get the following message and will have to bring up the switch manually:

System Bootstrap, Version 5.2(1)CSX

Copyright (c) 1994-1999 by cisco Systems, Inc.

c6k_sup1 processor with 65536 Kbytes of main memory

Autoboot: failed, BOOT string is empty

rommon 1 >

To bring up the switch manually, you should have either the Cat OS or the Cat IOS image in the supervisor's boot Flash or slot 0. To list the content of slot 0 or bootflash, type dir slot0: and dir bootflash:, respectively. See the following output.

When you have identified where the image is located, follow the instructions in one ofthese two sections:

•If you are using boot loader release c6msfc-boot-mz.120-7.XE1 or later, go to the section "Loading the Catalyst IOS Image."

•If you are using boot loader release c6msfc-boot-mz.120-7.XE, go to the section "Loading the Catalyst OS Image."

Come back to this point after you have loaded either the Cat IOS or the Cat OS image.

The RP is at the boot prompt, and you are ready to bring up the switch running Cat IOS. Ensure that you have the config-register set to 0x2 before you reboot. You also may want to check that the right boot variables are set correctly. If they are not, change them to reflect the right image names. See the following example:

boot system flash sup-bootflash:c6sup-jsdbg-mz.120-7T.XE1.2.02.bin

boot bootldr bootflash:c6msfc-bootdbg-mz

Note: If the boot variables are not set at all, the switch will attempt to boot from the first file in the respective boot Flash.

Method 2: OOB Boot Loader Recovery Procedure Using xmodem

This alternative is recommended only in case of a disaster recovery situation, when no other option is possible.

The first step is to load the Cat IOS or Cat OS image in the supervisor boot Flash. Make sure that you have the Cat OS image either in the supervisor boot Flash, or a Flash card inserted on slot 0, and follow the instructions in the sections "Loading the Catalyst IOS Image" or "Loading the Catalyst OS Image," later in this chapter.

When you have loaded the Cat IOS or Cat OS image loading procedure, make sure that you at the MSFC's ROMMON prompt.

Note: Currently, the MSFC in ROMMON cannot see the supervisor's boot Flash or slot 0.

Also remember to have the boot loader image available in the computer from which you are performing the xmodem download. At this point, you are ready to initiate the xmodem download. It will take between 40 and 45 minutes to complete.

At the MSFC's ROMMON prompt, type the following command:

xmodem -s9600 -c

The -s9600 option sets the speed, while the -c option performs checksum.

System Bootstrap, Version 12.0(3)XE, RELEASE SOFTWARE

Copyright (c) 1998 by cisco Systems, Inc.

Cat6k-MSFC platform with 65536 Kbytes of main memory

rommon 1 >

rommon 1 > xmodem -s9600 -c

Do not start sending the image yet...

Invoke this application for disaster recovery.

Do you wish to continue? y/n [n]: y

Note, if the console port is attached to a modem, both the

console port and the modem must be operating at the same baud

rate. Use console speed 9600 bps for download [confirm]

Download will be performed at 9600. Make sure your terminal

emulator is set to this speed before sending file.

Ready to receive file ...

In your terminal emulator, type send command or click on the appropriate icon to start the download process. The transfer will take between 40 and 45 minutes to complete.

We have found that the first attempt may fail. If it does, run the xmodem command again without resetting the MSFC. At the end of the successful download, you will the following message:

Download Complete!

When the download has completed, the image will be decompressed and run by the MSFC. The next prompt will be the boot prompt at the MSFC.

The xmodem download did not copy the boot loader image into the MSFC boot Flash. The download simply loaded and uncompressed image to run the MSFC.

The next step is to copy the boot loader image form the supervisor's slot 0 into the MSFC's boot Flash.

From the MSFC boot prompt, you will not be able to see the supervisor's slot 0 or display its contents. You need to remember the boot loader image name so that you can issue the following command:

If you are running the Cat OS image, use:

copy sup-slot0:<boot loader image> bootflash:<boot loader image>

If you are running the Cat IOS image, use:

download slot0:<boot loader image> bootflash:<bootloader image>

Note: Remember, the MSFC will not be capable of copying an image from any location other than the supervisor's slot 0.

Now you are ready to bring up the switch running Cat IOS. Ensure you have the config-register set to 0x2 before you reboot and that the right boot variables are correctly set. The following commands set the boot variables:

boot system flash sup-bootflash:<CatIOS image>

boot bootldr bootflash:<boot loader image>

Loading the Catalyst IOS Image

Load the Cat IOS image by typing the following command:

boot <location>:c6sup-jsdbg-mz.120-7T.XE1.2.02.bin

In this command, <location> is either slot0 or bootflash.

Note: Loading this image will take you directly to the MSFC's ROMMON prompt.

You now need to format the MSFC's boot Flash and copy the boot loader image from the supervisor's slot 0.

Note: You will not be able to display the contents of slot 0, so you need to remember the boot loader image name to load it from the supervisor's slot 0.

Router(boot)# dir slot0:

^

% Invalid input detected at '^' marker.

First, format MSFC's boot Flash.

Router(boot)# format bootflash:

Format operation may take a while. Continue? [confirm]

Format operation will destroy all data in "bootflash:". Continue? [confirm]

Formatting sector 1

Format of bootflash: complete

Copy the boot loader image to the MSFC's boot Flash by typing the following command:

copy sup-slot0:<boot loader image> bootflash:<boot loader image>

See the following output from the last few steps.

Router(boot)# copy sup-slot0:c6msfc-boot-mz bootflash:c6msfc-boot-mz

Destination filename [c6msfc-boot-mz]?

Accessing sup-slot0:c6msfc-boot-mz...

Loading slot0:c6msfc-boot-mz from 127.0.0.11 (via EOBC0): !

Loading slot0:c6msfc-boot-mz from 127.0.0.11 (via EOBC0):

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK

- 1603124/3206144 bytes]

Router(boot)# dir bootflash:

Directory of bootflash:/

1 -rw- 1877456 Jan 01 2000 00:38:56 c6msfc-bootdbg-mz

15990784 bytes total (14113200 bytes free)

At this point, go back to the main recovery procedures to finalize the process.

Cisco 2600 TFTP Download and Startup

Introduction

This section explains how to recover a Cisco 2600 router from either a corrupted or missing ios image. To gain access to the rommon command line interpreter, hit the break key during the first 15 seconds after the router has been powered on. From the rommon> prompt you may then use the tftpdnld command to tftpboot an ios image to the router.

rommon 1 > tftpdnld

Missing or illegal ip address for variable IP_ADDRESS

Illegal IP address.

usage: tftpdnld [-r]

Use this command for disaster recovery only to recover an image via TFTP.

Monitor variables are used to set up parameters for the transfer.

(Syntax: "VARIABLE_NAME=value" and use "set" to show current variables.)

Would you like to enter the initial configuration dialog? [yes/no]: no

Would you like to terminate autoinstall? [yes]:

Press RETURN to get started!

Passed

00:00:24: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to up

00:00:24: %LINK-3-UPDOWN: Interface FastEthernet0/1, changed state to up

00:00:24: %LINK-3-UPDOWN: Interface Serial0/0, changed state to down

00:00:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state
to up

00:00:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/1, changed state
to down

00:00:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0, changed state to down

00:00:58: %LINK-5-CHANGED: Interface BRI0/0, changed state to administratively down

00:00:59: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0, changed state to down

00:00:59: %IP-5-WEBINST_KILL: Terminating DNS process

00:01:00: %LINK-5-CHANGED: Interface Serial0/0, changed state to administratively down

00:01:00: %LINK-5-CHANGED: Interface FastEthernet0/0, changed state to administratively
down

00:01:00: %LINK-5-CHANGED: Interface FastEthernet0/1, changed state to administratively
down

Troubleshooting the Power and Cooling Systems

Check the following items to help isolate the problem:

•When the power switch is in the on position (|) and the power LED is on, make sure that the fan is operating. If not, check the fan.

•If the router shuts down after being on a short time, check the environmental conditions. The router might be overheating, resulting in a thermal-induced shutdown. Verify that the chassis intake and exhaust vents are clear. The operating temperature for the router is 32°F to 104°F (0°C to 40°C). If the router fails to boot but the power LED is on, check the power supply.

•If the router constantly or intermittently reboots, there might be a problem with either the processor or the software, or a DRAM single in-line memory module (SIMM) might be installed incorrectly.

Cisco 3600 Startup

Introduction

This section explains how to recover a Cisco 3600 router from either a corrupted or missing ios image. To gain access to the rommon command line interpreter, hit the break key during the first 15 seconds after the router has been powered on. From the rommon> prompt you may then use the xmodem command to transfer an ios image to the router via the console interface of the router.