Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Troubleshooting PTX5000 Components

PTX5000 Troubleshooting Resources Overview

To troubleshoot a PTX5000, you use the Junos OS command-line interface (CLI), LCD, alarms, devices connected to the alarm relay contacts, and LEDs on both the components and craft interface.

  • LEDs—When the Routing Engine detects an alarm condition, it lights the red or yellow alarm LED on the craft interface as appropriate. In addition, you can also use the component-specific LEDs on the craft interface and on the faceplate of a component to troubleshoot the PTX5000.

  • LCD—When a red or yellow alarm occurs, the cause of the alarm messages is displayed on the craft interface LCD. Use the CLI to display more information about the alarm.

  • Alarm devices connected to the alarm relay contact—When a red or yellow alarm occurs, it trips the corresponding alarm relay contact.

  • CLI—The CLI is the primary tool for controlling and troubleshooting hardware, Junos OS, routing protocols, and network connectivity. CLI commands display information from routing tables, information specific to routing protocols, and information about network connectivity derived from the ping and traceroute utilities. For information about using the CLI to troubleshoot the Junos OS, see the appropriate Junos OS configuration guide.

  • JTAC—If you need assistance during troubleshooting, you can contact the Juniper Networks Technical Assistance Center (JTAC) by using the Web or by telephone. If you encounter software problems, or problems with hardware components not discussed here, contact JTAC.

PTX5000 LED Overview

Craft Interface LEDs

The craft interface displays system status messages and allows you to troubleshoot the PTX5000. See PTX5000 Craft Interface LEDs.

Note:

The FPC LEDs are located on the FPC faceplate.

LEDs on the craft interface include:

  • Red and yellow alarm LEDs—One large red circular LED and one large yellow triangular LED indicate two levels of alarm conditions. You can determine the cause of the alarm condition by looking at the LCD on the craft interface.

  • SIB LEDs—One bicolor green and red OK indicates the status of each SIB. One green (ACT) LED indicates if the SIB is active and passing traffic. The SIB LEDs are located on the left of the craft interface, and are labeled SIB0 through SIB8.

  • Host subsystem LEDs—Three LEDs (one green MASTER, one green OK, and one red FAIL) indicate the status of each host subsystem. The host subsystem LEDs are located on the upper right of the craft interface, and are labeled HOST0 and HOST1.

  • CCG LEDs—Three LEDs (one green MASTER, one green OK, and one red FAIL) indicate the status of each host subsystem. The CCG LEDs are located on the upper left of the craft interface, and are labeled CCG0 and CCG1.

  • Fan tray LEDs—One bicolor green and red LED for each fan tray labeled 0, 1, and 2 that indicates the status of the fan tray.

  • PDU LEDs—One bicolor green and red OK LED for each PDU labeled 0 and 1, which indicates the status of the PDU.

  • PSM LEDs—One bicolor green and red LED for each PSM labeled 0 and, 1, 2, and 3, which indicates the status of the PSM.

Component LEDs

The following LEDs are located on various PTX5000 components and display the status of those components:

PTX5000 Alarm Messages Overview

When the Routing Engine detects an alarm condition, it lights the red or yellow alarm LED on the craft interface as appropriate, trips the corresponding alarm relay contact, and reports the cause of the alarm in the craft interface LCD.

Chassis Alarm Messages

Chassis alarm messages Indicate a problem with a chassis component such as the cooling system or power system.To view a more detailed description of the alarm cause, issue the show chassis alarms CLI command:

For more information and troubleshooting for chassis alarms, see the following documentation:

Interface Alarm Messages

Interface alarms indicate a problem with a specific network interface.

Troubleshooting the PTX5000 Centralized Clock Generators

Problem

Description

The following alarms and LEDs indicate a problem with a CCG:

Solution

To troubleshoot the CCGs:

  1. Use the CLI to check for alarms. Issue the show chassis alarms command to view the alarms.

  2. Check the LEDs on the faceplate of each CCG and on the craft interface.

  3. Issue the show chassis environment ccg command to check the status of the CCGs.

In Table 1, the text in the column labeled ”LCD Message” appears in the display of the craft interface. The text in the column labeled “CLI Message” appears in the output from the show chassis alarms command.

Table 1: Troubleshooting Chassis Alarm Messages for the CCGs

Alarm Type

LCD Message

CLI Message

Alarm Condition

Red

CCG CCG-number Failure

CCG CCG-number Failure

A CCG has failed.

No CG Online

No CG Online

No CCGs are installed, or the CCGs installed are not online

