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

Table of Contents

Troubleshooting the Cisco AccessPath-TS3 Model 530 Integrated Access System
Cisco AccessPath-TS3 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)
Troubleshooting Suggestions
Contacting Customer Service
Cisco Connection Online

Troubleshooting the Cisco AccessPath-TS3 Model 530 Integrated Access System


This appendix contains procedures for troubleshooting the Cisco AccessPath-TS3 Model 530 Integrated Access System hardware installation. If you need more information, refer to the section "Related and Referenced Documents" in the preface "About This Guide."

Your AccessPath-TS3 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 included because they also pertain to DC line voltages.


Note      This appendix covers only hardware troubleshooting. For more information, see the documents Cisco AccessPath-TS3 Integrated Access System Software Configuration Guide and Cisco AccessPath Manager 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 Integrated Access System Software Configuration Guide and the other documentation that shipped with your AccessPath-TS3 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 maintaining and scaling the AccessPath-TS3 system is provided in the appendix "Maintaining and Scaling the Cisco AccessPath-TS3 Model 530 Integrated Access System." Information on cabling specifications for the AccessPath-TS3 system is provided in the appendix "Cabling Specifications for the Cisco AccessPath-TS3 Model 530 Integrated Access System."


Figure A-1 shows the general troubleshooting strategy described in this appendix. Refer to this figure, as necessary, to follow the steps for isolating problems to a specific subsystem; then resolve the problem if possible.


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.

Cisco AccessPath-TS3 Integrated Access System LED Diagrams

In order to troubleshoot the AccessPath-TS3 system, you should know the significance of each of the LEDs on its shelves.

The location of the power OK LED on each shelf is shown in Figure A-2 through Figure A-4. At initial startup, the OK LEDs should flash on. After all devices have initialized, the LEDs should remain on. If the LEDs are on, 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, 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 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.

Dual 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.

Dual 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. Also known as a network terminating unit in Europe.

3AIS = alarm indication signal.

4LOS = loss of signal

5OOF = out of frame.

Troubleshooting Overview

This section describes the troubleshooting methods that you can use and shows how the AccessPath-TS3 system shelves are divided into subsystems for more efficient problem solving. Each of the recommendations and procedures that follow applies to all of the shelves in the AccessPath-TS3 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 AccessPath-TS3 system consists 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.

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

Identifying Startup Problems

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

Except for the fan tray and network processing engine, LEDs indicate the state of each system 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.

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

1. At initial startup, the Power OK LED(s) on each of the shelves should flash. After all devices have initialized, the Power OK LED 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 Supply OK LED


2. You should immediately hear the fans operating. They should operate 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 should all turn green immediately when you turn on the power supply switch. This is true, for example, of the PS1 and PS2 LEDs on the supervisor engine module faceplate on the switch shelf. 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 Only). 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 "Troubleshooting Suggestions" later in this appendix.

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 module is receiving power, has been recognized by the supervisor engine module, and contains a valid Flashcode version. However, it does not indicate the state of the individual interfaces on the switching module. If a switching module Status LED is orange or red, proceed to the section "Troubleshooting Suggestions" later in this appendix.

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 you start 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 the I/O controller is not connected to the router midplane. Proceed to the section "Troubleshooting the I/O Controller," later in this appendix.

If this LED remains off when you start the router, there 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," later in this appendix.

If this LED remains off when you start the router, there is probably a problem with the Fast Ethernet port 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. 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 adapter. If an enabled LED fails to go on, proceed to the section "Troubleshooting the Port Adapters" later in this appendix.

9. When all LEDs go on, indicating 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:


Step 1   Check the power supply LEDs. Is at least one power supply LEDs on for each shelf?

    (a). On the Switch Shelf, make sure the power supply is flush with the back of the chassis. Tighten the captive installation screws.

    (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 power 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 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 with a new power cord, the power supply is probably faulty. Contact customer service to order a replacement power supply

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 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 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 are installed properly and the system software has initialized successfully. Then, if necessary, you can troubleshoot individual port adapters.

Troubleshooting the I/O Controller

In these procedures it is assumed 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" earlier in this appendix), check the following items to help isolate the problem:

Troubleshooting the Network Processing Engine

In these procedures, it is assumed 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. 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?

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.

2. If the following message is displayed, 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. (Refer to the section "Troubleshooting the Power Subsystem" earlier in this appendix.) 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 into it. Refer to the section "Preventive Site Configuration: Maintaining Normal Operation" in the Cisco 7206 Installation and Configuration Guide.

The preceding 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. (Refer to the section "Functional Overview" in the chapter "Product Overview" in the Cisco 7206 Installation and Configuration Guide for descriptions of the show environment and show environment table commands.)

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. Contact a customer service representative for instructions.

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 problem with the supervisor engine module or switching module:

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 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.

Troubleshooting Suggestions

Use the following suggestions to help you isolate or solve a system problem:

1. To solve startup problems, check for the following:

2. If you have trouble with the system software, check the status of the supervisor engine module, which contains the system operating software.

Contacting Customer Service

If you still cannot 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 sections "Related and Referenced Documents" in the chapter "About This Guide.")

If you still cannot solve a startup problem, refer to Cisco Connection Online below.

Cisco Connection Online

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.


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