Cisco ASR 5500 Installation Manual
Hide thumbs Also See for ASR 5500:

Advertisement

Quick Links

Troubleshooting
This chapter provides information and instructions for using the system command line interface (CLI) for
troubleshooting any issues that may arise during system operation.
Refer to the ASR 5500 Installation Guide for comprehensive descriptions of the hardware components addressed
by these troubleshooting procedures.
Detecting Faulty Hardware
When power is applied to the chassis, power is sequentially applied to the Management I/O (MIO/UMIO/MIO2)
cards, Data Processing Cards (DPC/UDPC/DPC2/UDPC2s), Fabric and Storage Cards (FSCs), and System
Status Cards (SSCs).
Each PFU and card installed in the system incorporates light emitting diodes (LEDs) that indicate its operating
status. This section describes how to use these status LEDs to verify that all of the installed components are
functioning properly.
Important
As the system progresses through its boot process, some cards will not exhibit immediate LED activity. Allow
several minutes to elapse after a reboot is initiates before checking the LEDs on the various cards to verify
that the boot process has successfully completed.
Licensing Issues
The system boot process is governed by StarOS licenses. During the startup process, each card performs a
series of Power-On Self Tests (POSTs) to ensure that the hardware is operational. These tests also verify that
the card meets all license requirements to operate in this chassis.
Refer to Chassis Universal License Requirements in the ASR 5500 Installation Guide for additional information
on the effect licenses and card types have on the boot process.
Detecting Faulty Hardware, on page 1
Taking Corrective Action, on page 20
Verifying Network Connectivity, on page 23
Using the System Diagnostic Utilities, on page 26
Generating an SSD, on page 29
Configuring and Using the Support Data Collector, on page 29
Troubleshooting
1

Advertisement

Table of Contents
loading