CCG CCG-number Ext-A LOS

CCG CCG-number External-A LOS

Loss of signal has occurred on the Bits-A port configured to be the primary or secondary clocking source, .

CCG CCG-number Ext-B LOS

CCG CCG-number External-B LOS

Loss of signal has occurred on the Bits-B port configured to be the primary or secondary clocking source.

CCG CCG-number EXT SYNC UNSUPP

CCG CCG-number EXT SYNC UNSUPP

External synchronization is not supported.

Yellow

CCG CCG-number Not Online

CCG CCG-number Not Online

A CCG is offline.

Table 2: Troubleshooting CCG LEDs

Label

Color

State

Description

Recovery

FAIL

Yellow

On steadily

The CCG has detected a failure.

Replace the CCG.

OK

Off

The CCG is not online or is not powered on.

Bring the CCG online.

Table 3: Troubleshooting CCG Port LEDs

Label

Color

State

Description

FAULT

Yellow

On steadily

The CCG has detected a failure.

LINK

Note:

The LINK LEDs are supported only for the BITS ports. This LED is not supported for the GPS ports.

Yellow

On steadily

BITS loss of signal

Off

No loss of signal

Troubleshooting the PTX5000 Cooling System

Troubleshooting the PTX5000 Fan Trays

Problem

Description

The following alarms and LEDs indicate a problem with the fan trays:

Solution

To troubleshoot the fan trays:

  1. Check the alarms.

    • Issue the show chassis alarms command to get information about the source of an alarm condition:

    • Find the source of the problem by looking at the display on the craft interface. The number of alarm conditions, as well as the source of each alarm, appears on the screen.

  2. Use the show chassis fan command to verify that the status of each fan is OK.

    Note:

    Fan Tray 0 and Fan Tray 1 refer to the fans in the horizontal fan trays that cool zone 1, and Fan Tray 2 refers to fans in the vertical fan tray that cools zone 0.

  3. If only one fan has failed and the other fans are functioning normally, the fan is probably faulty and you need to replace the fan tray.

  4. Use the show chassis zones command to verify the status of each cooling zone.

  5. Use the show chassis zones detail command to verify the status of each component in cooling zone 0 and cooling zone 1.

In Table 4, the text in the column labeled ”LCD Message” appears in the display of the craft interface. The text in the column labeled “CLI Message” appears in the output from the show chassis alarms command.

Table 4: Troubleshooting Fan Tray Alarms

Alarm Type

LCD Message

CLI Message

Alarm Condition

Recovery

Red

Fan Failure

fan-name Failure

A fan has failed.

Replace the fan tray.

 

Fans Missing

Too many fans missing or failing

A fan tray is missing or too many fan trays have failed.

Reinstall the fan tray in the chassis.

Yellow

Fan Removed

fan-name Removed

A fan tray has been removed.

Reinstall the fan tray in the chassis.

Table 5: Troubleshooting Fan Tray LEDs on the Craft Interface

Color

State

Description

Recovery

Red

On steadily

The fan tray has failed.

Replace the fan tray.

Off

The fan tray is offline or absent.

Reinstall the fan tray in the chassis.

Troubleshooting Temperature Alarms

Problem

Description

The following alarms or other conditions indicate a problem with the temperature of the hardware components:

  • Table 6 lists the alarms.

  • The PTX5000 is powered off immediately if the temperature of a component exceeds the preconfigured maximum Fire Shutdown threshold.

Solution

