Basic Troubleshooting Tasks and Startup Issues

Transcription

1 CHAPTER 1 This chapter describes the basic procedures that users should perform before undertaking a detailed troubleshooting analysis of the Cisco series router or logging a case with the Cisco Technical Assistance Center (TAC). These basic troubleshooting checks are organized as follows: Basic Troubleshooting Tasks, page 1-1 Confirming the Hardware Installation, page 1-1 Displaying Cisco IOS Software Version and System Environment Information, page 1-2 Hardware Troubleshooting Flowchart, page 1-4 Cisco Series Router System Startup Sequence, page 1-5 Basic Troubleshooting Tasks If you encounter a problem after you install the Cisco series router, perform the following troubleshooting checks on the equipment before you contact the Cisco Technical Assistance Center (TAC) or before you perform a detailed troubleshooting analysis: 1. Is the power on 2. Is the PRE seated securely in the chassis 3. Are the other line cards firmly seated and securely screwed to the chassis 4. Are power leads and data cables firmly connected at both ends 5. Are the blower module and PEMs properly connected and secured to the chassis 6. Are the ports properly configured Refer to the Cisco Series Router Line Card Hardware Installation Guide for configuration examples. Confirming the Hardware Installation Start troubleshooting the installation by issuing the show hardware command. The show hardware command displays all hardware components that are recognized by the system. These components can include Performance Routing Engines (PREs) Gigabit Ethernet line cards (GEs) 1-1

2 Displaying Cisco IOS Software Version and System Environment Information Chapter 1 OC-12 Packet Over SONET (POS) line cards CT3 Subscriber line cards If an installed item does not appear in the command output, make sure the item is properly installed. For example, make sure the line cards are fully inserted into the slot and the captive screws are tightened. If the problem persists, consult the Cisco series router release notes to confirm that this is not an existing problem. Finally, you should consider replacing the component. The following example is sample output from the show hardware command: Router# show hardware Cisco Internetwork Operating System Software IOS (tm) Software (C10K-P6-M), Experimental Version 12.0( :073152) [ : ] Copyright (c) by Cisco Systems, Inc. Compiled Wed 08-Mar-00 04:49 by chrel Image text-base:0x , data-base:0x60a44000 ROM:System Bootstrap, Version 12.0( :180332) [REL-omega_isp.ios-rommon 101], DEVELOPMENT SOFTWARE BOOTFLASH:10000 Software (C10K-EBOOT-M), Experimental Version 12.0( :074438) [ : ] omega-1 uptime is 9 minutes System returned to ROM by power-on Running default software cisco C10000 (CRE-RP) processor with K/32768K bytes of memory. Processor board ID dt-omega-1_ R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache Unknown midplane, Version 1.0 Last reset from power-on Toaster processor tmc0 is running. Toaster processor tmc1 is running. 1 Ethernet/IEEE interface(s) 1 FastEthernet/IEEE interface(s) 1 GigabitEthernet/IEEE interface(s) 257 Serial network interface(s) 1 Packet over SONET network interface(s) 12 Channelized T3 port(s) 509K bytes of non-volatile configuration memory K bytes of Flash PCMCIA card at slot 0 (Sector size 128KB) K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes) K bytes of Flash internal SIMM (Sector size 256KB). Configuration register is 0x2 Displaying Cisco IOS Software Version and System Environment Information Run the show version and show environment commands to determine if the Cisco series router is operating within acceptable bounds. Using the show version Command Use the show version command to confirm that you are running the proper version of IOS and have a sufficient amount of system memory. The command also reports the system uptime and the method by which the system was powered up. 1-2