Summary of Contents for Cisco ASR 5500

  • Page 1 This chapter provides information and instructions for using the system command line interface (CLI) for troubleshooting any issues that may arise during system operation. Refer to the ASR 5500 Installation Guide for comprehensive descriptions of the hardware components addressed by these troubleshooting procedures.
  • Page 2: Using The Cli To View Status Leds

    Troubleshooting Using the CLI to View Status LEDs Using the CLI to View Status LEDs Status LEDs for all cards can be viewed via the CLI by entering the Exec mode show leds all command. show leds all [local]host_name# The following displays a sample of this command's output. Slot 01: Run/Fail: Green | Active: Off | Redundant: Green Slot 02: Run/Fail: Green...
  • Page 3: Checking The Leds On The Mio Card

    Troubleshooting Checking the LEDs on the MIO Card Table 1: PFU LED States Color Description Troubleshooting Blue Power feed is supplying -48VDC to this None needed. power plane None PFU is not receiving power to one or more Verify that each circuit breaker is in the ON of its power planes.
  • Page 4: Mio Run/Fail Led States

    Troubleshooting MIO Run/Fail LED States Figure 2: MIO Card Status LEDs The possible states for all MIO/UMIO/MIO2 LEDs are described in the sections that follow. MIO Run/Fail LED States The MIO/UMIO/MIO2 Run/Fail LED indicates the overall status of the card. This LED should be steady green for normal operation.
  • Page 5: Mio Active Led States

    Verify that the power source is supplying ample voltage and current to the chassis. Verify that the card is properly installed per the instructions in the ASR 5500 Installation Guide. If all of the above suggestions have been verified, it is possible that the MIO is not functional.
  • Page 6: Mio Redundancy Led States

    Troubleshooting MIO Redundancy LED States MIO Redundancy LED States The Redundancy LED on the MIO/UMIO/MIO2 indicates that software is loaded on the card, but it is serving as a redundant component. For the MIO/UMIO/MIO2 installed in slot 6, this LED should be green for normal operation.
  • Page 7: Mio Busy Led States

    Troubleshooting MIO Busy LED States Color Description Troubleshooting Blinking Green Tasks or processes being migrated from the Refer to Monitoring the System for active MIO to the standby MIO. information on determining the status of the MIO/UMIO /MIO2and system software processes.
  • Page 8: Mio Interface Activity Led States

    Troubleshooting MIO Interface Activity LED States Table 7: MIO Interface Link LED States Color Description Troubleshooting Green Link is up None needed. NOTE: This LED will not indicate the presence of a network link until the interface parameters are set during the software configuration process.
  • Page 9: Dpc Run/Fail Led States

    Troubleshooting DPC Run/Fail LED States Figure 3: DPC Status LEDs The possible states for all of the DPC/UDPC or /DPC2/UDPC2 LEDs are described in the sections that follow. DPC Run/Fail LED States The DPC/UDPC or /DPC2/UDPC2 Run/Fail LED indicates the overall status of the card. This LED should be green for normal operation.
  • Page 10: Dpc Active Led States

    Troubleshooting DPC Active LED States Color Description Troubleshooting None Card is not receiving power. Verify that the LEDs on the PFUs are blue. If they are not, refer to Checking the LEDs on the PFU, on page 2 for troubleshooting information.
  • Page 11: Dpc Redundancy Led States

    Troubleshooting DPC Redundancy LED States Color Description Troubleshooting None Card is not receiving power. Verify that the Run/Fail LED is green. If so, the card is receiving power and POST results are positive. If it is off, refer to Card is in Standby Mode. Run/Fail LED States, on page 9 troubleshooting information.
  • Page 12: Checking The Leds On The Fsc

    Troubleshooting Checking the LEDs on the FSC Checking the LEDs on the FSC Each FSC is equipped with the following LEDs as shown in the accompanying figure: • Run/Fail • Active • Redundancy • Drive 1 Activity • Drive 2 Activity Figure 4: FSC Status LEDs The possible states for all FSC LEDs are described in the sections that follow.
  • Page 13: Fsc Active Led States

    Verify that the power source is supplying ample voltage and current to the chassis. Verify that the card is properly installed per the instructions in the ASR 5500 Installation Guide. If all of the above suggestions have been verified, it is possible that the FSC is not functional.
  • Page 14: Fsc Redundancy Led States

    Troubleshooting FSC Redundancy LED States Color Description Troubleshooting None Card is not receiving power. Verify that the Run/Fail LED is green. If so, the card is receiving power and POST results are positive. If it is off, refer to Card is in Standby Mode. Run/Fail LED States, on page 12 troubleshooting information.
  • Page 15: Checking The Leds On The Ssc

    Troubleshooting Checking the LEDs on the SSC Important The FSC-400GB is equipped with a single 400 GB drive. Only the Drive 1 Activity LED will be active; the Drive 2 Activity LED will always be off (None). The possible states for this LED are described in the following table. If the LED is not green, use the troubleshooting information also provided to diagnose the problem.
  • Page 16: Ssc Run/Fail Led States

    Troubleshooting SSC Run/Fail LED States Figure 5: SSC Status LEDs The possible states for all SSC LEDs are described in the sections that follow. SSC Run/Fail LED States The SSC Run/Fail LED indicates the overall status of the card. This LED should be green for normal operation. The possible states for this LED are described in the following table.
  • Page 17: Ssc Active Led States

    Verify that the power source is supplying ample voltage and current to the chassis. Verify that the card is properly installed per the instructions in the ASR 5500 Installation Guide. If all of the above suggestions have been verified, it is possible that the SSC is not functional.
  • Page 18: Ssc Redundancy Led States

    Troubleshooting SSC Redundancy LED States SSC Redundancy LED States The Redundancy LED on the SSC indicates that software is loaded on the card, but it is serving as a standby component. SSC support 1:1 redundancy; the Redundancy LED should be green on the other SSC for normal system operation.
  • Page 19: Ssc System Service Led States

    Troubleshooting SSC System Service LED States Color Description Troubleshooting None Card is not receiving power Verify that the Run/Fail LED is green. If so, the card is receiving power and POST results are positive. If it is off, refer to the SSC Run/Fail LED States section for troubleshooting information.
  • Page 20: Taking Corrective Action

    Troubleshooting Taking Corrective Action Taking Corrective Action In the event that an issue was discovered with an installed application or line card, depending on the severity, it may be necessary to take corrective action. The system provides several redundancy and fail-over mechanisms to address issues with application and line cards in order to minimize system downtime and data loss.
  • Page 21: Migrating A Dpc

    Troubleshooting Migrating a DPC You will receive the following prompt: Are You Sure? [Yes|No]: Step 2 Press Y to start the switchover. Step 3 Verify that the busy-out was successful by entering the show card table command at the Exec mode prompt: Check the entry in the Oper State column next to the DPC/UDPC or DPC2/UDPC2 just busied-out.
  • Page 22: Initiate A Card Halt

    Troubleshooting Initiate a Card Halt Initiate a Card Halt Important Do not initiate a card halt for an active FSC if there are less than two active FSCs in the system. The system returns an error message if there are less than two active FSCs. There are similar restrictions when executing the card reboot or card upgrade commands on active FSCs.
  • Page 23: Verifying Network Connectivity

    Troubleshooting Verifying Network Connectivity Verifying Network Connectivity There are multiple commands supported by the system to verify and/or troubleshoot network connectivity. Note that network connectivity can only be tested once system interfaces and ports have been configured and bound. The commands specified in this section should be issued on a context-by-context basis. Contexts act like virtual private networks (VPNs) that operate independently of other contexts.
  • Page 24: Using The Traceroute Or Traceroute6 Command

    Troubleshooting Using the traceroute or traceroute6 Command • Attempt to ping a different device on the same network. If the ping was successful then it is likely that your system configuration is correct. Verify that the device you are attempting to ping is powered and functioning properly.
  • Page 25: Viewing Ip Routes

    Troubleshooting Viewing IP Routes Viewing IP Routes The system provides a mechanism for viewing route information to a specific node or for an entire context. This information can be used to verify network connectivity and to ensure the efficiency of the network connection.
  • Page 26: Using The System Diagnostic Utilities

    Troubleshooting Using the System Diagnostic Utilities Using the System Diagnostic Utilities The system provides protocol monitor and test utilities that are useful when troubleshooting or verifying configurations. The information generated by these utilities can help identify the root cause of a software or network configuration issue.
  • Page 27: Using The Protocol Monitor For A Specific Subscriber

    Troubleshooting Using the Protocol Monitor for a Specific Subscriber C - Control Events (ON ) D - Data Events (ON ) E - EventID Info (ON ) H - Display ethernet (ON ) I - Inbound Events (ON ) O - Outbound Events (ON ) S - Sender Info (OFF)
  • Page 28 Troubleshooting Using the Protocol Monitor for a Specific Subscriber Step 5 Repeat step 6 as needed to enable or disable multiple protocols. Step 6 Press Enter to refresh the screen and begin monitoring. The following displays a portion of a sample of the monitor's output for a subscriber named user2@aaa. The default protocols were monitored.
  • Page 29: Generating An Ssd

    Troubleshooting Generating an SSD Generating an SSD An SSD is an instance of the output when the Exec mode show support details command is run. It displays a comprehensive list of system information that is useful for troubleshooting purposes. In most cases, the output of this command is requested by the Technical Assistance Center (TAC).
  • Page 30 Troubleshooting Configuring and Using the Support Data Collector Refer to the Support Data Collector chapter for a complete description of SDC functionality. Troubleshooting...

This manual is also suitable for:

Asr 5500 series

Table of Contents