To troubleshoot temperature alarms:

  1. Find the source of the problem by looking at the display on the craft interface. The number of alarm conditions, as well as the source of each alarm, appears on the screen. Issue the show chassis alarms command to get information about the source of an alarm condition:

  2. Verify that there is sufficient air flow. See PTX5000 Clearance Requirements for Airflow and Hardware Maintenance, Maintaining the PTX5000 Fan Trays, and Maintaining the PTX5000 Air Filters.

    Place your hand near the exhaust vents at the rear of the chassis to determine whether the fans are pushing air out of the chassis.

    • Zone 0: The air exhausts from the left side of the SIBs.

    • Zone 1: The exhaust vent is located at the upper rear of the chassis.

    • Power system: The air exhausts from the power supply modules (PSMs).

  3. Verify that the cooling system in the chassis is operating properly. See Troubleshooting the PTX5000 Cooling System.

  4. Verify that the room temperature is within acceptable limits. Use the show chassis temperature-thresholds to show the temperature thresholds for various components.

    Note:

    Exhaust A, Exhaust B, TLn, TQn, Ambient, Exhaust, and Junction correspond to temperature sensors located on the respective hardware component.

  5. Look at the PDU and PSM LEDs on the craft interface.

  6. If both PDUs fail, the system temperature might have exceeded the threshold, causing the system to shut down. If the temperature exceeds the acceptable maximum, the Control Board turns off the PDUs.

  7. Check the temperature of components that are monitored for temperature alarms by issuing the show chassis environment monitored command. For more information about temperature alarms, see Table 6.

    Verify that the status of each component is OK.

    Note:

    Exhaust A, Exhaust B, TLn, TQn, Ambient, Exhaust, and Junction correspond to temperature sensors located on the respective hardware component.

    The output is similar to the following:

  8. If there is a temperature alarm for a hardware component, issue on the following commands for more detail.

    • Use the show chassis environment routing-engine command to check the temperature of each Routing Engine.

    • Use the show chassis environment cb command to check the temperature of each Control Board.

      Note:

      Exhaust A and Exhaust B correspond to temperature sensors located on the Control Boards.

    • Use the show chassis environment sib command to check the temperature of each SIB. In this example, SIB 3 status is not listed.

      Note:

      Intake, Exhaust, and Junction correspond to temperature sensors located on the sibs.

    • Use the show chassis environment fpc command to check the temperature of FPC.

      Note:

      PMB, Intake, Exhaust A, Exhaust B, TLn, and TQn correspond to temperature sensors located on the FPCs.

  9. Use the show chassis environment command to verify that the status of each component is OK.

    Note:

    Exhaust A, Exhaust B, TLn, TQn, Ambient, Intake, Exhaust, and Junction correspond to temperature sensors located on the respective hardware component.

In Table 6, the text in the column labeled ”LCD Message” appears in the display of the craft interface. The text in the column labeled “CLI Message” appears in the output from the show chassis alarms command. An alarm indicates that the temperature for a component exceeds the preconfigured temperature warm or temperature hot threshold.

Table 6: Troubleshooting Temperature Alarms

Alarm Type

LCD Message

CLI Message

Alarm Condition

Solution

Red

Sensor Failure

Temperature sensor failure

A temperature sensor failed.

Contact JTAC.

cb-number Hot

cb-numer Temperature Hot

The Control Board temperature exceeded the hot temperature threshold. If this condition persists, the Control Board shuts down.

  • Issue the show chassis routing-engine command.

FPC FPC-number PIC PIC-number Hot

FPC FPC-number PIC PIC-number Temperature Hot

The FPC temperature exceeded the hot temperature threshold. If this condition persists, the FPC shuts down.

  • Issue the show chassis fpc command.

  • Verify that the room temperature is within acceptable limits.

  • Verify that there is sufficient air flow.

  • Verify that the cooling system in the chassis is operating properly.

 

sib-number Hot

sib-number Temperature Hot

The SIB temperature exceeded the hot temperature threshold. If this condition persists, the SIB shuts down.

  • Issue the show chassis sib command.

  • Verify that the room temperature is within acceptable limits.

  • Verify that there is sufficient air flow.

  • Verify that the cooling system in the chassis is operating properly.

Yellow

cb-number Warm

cb-numberTemperature Warm

The Control Board temperature exceeded the warm temperature threshold.

  • Verify that the fans in the vertical fan tray have not failed.

  • Verify that fans in the vertical fan tray are running at appropriate speed.

  • Issue the show chassis routing-engine command.

sib-number Warm

sib-number Temperature Warm

The SIB temperature exceeded the warm temperature threshold.

  • Verify that the fans in the vertical fan tray have not failed.

  • Verify that fans in the vertical fan tray are running at appropriate speed.

  • Issue the show chassis sib command.

  • Verify that there is sufficient air flow to the rear fan tray.

FPC FPC-number PIC PIC-number Warm

FPC FPC-number PIC PIC-numberTemperature Warm

The FPC temperature exceeded the warm temperature threshold.

  • Verify that the fans in the horizontal fan trays have not failed.

  • Verify that fans in the horizontal fan trays are running at the appropriate speed.

  • Issue the show chassis fpc command.

Troubleshooting the PTX5000 Power System

Troubleshooting the PTX5000 Power Distribution Units

Problem

Description

The following alarms and LEDs indicate a problem with the power system during normal operations:

  • Table 7 lists alarms for the PDUs.

  • Table 8 lists abnormal LED states for the PDUs.

