Troubleshooting T320 Router Hardware Components; Overview Of Troubleshooting Resources For The T320 Router; Troubleshooting Using The T320 Command-Line Interface - Juniper T320 Hardware Manual

CHAPTER 13
Troubleshooting T320 Router Hardware
Components

Overview of Troubleshooting Resources for the T320 Router

Troubleshooting Using the T320 Command-Line Interface

Copyright © 2010, Juniper Networks, Inc.
Overview of Troubleshooting Resources for the T320 Router on page 127
Troubleshooting the T320 Cooling System on page 132
Troubleshooting the T320 FPCs and PICs on page 133
Troubleshooting the T320 Power System on page 135
These topics describe how to troubleshoot problems with hardware components installed
in the router. If you encounter software problems, or problems with hardware components
not discussed here, contact the Juniper Networks Technical Assistance Center (JTAC)
as described in "Contacting Customer Support" on page 266.
Troubleshooting Using the T320 Command-Line Interface on page 127
Troubleshooting Using the T320 LEDs on page 128
Troubleshooting Using the T320 Chassis and Interface Alarm Messages on page 129
Troubleshooting from the Juniper Networks Assistance Center on page 132
The Junos OS command-line interface (CLI) is the primary tool for controlling and
troubleshooting T320 router hardware, the 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
and traceroute utilities.
You enter CLI commands on one or more external management devices connected to
the Routing Engine through ports on the Connector Interface Panel (CIP). The port labeled
attaches the Routing Engine to a laptop, modem, or other auxiliary device,
AUXILIARY
the port labeled CONSOLE
attaches to a management LAN.
For information about using the CLI to troubleshoot the Junos OS, see the appropriate
Junos OS configuration guide.
attaches to a system console, and the port labeled
ping
ETHERNET
127