|
|
This chapter provides general information for troubleshooting hardware faults during installation of the Cisco 6400 universal access concentrator (UAC). For information about troubleshooting the software, refer to the Cisco 6400 UAC Software Configuration Guide.
This chapter includes the following sections:
If you encounter a problem after you have installed the Cisco 6400, you should perform a few basic troubleshooting procedures on your equipment before contacting customer service. These simple checks involve answering the following questions:
You should refer to the following materials:
Table 4-1 lists tools and test equipment that you should have to perform general maintenance and troubleshooting tasks on the Cisco 6400.
| Equipment Item | Description |
|---|---|
Number 2 Phillips and flathead screwdrivers | Small and medium sized |
Voltage tester |
|
Optical fiber test equipment |
|
Figure 4-1 is a flowchart to help you determine which component of your Cisco 6400 UAC may have malfunctioned. The decimal numbers in the following figure refer to the sections in this chapter where the various system elements are discussed.
If an error is detected during a system powerup or hardware reset, the red NSP STATUS LED lights. The watchdog timer or software warm-start functions may run minimum diagnostics.
If any failures occur during the power-on sequence, forward a copy of the output to the technical assistance center (TAC) for diagnosis.
Use the show hardware command to display the hardware components installed. These components can include:
The following example shows output from the show hardware command:
Switch# show hardware 6400 named santa-2a-16, Date: 23:29:23 UTC Tue Jan 4 2000 Feature Card's FPGA Download Version: 0 Slot Ctrlr-Type Part No. Rev Ser No Mfg Date RMA No. Hw Vrs Tst EEP ---- ------------ ---------- -- -------- --------- -------- ------- --- --- 8/0 155SM NLC 73-2890-02 02 09691183 Jul 20 98 00-00-00 1.0 0 2 1/1 155SM NLC 73-2892-02 02 09591457 Jul 20 98 00-00-00 1.0 0 2 0/0 CPU card 73-2996-02 02 09165973 Jul 20 98 00-00-00 2.0 0 2 0/1 FC-PFQ 73-2281-04 A0 08783319 Apr 25 98 00-00-00 4.1 0 2 DS1201 Backplane EEPROM: Model Ver. Serial MAC-Address MAC-Size RMA RMA-Number MFG-Date ------- ---- -------- ------------ -------- --- ---------- ----------- C6400 2 100001 00107BA9C600 128 0 0 Jul 20 1998
Use the show version and show environment commands to display the following Cisco 6400 information:
The following example shows output of the show version command:
switch# show version Cisco Internetwork Operating System Software IOS (tm) PNNI Software (6400-WP-M), Version XX.X(X), RELEASE SOFTWARE (fc1) Copyright (c) 1986-1998 by cisco Systems, Inc. Compiled Tue 07-Oct-97 04:53 by Image text-base: 0x60010910, data-base: 0x604E6000 ROM: System Bootstrap, Version XX.X(X.X.WAX.0) [integ 1.4.WAX.0], RELEASE SOFTWARE Switch uptime is 2 weeks, 2 days, 39 minutes System restarted by power-on System image file is "bootflash:6400-wp-mz.112-8.0.1.FWA4.0.16", booted via bootflash cisco NSP (R4700) processor with 65536K bytes of memory. R4700 processor, Implementation 33, Revision 1.0 Last reset from power-on 1 Ethernet/IEEE 802.3 interface(s) 20 ATM network interface(s) 123K bytes of non-volatile configuration memory. 8192K bytes of Flash internal SIMM (Sector size 256K). Configuration register is 0x2101 switch#
The following example shows output of the show environment command:
switch# show environment Temperature normal:chassis inlet measured at 27C/80F Temperature normal:chassis core measured at 33C/91F Fan: OK Power Entry Module 0 status: OK switch#
Configuration problems generally develop when the system is first installed, when the system configuration is changed, or when new equipment is added to the network and is not configured properly.
You should carefully review the port configuration information contained in your site log records, and verify that the physical equipment configuration matches the internal software configuration. By reviewing the port configuration information, you can determine whether any changes are needed to equipment and cabling in the central office or outside plant facilities.
Electrical problems are divided into two categories:
Site electrical problems can include:
Cisco 6400 electrical problems can be caused by:
The Cisco 6400 powers down when the temperature exceeds a specified threshold. If that happens, you should identify and correct the cause of the overheating before repowering the system.
If the blower module is unplugged for 2 minutes, the Cisco 6400 powers down automatically.
Signal input and output problems can occur at any point in the network and can be caused by mechanical defects in the cables, poor connections, or lack of signal caused by other equipment failures.
Refer to your site log and other facility records to check signal connections for your facility.
The ping command can be used to confirm network connections between the switch and another node on the network. The ping command sends Internet Control Message Protocol (ICMP) echo request packets out, and receives a confirmation if the connection is good. The ping command format is:
ping host [packet_size] [packet_count]
An optical signal I/O problem can be caused by:
The power budget (PB) is the maximum possible amount of power transmitted. The following equation shows the calculation of the power budget:
PB = PTmin - PRmin
Where:
PTmin = Minimum transmitter power
PRmin = Minimum receiver sensitivity
Insufficient power budget occurs when the power margin (PM) is less than 0. PM is equal to the power budget minus the link loss (LL).
PM = PB - LL
Three factors contribute to link loss:
Receiver overload can occur when (PRmax - (PTmax - LL)) is less than 0, where PRmax is maximum receiver power and PTmax is maximum transmitter power. To prevent overloading the receiver, you can use an attenuator on the link between any single-mode SONET transmitter and the receiver. Doing so should increase the value of LL.
If an Ethernet connection on your Cisco 6400 fails to work properly, and the corresponding LNK (Link) LED is not lit (steady green), check for the following problems:
If the LNK LED is lit (steady green), but the Ethernet port does not seem to be working properly, make sure that the port in question is configured properly and is not administratively shut down. If you have a working console connection, perform the following steps:
Step 1 At the switch prompt, enter show int ether0/0/0. If the port is administratively down, enter these commands to enable it:
switch> configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config-if)# int eth0/0/0 switch(config-if)# no shut switch(config-if)# exit switch(config)# exit switch#
Step 2 Check that the Ethernet port in question has a valid IP address assigned to it.
For more information about configuring Ethernet ports, refer to the Cisco 6400 UAC Software Configuration Guide.
If the cable, connections, power, and configuration all check out, and you still cannot connect to the Ethernet port on the module, replace the module in question. If the problem persists, contact Cisco's TAC for further assistance. See "Cisco Connection Online" section
If the console screen connected to a Cisco 6400 console port appears frozen or fails to work properly, check for the following problems:
Information about the Cisco 6400 field-replaceable units (FRUs) is given in the following sections:
All Cisco 6400 FRUs are hotswappable. Procedures for removing and replacing the FRUs can be found in the Cisco 6400 UAC FRU Installation and Replacement.
Table 4-2 lists general FRU fault symptoms and recommendations.
| Symptom | Steps to Take | ||||||||
|---|---|---|---|---|---|---|---|---|---|
System fails to come up. |
| ||||||||
System experiences a critical alarm. (Critical LED on NSP lights yellow.) | Enter the show facility-alarm status command at the console. | ||||||||
System experiences a major alarm. (Major LED on NSP lights yellow.) | Enter the show facility-alarm status command at the console. | ||||||||
System experiences a minor alarm. (Minor LED on NSP lights yellow.) | Enter the show facility-alarm status command at the console. | ||||||||
You cannot establish a console or Telnet connection to the system. | For information about troubleshooting Ethernet connections, refer to the section, "Ethernet Connections." For information about troubleshooting the console port serial connections, refer to the section, "Console Port Serial Connections." | ||||||||
System overheats. | Troubleshoot the blower module (see Table 4-12). | ||||||||
System experiences a power problem. | Troubleshoot the PEM(s), referring to the PEM section of this table and to Table 4-14 (DC PEM) and Table 4-16 (AC PEM). |
Figure 4-2 shows the NSP indicators and connectors on the faceplate.
Table 4-3 describes the LEDs on the NSP faceplate.
| LED | Status | Condition |
|---|---|---|
STATUS | Steady yellow | Cisco IOS is not running. |
FAIL | Yellow | NSP has failed. |
ETH ACT (Activity) LNK (Link) |
Green Steady green |
Packets are being transmitted and received. Port is operational. |
PCMCIA Slot 0 PCMCIA Slot 1 | Steady green Steady green | Slot is active. Slot is active. |
ALARMS CRITICAL MAJOR |
Yellow Yellow Yellow |
Alarm is active. |
Table 4-4 lists the NSP fault indications and recommended actions.
| Symptom | Steps to Take | ||||||||||
STATUS LED is not lit. |
| ||||||||||
FAIL LED is yellow, indicating that the NSP failed. | Reinsert the NSP. If the problem persists, contact Cisco's TAC. | ||||||||||
The NSP comes up, but you cannot establish a console or Telnet connection to the system. |
switch> configure terminal Enter configuration commands, one per line. End with CNTL/Z. switch(config-if)# int eth0/0/0 switch(config-if)# no shut switch(config-if)# exit switch(config)# exit switch#
| ||||||||||
Card cannot be fully inserted into its slot. | Ensure that you are using slot 0A or 0B for the NSP module. |
Figure 4-3 shows the NRP indicators and connectors on the faceplate.
Table 4-5 describes the LEDs on the NRP faceplate.
| LED | Status | Condition |
|---|---|---|
STATUS | Steady green | NRP is active (primary). |
FAIL | Steady yellow | NRP has failed. |
ETH ACT (Activity) LNK (Link) |
Blinking green Steady green |
Packets are being transmitted and received. Port is operational. |
FE ACT (Activity) LNK (Link) |
Blinking green Steady green |
Packets are being transmitted and received. Port is operational. |
Table 4-6 lists the NRP module fault indications and recommended actions.
| Symptom | Steps to Take | ||||||
STATUS LED is not lit. |
| ||||||
FAIL LED is yellow, indicating that the NRP failed. | Reinsert the NRP. If the problem persists, contact Cisco's TAC. | ||||||
Module cannot be fully inserted into its slot. | Inspect connectors on both the card and the backplane, looking for bent pins or other damage. Use slots 1 to 8 (slots 0A and 0B are reserved for NSP modules). | ||||||
Module experiences problems in one slot but operates normally in another. | Contact Cisco's TAC. |
Figure 4-4 shows the OC3/STM-1 NLC indicators and connectors on the faceplate.
 | Warning
