cc/td/doc/product/access/ap/ap_ts3
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Troubleshooting the Cisco AccessPath-TS3 Model 531 System
Cisco AccessPath-TS3 Model 531 Integrated Access System LED Diagrams
Troubleshooting Overview
Troubleshooting the Power Subsystem
Troubleshooting the Processor Subsystem (Router Shelf Only)
Troubleshooting the Cooling Subsystem
Troubleshooting Modules (Switch Shelf Only)
System-Level Troubleshooting Suggestions
Contacting Customer Service

Troubleshooting the Cisco AccessPath-TS3 Model 531 System


This appendix contains procedures for troubleshooting the Cisco AccessPath-TS3 Model 531 Integrated Access System hardware installation.

Your Cisco AccessPath-TS3 Model 531 system went through extensive testing before leaving the factory. However, if you encounter problems starting the system, use the information in this appendix to help isolate the cause of the problems. Problems with the initial startup are often caused by a switching module that has become dislodged from the backplane or a power supply that has been disconnected from the power cord connector.

This appendix contains the following sections:

Although temperature conditions above the maximum acceptable level rarely occur at initial startup, environmental monitoring functions are also included because they monitor DC line voltages.


Note      This appendix covers only hardware troubleshooting. For software troubleshooting information, refer to the Cisco AccessPath-TS3 Integrated Access System Software Configuration Guide.


When the initial system boot is complete, verify the following:

If each of these conditions is met and the hardware installation is complete, you probably have a software configuration problem. Refer to the Cisco AccessPath-TS3 Model 531 Integrated Access System Software Configuration Guide and the other documentation that shipped with your Cisco AccessPath-TS3 Model 531 system to troubleshoot the software.

However, if any of these conditions are not met, use the procedures in this appendix to isolate and, if possible, resolve the problem.


Note      Information on scaling the Cisco AccessPath-TS3 Model 531 system is provided in the
Cisco AccessPath-TS3 Model 531 Integrated Access System Hardware Scaling and Configuration Guide.


Figure A-1 on the following page shows the general troubleshooting strategy described in this appendix. Follow the steps presented in Figure A-1 to isolate problems to a specific subsystem and to resolve the problem.


Figure A-1   Troubleshooting Strategy for Startup Problems


If you are unable to easily solve the problem, contact a customer service representative for assistance and further instructions. Refer to the section "Contacting Customer Service," at the end of this appendix for more information on contacting customer service.

Cisco AccessPath-TS3 Model 531 Integrated Access System LED Diagrams

To troubleshoot the Cisco AccessPath-TS3 Model 531 system, you should know the significance of each of the LEDs on its shelves.

Figure A-2 through Figure A-4 show the location of the power OK LED on each of the shelves. At initial startup, the OK LEDs should flash on. After all devices have initialized, the LEDs should remain on. This indicates that each shelf is functioning properly.

Access Server Shelf LEDs

The LEDs indicate the current operating condition of the Access Server Shelves. You can observe the LEDs, note any fault condition that the product is encountering, and then contact your system administrator or a customer service representative, if necessary.


Figure A-2   
Access Server Shelf T1 PRI Card Panel LEDs

Figure A-3   Access Server Shelf E1 PRI Card Panel LEDs



Figure A-4   Access Server Shelf 12-Port Modem Card LEDs


Table A-1   LED States

Chassis/Card LED State Description

Access Server Shelf chassis

Alarm

On

Alarm error has been detected.

AUI

Flickering

Off

Ethernet LAN connection is transmitting and receiving data normally.

Ethernet LAN connection is not transmitting or receiving data. Check the Ethernet cable connections.

Serial

Flickering

Associated serial port connection is transmitting and receiving data normally.

System Status (Located to the right of the Console/Auxiliary ports)

Off

On

Blinking

Power is off or system has not booted.

System is operating normally.

Memory failure has occurred.

Quad T1 PRI1 card

Activity

Flickering

CSU/DSU2 in the card is communicating with a remote CSU/DSU.

Board OK

On

T1 PRI card has passed initial power-up diagnostics tests and is operating normally.

Loopback

On

Local or remote loopback diagnostic test is running on the associated T1 port.

Remote Alarm

On

Remote AIS has been received on the associated T1 port. The AIS3 is received on LOS4.

Local Alarm

On

Associated T1 port has detected local LOS or OOF5 errors.

Quad E1 PRI card

Activity

Flickering

CSU/DSU in the card is communicating with a remote CSU/DSU.

Board OK

On

E1 PRI card has passed initial power-up diagnostics tests and is operating normally.

Loopback

On

Local or remote loopback diagnostic test is running on the associated E1 port.

120

On

Port is configured for 120-ohm line termination.

Remote Alarm

On

Remote AIS has been received on the associated E1 port. The AIS is received on LOS.

Local Alarm

On

The associated E1 port has detected local LOS or OOF errors.

12-Port Modem card

ACT (Activity)

