Cisco 7600 Series Router Module Installation Guide
Troubleshooting
Downloads: This chapterpdf (PDF - 181.0KB) The complete bookPDF (PDF - 5.69MB) | Feedback

Troubleshooting

Table Of Contents

Troubleshooting

Troubleshooting Router Start Up Issues

Troubleshooting Router Booting Issues

Troubleshooting Router Boot Failure from the Flash Memory

Troubleshooting Vector Errors When Booting from Flash Memory

Router Partially Boots from Flash and Displays Boot Prompt

Troubleshooting Router Freeze After the ROM Monitor Initializes

Troubleshooting Router Freeze in the ROM Monitor Mode

Troubleshooting Scrambled Output When Booting from ROM

Troubleshooting Local Timeouts When Booting from ROM

Troubleshooting Unresponsive Terminal Connection to  Unconfigured Access Server

Obtaining Technical Assistance


Troubleshooting


Troubleshooting Router Start Up Issues

When you start up a Cisco 7600 series router, the following occurs:

The AC (or DC) OK LED is switched on and remains so till the system receives power.

The blower is initiated.

The supervisor and the front-panel Normal LEDs are enabled (to indicate normal system operation) and remain so during system operation.

The LEDs enabled on each interface processor should be switched on (to indicate that the supervisor has completed initialization of the interface processor).

Possible Problem Area
Solution

Power subsystem

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

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

3. Ensure that the power source, power cable, and power supply are functioning correctly. Swap parts to see whether any of the components are 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 whether or not 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 completely in the backplane sockets.

2. If the system and blower starts up, but shuts down after two minutes, one or more fans might have failed or might be operating out of tolerance and this error message is displayed.

%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 this message at startup, it means that the system has detected an over temperature 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 does not enter the inlet vents and that there is sufficient clearance around the chassis to allow the cool air in.

Processor subsystem

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

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

3. If the supervisor Link LED is a flashing orange, the system has detected a processor hardware failure. Contact a technical support representative for instructions.

4. Check to see whether the Supervisor 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 be powered on when the Supervisor has initialized the interface processor.

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

1 supervisor = Route Switch Processor


When the 7600 series system initializes successfully, the system banner should be displayed on the console screen. If not, make sure that the console terminal is properly connected to the supervisor console port and that the terminal is set correctly. The system banner should look like this:

System Bootstrap, Version 12.2(33r)SRD5, RELEASE SOFTWARE (fc1)Technical Support: http://www.cisco.com/techsupport

Copyright (c) 2009 by cisco Systems, Inc.

C7600-RSP720/SP platform with 1048576 Kbytes of main memory

Troubleshooting Router Booting Issues

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

Flash memory— A nonvolatile storage medium that can be electrically erased and reprogrammed.

PC Flash memory card—A removable Flash memory card.

Troubleshooting Router Boot Failure from the Flash Memory

Table 4-1 outlines the solutions for boot failure from the flash memory.

Table 4-1 Booting: Router Fails to Boot from Flash Memory 

Possible Problem
Solution

Incorrect or corrupted image (executive command does not function)

1. Check the configuration register using the show version command. Set the register to boot from Flash memory. For information about configuration register settings, refer the 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 command at the router to retrieve the image.

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

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

Note: Using the copy running-config startup-config command at this point on a Cisco 7600 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.

This is the required 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:

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

Router# reload

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

This is the required syntx 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


Troubleshooting Vector Errors When Booting from Flash Memory

Table 4-2 outlines the solutions for vector errors when the router boots from the flash memory.

Table 4-2 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 command.

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

Decompress the image at the TFTP server, since this is not possible at the router side.

8. Use the copy tftp flash privileged 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

 

The router prompts you to enter the IP address of the TFTP server and the name of the image file that you are copying to the server. Here is a sample output for this command using the IP address 131.108.10.6 and filename c7600rsp72043-adventerprisek9-mz.122-33.SRE1:

IP address of remote host [255.255.255.255]? 131.108.10.6

Name of file to copy []? c7600rsp72043-adventerprisek9-mz.122-33.SRE1

writing c7600rsp72043-adventerprisek9-mz.122-33.SRE1

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

10. Use the show running-config privileged 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.

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}

Syntax description:

startup-config—Specifies the configuration used for initialization as the destination of the copy operation.

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.