Class 1 laser product. |
| Warning
Invisible laser radiation present. |
| Warning Because invisible radiation may be emitted from the aperture of the port when no fiber cable is connected, avoid exposure to radiation and do not stare into open apertures. |
| Warning Alleviates ja suojalukitus ohitettaessa olet alttiina nãkymãttõmãlle lasersãteilylle. Ãjã katso sãteeseen. |
| Warning Osynlig laserstrålning när denna del är öppen och förregleringen är urkopplad. Rikta inte blicken in mot strålen. |
Figure 4-5 shows the DS3 NLC indicators and connectors on the faceplate.
Table 4-7 describes the LEDs on the OC-3/STM-1 and DS3 NLC faceplates.
| LED | Status | Condition |
|---|---|---|
FAIL | Steady yellow | OC-3/STM-1 NLC failed |
PORT 0 TX (transmit)
STATUS | Green Green
Green | Transmit activity
Active (primary) |
PORT 1 TX (transmit) RX (receive)
STATUS | Green
Green
Steady green | Transmit activity
Receive activity.
Active |
Table 4-8 lists the OC-3/STM-1 and DS3 NLC fault indications and recommended actions.
| Symptom | Steps to Take | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
STATUS LED is not lit. |
| ||||||||||||||
FAIL LED is lit. |
| ||||||||||||||
Interface fails to come up. |
| ||||||||||||||
Card cannot be fully inserted into its slot. |
|
Figure 4-6 shows the OC12/STM-4 NLC indicators and connectors on the faceplate.
| Warning Class 1 laser product. |
| Warning Because invisible radiation may be emitted from the aperture of the port when no fiber cable is connected, avoid exposure to radiation and do not stare into open apertures. |
| Warning Invisible laser radiation present. |
| Warning Alleviates ja suojalukitus ohitettaessa olet alttiina nãkymãttõmãlle lasersãteilylle. Ãjã katso sãteeseen. |
| Warning Osynlig laserstrålning när denna del är öppen och förregleringen är urkopplad. Rikta inte blicken in mot strålen. |
Table 4-9 describes the LEDs on the OC-12/STM-4 NLC faceplate.
| LED | Status | Condition |
|---|---|---|
FAIL | Steady yellow | OC-12/STM-4 NLC failed |
TX (transmit) RX (receive)
STATUS | Green
Green
Green | Transmit activity
Receive activity
Active (primary) |
Table 4-10 lists the OC-12/STM-4 NLC fault indications and recommended actions.
| Symptom | Steps to Take | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
STATUS LED is not lit. |
| ||||||||||||||
FAIL LED is lit. |
| ||||||||||||||
Interface fails to come up. |
| ||||||||||||||
Card cannot be fully inserted into its slot. |
|
Figure 4-7 shows the blower module front panel and its indicators.
Table 4-11 describes the blower module LEDs located on the front center panel.
| LED | Status | Condition |
|---|---|---|
Steady green | Fans are operational. | |
SINGLE FAN FAILURE | Steady yellow | Failure has occurred and alarms are triggered. |
MULTI-FAN FAILURE | Steady yellow | Redundant fan has failed and the system will shut down. |
Table 4-12 lists the blower module fault indications and recommended action.
| Symptom | Steps to Take | ||||||||||
Green LED on blower module fails to go on. |
| ||||||||||
|
Figure 4-8 shows the DC PEM and its indicators.
Table 4-13 describes the DC PEM LEDs located on the bottom front panel.
| LED | Status | Condition |
|---|---|---|
POWER | Steady green | Power is available. |
FAULT | Steady yellow | The PEM has failed or is turned off. |
MISWIRE | Steady yellow | Cables are wired incorrectly and should be reversed. |
Table 4-14 lists the DC PEM fault indications and recommended actions.
| Symptom | Steps to Take | ||||||||||
Green LED on PEM fails to go on. |
| ||||||||||
PEM experiences problems in one slot but operates normally in the other. |
| ||||||||||
Figure 4-9 shows the AC PEM and its indicators.
Table 4-15 describes the AC PEM LEDs located on the bottom front panel.
| LED | Status | Condition |
|---|---|---|
POWER | Steady green | Power is available. |
FAULT | Steady yellow | The PEM has failed or is turned off. |
Table 4-16 lists the AC PEM fault indications and recommended actions.
| Symptom | Steps to Take | ||||||||||
Green LED on PEM fails to go on. |
| ||||||||||
PEM experiences problems with one cable but operates normally with the other. |
| ||||||||||
Posted: Mon Nov 22 18:32:35 PST 1999
Copyright 1989-1999©Cisco Systems Inc.