Flickering

Modem card is processing transmit, receive, and modem interrupts normally.

OK (Board OK)

On

Off

Modem card has passed the initial power-up diagnostic tests and is operating normally.

Fault condition is present on the card.

1PRI = Primary Rate Interface.

2CSU/DSU = channel service unit/data service unit.

3AIS = alarm indication signal.

4LOS = loss of signal.

5OOF = out of frame.

Troubleshooting Overview

This section describes the troubleshooting methods used in this appendix and describes how the Cisco AccessPath-TS3 Model 531 system shelves are divided into subsystems for more efficient problem solving. Each of the recommendations and procedures below applies to all of the shelves in the Cisco AccessPath-TS3 Model 531 system unless indicated otherwise.

Problem Solving to the System-Component Level

The key to solving problems with the system is to isolate the problem to a specific system component or subsystem. Because startup problems can usually be attributed to a single component, it is more efficient to isolate the problem to a subsystem rather than troubleshoot each separate component in the system.

The Cisco AccessPath-TS3 Model 531 system shelves each consist of the following subsystems:

You should be able to hear the fan assembly to determine whether or not it is operating.

There are no installation adjustments that you can make if the fan assembly does not function properly at initial startup. Replace the fan tray if you determine a fan is not functioning properly.

The following recommendation is for the Switch Shelf only. If the fan LED is orange and you determine that the fan assembly is not operating, you should immediately contact a customer service representative.


Note A port adapter that is partially installed in the midplane can cause the system to hang and crash.


The following sections will help you isolate a problem to 1 of these subsystems and direct you to the appropriate troubleshooting section.

Identifying Startup Problems