Solution

  1. Verify that the source customer-site circuit breaker has the proper current rating. See PTX5000 DC Power Electrical Safety Guidelines or PTX5000 AC Power Electrical Safety Guidelines.

  2. Verify that the power feeds are properly distributed.

    • All inputs on a DC PDU in slot PDU0 must be powered by dedicated power feeds derived from feed A, and all inputs on a DC PDU in slot PDU1 must be powered by dedicated power feeds derived from feed B. This configuration provides the commonly deployed A/B feed redundancy for the system.

    • The AC power cord on an AC power supply in slot PDU0 must be powered by a dedicated power feed derived from feed A, and The AC power cord on an AC power supply in slot PDU1 must be powered by dedicated power feeds derived from feed B. This configuration provides the commonly deployed A/B feed redundancy for the system.

  3. Issue the show chassis alarms command to check for PDU alarms. See Table 7.

  4. Check the display on the craft interface to determine the source of a yellow or red alarm). Junos OS constantly updates the screen with status information for each component.

    Note:

    From the rear of the chassis, the PDUs are labeled PDU1 and PDU0, from left to right.

  5. Check the LEDs on each PDU faceplate. See Table 8.

  6. Verify that the DC power cable or the AC power cord from the power source to the PDU is not damaged. If the insulation is cracked or broken, immediately replace the DC power cable or AC power cord.

  7. Check the status of the PDUs by issuing the show chassis environment pdu command. The state of the PDU must be online. If the output indicates that a PSM in the PDU is present, see Troubleshooting the PTX5000 Power Supply Modules.

    The following example shows output for a DC PDU.

    The following example shows output for an AC PDU.

  8. Check the input voltage to the PDUs by issuing the show chassis power command.

    In the following example for a 120-A DC PDU, Input 1 on PSM 2 is not receiving input voltage.

    In the following example for a delta AC PDU, the input voltage is within range for all PSM.

  9. If you cannot determine the cause of the problem or need additional assistance, contact customer support.

Table 7: Troubleshooting Power Distribution Unit Alarms

Alarm Type

LCD Display Message

CLI Message

Alarm Condition

Solution

Red

PDU pdu-number Not OK

PDU pdu-number Not OK

An electronic fuse has tripped.

  1. Remove and reinstall the component that caused the electronic fuse to trip.

  2. Remove and reinstall the PDU to reset the electronic fuses.

PDU pdu-number Not Recognized

PDU pdu-number Not Recognized

The PDU is not supported.

Install a supported PDU.

PDU pdu-number Absent

PDU pdu-number Absent

The PDU is not installed.

Two PDU are required at all times. Install the PDU in the empty slot.

Mix of PDUs

Mix of PDUs

Different types of PDUs are present in the chassis.

Note:

Both AC and DC PDUs might be present.

Zoning and nonzoning PDUs might be present.

Install the same type of PDUs in each slot.

PDU %d Conv Failed

PDU %d Converter Failed

One or more 36-V booster converter fails in a high-capacity PDU.

If two or more 36-V booster converter fails, fan trays fail and the router might get overheated. Therefore, when this alarm is raised, check the PDU and replace the PDU if required.

Table 8: Troubleshooting PDU LEDs

LED

State

Condition

Solution

–48 V 120 A on the 120-A DC PDU

Off

The input is not receiving voltage or is under –40 V.

  • Verify that the customer-site circuit breakers are switched on. If the customer-site circuit breakers are off, switch them on.

  • Verify that the circuit breakers on the 120-A DC PDU are switched to the on position (|) .

  • Verify that the input power tray is receiving power within the supported voltage range.

    If the customer-site circuit breakers are switched on but the input power tray is not receiving power, switch off the customer-site circuit breakers, and reinstall the DC power source cables.

DC IN on the 60-A DC PDU

Off

The input voltage is not present or is under –40 V.

Verify that the customer-site circuit breakers are switched on and that the input power tray is receiving power within the supported voltage range.

  • If the customer-site circuit breakers are off, switch them on.

  • If the customer-site circuit breakers are switched on but the input power tray is not receiving power, switch off the customer-site circuit breakers, and reinstall the DC power source cables.

DC IN on the 60-A DC PDU

Off

The input voltage is not present or is under –40 V.

Verify that the customer-site circuit breakers are switched on and that the input power tray is receiving power within the supported voltage range.

  • If the customer-site circuit breakers are off, switch them on.

  • If the customer circuit breakers are switched on but the input power tray is not receiving power, switch off the customer-site circuit breakers, and reinstall the DC power source cables.

PSM_0 through PSM_7 on the High Capacity DC PDU

Off

Input voltage is not present, or is under –20 V.

