Troubleshooting Components; Ptx5000 Troubleshooting Resources Overview; Chapter 37 Troubleshooting Components - Juniper PTX5000 Hardware Manual

CHAPTER 37

Troubleshooting Components

PTX5000 Troubleshooting Resources Overview

Copyright © 2017, Juniper Networks, Inc.
PTX5000 Troubleshooting Resources Overview on page 503
PTX5000 LED Overview on page 504
PTX5000 Alarm Messages Overview on page 505
Troubleshooting the PTX5000 Centralized Clock Generators on page 507
Troubleshooting the PTX5000 Cooling System on page 509
Troubleshooting the PTX5000 Host Subsystem on page 520
Troubleshooting the PTX5000 Routing Engines on page 522
Troubleshooting the PTX5000 Control Boards on page 524
Troubleshooting the PTX5000 FPCs on page 526
Troubleshooting PTX5000 PICs and PIC Cables on page 529
Troubleshooting the PTX5000 Power System on page 535
Troubleshooting the PTX5000 Switch Fabric on page 546
Troubleshooting the PTX5000 Switch Interface Boards on page 548
To troubleshoot a packet transport router, 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 packet transport router.
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
503