|
|
This chapter provides procedures for troubleshooting hardware and booting problems. Although this chapter provides specific procedures for some Cisco products, always refer to your hardware installation and maintenance publication for more detailed information about your specific platform, including descriptions of specific LEDs, configuration information, and additional troubleshooting information.
This chapter begins with the following sections:
The remaining sections describe symptoms, problems, and solutions for Flash boot, netboot, ROM boot, and other bootup problems.
Cisco routers can initialize the system (boot) in any of four different ways:
This section provides general information about router booting. The following topics are covered in this section:
During netbooting sessions, routers behave like hosts: they route via proxy ARP, Serial Line Address Resolution Protocol (SLARP) information, Internet Control Message Protocol (ICMP) redirects, or a default gateway. When netbooting, routers ignore dynamic routing information, static IP routes, and bridging information. As a result, intermediate routers are responsible for handling ARP and User Datagram Protocol (UDP) requests correctly. For serial and HSSI media, ARP is not used.
Before netbooting 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 "Router Cannot Netboot 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.
Although netbooting is useful, network or server failures can make netbooting 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:
Following is an example of how to configure a router with a fault-tolerant boot sequence.
goriot#configure terminalEnter configuration commands, one per line. End with CNTL/Z. goriot(config)#boot system flashgsxxgoriot(config)#boot systemgsxx131.108.1.101goriot(config)#boot system romgoriot(config)#^Zgoriot# %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, netboot, and ROM. Providing alternative sources can help to mitigate any failure of the TFTP server or the network.
When netbooting, 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 netbooting display) and out-of-order packets (shown as uppercase Os) do not necessarily prevent a successful netboot. It is acceptable to have either or both of these occur during the process.
The following examples show console output from netbooting sessions that were successful even though timeouts and out-of-order packets occurred (exclamation points represent sucessfully received packets):
Booting gs3-bfx from 131.108.1.123: !.!!!!!!!!!!!!!!!!!!!!!! Booting gs3-bfx from 131.108.1.123: !O.O!!!!!!!!!!!!!!!!!!!!!!
If a netboot generates excessive out-of-order packets and timeouts, problems might result. These problems are discussed later in this chapter.
If you cannot resolve your booting problem using the procedures outlined in this chapter, collect the following information for your technical support representative:
When you start up a Cisco 7500 series router, the following should occur:
When the system has initialized successfully, the system banner (which should look similar to the following example) 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.
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 problems occur, try to isolate the problem to a specific subsystem. The Cisco 7500 series routers have the following subsystems:
Step 1 Check to see if the blower is operating and 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.
Step 2 Make sure the power switch is set correctly to the on position.
Step 3 Make sure the power source, power cable, and power supply are functioning correctly. Swap parts to see if one of the components is faulty.
Step 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.
Step 1 Check to see if 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:
Step 2 If the system and blower start up but shut down after about two 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:
If the blower or the blower control board fails, you must replace the blower module.
Step 3 If you see the following message at startup, the system has detected an overtemperature condition or out-of-tolerance power inside the chassis:
If an environmental shutdown results from an out-of-tolerance power condition, the Output Fail LED will go on before the system shuts down.
This 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.
Step 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.
Step 1 Check the RSP LEDs. If no LEDs come on, ensure that the power supplies and blower are functioning properly.
Step 2 Check the seating of the RSP. If the RSP is not seated properly it will hang the system.
Step 3 If the RSP CPU Halt LED is on, the system has detected a processor hardware failure. Contact a technical support representative for instructions.
Step 4 Check to see if the RSP Normal LED is on, indicating that the system software ha s initialized successfully and the system is operational.
Step 5 Check the Enabled LED on each interface processor. This LED should go on when the RSP has initialized the interface processor.
Step 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.
When you start up a Cisco 7000 series router, the following should occur:
When the system has initialized successfully, the system banner (which should look similar to the following example) 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.
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:
Step 1 Check to see if the DC OK LED is on.
Step 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.
Step 3 If the LED is not on and there is no other activity, make sure the power switch is fully in the on position.
Step 4 Make sure the power source, power cable, and power supply are functioning correctly. Swap parts to see if one of the components is faulty.
Step 5 Ensure that the fan tray is seated properly. Make sure the fan control board edge connector is inserted fully in the backplane socket.
Step 1 Check to see if the fans are operating.
Step 2 If the fans are not operating and the DC OK LED is off, there might be a problem with the +24V DC power.
Step 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.
Step 4 If the system and the fans start up but shut down after about two minutes, one or more fans has failed or is operating out of tolerance. You will see an error message similar to the following:
If one or more fans or the fan control board fails, you must replace the fan tray.
Step 5 If you see the following error message, the system has detected an overtemperature condition or out-of-tolerance power inside the chassis:
If an environmental shutdown results from an out-of-tolerance power condition, the DC OK LED will go off before the system shuts down.
This 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.
Step 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.
Step 1 Check to see if the RP LEDs come on when system power is turned on.
Step 2 If none of the RP LEDs come on, make sure that both the fan and power supply are functioning properly.
Step 3 If the power supply and fans appear operational but none of the RP LEDs are on, an improperly connected RP, SP (or SSP), or interface processor might have hung the bus.
Step 4 If the SP (or SSP) Enabled LED is off but any of the RP LEDs are on, make sure the SP (or SSP) is seated in its slot properly.
Step 5 Check to see if the Boot Error LED is on. If it is, the system software is unable to start up. If you have a spare RP with the system software ROMs installed, replace the installed RP with the spare to see if the system will boot.
Step 6 Check to see if 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.
Step 7 Check to see if all interface processor Enabled LEDs are on.
Step 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.
When you start up a Cisco 4000 series or a Cisco 3000 series router, the following should occur:
When the system has initialized successfully, the system banner (which should look similar to the following example) should be displayed on the console screen.
System Bootstrap, Version 4.14(9), SOFTWARE
Copyright (c) 1986-1994 by cisco Systems
4000 processor with 16384 Kbytes of main memory
Loading xx-j-mz.112-0.15 at 0x4A790, size = 3496424 bytes [OK]
F3: 8988+3487404+165008 at 0x12000
Self decompressing the image : ###[...]#### [OK]
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) 4000 Software (XX-J-M), Version 11.2(0.15), BETA TEST SOFTWARE
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Wed 03-Jul-96 01:21 by susingh
Image text-base: 0x00012000, data-base: 0x006F6494
cisco 4000 (68030) processor (revision 0xA0) with 16384K/4096K bytes of memory.
Processor board ID 5007155
G.703/E1 software, Version 1.0.
Bridging software.
SuperLAT software copyright 1990 by Meridian Technology Corp).
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
TN3270 Emulation software (copyright 1994 by TGV Inc).
Basic Rate ISDN software, Version 1.0.
2 Ethernet/IEEE 802.3 interfaces.
4 Serial network interfaces.
8 ISDN Basic Rate interfaces.
128K bytes of non-volatile configuration memory.
4096K bytes of processor board System flash (Read/Write)
Press RETURN to get started!
If problems occur, try to isolate the problem to a specific subsystem. The Cisco 4000 and Cisco 3000 series routers have the following subsystems:
Step 1 Check to see if the blower is operating. If it is not, check the AC power input, AC power source, router circuit breaker, and the power supply cable.
Step 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:
Make sure that the fans are working and that there is no air blockage to cooling vents.
Step 3 If the system partially boots but LEDs do not light, contact your technical support representative.
Step 1 Make sure that NPMs are properly connected to the motherboard connector.
Step 2 Check the external cables.
Step 3 Check the processor or software for proper configuration.
Step 4 Check the external console connection and verify that the console baud rate is correct.
When you start up a Cisco 2500 series router, the following should occur:
When the system has initialized successfully, the system banner (which should look similar to the following example) should be displayed on the console screen.
System Bootstrap, Version (3.3), SOFTWARE
Copyright (c) 1986-1993 by cisco Systems
2500 processor with 16384 Kbytes of main memory
Unknown or ambiguous service arg - udp-small-servers
Unknown or ambiguous service arg - tcp-small-servers
Booting igs-in-l.110-9 from Flash address space
F3: 3844616+90320+228904 at 0x3000060
Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
Cisco Internetwork Operating System Software
IOS (tm) 3000 Software (IGS-IN-L), Version 11.0(9), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-1996 by cisco Systems, Inc.
Compiled Tue 11-Jun-96 01:15 by loreilly
Image text-base: 0x03020F8C, data-base: 0x00001000
cisco 2500 (68030) processor (revision A) with 16384K/2048K bytes of memory.
Processor board ID 01062462, with hardware revision 00000000
Bridging software.
X.25 software, Version 2.0, NET2, BFE and GOSIP compliant.
Basic Rate ISDN software, Version 1.0.
1 Ethernet/IEEE 802.3 interface.
2 Serial network interfaces.
1 ISDN Basic Rate interface.
32K bytes of non-volatile configuration memory.
4096K bytes of processor board System flash (Read ONLY)
Press RETURN to get started!
If problems occur, try to isolate the problem to a specific subsystem. The Cisco 2500 series routers have the following subsystems:
Step 1 If the Power LED is off, make sure that the power supply is plugged into the wall receptacle and that the cable from the power supply to the router is connected.
Step 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.
Step 3 If the system does not boot up but LEDs are on, check the 12V power supply.
Step 4 If the system partially boots but LEDs are not on, check the 5V power supply.
Step 1 If a network interface is not recognized by the system, check the interface cable connection and the LED on the network interface.
Step 2 If a network interface is recognized but will not initialize, check the interface cable connection.
Step 3 If the system will not boot properly or constantly or intermittently reboots, there might be a processor or software problem. Make sure that DRAM SIMM modules are seated properly.
Step 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.
Step 5 If the system powers on and boots with a particular interface disconnected, check the network interface connection.
When you start up a Cisco 2000 series router, the following should occur:
When the system has initialized successfully, the system banner should be displayed on the console screen.
If there are problems during bootup, perform the steps in the following procedure.
Step 1 Check to see if the fan is operating. If it is not, check the fan or the 12V power supply.
Step 2 If the system shuts down after being on for a short time, check the power supply.
Step 3 If the power supply appears operational, the router might have shutdown due to overheating. Ensure that the chassis intake and exhaust vents are clear.
Step 4 If the system does not boot up but the System OK LED is on, check the 12V power supply to make sure it is not faulty.
Step 5 If the system partially boots but the System OK LED is not on, check the 5V power supply to make sure it is not faulty.
When you start up a Catalyst 5000 series LAN switch, the following should occur:
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:
Step 1 Check to see if 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.
Step 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.
Step 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.
Step 4 Repeat these steps for the second power supply if present.
Step 1 Check to see if the Fan LED on the supervisor engine module is green. If it is not, check the power subsystem to see if it is operational.
Step 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.
Step 3 If the Fan LED is still red, the system has probably detected a fan assembly failure. Contact a technical support representative for assistance.
Step 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.
Step 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.
Step 3 Check all cabling and connections. Replace any faulty cabling.
When you start up a Catalyst 3000 series LAN switch, the following should occur:
The console screen displays a script and system banner while booting, which should be similar to the following:
Cisco Catalyst Boot Firmware P/N 57-1327-02, Copyright 1995 - Initiating bootstrapping sequence. - Boot image integrity check...Passed. - Control transferred to boot process. - Relocating main image to DRAM.......Done. - Main image integrity check...succeeded. - Control transferred to main process. Cisco Catalyst 3000 System Software Version 1.1.1-B7, Copyright 1994, 1995. System started on Fri. November 17, 1995 13:02:46 4 Megabytes System memory 2 Megabytes Network memory - Initialization started - File system initialized - System temperature is within safe operating levels - Warmboot initialization started - Checking file system integrity - LAN ports detected: - 10Base-T : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 - StkPort : 25 - Initializing Ports: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 25 - Initializing system address table - No existing diagnostic information, forcing diagnostic mode - Starting Power Up Diagnostics test - UART loopback test on diagnostic port...Passed - UART loopback test on console port...Passed - RTC memory test...Passed - Real Time Clock test...Passed - CPU loopback test..............Passed - Ethernet Port loopback test...................Passed - Ethernet Port fast transmit loopback test...................Passed - Ethernet Port fast receive loopback test...................Passed - Ethernet Port cross port loopback test...................Passed - Ethernet Port broadcast test...................Passed - Catalyst Stack Port loopback test...Passed - Catalyst Stack Port cross port loopback test...Passed - Catalyst Stack Port broadcast test...Passed - CPU broadcast test...Passed - Completed Power Up Diagnostics test - System entering stand-alone mode - Catalyst initiating bootp requests on one or more VLANs - System initialization complete - Enabling port: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 25 Press RETURN key to activate console...
If problems occur, try to isolate the problem to a specific subsystem. The Catalyst 3000 series LAN switches have the following subsystems:
Step 1 Check to see if the Power LED is on. If it is not on and the fans are not running, check the AC power cord and the AC receptacle the cord is plugged into.
Make sure the cord is intact and properly attached. Swap the cord with another cord to see if the cord is faulty. Make sure the receptacle is receiving power.
Step 2 If the Fault LED comes on after power up or after the unit has been running for a period of time, cycle the power to the unit.
Step 3 Check to see if the fans are running and that the chassis intake vents and exhaust ports are clear.
Step 4 Use the console connection to check if a temperature error has occurred.
Step 1 If a network interface is not recognized by the system, check the interface cable and connection and the LED that corresponds to the network interface.
Step 2 If a network interface is recognized but will not communicate properly, check the interface cable and connections.
Step 3 If the system will not boot properly or intermittently reboots, the processor may be faulty or the hardware or software setup may be incorrect.
Step 4 If the system boots but the console is frozen, check the external console connection and verify the console setup.
When you start up a Catalyst 2900 series LAN switch, the following should occur:
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:
Step 1 Check the Power LED. If the LED 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.
Step 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.
Step 1 Check to see if the Fan LED on the supervisor engine module is green. If it is not, check the power subsystem to see if it is operational.
Step 2 If the Fan LED is red, contact a technical support representative for assistance.
Step 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.
Step 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.
Step 3 Check all cabling and connections. Replace any faulty cabling.
When you start up a Catalyst 1600 Token Ring switch, the self-test program automatically checks to see if the switch is operating correctly. The self-test begins by testing low-level hardware functions and then conducts high-level self-tests. During the high-level self-test, the LCD panel displays the following:
If the Catalyst 1600 fails the low-level test, the startup process is halted. If the Catalyst 1600 fails a high-level test, the self-test program restarts and the number of the failed test is displayed. High-level tests are repeated until the self-test is completed successfully.
If a hardware error occurs, contact your technical support representative. Be sure to note the number of the failed test and the version number of the software containing the self-test program.
When you start up a LightStream 2020 ATM switch, the blowers start running and the test and control system (TCS) applies power to the cards and initiates a series of diagnostics known as the power-on self-test (POST). POST diagnostics run automatically on each card whenever the system or the slot is powered up or when the card is reset. If a card passes POST, the green RDY LED turns on. If a card fails POST, its yellow FLT LED turns on.
If a problem occurs during system initialization, perform the following procedure first:
Step 1 Make sure that power cords and data cables are firmly connected at both ends.
Step 2 Make sure all cards (front and back of the chassis) are firmly seated in the midplane and screwed securely to the chassis.
Step 3 Make sure power supplies, blowers, and disk drives are properly connected and screwed securely to the chassis.
If you are experiencing any of the following symptoms, you might need to replace the blower.
In a system with one power tray, no power will be present if the power tray is faulty. There might be a problem with the power tray if cycling the system's power has no effect.
A system with two power trays can operate normally when only one is working. If you suspect a problem, use the command-line interface (CLI) command show chassis powersupply. If a status line for an occupied slot says anything other than Good, check the faulty power tray to see that it is properly connected. Replace the power tray if necessary.
If you are experiencing any of the following symptoms, you might need to replace the switch card.
If the NP fails to power up, check its access card at the back of the chassis. An NP requires an NP access card (NPAC); it cannot operate with any other kind of access card.
If the system fails to boot, it could indicate either a problem with the NP, a problem with the NP's hard disk drive, or a problem with the software on the hard drive.
If you are experiencing any of the following symptoms, you might need to replace the NP card.
The following tips will help you distinguish between problems in a line card and problems in an access card:
If you are having trouble bringing up an interface module, check the following:
If you are having signal quality problems with a physical interface on an access card, check the following:
If you are experiencing any of the following symptoms, you might need to replace the line card or its access card.
Disk assembly problems are indicated by the following symptoms:
If a disk problem is indicated, check the disk assembly connector for bent or broken pins. If any pins are bent or damaged, they are the likely source of the problem. Replace the disk assembly connector.
If the connector is in good condition, the problem may be in the disk assembly itself, or in the software on the disk. If you suspect a problem with the software, you should be able to correct it by reinstalling the software as described in the LightStream 2020 Network Operations Guide.
Midplane problems are indicated by the following symptoms.
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, then reboot.
 | Warning 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. |