Startup problems might occur because of the source power or a board (network processing engine, I/O controller, or port 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.

With the exception of the fan tray and network processing 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, then proceed to the appropriate sections to try to resolve the problem.

LEDs indicate the status of all components (except for the system fan assembly) during the system startup sequence. By checking these LEDs, you can determine when and where the system failed.

When you start up the system by turning ON the power supply switch(es), the following should occur:

1. At initial startup, the Power OK LEDs on each of the shelves should flash. After all devices have initialized, the Power OK LEDs should remain on. Refer to Figure A-5 through Figure A-8 for the location of the Power OK LED on each of the shelves.


Figure A-5   System Controller System LED



Figure A-6   Access Server Shelf Power OK LED



Figure A-7   Router Shelf I/O Power OK LED



Figure A-8   Switch Shelf Power LED


2. You should immediately hear the fans operating. They should be operating whenever system power is on.

If the fan assembly is not operating, proceed to the section "Troubleshooting the Cooling Subsystem". If you determine that the power supplies are functioning normally but the fan LED on the supervisor engine module is orange and the fan assembly is not operating, contact a customer service representative. Do not attempt to make any adjustments to the fan assembly. If a fan does not function properly at initial startup, there are no installation adjustments that you should make.

3. The power supply LEDs (for example, on the Switch Shelf, the PS1 or PS2 LEDs on the left side of the supervisor engine module faceplate) should all turn green immediately when you turn on the power supply switch. They should remain green during normal system operation.

If any of the power supply LEDs do not go on, proceed to the section, "Troubleshooting the Power Subsystem".

4. (Switch Shelf). The LEDs on the supervisor engine module should go on as follows:

If any LEDs on the supervisor engine module faceplate are orange or red, proceed to the section "System-Level Troubleshooting Suggestions".

5. (Switch Shelf) only. The status LED on each switching module should turn green when the supervisor engine module completes initialization. This LED indicates that the switching modules are receiving power, have been recognized by the supervisor engine module, and contain a valid Flashcode version. However, it does not indicate the state of the individual interfaces on the switching modules. If a switching module Status LED is orange or red, proceed to the section "System-Level Troubleshooting Suggestions" section.

6. The boot information and system banner should now be displayed. If they are not, refer to the section "Connecting the Console Port" in the chapter "Installing the Switch" in the Catalyst 5000 Series Hardware Installation and Maintenance Guide to verify that the terminal is set correctly and that it is properly connected to the supervisor engine module console port.

7. The LEDs on the I/O controller should go on as follows:

If this LED remains off when starting the router, either there is a problem with the power supply (it is damaged or not connected to the router midplane), or the network processing engine or I/O controller are not connected to the router midplane. Proceed to the section "Troubleshooting the I/O Controller".

If this LED remains off when starting the router, it is probably a problem with the network processing engine or the I/O controller (they are damaged or not connected to the router midplane). Proceed to the section "Troubleshooting the I/O Controller".

If this LED remains off when starting the router, it is probably a Fast Ethernet port problem on the I/O controller. Proceed to the section "Troubleshooting the I/O Controller," later in this appendix.

8. The enabled LED on each port adapter goes on when the network processing engine completes its initialization of the port adapter for operation. The enabled LED indicates that the port adapter is receiving power and has been recognized by the network processing engine; it does not indicate the state of the individual interfaces on the port adapters. If an enabled LED fails to go on, proceed to the section "Troubleshooting the Port Adapters".

9. When all LEDs go on to indicate that the system has booted successfully, the initial system banner should be displayed on the console screen. If it is not displayed, refer to the section "Console and Auxiliary Port Connection Equipment" in the chapter "Installing the Cisco 7206" in the Cisco 7206 Installation and Configuration Guide to verify that the terminal is set correctly and that it is properly connected to the I/O controller's console port.

Troubleshooting the Power Subsystem

Check the following to isolate a power subsystem problem.


Note      The numbers of power supplies and LEDs will vary depending upon the individual device.



Step 1   Check the power supply LEDs. Is at least 1 power supply LED ON for each shelf?

    (a). (Router Shelf Only) Make sure the power supply is flush with the back of the chassis. Check the clips that lock the cords into place.

    (b). Make sure the power cable is connected at both ends.

    (c). If both power LEDs were on previously and the power supply was operating, turn OFF the power switch, wait for the supply to cool, and turn the switch back ON. If the power supply LEDs remain off, there might be a problem with the input source or the power cable.

    (d). Turn OFF the power to the switch, connect the power cord to another power source if one is available, and turn the power back ON. If the LED(s) then go on, the problem is the original power source.

    (e). If the LED(s) fail to go on after you connect the power supply to a new power source, replace the power cord and then turn the switch back ON.

    (f). If the LED(s) go on, return the original power cord for replacement. If they do not go on, repeat this step for the second (redundant) power supply cord.

    (g). If the LED(s) still fail to go on when the switch is connected to a different power source using a new power cord, the power supply is probably faulty.

    (h). 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 2   Check the OK or PS LED for the redundant power supply. Is it on?

If you are unable to resolve the problem or if you determine that either a power supply or chassis connector is faulty, contact a customer service representative. See the section "Contacting Customer Service" at the end of this appendix.

Troubleshooting the Processor Subsystem (Router Shelf Only)

The processor subsystem of the Router Shelf comprises the I/O controller, network processing engine, and all port adapters.

The I/O controller and network processing engine are required system components. The system cannot operate unless the I/O controller and network processing 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 will send incomplete signals to the processor, which will fault the PCI bus and cause the system to hang.

Therefore, first ensure that the I/O controller and the network processing engine are installed properly and the system software has initialized successfully. Then, if necessary, you can troubleshoot individual port adapters.

Troubleshooting the I/O Controller

These procedures assume that the I/O controller, network processing 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 (refer to the section "Identifying Startup Problems". Check the following items to help isolate the problem:

Troubleshooting the Network Processing Engine

These procedures assume that the I/O controller, network processing 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 enabled LED does not go on as expected, make sure the power to the router is turned OFF, reseat the network processing 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.

Troubleshooting the Port Adapters

Check the following to help isolate a problem with the port adapters:

If yes, the system is operational.

Troubleshooting the Cooling Subsystem

Check the following items to help isolate a problem with the cooling subsystem (fan assembly):

1. When you start up the system, do the fans start operating?

2. The following message, if displayed, indicates that the system has detected an overtemperature condition or out-of-tolerance power inside the chassis:

3. (Switch Shelf only.) Check the fan LED on the supervisor engine module. Is it green?

To ensure that the fan assembly is seated properly, first remove and reinstall it and then restart the system. See the section "Replacing the Chassis Fan Assembly" in the chapter, "Replacing Chassis Components" in the Catalyst 5000 Series Hardware Installation and Maintenance Guide.

4. Check the fan LED again. Is it still orange?

If yes, the system has detected a fan assembly failure.

If you experience trouble with the startup that is not resolved with these procedures, contact a service representative for assistance and further instructions.

Troubleshooting Modules (Switch Shelf Only)

Check the following items to help isolate a supervisor engine module or switching module problem:

Reseat the module until both ejector levers are at a 90-degree orientation to the rear of the chassis. (For a description and illustration of the ejector levers, refer to "Installing and Configuring Switching Modules" in the chapter, "Maintaining the Catalyst 5000 Series Switch" in the publication Catalyst 5000 Series Hardware Installation and Maintenance.) Tighten the captive installation screws at the left and right of the module faceplate, and restart the system.

If you still experience trouble with the startup, contact a customer service representative for assistance.

System-Level Troubleshooting Suggestions

Use the following suggestions to assist in isolating or solving a system problem:

Contacting Customer Service

If you are unable to solve a startup problem after using the troubleshooting suggestions in this appendix, check the online documentation available on the World Wide Web. (For more information, see the section "Related and Referenced Documents" in the preface "About This Guide.")

If you are still unable to resolve a startup problem, contact a customer service representative for assistance and further instructions. Before you call, have the following information ready to help your customer service representative assist you as quickly as possible:


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Jan 20 21:54:12 PST 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.