Verify that the customer-site circuit breakers are switched on and that the input terminals are receiving power within the supported voltage range.

  • If the customer-site circuit breakers are off, switch them on.

  • If the customer circuit breakers are switched on but the input terminals are not receiving power, switch off the customer-site circuit breakers, and reinstall the DC power source cables.

SW ON on the 60-A DC PDU

Off

The LED might be off for one of the following reasons:

  • The input power switches are off.

  • The host subsystem detected a problem and turned off the input power switches.

  • The input is not receiving any voltage.

  1. Verify that the input power switches on the 60-A DC PDU are switched to the on position (|) .

  2. If the input power switches on the 60-A DC PDU are switched to the on position (|), verify that the voltage is above –40 V.

CB ON on the 120-A DC PDU, delta AC PDU, or wye AC PDU

Off

The LED might be off for one of the following reasons:

  • The circuit breakers on the 120-A DC PDUare off.

  • The circuit breaker on a delta AC PDU or wye AC PDU is off.

  • The input is not receiving any voltage.

  • The host subsystem detected a problem and turned off one or more circuit breakers.

  1. Verify that the circuit breaker on the PDU are switched to the ON position (|) .

  2. Verify that the PDU is receiving input voltage within the supported range.

    • For the 120-A DC PDU, verify that the input voltage is above –40 V.

    • For the three-phase delta AC PDU or three-phase wye AC PDU, input voltage is not present, or is under –100 V.

PDU OK on the 60-a DC PDU, 120-a DC PDU, High Capacity DC PDU, delta AC PDU, and wye AC PDU

Red

The PDU has failed.

An electronic fuse might have tripped or failed.

  1. Verify that the fan trays in the power supply modules are operating and that no red alarm condition exits.

  2. Check all air filters to be sure they are functioning and providing sufficient airflow through the chassis.

  3. Issue the show chassis environment pdu command to determine the cause of the problem.

Off

The LED might be off for one of the following reasons:

  • The PDU is starting.

  • The PDU is not receiving input voltage.

  • The circuit breakers on the 120-A DC PDU might be off.

  • The circuit breaker on the three-phase delta AC PDU or three-phase wye AC PDU might be off.

  • The input power switches on the 60-A DC PDU might be off.

  1. Connect the PDU to a different power source with a new DC power cable or AC power cord.

  2. If the PDU OK LED still does not light, the PDU might be the source of the problem. Replace the PDU with a spare.

    If the PDU OK LED on the installed spare is lit green, the PDU that was replaced might be faulty. To return it for replacement, see Contact Customer Support to Obtain Return Material Authorization.

Troubleshooting the PTX5000 Power Supply Modules

Problem

Description

The following alarms, LEDs, and other conditions indicate a problem with the power supply modules during normal operations:

Solution

  1. Check the status of the PSMs by issuing the show chassis environment pdu command. The state of the PSM must be online for all installed PSMs.

  2. Issue the show chassis alarms command to check for alarms. See Table 9.

  3. Check the display on the craft interface to determine the source of a yellow or red alarm). Junos OS constantly updates the screen with status information for each component.

  4. If you cannot determine the cause of the problem or need additional assistance, contact customer support.

Table 9: Troubleshooting PSM Chassis Alarms

Alarm Type

LCD Display Message

CLI Message

Alarm Condition

Solution

Red

PSM psm-number Not OK

PSM psm-number Not OK

The specified PSM has failed. The failure could be due to bad input, overtemperature, fan failure, and so on.

  1. Use the show chassis environment pdu for more information about the failure.

  2. Check that the input for the PSM on the PDU is correctly connected.

  3. Reinstall the PSM to clear alarms.

  4. If the input is correctly connected, replace the PSM.

PSM psm-number Not Recognized

PSM psm-number Not Recognized

The PTX5000 does not support the PSM.

Replace the PSM with a supported PSM.

No Redundant Power for FPC 0-7

No Redundant Power for FPC 0-7

One or more FPCs do not have redundant PSMs. If the PSM that provides power to the FPCs fails, the FPCs will lose service.

  1. If any PSM is missing, install the missing PSM.

  2. If a PSM fails, reinstall or replace the PSM.

No Power for FPC 0-7

No Power for FPC 0-7

The FPCs will lose service.

PSM2 and PSM3 in both PDU0 and PDU1 are Absent or Not OK.

  1. Verify that the minimum number of PSMs are installed. SeeUnderstanding Normal-Capacity Power System Power Zones. For a PSM that is required but Absent, install the missing PSMs.

  2. For a required PSM that is present but Not OK or failed, reinstall or replace the PSM.

