Downloads |
 Feedback
|
Table Of Contents
Which prompt do you see on the console?
Router in Boot Mode: Router (boot)>
Online Troubleshooting Resources
Problem Solving Using a Subsystems Approach
Troubleshooting the Power Subsystem
Troubleshooting the I/O Subsystem
Troubleshooting the Cooling Subsystem
Troubleshooting the Processor Subsystem
Configuring Autoboot to Boot from the Network
Configuring Autoboot to Boot from a Local Device
Troubleshooting
Your Cisco 7304 router went through extensive testing before leaving the factory. However, if you encounter problems starting the router, use the information in this chapter to help isolate the cause of the problems. This chapter contains the following sections:
•
Troubleshoot Startup Problems
•
•
•
The procedures in this chapter assume that you are troubleshooting the initial system startup, and that your router is in the original factory configuration. If you have removed or replaced components or changed any default settings, the recommendations in this chapter might not apply. Make sure to review the safety warnings listed in the publication Cisco 7304 Internet Routers Regulatory Compliance and Safety Information document that accompanied your Cisco 7304 router before using the troubleshooting procedures in this chapter.
Troubleshoot Startup Problems
This section assumes you are able to boot the router. If you cannot, go to Troubleshooting Overview.
Which prompt do you see on the console?
•
•
•
•
Check the LEDs
If you get no response from the console after pressing Return a couple times, check the processing engine and power supply LEDs. Refer to Chapter 1, the "Hardware Overview" section for processing engine LED information, and Chapter 2, the "Power Supply Overview" section for power supply LED information.
Check Terminal Settings
Terminal Settings
•
•
•
•
•
ROMmon prompt: rommon # >
Use this procedure to recover a router stuck in ROMmon mode (rommon # > prompt).
Step 1
rommon 1 > devDevices in device table:id namebootdisk: boot diskdisk0: PCMCIA slot 0eprom: epromrommon 2 >Step 2
rommon 3 > dir disk0:Directory of disk0:3 4965400 -rw- c7300-js-mz.121-99.WS_DAILY_BUILD_200107061216 1867 -rw- running-configrommon 4 >Step 3
rommon 5 > boot disk0:c7300-js-mz.121-99.WS_DAILY_BUILD_20010706Self decompressing the image : ###################################################################################### ###################################################################################### ###################################################################################### ###################################################################################### ############################################################################# [OK]Step 4
Router# show bootvariableBOOT variable = disk0:c7300-js-mz.121-99.WS_DAILY_BUILD_20010706,12CONFIG_FILE variable does not existBOOTLDR variable =Configuration register is 0x2101Router#conf tEnter configuration commands, one per line. End with CNTL/Z.Step 5
Router(config)# no boot systemRouter(config)#boot system disk0:c7304-js-mz.121.99Router(config)#^ZRouter#22:51:40: %SYS-5-CONFIG_I: Configured from console by consoleA newly defined variable does not go into effect yet, as seen from show bootvariable.
Router# show bootvariableBOOT variable = disk0:c7300-js-mz.121-99.WS_DAILY_BUILD_20010706,12CONFIG_FILE variable does not existBOOTLDR variable =Configuration register is 0x2102The newly defined variable only takes effect after using the copy running-config startup-config command or after a save of system configuration during the reload command.
Router# copy running-config startup-configBuilding configuration...[OK]Router#sh bootvBOOT variable = disk0:c7304-js-mz.121.99,12CONFIG_FILE variable does not existBOOTLDR variable =Configuration register is 0x2102Step 6
a.
rommon 1 > confreg 0x2101b.
rommon 2 > resetor> iThe System Bootstrap message appears and the router loads an image from bootdisk. On the screen, you should see something similar to the following:
System Bootstrap, Version 12.1(9) [biff-ws28 124], RELEASED SOFTWARECopyright (c) 1994-2001 by cisco Systems, Inc.C7300 platform with 131072 Kbytes of main memoryCurrently running ROMMON from OTP ROMSelf decompressing the image : ###################################################################################### ###################################################################################### ###################################################################################### ######################################################### [OK]Restricted Rights LegendYou should now have a prompt similar to Router (boot)>. Upgrade the Cisco IOS software by following the procedure in the "Router in Boot Mode: Router (boot)>" section.
Note
rommon 3 > boot disk0:c7300-js-mz (where disk0:is the flash disk with the image c7300-js-mz copied from another Cisco 7304 router)Step 7
If you do not have another Cisco 7304 router, call TAC to request a CompactFlash Disk with a valid boot image.
Bootldr Command
Use the bootldr command to specify an image to boot the system in the case of a system crash. You can use the bootldr command in IOS or in ROMmon mode.
You can use the bootldr command in IOS:
Router>enableRouter#>configRouter(config)# boot bootldr bootdisk:c7300-boot-mz-my-imageRouter(config)# copy running-config startup-configThe show bootvar command can be used in ROMmon mode to verify that parameter settings are correct.
In cases where the system will not boot up, you can also use the bootldr command in ROMmon mode. First check to see if bootldr is set correctly:ROMMON>setIf bootldr is not set correctly, set it with the correct image:
ROMMON>BOOTLDR="bootdisk:c7300-boot-mz-my-image"
Caution
You can use the ROMmon command sync to save the current parameters that remain after a power cycle to NVRAM.
Use the set command to check your configuration.
Router in Boot Mode: Router (boot)>
If the router is in boot mode, it means the router has a corrupt or missing Cisco IOS image. Use this procedure to upgrade the Cisco IOS software.
Step 1
Note
Router(boot)>Router(boot)>enablePassword: passwordRouter(boot)#conf tEnter configuration commands, one per line. End with CNTL/Z.Router(boot)(config)#conRouter(boot)(config)#config-register 0x0Router(boot)(config)#^ZStep 2
Step 3
Router> enablePassword: passwordRouter#Router# copy tftp disk0:Step 4
Address or name of remote host [255.255.255.255]? 172.17.247.195Step 5
Source file name? c7300-js-mz.121-9.E
Note
Step 6
Destination file name c7300-js-mz.121-9.EPThe copying process takes several minutes; the time differs from network to network. During the copy process, messages are displayed to indicate which files have been accessed.The exclamation point (!) indicates that the copy process is taking place. Each exclamation point (!) indicates that ten packets were transferred successfully. A checksum verification of the image occurs after the image is written to Flash memory. The router reloads itself with the new image when the software upgrade is complete.Step 7
Router(boot)#reload*Mar 1 00:30:49.972: %SYS-5-CONFIG_I: Configured from console by consoleSystem configuration has been modified. Save? [yes/no]: NOProceed with reload? [confirm] YESBecause the configuration register is set to 0x0, the router will go into ROMmon when you reload and you will load the image you just copied. Follow the instructions in the "ROMmon prompt: rommon # >" section.
Step 8
rommon 1 > confreg 0x2101Step 9
Router# show versionCisco Internetwork Operating System SoftwareIOS (tm) 7300 Software (C7300-js-M), Version 12.1(9), CISCO RELEASED VERSIONCopyright (c) 1986-2001 by cisco Systems, Inc.Compiled Fri 06-Jul-01 02:01 by biffImage text-base: 0x40008970, data-base: 0x40BF6000ROM: System Bootstrap, Version 12.1(20010705:000010) [biff-ws28 124], RELEASED SOFTWAREROM: 7300 Software (C7300-BOOT-M), Version 12.1(9), CISCO RELEASED VERSIONRouter uptime is 18 minutesSystem returned to ROM by power-onSystem image file is "disk0:c7300-js-mz.121-99.WS_DAILY_BUILD_20010706"cisco 7300 (NSE100) processor (revision A) with 114688K/16384K bytes of memory.Processor board IDR7000 CPU at 350Mhz, Implementation 39, Rev 3.2, 256KB L2, 1024KB L3 Cache4 slot midplane, Version 65.48Last reset from watchdog nmiX.25 software, Version 3.0.0.PXF processor tmc0 is running.PXF processor tmc1 is running.1 FastEthernet/IEEE 802.3 interface(s)2 Gigabit Ethernet/IEEE 802.3 interface(s)509K bytes of non-volatile configuration memory.16064K bytes of ATA compact flash disk at bootdisk (Sector size 512 bytes).64000K bytes of ATA compact flash disk at disk 0 (Sector size 512 bytes).Configuration register is 0x2102
Troubleshooting Overview
This section describes the troubleshooting methods used in this chapter and describes how the Cisco 7304 router is divided into subsystems for more efficient problem solving. If you are unable to easily solve the problem, contact a customer service representative for assistance and further instructions. Provide the representative with the following information:
•
•
•
•
•
•
Table 4-1 shows the general troubleshooting strategy described in this chapter. Refer to this table, as necessary, to follow the steps to isolate problems to a specific subsystem; resolve the problem if possible.
Online Troubleshooting Resources
In addition to following the subsystems approach to troubleshooting, a variety of online troubleshooting resources are available.
For information on these resources, see the Cisco 7304 Internet Routers Troubleshooting Documentation Roadmap.
Problem Solving Using a Subsystems Approach
The key to solving problems with the system is isolating the problem to a specific subsystem. The first step in solving startup problems is to compare what the system is doing to what it should be doing. Because a startup problem is usually caused by a single component, it is more efficient to first isolate the problem to a subsystem rather than troubleshoot each component in the system. For these troubleshooting procedures, consider the following subsystems:
•
•
•
The following sections help you isolate a problem to one of these subsystems and direct you to the appropriate troubleshooting section.
Identifying Startup Problems
Startup problems are commonly due to the source power or to a line card that is dislodged from the system board. Although an overtemperature condition is unlikely at initial startup, the environmental monitoring functions are included in this chapter because they also monitor internal voltages.
When you start up the router for the first time, you should observe the startup sequence described in the "Starting the System and Observing Initial Conditions" section in "Starting and Configuring." This section contains a more detailed description of the normal startup sequence and describes the steps to take if the system does not perform that sequence as expected.
LEDs indicate all system states in the startup sequence. By checking the state of the LEDs, you can determine when and where the system failed in the startup sequence. Use the following descriptions to isolate the problem to a subsystem, and then proceed to the appropriate sections to try to resolve the problem.
When you start up the system by turning on the power supply switch, the following should occur:
•
•
Troubleshooting the Power Subsystem
Check the following to help isolate a problem with the power subsystem:
Note
Troubleshooting the I/O Subsystem
The procedures in this section assume that you have not made changes to your configuration file.
If the Cisco 7304 router LEDs on the processing engine do not go on as expected (see the "Identifying Startup Problems" section), check the following items to help isolate the problem:
Table 4-4 Troubleshooting the I/O Subsystem
LEDs remain off when the system power switch is turned on.
Power supply or cooling subsystem are faulty.
If the LEDs stay off, first see the "Troubleshooting the Power Subsystem" section and the "Troubleshooting the Cooling Subsystem" section to ensure that both the fans and the power supply are functioning properly.
Power supply and fans appear operational but none of the I/O LEDs are on.
An improperly connected line card has indefinitely paused the system.
Reseat the line card, tighten the locking thumbscrews, and then restart the system.
Troubleshooting the Cooling Subsystem
Check the following to help isolate a problem with the cooling subsystem:
Table 4-5 Troubleshooting the Cooling Subsystem
System shuts down and this error message
is displayed:Queued messages:%ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdownThis error message indicates that the system has detected an overtemperature condition or out-of-tolerance power condition inside the chassis.
The fans are not operating or the power supply is not operating.
To determine if the fans are operating, listen for them. In noisy environments, place your hand on the rear of the chassis to feel if air is being forced out the vents.
If the fans are not operating, call your local service representative.
Ensure that heated exhaust air from other equipment is not entering the router's inlet vents, and that there is sufficient clearance on the back of the chassis to allow complete ventilation. See "Installation and Maintenance," the "Site Requirement Guidelines" section for preventive site configurations.
Move other equipment or the router to ensure proper airflow.
The error message could indicate a faulty component or temperature sensor. Before the system shuts down, use the show environment or show environment table command to display the internal chassis environment. See "Starting and Configuring," the "Reporting Functions" section for descriptions of the show environment and show environment table commands.
Call your local customer service representative.
If an environmental shutdown results from an out-of-tolerance power condition, the system shuts down.
Troubleshooting the Processor Subsystem
The processor subsystem comprises the system board and the line card. A line card that is partially connected to the system board sends incomplete signals to the processor, which causes the system to pause indefinitely. Therefore, first ensure that the system software has initialized successfully and then check to see that all line cards and the processing engine are correctly seated.
Configuring Autoboot to Boot from the Network
To configure autoboot to boot from the network, you must have a usable network interface correctly configured. This procedure assumes your interface is configured and that a default gateway is set if the TFTP server is not local.
Follow these steps for configuring autoboot to boot from the network:
Step 1
Step 2
Step 3
See the following example:
Router> boot sysem tftp server_name://c7300-js-mzRouter> boot bootldr bootdisk:c7300-boot-mzRouter> config-reg 0x2102Router> copy running-config startup-config
Configuring Autoboot to Boot from a Local Device
The procedure for booting from a local device is similar to booting from the network. However, if you are booting from a local device, specifying the boot loader image is not necessary.
See the following example:
Router> boot system flash disk0:c7300-js-mzRouter> config-reg 0x2102Bootldr Command
Use the bootldr command to specify the boot helper image for booting from the network. You can use the bootldr command in Cisco IOS or in ROMmon mode.
You can use the bootldr command in Cisco IOS:
Router> enableRouter#> configRouter(config)# boot bootldr bootdisk:c7300-boot-mz-my-imageRouter(config)Router copy running-config: startup-configThe show bootvar command can be used in ROMmon mode to verify that parameter settings are correct.
In cases where the system will not boot up, you can also use the bootldr command in ROMmon mode. First check to see if bootldr is set correctly:
ROMMON>setIf bootldr is not set correctly, set it with the correct image:
ROMMON>BOOTLDR="bootdisk:c7300-boot-mz-my-image"
Caution
You can use the ROMmon command sync to save the current parameters that remain after a power cycle to NVRAM.
Use the set command to check your configuration.