Enter the reload privileged command to restart the router.

1 TFTP = Trivial File Transfer Protocol


Router Partially Boots from Flash and Displays Boot Prompt

Table 4-3 describes the solutions for a partial reboot of the router from the flash memory

Table 4-3 Booting: Router Partially Boots from Flash and Displays Boot Prompt 

Possible Problem
Solution

No system image in Flash memory

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

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

router# copy flash tftp filename

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 c7600rsp72043-adventerprisek9-mz.122-33.SRE1 follows:

IP address of remote host [255.255.255.255]? 131.108.10.6

Name of file to copy []? c7600rsp72043-adventerprisek9-mz.122-33.SRE1

writing c7600rsp72043-adventerprisek9-mz.122-33.SRE1 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

router#

3. Enter the reload privileged command to reboot the router.

Syntax:

This is the syntax for the reload command:

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

Examples:

This illustrates how to use the reload command to immediately reload the software on the router:

Router# reload

This 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]

Missing boot system flash global configuration command

1. Use the show running-config privileged command to determine whether the configuration includes a boot system flash global configuration command entry. Use the show startup-config privileged 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.

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 command. The required syntax is as follows:

copy running-config {rcp | startup-config | tftp | file-id} 

Missing boot system flash global configuration command (continued)

Syntax description:

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 command to check the configuration register setting. Make sure that it is set to boot from Flash memory. See the hardware installation and maintenance publication for details regarding configuration register settings.

1 TFTP = Trivial File Transfer Protocol

2 NVRAM = nonvolatile random-access memory


.

Troubleshooting Router Freeze After the ROM Monitor Initializes

When a user boots a router from the ROM, the system hangs after the ROM monitor initializes.

Table 4-4 describes solutions for this problem.

Table 4-4 Booting: Router Hangs After ROM Monitor Initializes 

EPROM1 size setting is incorrect

1. Power down the system.

2. Inspect EPROM size jumpers. See the hardware installation and maintenance publication for your router to determine the proper setting.

3. Move jumpers as required.

Configuration register is not set correctly

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.

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.

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

1 EPROM = erasable programmable read-only memory


Troubleshooting Router Freeze in the ROM Monitor Mode

When a user boots a router from ROM, the system boots into ROM monitor mode but does not boot the complete system image and the router remains in the ROM monitor mode.

Table 4-5 describes solutions for the router frozen in the ROMMON mode.

Table 4-5 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 a blank 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 command to determine the configuration register setting.

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

5. For details about setting the configuration register, see the 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.


Troubleshooting Scrambled Output When Booting from ROM

When the user boots from the ROM, the router displays an indecipherable text on the console.

Table 4-6 describes the solutions for indecipherable text when booting from the ROM.

Table 4-6 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 faulty cabling (broken wire), adapters (loose pin), router ports, and so forth.


Troubleshooting Local Timeouts When Booting from ROM

"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 4-7 outlines the solutions to troubleshoot local timeouts when booting from the ROM.

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


Troubleshooting Unresponsive Terminal Connection to  Unconfigured Access Server

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 4-8 outlines the solutions to troubleshoot unresponsive terminal connection to non-configured server.

Table 4-8 Booting: Unresponsive Terminal Connection to Unconfigured Access Server

Possible Problem
Solution

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 waits 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," 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. Connect your terminal to the auxiliary port of a configured 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.

Hardware problem

1. Check all hardware—including cabling (broken wires), adapters (loose pins), access server ports, and the terminal itself—for damage.

2. Replace any hardware that is damaged or excessively worn.


Obtaining Technical Assistance

If you are unable to solve a problem on your own based on the solutions provided, consult a Cisco customer service representative for assistance. When you call, ensure that you have the following information:

Chassis and module serial number.

Card information :Use the show module and show inventory command to determine which cards are installed.

Cisco IOS software release number: Use the show version command to determine this number.

Brief description of the symptoms and steps to isolate and solve the problem.

Maintenance agreement or warranty information.

ROM images. (Use the show version executive command.)

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

Figure 4-1 An Example of a Boot ROM Label—Boot ROM Version 12.2(33r)SRD5

NVRAM configurations for client and adjacent routers.

Debugging output from adjacent routers using the following privileged executive commands:

debug ip packet

debug arp

debug ip udp

debug tftp