No Redundant Power for Rear Chassis

No Rdnt Pwr Rear

Redundant power is not available for the components in the rear of the chassis.

  1. If any PSM is missing, install the missing PSM.

  2. If a PSM fails, reinstall or replace the PSM.

No Redundant Power for Fan 0-2

No Redundant Power for Fan 0-2

Redundant power is not available for the fan trays.

  1. If PSM0 in either PDU is missing, install the missing PSM.

  2. If a PSM fails, reinstall or replace the PSM.

No Power for Fan 0-2

No Power for Fan 0-2

The router shuts down.

PSM0 and PSM1 in both PDU0 and PDU1 are Absent or Not OK.

  1. PSM0 is required in both PDUs. For an Absent PSM, install the missing PSM.

  2. For a PSM that is present but Not OK or failed, reinstall or replace the PSM.

PSM psm-number Absent

PSM psm-number Absent

The PSM is not installed.

Note:

This alarm is generated by the following Junos OS Releases: 12.1X48 12.3, and 13.2R1. Junos OS Release 13.2R2 and later does not generate this alarm.

If a required PSM is missing, install the PSM.

If PSMs are not missing and you continue to get the alarm, you can install Junos OS Release 13.2R2 or later.

Pwr Mgmt Non Op

Power Manager Non Operational

Different types of PSMs are present in the chassis.

Note:

Zoning and nonzoning PSMs might be present.

Install the same type of PSMs in each slot.

Troubleshooting the PTX5000 Host Subsystem

Problem

Description

The following alarms and LEDs indicate a problem with a host subsystem Control Board or Routing Engine:

Solution

To troubleshoot the host subsystems:

  1. Check the LEDs on the craft interface.

    If the red HOST0 FAIL or HOST1 FAIL LED is lit, look at the LCD on the craft interface to get more information about the cause of the problem.

  2. Check the LEDs on the faceplate of each Control Board and Routing Engine. See Troubleshooting the PTX5000 Control Boards and Troubleshooting the PTX5000 Routing Engines.

  3. Use the CLI to check for alarms. Issue the show chassis alarms command to view the alarms.

In Table 10, the text in the column labeled ”LCD Message” appears in the display of the craft interface. The text in the column labeled “CLI Message” appears in the output from the show chassis alarms command.

Table 10: Troubleshooting Host Subsystem Alarm Messages

Alarm Type

LCD Message

CLI Message

Condition

Recovery

Red

Host host-number Removed

Host host-number Removed

The Routing Engine or Control Board has been removed.

Reinstall the Routing Engine and Control Board.

Yellow

Host host-number Failure

Host host-number Failure

The Routing Engine or Control Board has been failed.

Replace the Routing Engine or Control Board.

Table 11: Troubleshooting Host Subsystem LEDs

Label

Color

State

Description

Recovery

OK

Off

Host subsystem is offline or absent.

If the host subsystem is absent, reinstall the Routing Engine or Control Board.

Bring the host subsystem online.

FAIL

Red

On steadily

Host subsystem has failed.

Replace the Routing Engine or Control Board.

Troubleshooting the PTX5000 Routing Engines

Problem

Description

The following indicate a problem with the Routing Engine:

  • Table 12 lists the LEDs.

  • An alarm indicates that a host subsystem has been removed or failed.

  • The ONLINE LED on the Routing Engine faceplate is lit steadily red.

Solution

  1. Issue the show chassis alarms command to check for alarms.

  2. Check the display on the craft interface to determine the source of a yellow or red alarm). Junos OS constantly updates the screen with status information for each component.

  3. Check the ONLINE LED on the Routing Engine faceplate. If the ONLINE LED is red, issue the chassis routing-engine command to check the status of the Routing Engine.

  4. Use the show chassis alarms command to display Routing Engine alarms.

Table 12: Troubleshooting Routing Engine LEDs

Label

Color

State

Description

Recovery

Online

Red

On steadily

Routing Engine is not functioning normally.

Replace the Routing Engine.

Off

Routing Engine is not online or not functioning normally.

Bring the Routing Engine online.

Troubleshooting the PTX5000 Control Boards

Problem

Description

The following alarms and LEDs indicate a problem with a Control Board:

Solution

To troubleshoot the Control Boards:

  1. Check the LEDs on the faceplate of each Control Board and the craft interface.

  2. Use the CLI to check for alarms. Issue the show chassis alarms command to view the alarms.

In Table 13, the text in the LCD Message column appears in the display of the craft interface. The text in the CLI Message column appears in the output from the show chassis alarms command.

