Detecting Faulty Hardware
Licensing Issues
Using the CLI to View Status LEDs
[local]host_name# show leds all
Slot 01: Run/Fail: Green | Active: Off | Redundant: Green
Slot 02: Run/Fail: Green | Active: Off | Redundant: Green
Slot 03: Run/Fail: Green | Active: Off | Redundant: Green
Slot 05: Run/Fail: Green | Active: Green | Redundant: Green Master: Green
Slot 06: Run/Fail: Green | Active: Off | Redundant: Green Master: Off
Slot 08: Run/Fail: Green | Active: Off | Redundant: Green
Slot 11: Run/Fail: Green | Active: Green | Redundant: Green Status: Green | Service: Off
Slot 12: Run/Fail: Green | Active: Green | Redundant: Green Status: Green | Service: Off
Slot 13: Run/Fail: Green | Active: Green | Redundant: Green
Slot 14: Run/Fail: Green | Active: Green | Redundant: Green
Slot 15: Run/Fail: Green | Active: Green | Redundant: Green
Slot 16: Run/Fail: Green | Active: Green | Redundant: Green
Slot 17: Run/Fail: Green | Active: Green | Redundant: Green
Checking the LEDs on the PFU
| Color | Description | Troubleshooting |
|---|---|---|
| Blue | Power feed is supplying -48VDC to this power plane | None needed. |
| None | PFU is not receiving power to one or more of its power planes. | Verify that each circuit breaker is in the ON position. |
| Verify that the RTN and -48VDC lugs are attached properly to the posts on the upper rear of the chassis. | ||
| Verify that the ground lug is attached properly. | ||
| Use a voltmeter to verify that the power distribution panel is supplying the correct voltage and sufficient current to the terminals at the rear of the PFU. | ||
| Check the cables from the power source to the rack for continuity. | ||
| If a power distribution panel (PDP) is installed between the power distribution frame (PDF) and the chassis, verify that its circuit breakers are set to ON. | ||
| If a PDP is installed between the PDF and the chassis, check the cables from the PDP to the chassis for continuity. | ||
| If all of the above suggestions have been verified, then it is likely that the PFU is not functional. Please contact your service representative. |
Checking the LEDs on the MIO and UMIO
MIO/UMIO Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected |
None needed.
|
| Blinking Green | Card is initializing and/or loading software |
This is normal operation
during boot-up.
|
| Red | Card powered with error(s) detected |
Errors were detected
during the Power On Self Tests (POSTs). It
is likely that the errors were logged to the system's command line interface
during boot.
|
| 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 for troubleshooting information. |
| 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. Please contact your service representative. |
MIO/UMIO Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active | None needed for the MIO/UMIO in slot 5. If green for the MIO/UMIO in slot 6, verify that the MIO/UMIO in slot 5 is installed and licensed properly according to the instructions in the ASR 5500 Installation Guide. |
| Blinking Green | Tasks or processes being migrated from the active MIO to the standby MIO. | Refer to Monitoring the System for information on determining the status of the MIO/UMIO and system software processes. |
| None |
Card is not receiving power.
OR
Card has failed.
|
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 MIO/UMIO RunFail LED States for troubleshooting information. |
MIO/UMIO Redundancy LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in redundant mode | None needed. If green for the MIO/UMIOs in slot 5 and slot 6, the cards and ports are fully backed up. |
| Amber | Card or port on this card is not backed up by other MIO. | Check the status of the other MIO/UMIO. If it has failed or one or more of its ports are no longer active, the system can continue to function but redundancy is compromised. |
| Refer to Monitoring the System for information on determining the status of the MIO/UMIO and system software processes. | ||
| Blinking Amber | Tasks or processes being migrated from the active MIO to the standby MIO. | Refer to Monitoring the System for information on determining the status of the MIO/UMIO and system software processes. |
| None |
Card is not receiving power.
OR
Card has failed.
|
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 MIO/UMIO RunFail LED States for troubleshooting information on. |
MIO/UMIO Master LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | This card is the Active MIO. |
None needed.
|
| Blinking Green | Tasks or processes being migrated from the active MIO to the standby MIO. |
Refer to Monitoring the System for
information on determining the status of the MIO/UMIO and
system software processes.
|
| None |
This card is the Standby
MIO.
OR
Card has failed.
|
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 MIO/UMIO RunFail LED States for troubleshooting information. |
| Refer to Monitoring the System for information on determining the status of he MIO/UMIO and system software processes. |
MIO/UMIO Busy LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Files are being transferred to or accessed from the RAID configuration on the FSCs. | None required. |
| None |
No RAID activity.
OR
RAID configuration is
unavailable.
|
MIO/UMIO – 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.
|
| None |
No power to card.
OR
Link is down.
|
Verify that the Run/Fail LED is green. If so, the card is receiving power. If it is off, refer to MIO/UMIO Run/Fail LED States for troubleshooting information. |
| Verify that the interface is cabled properly. | ||
| Verify that the device on which the interface is located is cabled and powered properly. |
MIO/UMIO – Interface Activity LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Flashing Green | Traffic is present on the link |
None needed.
|
| None | No traffic is present on the link |
None needed if there
is no activity on the link. Prior to interface configuration, this
is normal operation.
|
Checking the LEDs on the DPC and UDPC
DPC/UDPC Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered up with no errors detected. | None needed. |
| Blinking Green | Card is initializing and/or loading software. | This is normal operation during boot-up. |
| Red | Card powered up with error(s) detected. | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the system's command line interface during boot. |
| 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 for troubleshooting information. |
| Verify that the power source is supplying ample voltage and current to the chassis. | ||
| Verify that the card is properly installed and licensed per the instructions in the ASR 5500 Installation Guide. | ||
| If all of the above suggestions have been verified, it is possible that the DPC/UDPC is not functional. Please contact your service representative. |
DPC/UDPC Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. | The first time power is applied to the system, all of the DPC/UDPCs should be booted into the standby mode. Therefore, this LED should be off. |
| Blinking Green | Tasks or processes are being migrated from an active DPC to a standby DPC. | Verify that the Redundancy LED on a standby DPC/UDPC is also blinking green. If so, there is an issue with the active DPC/UDPC and it is transferring its processes. |
| Refer to Monitoring the System for information on determining the status of the DPC/UDPC and system software processes and functionality. | ||
| None |
Card is not receiving power.
OR
Card is in Standby Mode.
|
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 DPC/UDPC Run/Fail LED States for troubleshooting information. |
| Check the state of the Redundancy LED. If it is green, the card is in standby mode. This is normal operation for the initial power-up. If needed, refer to the Configuring DPC Availability section of System Settings for information on making the card active. |
DPC/UDPC Redundancy LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in standby mode. | None needed. There is at least one DPC/UDPC in Standby mode. |
| Amber | Card is not backed up by a standby DPC. | Check the status of the other DPC/UDPCs. If one DPC/UDPC has failed or has been removed from the chassis, the system can continue to function but redundancy is compromised. |
| Refer to Monitoring the System for information on determining the status of the DPC/UDPC and system software processes. | ||
| Blinking Amber | Tasks or processes being migrated from an active DPC to the standby DPC. | Refer to Monitoring the System for information on determining the status of the DPC/UDPC and system software processes. |
| None |
Card is not receiving power.
OR
Card has failed.
|
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 DPC/UDPC Run/Fail LED States for troubleshooting information. |
Checking the LEDs on the FSC
FSC Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected | None needed. |
| Blinking Green | Card is initializing and/or loading software | This is normal operation during boot-up. |
| Red | Card powered with error(s) detected | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the system's command line interface during boot. |
| 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 for troubleshooting information. |
| 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. Please contact your service representative. |
FSC Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. |
The first time power
is applied to the system, all of the FSCs should be booted
into the ready mode. Therefore, this LED should be
on.
|
| Blinking Green | Tasks or processes being migrated from an active FSC to a standby FSC. | Verify that the Redundancy LED on a standby FSC is also blinking green. If so, there is an issue with the active FSC and it is transferring its processes. |
| Refer to Monitoring the System for information on determining the status of the FSC and system software processes and functionality. | ||
| None |
Card is not receiving power.
OR
Card is in Standby Mode.
|
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 FSC Run/Fail LED States for troubleshooting information. |
| Check the state of the Redundancy LED. If it is green, the card is in standby mode. |
FSC Redundancy LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in redundant mode |
None needed. There
is at least one FSC in Standby mode.
|
| Amber | Card is not backed up by a standby FSC. | Check the status of the other FSCs. If one FSC has failed or has been removed from the chassis, the system can continue to function but redundancy is compromised. |
| Refer to Monitoring the System for information on determining the status of the FSC and system software processes. | ||
| Blinking Amber | Tasks or processes being migrated from an active FSC to the standby FSC. |
Refer to Monitoring the System for
information on determining the status of the FSC and system software processes.
|
| None |
Card is not receiving power.
OR
Card has failed.
|
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 FSC Run/Fail
LED States for troubleshooting information.
|
FSC Drive n Activity LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Files are being transferred to or accessed from the RAID configuration by the MIO. | None required. |
| None |
There is no RAID activity.
OR
RAID configuration is
unavailable.
|
Checking the LEDs on the MIO and UMIO |
| 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 FSC RunFail LED States for troubleshooting information. |
Checking the LEDs on the SSC
SSC Run/Fail LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card powered with no errors detected | None needed. |
| Blinking Green | Card is initializing and/or loading software | This is normal operation during boot-up. |
| Red | Card powered with error(s) detected | Errors were detected during the Power On Self Tests (POSTs). It is likely that the errors were logged to the system's command line interface during boot. |
| 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 for troubleshooting information. |
| 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. Please contact your service representative. |
SSC Active LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is active. |
The first time power
is applied to the system, both SSCs should be booted into
the ready mode. Therefore, this LED should be on.
|
| Blinking Green | Tasks or processes being migrated from an active FSC to a standby FSC. | Verify that the Redundancy LED on a Istanbul SSC is also blinking green. If so, there is an issue with the active SSC and it is transferring its processes. |
| Refer to Monitoring the System for information on determining the status of the SSC and system software processes and functionality. | ||
| None |
Card is not receiving power.
OR
Card is in Standby Mode.
|
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. |
| Check the state of the Redundancy LED. If it is green, the card is in standby mode. |
SSC Redundancy LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | Card is in standby mode |
None needed. The
other SSC should be in Standby mode.
|
| Amber | Card is not backed up by the standby SSC. | Check the status of the other SSC. If one it has failed or has been removed from the chassis, the system can continue to function but redundancy is compromised. |
| Refer to Monitoring the System for information on determining the status of the SSC and system software processes. | ||
| Blinking Amber | Tasks or processes being migrated from the active SSC to the standby SSC. | Refer to Monitoring the System for information on determining the status of the SSC and system software processes. |
| None |
Card is not receiving power.
OR
Card has failed.
|
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. |
SSC System Status LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Green | System is operating normally | None required. |
| Red | The system has experienced a loss of service. | Refer to Monitoring the System for information on determining the status of system hardware and software processes. |
| 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. |
SSC System Service LED States
| Color | Description | Troubleshooting |
|---|---|---|
| Amber | System requires maintenance (fan filter, temperature warning, PFU outage etc.). | Monitoring the System for show commands, the outputs of which will assist in further determining the problem. |
| Refer to System Logs for information on how to view logs. | ||
| None |
No component failures
have been detected.
OR
Card is not receiving power.
|
No maintenance needed. |
Testing System Alarm Outputs
[local]host_name# test alarm { audible | central-office [ critical | major | minor ] }
Taking Corrective Action
[local]host_name# card switch from <5 or 6> to <6 or 5>
You
will receive the following prompt:
Are You Sure? [Yes|No]:
[local]host_name# card busy-out slot_number
You
will receive the following prompt:
Are You Sure? [Yes|No]:
[local]host_name# card migration from original_slot# to final_slot#
You
will receive the following prompt:
Are You Sure? [Yes|No]:
Halting Cards
IMPORTANT:
[local]host_name# card halt slot#
slot# is
the chassis slot number in which the card to be halted is installed. It
can be any integer from 1 through 4, and 7 through 18. You
will receive the following prompt:
Are You Sure? [Yes|No]:
[local]host_name# card reboot slot# -force
You
will receive the following prompt:
Are You Sure? [Yes|No]:
Verifying Network Connectivity
Using the ping or ping6 Command
Syntax
ping host_ipv4_address [ count num_packets ] [ flood ] [ pattern packet_pattern ] [ size octet_count ] [ src { src_host_name | src_host_ipv4_address } ] [ vrf vrf_nam ]
ping6 host_ipv6_address [ count num_packets ] [ flood ][ pattern packet_pattern ] [ size octet_count ] [ src { src_host_name | src_host_ipv6_address } ] [ vrf vrf_nam ]
PING 192.168.250.1 (192.168.250.1): 56
data bytes
64 bytes from 192.168.250.1: icmp_seq=0
ttl=255 time=0.4 ms
64 bytes from 192.168.250.1: icmp_seq=1
ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=2
ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=3
ttl=255 time=0.2 ms
64 bytes from 192.168.250.1: icmp_seq=4
ttl=255 time=0.2 ms
--- 192.168.250.1
ping statistics ---
5 packets transmitted, 5
packets received, 0% packet loss
round-trip
min/avg/max = 0.2/0.2/0.4 ms
Using the traceroute or traceroute6 Command
traceroute – IPv4
traceroute { host_name | host_ipv4_address } [ count packets ] [ df ] [ maxttl max_ttl ] [ minttl min_ttl ] [ port port_number ] [ size octet_count ] [ src { src_host_name | src_host_ipv4_address } ] [ timeout seconds ] [ vrf vrf_nam ]
traceroute6 – IPv6
traceroute6 { host_name | host_ipv6_address } [ count packets ] [ maxttl max_ttl ] [ port port_number ] [ size octet_count ] [ src { src_host_name | src_host_ipv6_address } ] [ timeout seconds ] [ vrf vrf_nam ]
Viewing IP Routes
"*" indicates
the Best or Used route.
Destination Nexthop Protocol
Prec Cost Interface
*0.0.0.0/0 10.0.4.1 static 0 0
SPIO1
*10.0.4.0/24 0.0.0.0 kernel 0 0
SPIO1
*10.0.4.0/32 0.0.0.0 kernel 0 0
SPIO1
*10.0.4.3/32 0.0.0.0 kernel 0 0
SPIO1
*10.0.4.255/32 0.0.0.0 kernel 0 0
SPIO1
Viewing the Address Resolution Protocol Table
[local]host_name# show ip arp [ arp_ip_address ]
IMPORTANT:
Flags codes:
C - Completed, M - Permanent, P - Published, ! - Not answered
T - has requested
trailers
Address Link
Type Link Address Flags Mask
Interface
10.0.4.240 ether 00:05:47:02:20:20
C MIO1
10.0.4.7 ether 00:05:47:02:03:36
C MIO1
10.0.4.1 ether 00:01:30:F2:7F:00
C MIO1
Using the System Diagnostic Utilities
Using the Monitor Utility
[local]host_name# monitor protocol
An output listing
all the currently available protocols, each with an assigned
number, is displayed.
WARNING!!! You
have selected options that can DISRUPT USER SERVICE
Existing CALLS MAY
BE DROPPED and/or new CALLS MAY FAIL!!!
(Under heavy
call load, some debugging output may not be displayed)
Proceed? - Select (Y)es
or (N)o
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)
T - Timestamps (ON )
X - PDU Hexdump (OFF)
A - PDU Hex/Ascii (OFF)
+/- Verbosity
Level ( 1)
L - Limit
Context (OFF)
M - Match
Newcalls (ON )
R - RADIUS
Dict (no-override)
G - GTPP Dict (no-override)
Y - Multi-Call
Trace ((OFF))
(Q)uit, <ESC>
Prev Menu, <SPACE> Pause, <ENTER> Re-Display
Options
[local]host_name# monitor subscriber { callid | imei | imsi | ipaddr | ipv6addr | msid | msisdn | next-call | pcf | peer-fa | peer-lac | sgsn-address | type | username }
IMPORTANT:
---------------------------------------------------------------------------
Incoming Call:
---------------------------------------------------------------------------
MSID: 0000012345
Callid: 002dc6c2
Username: user2@aaa
SessionType: unknown
Status: Active
Service Name: xxx1
Src
Context: source Dest Context:
---------------------------------------------------------------------------
<<<<OUTBOUND
10:02:35:415 Eventid:25001(0)
PPP Tx PDU (9)
PAP 9: Auth-Ack(1), Msg=
<<<<OUTBOUND
10:02:35:416 Eventid:25001(0)
PPP Tx PDU (14)
IPCP 14: Conf-Req(1), IP-Addr=192.168.250.70
<<<<OUTBOUND
10:02:35:416 Eventid:25001(0)
PPP Tx PDU (27)
CCP 27: Conf-Req(1), MPPC, Stac-LZS, Deflate, MVRCA
INBOUND>>>>> 10:02:35:517 Eventid:25000(0)
PPP Rx PDU (30)
IPCP 30: Conf-Req(1), IP-Comp
VJ-Comp, IP-Addr=0.0.0.0, Pri-DNS=0.0.0.0,
Sec-DNS=0.0.0.0
<<<<OUTBOUND
10:02:35:517 Eventid:25001(0)
PPP Tx PDU (26)
IPCP 26: Conf-Rej(1), IP-Comp
VJ-Comp, Pri-DNS=0.0.0.0, Sec-DNS=0.0.0.0
INBOUND>>>>> 10:02:35:517 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Ack(1), IP-Addr=192.168.250.70
INBOUND>>>>> 10:02:35:518 Eventid:25000(0)
PPP Rx PDU (31)
LCP 31: Prot-Rej(1), Rejected-Protocol=CCP (0x80fd)
INBOUND>>>>> 10:02:35:518 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Req(2), IP-Addr=0.0.0.0
<<<<OUTBOUND
10:02:35:518 Eventid:25001(0)
PPP Tx PDU (14)
IPCP 14: Conf-Nak(2), IP-Addr=192.168.250.87
INBOUND>>>>> 10:02:35:519 Eventid:25000(0)
PPP Rx PDU (12)
IPCP 12: Conf-Req(3), IP-Addr=192.168.250.87