Table of Contents
Troubleshooting the Installation
Your Cisco 7200 VXR router went through extensive testing before leaving the factory. However, if you encounter problems starting the router, use the information in this appendix to help isolate the cause of the problems. This appendix contains the following sections:
The procedures in this appendix 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 appendix might not apply. Make sure to review the safety warnings listed in the publication Regulatory Compliance and Safety Information for the Cisco 7200 Series Routers that accompanied your Cisco 7200 VXR router before using the troubleshooting procedures in this appendix.
This section describes the troubleshooting methods used in this appendix and describes how the Cisco 7200 VXR routers are 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:
- Date you received the router
- Chassis serial number
- Type of software and release number
- Brief description of the problem you are having
- Brief explanation of the steps you have taken to isolate and resolve the problem
- Maintenance agreement or warranty information
Figure A-1 shows the general troubleshooting strategy described in this appendix. Refer to this chart, as necessary, to follow the steps to isolate problems to a specific subsystem; resolve the problem if possible.
Figure A-1: Troubleshooting Strategy for Startup Problems
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.
Startup problems are commonly due to the source power or to a board (network processing engine or network services engine, I/O controller, or port or service adapter) that is dislodged from the midplane. Although an overtemperature condition is unlikely at initial startup, the environmental monitoring functions are included in this appendix 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 section "Starting the System and Observing Initial Conditions" in the chapter "Observing System Startup and Performing a Basic Configuration." 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.
With the exception of the fan tray and network processing engine or network services engine, 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:
- If the green power OK LED does not come on, proceed to the section Troubleshooting the Processor Subsystem
 |