Table 13: Troubleshooting Control Board Alarms

Alarm Type

LCD Message

CLI Message

Alarm Condition

Recovery

Red

CB cb-number Failure

CB cb-number Failure

A Control Board failed.

Replace the Control Board

CB cb-number Removed

CB cb-number Removed

A Control Board has been removed.

Reinstall the Control Board

Yellow

CB cb-number Ethernet Switch Failure

CB cb-number Ethernet Switch Failure

The Ethernet switch on the Control Board has failed.

Replace the Control Board.

Table 14: Troubleshooting Control Board LEDs

Label

Color

State

Description

Recovery

FAIL

Yellow

On steadily

Control Board has failed.

Replace the Control Board.

OK

Off

Control Board is offline.

Bring the Control Board online.

Troubleshooting the PTX5000 Switch Fabric

Problem

Description

The switch fabric in the PTX5000 includes the SIBs and the FPCs. A link that is in a down or error state indicates a problem with the switch fabric.

Solution

To troubleshoot the switch fabric:

  1. Verify that all nine SIBs and all installed FPCs are online. Use the show chassis fabric summary command to check for errors.

    If a SIB or FPC is Offline, see Troubleshooting the PTX5000 FPCs and Troubleshooting the PTX5000 Switch Interface Boards to correct the problem before proceeding.

  2. Use the show chassis fabric topology command to query the state of the links between the SIBs and FPCs.

    • For an FPC and a SIB that are online, the Down state indicates that the link between an FPC and a SIB is powered down. The Down state for the links can also indicate that an FPC or a SIB is offline.

    • The Error state indicates that the link between an FPC and a SIB is not operational. The partner link may be in the Down or OK state. If the state of the link is Error, replace the FPC and SIB with a spare to determine if the fault follows the FPC or SIB. After removing an FPC or a SIB, inspect the FPC or SIB connectors for bent pins. If the FPC or SIB is faulty, return it. Before installing a spare FPC or SIB, use a flashlight to inspect the midplane for bent pins. If any pins on the midplane appear to be bent, contact JTAC immediately.

  3. Display the system log messages to obtain information about link failures. The /var/log/messages file is a commonly configured destination for system log messages. To display it, issue the show log messages command. For example:

    For more information about system log messages, see the System Log Explorer.

    Your customer support representative can assist you with using the information in the system log to determine if you have a faulty SIB or FPC.

  4. Use the show chassis fabric fpcs command to check that the fabric planes are enabled.

  5. Use the show chassis fabric plane-location command to display which SIBs correspond to the planes.

  6. Use the show chassis fabric match error command.

Troubleshooting the PTX5000 Switch Interface Boards

Problem

Description

The following alarms and LEDs indicate a problem with a SIB:

Solution

To troubleshoot the SIBs:

  1. Check the SIB LEDs on the SIB faceplate and on the craft interface.

  2. Use the CLI to check for alarms. Issue the show chassis alarms command to view the alarms.

  3. Check the status of the sibs. Issue the show chassis sib command.

In Table 15, the text in the column labeled ”LCD Message” appears in the display of the craft interface. The text in the column labeled “CLI Message” appears in the output from the show chassis alarms command.

Table 15: Troubleshooting SIB Alarms

Alarm Type

LCD Message

CLI Message

Alarm Condition

Recovery

Red

SIB sib-number Failure

SIB sib-number Fault

A SIB has failed. This might affect traffic-forwarding capacity.

Replace the failed SIB.

Restart the SIB. If this does not fix the issue, contact JTAC.

Yellow

SIB sib-number FPC Links

SIB sib-number FPC Link Error

The SIB has detected link errors between the SIB and FPCs. This error may affect FPC traffic forwarding.

To isolate the problem:

  1. Replace the SIB and then the FPC. This may affect the traffic.

  2. If the problem persists, replace the SIB.

  3. If the problem still persists, replace the particular FPC that was associated with the link error.

  4. If you are unable to isolate the problem, contact JTAC. JTAC has to analyze the logs to determine further action.

SIB sib-number Cell drops

SIB sib-number Cell Drop error

The SIB has detected fabric cell drops. This might affect traffic-forwarding capacity

Restart the SIB. If this does not fix the issue, contact JTAC.

SIB sib-number Not Online

SIB sib-number Not Online

The SIB is not in an active state. This might affect the traffic-forwarding capacity.

Bring the SIB online. Issue the request chassis sib online slot slot-number command.

If this does not fix the issue, contact JTAC.

SIB sib-number Absent