If a part replacement appears to solve a problem, reinstall the suspect part to verify the failure. Always double-check a repair.
Symptom: When booting a router from Flash memory, the boot process appears to complete, but the router does not route traffic or communicate with neighbors. EXEC commands might or might not appear to function.
Table 3-1 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: Vector errors occur when booting a router from Flash memory.
Table 3-2 outlines the problems that might cause this symptom and describes solutions to those problems.
| Possible Problem | Solution |
|---|---|
| Compressed system image | Step 1 Power-cycle the router.
Step 2 Within the first 60 seconds of booting, press the Break key to access the ROM monitor. Step 3 At the ROM monitor prompt ( Step 4 Enter b to boot the router. The router will enter setup mode. Step 5 Press Ctrl-C to bypass the setup. Step 6 Enter the configure memory privileged EXEC command. Step 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 TFTP server. Decompress the image at the TFTP server. This cannot be done at the router. Step 8 Use the copy tftp flash privileged EXEC command at the router to retrieve the uncompressed image. Step 9 Check the configuration register using the show version EXEC command. Set the router to boot from Flash memory. Step 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. Step 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. Step 12 Enter the reload privileged EXEC command to restart the router. |
| Router hardware problem | Troubleshoot router hardware as discussed earlier in this chapter. |
Symptom: When 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 will not route, although EXEC commands might appear to be operational.
Table 3-3 outlines the problems that might cause this symptom and describes solutions to those problems.
| Possible Problem | Solution |
|---|---|
| No system image in Flash memory | Step 1 Use the show flash EXEC command to determine whether an image exists in Flash memory.
Step 2 If no image exists, use the copy tftp flash privileged EXEC command to copy the system image from your TFTP server to the router's Flash memory. Step 3 Enter the reload privileged EXEC command to reboot the router. |
| Missing boot system flash global configuration command | Step 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 if the boot system flash command is included in the configuration stored in NVRAM.
Step 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. Step 3 Add the boot system flash command or reorder the boot system commands if necessary. Step 4 Save the configuration change to NVRAM using the copy running-config startup-config privileged EXEC command. |
| Misconfigured configuration register | Use the show version EXEC command to check the configuration register setting. Make sure it is set to boot from Flash memory. Refer to your hardware installation and maintenance publication for details regarding configuration register settings. |
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 netboot session:
Booting gs3-bfx..........[failed]
Table 3-4 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: A router cannot boot properly when booting from another router acting as a TFTP server.
Table 3-5 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: Timeouts or out-of-order packets prevent successful netbooting. The number of timeouts and out-of-order packets indicated on the router's console display might vary.
The following example shows a netbooting 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 netbooting (as well as network service availability) might be inconsistent.
Table 3-6 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: Invalid routes prevent successful netbooting. 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 netboot sequence still fails. The boot message would be similar to the following:
Booting gs3-bfx!..........[failed]
Table 3-7 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: Client ARP requests time out during a netboot. If the router does not receive an ARP response, a message similar to the following is displayed on the console:
Booting gs3-bfx..........[timed out]
Table 3-8 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: An undefined load module error occurs during a netboot. The console display indicates an "undefined load module" error, and the router is unable to boot.
Table 3-9 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: When 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-10 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: Router is stuck in ROM monitor mode. When booting a router from ROM, the system boots into ROM monitor mode but does not boot the complete system image.
Table 3-11 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: When booting from ROM, the router displays indecipherable textual output on the console.
Table 3-12 outlines the problems that might cause this symptom and describes solutions to those problems.
Symptom: "Local timeout" error messages are generated when booting from ROM. The router is unable to complete its boot process and will not start the ROM monitor.
Table 3-13 outlines the problems that might cause this symptom and describes solutions to those problems.
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-14 outlines the problems that might cause this symptom and describes solutions to those problems.
| 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) | Step 1 Check if flow control is configured on your terminal.
Step 2 Disable all flow control on the terminal. With flow control enabled, the terminal will wait indefinitely for a CTS1 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. Step 3 Alternatively, you can strap 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," or short, 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. Step 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. |
| Hardware problem | Step 1 Check all hardware for damage, including cabling (broken wires), adapters (loose pins), access server ports, and the terminal itself.
Step 2 Replace any hardware that is damaged or excessively worn. For more information, refer to the hardware troubleshooting information earlier in this chapter. |
|
|