Note The I/O controller without the Fast Ethernet port does not have the FE enabled LED and the FE link LED. The I/O controller without the Fast Ethernet port and the I/O controller that is equipped with a single MII receptacle do not have the MII enabled, RJ-45 enabled, and RJ-45 Link LEDs. |
- The FE link LED comes on only when the Fast Ethernet port on the I/O controller is receiving a carrier signal from the network. This LED remains off during normal operation of the router unless there is an incoming carrier signal, and does not indicate startup problems.
- If this LED remains off when you start the router, it is probably a problem with the Fast Ethernet port on the I/O controller. Proceed to the "Troubleshooting the I/O Controller" section.
- The MII enabled LED comes on after the enabled LED and indicates that the Fast Ethernet port's MII receptacle is initialized and enabled for operation by the system, and configured for operation. This LED comes on during a successful router boot and after the MII receptacle has been configured as the media type for the Fast Ethernet port (the RJ-45 receptacle is the default media type for the Fast Ethernet port). This LED remains on during normal operation of the router.
- If this LED remains off when you start the router, it is probably a problem with the Fast Ethernet port on the I/O controller. Proceed to the "Troubleshooting the I/O Controller" section.
- The RJ-45 enabled LED comes on after the enabled LED and indicates that the Fast Ethernet port's RJ-45 receptacle (the default media type for the Fast Ethernet port) is initialized and enabled for operation by the system. This LED comes on during a successful router boot and remains on during normal operation of the router.
- If this LED remains off when you start the router, it is probably a problem with the Fast Ethernet port on the I/O controller. Proceed to the "Troubleshooting the I/O Controller" section.
- The RJ-45 link LED comes on only when the Fast Ethernet RJ-45 receptacle is receiving a carrier signal from the network. This LED remains off during normal operation of the router unless there is an incoming carrier signal, and does not indicate startup problems.
- If this LED remains off when you start the router, it is probably a problem with the Fast Ethernet port on the I/O controller. Proceed to the "Troubleshooting the I/O Controller" section.
|
Note An MII link LED is not provided on the I/O controller because the LED is provided on external transceivers that are required for connecting to the MII receptacle on the I/O controller. See the section "Connecting to the Fast Ethernet Port" in the earlier chapter "Installing a Cisco 7200 VXR Router" for Fast Ethernet MII connection requirements. |
- The slot 1 and slot 2 LEDs only come on when either PCMCIA slot is being accessed by the system. These LEDs remain off during normal operation of the router and do not indicate startup problems.
Check the following to help isolate a problem with the power subsystem:
- On the first power supply, is the power OK LED on?
- If yes, the power source is good, and the power supply is functional.
- If no, make sure the power cable is connected at both ends.
- If the power OK LED remains off, and the power switch is set correctly, suspect the power source or the power cable. Turn the switch off, connect the power cable to another power source, if available, and turn the switch back on. If the LED comes on, the problem is the first power source.
- If the power OK LED fails to come on after you connect the power supply to a new power source, replace the power cord, and turn the switch back on. If the AC power (or input power) LED then comes on, return the first power cable for replacement.
- If the LED still fails to come on when the power supply is connected to a different power source with a new power cable, the power supply is probably faulty. If a second power supply is available, install it in the other power supply bay and contact a service representative for further instructions.
- Is the power OK LED on for the second (redundant) power supply?
If you are unable to resolve the problem or you determine that either a power supply or chassis connector is faulty, contact a service representative for instructions.
The processor subsystem comprises the I/O controller, network processing engine or network services engine, and all port adapters. The I/O controller and network processing engine or network services engine are required system components. The system cannot operate unless the I/O controller and network processing engine or network services engine are installed properly; however, the system can operate without any port adapters installed as long as none are in partial contact with the midplane pins. A port adapter that is partially connected to the midplane sends incomplete signals to the processor, which faults the PCI bus and causes the system to hang. Therefore, first ensure that the I/O controller and the network processing engine or network services engine are installed properly and the system software has initialized successfully. Then, if necessary, you can troubleshoot individual port adapters.
The procedures in this section assume that the I/O controller, network processing engine or network services engine, and router itself are in the original factory configuration, and that you have not made changes to your configuration file.
If the I/O controller LEDs do not go on as expected (see the "Identifying Startup Problems" section), check the following items to help isolate the problem.
- Do all of the I/O controller LEDs remain off when the system power switch is
turned on?
- 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.
- If the power supply and fans appear operational but none of the I/O controller LEDs are on, suspect that an improperly connected I/O controller or port adapter has hung the system. Tighten all captive installation screws, and then restart the system.
- With the power supply turned off, reseat the I/O controller in its slot and restartthe router.
- Is the I/O controller enabled LED on?
- If yes, the system software has initialized successfully, and the system is operational.
- If the enabled LED remains off, the system detected a processor hardware failure. (This LED should be on in normal operation.) Contact a service representative for instructions.
The procedures in this section assume that the I/O controller, network processing engine or network services engine, and router itself are in the original factory configuration, and that you have not made changes to your configuration file. Also see the troubleshooting chapter of the Network Processing Engine and Network Services Engine Installation and Configuration guide for the network services engine parallel express forwarding (PXF) processor information.
If the I/O controller enabled LED does not go on as expected, make sure the power to the router is turned off, reseat the network processing engine or network services engine in its slot, and restart the router.
If the enabled LED remains off, the system detected a processor hardware failure. (This LED should be on in normal operation.) Contact a service representative for instructions.
Check the following to help isolate a problem with the port or service adapters:
- Are all adapter enabled LEDs on?
- If yes, the system is operational.
- Are any adapter enabled LEDs off?
- If the enabled LED on an individual adapter is off, suspect that the adapter has pulled away from the midplane. Reseat the adapter in its slot (you do not have to turn off the system power when removing or replacing port and service adapters). After the system reinitializes the interfaces, the enabled LED on the adapter should go on.
- If the enabled LED remains off, the system detected a processor hardware failure. (This LED should be on in normal operation.) Contact a service representative for instructions.
Check the following to help isolate a problem with the cooling system:
- When you start up the system, do the fans start operating?
- To determine if the fans are operating, listen for them. In noisy environments, place your hand on the left side of the chassis (when viewing the chassis from the front) to feel for air being forced out the vents.
- The following message, if displayed, indicates that 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 power OK LED goes off, and the system shuts down. (See the "Troubleshooting the Power Subsystem" section.) Although an overtemperature condition is unlikely at initial startup, ensure that heated exhaust air from other equipment is not entering the router's inlet vent, and that there is sufficient clearance around the sides of the chassis to allow cooling air to flow. See the section "Site Requirement Guidelines" in the chapter "Preparing for Installation" for preventive site configurations.
- The above message could also 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 the section "Functional Overview" in the chapter "Cisco 7200 VXR Product Overview" for descriptions of the show environment and show environment table commands.)
If you experience trouble with the startup that is not resolved with these procedures, contact a service representative for assistance and further instructions.
Posted: Thu Mar 30 13:30:04 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.