3 Chapter 1 Displaying Cisco IOS Software Version and System Environment Information In the following sample of output from the show version command, some of the information that may be useful for troubleshooting appears in bold type: Router# show version Cisco Internetwork Operating System Software IOS (tm) 10K Software (C10K-EBOOT-M), Experimental Version 12.0( :085921) [BLD-omega_isp.ios-weekly 101] Copyright (c) by Cisco Systems, Inc. Compiled Thu 16-Sep-99 05:20 by Image text-base: 0x , data-base: 0x6047A000 ROM: System Bootstrap, Version 12.0( :134935) [fyang-cre1 1004], DEVELOPM ENT SOFTWARE another-omega uptime is 6 hours, 7 minutes System returned to ROM by power-on at 14:12:52 EST Fri Jan System image file is "bootflash:c10k-eboot-mz" cisco C10000 (CRE-RP) processor with K/16384K bytes of memory. Processor board ID noserial R7000 CPU at 262Mhz, Implementation 39, Rev 1.0, 256KB L2, 2048KB L3 Cache Unknown midplane, Version 0.0 Last reset from register reset 1 Ethernet/IEEE interface(s) 1 FastEthernet/IEEE interface(s) 509K bytes of non-volatile configuration memory K bytes of Flash PCMCIA card at slot 0 (Sector size 128KB). Configuration register is 0x0 Using the show environment Command for Basic Troubleshooting Use the show environment command to Make sure the system operating temperature is equal to or less than 40 degrees C or 104 degrees F at the inlet. Report the operational status of the PEMs and blower If the operating temperature is not between 41 degrees F and 104 degrees F, refer to the Blower Module Faults section on page 2-5. The following example is sample output from the show environment command: Router# show environment Temperature normal:chassis inlet measured at 29C/84F Temperature normal:chassis core measured at 39C/102F Fan: OK Power Entry Module 0 type DC status: OK Power Entry Module 1 type AC status: Failure The Cisco series router default temperature alarm thresholds are programmed to assert at approximately these conditions: Minor inlet and core alarms will assert when the ambient temperature is within a few degrees of 40 degrees C. Major inlet and core alarms will assert when the ambient temperature is within a few degrees of 50 degrees C. Critical inlet and core alarms will assert when the ambient temperature is within a few degrees of 70 degrees C. 1-3

4 Hardware Troubleshooting Flowchart Chapter 1 A malfunctioning blower or blocked air passages could result in these alarms asserting at lower ambient temperatures. For customer sites where ambient temperatures are frequently close to 40 degrees C, and/or for customers who do not wish to receive these alarms, the minor and major thresholds can be adjusted. Hardware Troubleshooting Flowchart Use Figure 1-1 to determine which component of your Cisco series router is malfunctioning. Figure 1-1 describes a series of hardware dependent startup events that must take place for a Cisco series router to allow the passage of IP traffic. At each main point of the flowchart, there are pointers to the chapters in this guide that describe how to troubleshoot individual pieces of hardware. Note This flowchart does not address software configuration problems. Figure 1-1 Hardware Troubleshooting Flowchart Turn on PEM *Miswire LED off No Correct input wiring PEM Power OK LED on PRE Status LEDs OK System startup successful No No Line card No LEDs on Troubleshoot PEM Reseat PRE and restart Reseat line card and restart PEM No Power OK LED on PRE No status LEDs OK See section "PEM Faults" See section "PRE Module Faults" See appropriate line card fault Line card LEDs OK No section Obtain technical assistance

5 Chapter 1 Cisco Series Router System Startup Sequence Cisco Series Router System Startup Sequence Table 1-1 describes the visible sequence of events that occur during a typical Cisco series router power up. Table 1-1 Cisco Series Router System Startup Sequence Startup Event PEM is switched off Power on the router Event Description The AC or DC PEM Fault LED is lit. 1. The yellow Critical, Major, and Minor alarm and Fail LEDs illuminate for about 2 seconds. 2. The alphanumeric display on the PRE counts up through a range of numbers from 1111 to 9999 (1111, 2222, and so on). 3. The alphanumeric display counts up through a sequence of letters from AAA to CCC (AAA, BBB, and CCC). 4. The message ROM DONE appears on the alphanumeric display. Note If the system is not configured to auto boot, it stops at the ROM DONE message. The console displays a rommon> prompt. IOS loads 1. If the system is set to boot from the slot0: file system, the green slot 1 LED lights. 2. The message BOOT IMGE appears on the alphanumeric display. 3. The console displays a series of pound signs (#) as the IOS software image is decompressed. 4. The following messages appear on the alphanumeric display: IOS STRT IOS EXC IOS FPGA IOS FPOK IOS FILE IOS STBY IOS DRVR IOS LIB IOS MGMT IOS CONF The console displays:... Press RETURN to get started! 5. The following appears in the alphanumeric display: In a redundant configuration, the message IOS STBY appears on the alphanumeric display of the secondary PRE after a successful startup. If the boot process fails, no console access is available. If you cannot boot the Cisco series router, call the Cisco TAC. 1-5

6 Cisco Series Router System Startup Sequence Chapter 1 1-6