SIB sib-number Absent

A SIB has been removed.

Reinstall the SIB in the chassis.

Table 16: Troubleshooting SIB LEDs

Label

Color

State

Description

OK

Off

SIB is offline or not seated properly.

FAIL

Yellow

On steadily

SIB has failed.

Troubleshooting the PTX5000 FPCs

Problem

Description

Alarms listed in Table 17 and Table 18 indicate a problem with an FPC.

Solution

To troubleshoot an FPC:

  1. Look at the display on the craft interface to check the status of the FPC and the PICs that are plugged into it.

  2. Issue the show chassis alarms command.

  3. Verify that the FPC is properly seated in the midplane. Check that each ejector handle has been turned clockwise and is tight. Use a screwdriver to check that the screws inside the ejector handles are tight.

  4. Check the status of an FPC using the following CLI command:

  5. To determine the cause of link errors between the FPCs and SIBs, use the show chassis fabric summary command to check the status of the FPCs and SIBs.

  6. Use the following show chassis fpc detail command to display more detailed information. The following examples specify a slot number, which is optional:

    The output states indicate the following:

    • Diagnostics—The FPC failed to initialize.

    • No power—The FPC is not receiving enough power. Check the chassisd messages for power allocation information.

    • Offlined due to config—Check if the FPC is configuration to be off. See Configuring a FPC to Stay Offlinepower.

    • Unresponsive—There might be a hardware failure on the FPC. Reseat the FPC and reboot.

In Table 17, the text in the LCD Message column appears in the display of the craft interface. The text in the CLI Message column appears in the output of the show chassis alarms command.

Table 17: Troubleshooting FPC Alarms

Alarm Type

LCD Message

CLI Message

Alarm Condition

Recovery

Red

FPC fpc-number unreachable PFEs detected

FPC fpc-number unreachable PFEs detected

FPC is not able to forward traffic because of a fabric failure.

Contact JTAC. JTAC needs to analyze the logs to see the reason for the fabric failure.

FPC fpc-number unreachable PFEs offlined

FPC fpc-number unreachable PFEs offlined

FPC is not able to forward traffic due to a fabric failure.

Contact JTAC. JTAC needs to analyze the logs to see the reason for the fabric failure.

Yellow

Power Budget: Minor alarm

Power Budget: No redundant power

Redundant power is not available for one or more FPCs. If the nonredundant PSM providing power to an FPC fails, the FPC will lose service.

  • If any PSM is missing, add the PSM.

  • If any PSM fails, replace the PSM.

FPC fpc-number SIB Link Error

FPC fpc-number detects link error

An FPC detected link errors on the high speeds links between an FPC and SIB. This alarm might be caused by an error either on an FPC or on a SIB. The Packet Forwarding Engine's forwarding capacity might be affected.

  1. Restart the SIB, and then the FPC. This might affect the traffic.

  2. If the problem persists, replace the FPC.

  3. If the problem still persists, replace the particular SIB that was associated with the link error.

  4. If you are unable to isolate the problem, contact JTAC. JTAC needs to analyze the logs to determine further action.

Table 18: Troubleshooting FPC LEDs

Label

Color

State

Description

Recovery

OK

-

Off

FPC is offline or not seated properly.

Reinstall the FPC and verify the FPC.

FAULT

Red

On steadily

FPC has failed.

Replace the FPC.

Troubleshooting the PTX5000 PICs and PIC Transceivers

Troubleshooting PTX5000 PICs

Problem

Description

A PIC LED lit red indicates a problem with the PIC.

Solution

To troubleshoot a PIC:

  1. Check the STATUS LED of the PIC. Look at the LEDs located on the PIC faceplate. For information about the meaning of LED states on different PICs, see the PTX Series Interface Module Reference.

  2. Issue the show chassis alarms command to check for alarms. For information about the alarms on different PICs, see the PTX Series Interface Module Reference

  3. Check the status of the PICs. issue the show chassis fpc pic-status command. The PIC slots in each FPC are numbered from 0 through 1, top to bottom:

  4. Issue the show chassis pic fpc-slot fpc-slot pic-slot pic-slot command for more information about a specific PIC.

To troubleshoot the PIC cables:

  1. Check if the optical cables are plugged into the optics properly and ensure that they are intact.

Troubleshooting PTX5000 PIC Transceivers

Problem

Description

A problem has occurred with a PIC transceiver.

Solution

To troubleshoot a PIC transceiver:

  1. Check the status of the optical transceivers. Issue the show interfaces diagnostics optics command. Alarms and warnings should be Off.