Table of Contents

Troubleshooting the Installation

Troubleshooting the Installation

This chapter provides general information for troubleshooting hardware faults during installation of the Cisco 6400 carrier-class broadband aggregator. For information about troubleshooting the software, refer to the Cisco 6400 Software Setup Guide.

This chapter includes the following sections:

• General Troubleshooting Information
  
  
• Troubleshooting Flowchart
  
  
• General System Diagnostics
  
  
• Electrical Problems
  
  
• Signal Input/Output Problems
  
  
• Field-Replaceable Units
  
  

General Troubleshooting Information

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:

• Are the ports properly configured? Refer to the Cisco 6400 Software Setup Guide for configuration instructions.
  
  
• Are power leads and data cables firmly connected at both ends?
  
  
• Are all cards firmly seated and securely screwed to the chassis?
  
  
• Are the blower module and PEMs properly connected and secured to the chassis?
  
  

  ---

  Note   Check the release notes for more information on how to solve problems. Release notes can be found on Cisco.com. See the "Obtaining Documentation" section.

  ---

Reference Materials

Refer to the following materials:

• Cisco 6400 documents:
  
  
  • Cisco 6400 Software Setup Guide
    
    
  • Cisco 6400 Command Reference
    
    
  • Regulatory Compliance and Safety Information for the Cisco 6400 (78-5789-xx)
    
    
  • Cisco 6400 Site Planning Guide (78-5782-xx)
    
    
• Site log and equipment installation and maintenance records. (See "Configuration Worksheets.")
  
  

Recommended Tools and Test Equipment

To perform general maintenance and troubleshooting tasks on the Cisco 6400, you should have the following:

• Small and medium Number 2 Phillips and flat-blade screwdrivers
  
  
• Voltage tester
  
  
• Optical fiber test equipment
  
  

Troubleshooting Flowchart

Figure 4-1 is a flowchart to help you determine which component of your Cisco 6400 has malfunctioned. The decimal numbers in the following figure refer to the sections in this chapter where the various system elements are discussed.

General System Diagnostics

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 Cisco technical assistance center (TAC) for diagnosis. To contact TAC, refer to the "Obtaining Technical Assistance" section

Confirming the Hardware Installation

Use the show hardware command to display the hardware components installed. These components can include:

• Node line cards (NLCs)
  
  
• Node route processors (NRPs)
  
  
• Central processing unit (CPU)
  
  

The following example shows output from the show hardware command (this is only a sample; your output will not match exactly):

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
 

Displaying System Information

Use the show version and show environment commands to display the following Cisco 6400 information:

• Fan operation
  
  
• Temperature levels and alarms
  
  
• System status
  
  
• Modem status
  
  
• System uptime since last restart (in days, hours, minutes, and seconds)
  
  
• System name
  
  

Example

The following example shows output of the show version command (this is only a sample; your output will not match exactly):

Switch# show version

Cisco Internetwork Operating System Software
IOS (tm) 6400 Software (c6400r-g4p5-mz), Version 12.0(5)DC.......
Copyright (c) 1986-1999 by cisco Systems, Inc.
Compiled Tue 07-Oct-99 04:53 by jdoe
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#

Example

The following example shows output of the show environmentcommand (this is only a sample; your output will not match exactly):

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

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

Electrical problems are divided into two categories:

• Site electrical problems
  
  
• Cisco 6400 internal electrical problems
  
  

Site Electrical Problems

Site electrical problems can include:

• Improperly grounded equipment, particularly equipment racks and power grounds
  
  
• Fluctuating voltage, which can result from excessive power drains caused by other equipment (such as air conditioning units)
  
  
• Cable corrosion or defective power panels, circuit breakers or fuses, or cable connections
  
  
• Undersized power cables or excessive power cable lengths
  
  
• Excessive power demand on backup power systems or batteries when alternate power sources are used
  
  

Cisco 6400 Electrical Problems

Cisco 6400 electrical problems can include:

• Improperly grounded equipment, particularly equipment racks and power grounds
  
  
• Improper power cable connections to the Cisco 6400
  
  
• Improper installation of the power entry module (PEM) units in the system
  
  
• Improper installation of other plug-in units
  
  
• Circuit breakers that have tripped or that are defective
  
  
• Defective PEM units
  
  

Automatic Power-Down

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 two minutes, the Cisco 6400 powers down automatically.

Signal Input/Output Problems

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.

Checking Node Connections with the Ping Command

You can use the ping command 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]

Fiber-Optic Connections

An optical signal I/O problem can be caused by:

• Use of an incorrect type of fiber. Be sure to use single-mode fiber for a single-mode interface and multimode fiber for a multimode interface.
  
  
• Defective fiber.
  
  
• Transmit (TX) and Receive (RX) fibers that are reversed.
  
  
• Insufficient power budget on the optical link.
  
  
• Receiver overload on the optical link.
  
  

Evaluating the Power Budget

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:

• Fiber attenuation (single-mode) 0.5 dB/km
  
  
• Connector 0.5 dB
  
  
• Splice 0.5 dB
  
  

  ---

  Note   These are typical values; refer to the manufacturer's documentation for the actual values.

  ---

Receiver Overload

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.

Note   Refer to "System Specifications" for fiber-optic power levels for the OC-3/STM-1 and the OC-12/STM-4 NLCs.

Ethernet Connections

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:

• Visually check that an Ethernet cable is connected to the correct Ethernet port on the Cisco 6400, and that the other end of the cable is connected to a functional Ethernet hub.
  
  
• Check whether you are using the correct type of cable. The cable must meet the specifications given in the section "Connecting to a 10BASE-T Ethernet Network."
  
  
• The cable might be bad or broken. Replace the cable with a known, reliable straight-through Ethernet cable and check if the LNK LED comes on.
  
  
• Make sure the NSP module has booted up properly by checking the Status LED on its faceplate. This LED should be steady green. If necessary, remove and reinsert the module and boot it up again. Also, make sure the Ethernet hub you are using is powered up and operational.
  
  
• It is also possible that the Ethernet port might be functioning properly, but the LNK LED itself is broken. Check the Ethernet port (by trying to ping over it, for example) to determine if the problem is due to a bad LNK LED or if the Ethernet link itself is broken.
  
  

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, complete the following steps:

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 Software Setup 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 TAC for further assistance. See the "Obtaining Technical Assistance" section.

Console Port Serial Connections

If the console screen connected to a Cisco 6400 console port appears frozen or fails to work properly, check for the following problems:

• Check the console cable and make sure it is properly connected to the correct console port on the Cisco 6400 system at one end and to your terminal equipment at the other end.
  
  
• Verify that you are using the right type of cable and adapter. For information about pin-out connections, refer to "Hardware Description," and for installation instructions, refer to "Installing the Cisco 6400."
  
  
• Make sure the cable is not defective or broken. Replace the cable with another high quality cable if possible, and check to see if the console port starts working.
  
  
• Check that your terminal equipment is configured with the correct settings for the console port. The default console port settings are:
  
  
  • 9600 baud
    
    
  • 8 data bits
    
    
  • 1 stop bit
    
    
  • No parity
    
    
  • No flow control
    
    
• Check the LEDs on the NSP faceplate to make sure that the node switch processor (NSP) and the node router processor (NRP) module containing the console port have powered up properly. If necessary, remove and reinsert each module to power it up again. Also, make sure the terminal equipment is working properly.
  
  
• If the cable, connections, power, and terminal settings check out and you still cannot connect to the console port on the module, replace the module in question. If the problem persists, contact Cisco TAC for further assistance. Refer to the "Obtaining Technical Assistance" section.
  
  

Field-Replaceable Units

Information about the Cisco 6400 field-replaceable units (FRUs) is given in the following sections:

• General Troubleshooting Tips for Field-Replaceable Units
  
  
• NSP Module Faults
  
  
• NRP-1 Module Faults
  
  
• NRP-2SV Module Faults
  
  
• OC-3/STM-1 Single-Mode and Multimode NLCs and DS3 NLC Faults
  
  
• OC-12/STM-4 Single-Mode NLC Faults
  
  
• Blower Module Faults
  
  
• Power Entry Module Faults
  
  

General Troubleshooting Tips for Field-Replaceable Units

All Cisco 6400 FRUs are hot swappable. Procedures for removing and replacing the FRUs can be found in the Cisco 6400 Installation and Replacement of Field-Replaceable Units.

Table 4-1 lists general FRU fault symptoms and recommendations.

NSP Module Faults

Figure 4-2 shows the NSP indicators and connectors on the faceplate.

NSP LEDs

Table 4-2 describes the LEDs on the NSP faceplate.

Table 4-3 lists the NSP fault indications and recommended actions.

NRP-1 Module Faults

Figure 4-3 shows the NRP-1 indicators and connectors on the faceplate.

NRP-1 LEDs

Table 4-4 describes the LEDs on the NRP-1 faceplate.

Table 4-5 lists the NRP-1 module fault indications and recommended actions.

NRP-2SV Module Faults

Figure 4-4 shows the NRP-2SV indicators and connectors on the faceplate.

Warning Class 1 laser product. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Warning Invisible laser radiation present. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

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. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Warning Statement for Sweden

Warning Statement for Finland

NRP-2SV LEDs

The LEDs on the NRP-2SV indicate port and module status (Table 4-6).

Alphanumeric Display

The NRP-2SV faceplate also has a four-digit alphanumeric display that indicates status information and error codes.

OC-3/STM-1 Single-Mode and Multimode NLCs and DS3 NLC Faults

Figure 4-5 shows the OC3/STM-1 single-mode NLC indicators and connectors on the faceplate.

Figure 4-6 shows the OC3/STM-1 multimode NLC indicators and connectors on the faceplate.

Warning Class 1 laser product. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Warning Invisible laser radiation present. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

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. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Warning Statement for Sweden

Warning Statement for Finland

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

Table 4-8 lists the OC-3/STM-1 and DS3 NLC fault indications and recommended actions.

OC-12/STM-4 Single-Mode NLC Faults

Figure 4-8 shows the OC-12/STM-4 NLC indicators and connectors on the faceplate.

Warning Class 1 laser product. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Warning Invisible laser radiation present. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

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. To see translations of this warning, refer to the Regulatory Compliance and Safety Information document that accompanied this device.

Warning Statement for Finland

Warning Statement for Sweden

Table 4-9 describes the LEDs on the OC-12/STM-4 NLC faceplate.

Table 4-10 lists the OC-12/STM-4 NLC fault indications and recommended actions.

Note   Because the OC-12 has a single port, a second OC-12 module is required for an exernal loopback test. Contact Cisco TAC for more information.

Blower Module Faults

Figure 4-9 shows the blower module front panel and its indicators.

Table 4-11 describes the blower module LEDs located on the front center panel.

Table 4-12 lists the blower module fault indications and recommended action.

Power Entry Module Faults

Figure 4-10 shows the DC PEM and its indicators.

Table 4-13 describes the DC PEM LEDs located on the bottom front panel.

Table 4-14 lists the DC PEM fault indications and recommended actions.

Figure 4-11 shows the AC PEM and its indicators.

Table 4-15 describes the AC PEM LEDs located on the bottom front panel.

Table 4-16 lists the AC PEM fault indications and recommended actions.