|
|
This appendix contains procedures for troubleshooting the Cisco AccessPath-VS3 Packet Telephony Concentrator hardware installation.
Your Cisco AccessPath-VS3 was tested extensively 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.
This appendix covers only hardware troubleshooting. For software troubleshooting information, refer to the Cisco AccessPath-VS3 Packet Telephony Concentrator Software Configuration Guide, which is available on the Cisco Documentation CD-ROM and the World Wide Web at:
http://www.cisco.com/univercd/cc/td/doc/product/access/ap/apvs3/vs3_sw/configs/index.htm
After the initial system boot is complete, verify the following:
1. Power supplies are installed properly and are supplying power to the system. Check that your power supplies are functioning correctly before power-on.
2. System fan assembly is operating.
3. System software boots successfully.
4. Supervisor engine module and all switching modules are properly installed in their slots, and each initialized without problems.
If any of these conditions are not met, use the procedures in this appendix to isolate and, if possible, resolve the problem.
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-VS3 Packet Telephony Concentrator Software Configuration Guide and the other documentation that shipped with your Cisco AccessPath-VS3 to troubleshoot the software.
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.
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" section, for more information on contacting customer service.
This section explains the meaning of the Cisco AccessPath-VS3 LEDs output.
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.
The LEDs indicate the current operating condition of the VoIP 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.
| Chassis/Card | LED | State | Description |
|---|---|---|---|
VoIP Access Server Shelf | 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 | 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. |
This section describes the troubleshooting methods outlined in this appendix and explains how to divide the Cisco AccessPath-VS3 shelves into subsystems for more efficient problem solving. Each of the recommendations and procedures below applies to all of the shelves in the Cisco AccessPath-VS3 unless otherwise indicated.
One 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-VS3 shelves each consist of the following subsystems:
 | Caution 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.
Startup problems might occur because either the source power or a board (network processing engine, I/O controller, or port adapter) is dislodged from the midplane. Although overheating 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 if and where the system fails in the startup sequence. Use the following descriptions to isolate the problem to a subsystem, then proceed to the appropriate sections to resolve the problem.
When you start up the system by toggling ON the power supply switch(es), the following should happen:
(a) The status LED should flash orange once and then stay orange during diagnostic boot tests. It should turn green as soon as the module is operational (online). If the system software does not start up, this LED will remain orange.
(b) Each link LED associated with a port should flash orange once and then stay orange during diagnostic boot tests. The link will turn green when its associated port is operational (online). If no signal is detected, it turns dark. The link LED blinks orange if its associated port is bad.
(c) The fan LED should always remain green. This LED lights orange only if the system detects a fan failure.
If any LEDs on the supervisor engine module faceplate are orange or red, proceed to the section "System-Level Troubleshooting Suggestions".
(a) The I/O power OK LED lights immediately and indicates that the I/O controller is receiving DC power from the Router shelf midplane. This LED lights during a successful router shelf boot and remains lit during normal operation of the router shelf.
If this LED remains dark after you start the Router shelf, either there is a problem with the power supply, or either the network processing engine or I/O controller is not connected to the router shelf midplane. Proceed to the section "Troubleshooting the I/O Controller".
(b) The enabled LED lights to indicate that the network processing engine and the I/O controller are enabled for operation by the system. It does not mean that the Fast Ethernet port on the I/O controller is functional or enabled. This LED lights during a successful Router shelf boot and remains on during normal operation of the router shelf.
If this LED remains off after starting the Router shelf, it is probably a problem with the network processing engine or the I/O controller. Proceed to the section "Troubleshooting the I/O Controller".
(c) The FE enabled LED lights to indicate that the Fast Ethernet port on the I/O controller is initialized and enabled for operation by the system. This LED lights during a successful Router shelf boot and remains on during normal operation of the router shelf.
If this LED remains off after you start the Router shelf, it indicates a Fast Ethernet port problem on the I/O controller. Proceed to the "Troubleshooting the I/O Controller" section.
(d) The FE link LED lights to indicate that the Fast Ethernet port on the I/O controller received a carrier signal from the network. This LED remains off during normal operation of the Router shelf unless there is an incoming carrier signal, and does not indicate startup problems.
(e) The slot 1 and slot 2 LEDs lights to indicate which Personal Computer Memory Card International Association (PCMCIA) slot is in use. During a successful Router shelf boot, these LEDs light and remain on if a Flash memory card is present in the slot. These LEDs also blink while either slot is being accessed by the system. These LEDs do not indicate startup problems.
Check the following to isolate a power subsystem problem:
Step 1 Check the power supply LEDs. Is at least 1 power supply LED ON for each shelf?
(a) Router Shelf Only—Confirm that the power supply is flush with the back of the cabinet. Check the clips that lock the cords into place.
(b) Confirm that the power cable is connected at both ends.
(c) If both power LEDs were on previously and the power supply was operating, toggle OFF the power switch, wait for the supply to cool, then toggle 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) Toggle OFF the power to the switch, connect the power cord to another power source, then toggle 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 light after you connect the power supply to a new power source, replace the power cord and then toggle the switch back ON.
(f) If the LED(s) light, return the original power cord for replacement. If they do not light, repeat this step for the second (redundant) power supply cord.
(g) If the LED(s) still fail to light after 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.
If you are unable to resolve the problem, or if you determine that either a power supply or cabinet connector is faulty, contact a customer service representative. See the section "Contacting Customer Service" section.
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 if 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.
These procedures assume that the I/O controller, network processing engine, and Router shelf 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 light up as they should, refer to the section "Identifying Startup Problems". Check the following items to help isolate the problem:
These procedures assume that the I/O controller, network processing engine, and Router shelf 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 light as expected, confirm the power to the Router shelf is toggled OFF, reseat the network processing engine in its slot, and restart the router shelf.
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 options to determine if every enabled LED on every port adapter is lit:
Step 1 If the enabled LED on an individual port adapter is dark, try reseating the port adapter in its slot. You do not have to turn off the system power while removing or replacing port adapters. After the system reinitializes the interfaces, the enabled LED on the port adapter should light.
Step 2 If the enabled LED remains dark, the system detected a processor hardware failure. Contact a service representative for instructions.
Check the following items to help isolate a problem with the cooling subsystem (fan assembly):
Queued messages:
%ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdown
Check the following items to help isolate a supervisor engine module or switching module problem:
Step 1 Is every status LED on?
Step 2 If any supervisor engine or switching module status LED lights red, the module might be useated. Reseat the module so that both ejector levers are at 90-degrees to the rear of the chassis. Tighten the captive screws in the left and right of the module faceplate, and restart the system.
If the status LED on a switching module is red, the module might be busy or disabled. Refer to the Catalyst 5000 Series Software Configuration Guide and the Catalyst 5000 Series Command Reference publication to configure or enable the interfaces. After the system reinitializes the interfaces, the status LED on the module should light green.
Step 3 If you still experience trouble with the startup, contact a customer service representative for assistance.
Use the following list to isolate or solve a startup problem:
If there is a problem with the system software, check the status of the supervisor engine module, which contains the system operating software.
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 "Cisco Connection Online" section.
If you are still unable to resolve a startup problem, contact a customer service representative for assistance. Before you call, have the following information ready to help your customer service representative assist you as quickly as possible:
You are then prepared to reference the following section "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.
Posted: Mon Oct 2 13:25:02 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.