Troubleshooting Components; M320 Troubleshooting Resources Overview - Juniper M320 Hardware Manual

CHAPTER 32

Troubleshooting Components

M320 Troubleshooting Resources Overview

Copyright © 2015, Juniper Networks, Inc.
M320 Troubleshooting Resources Overview on page 283
M320 LED Overview on page 284
M320 Chassis and Interface Alarm Messages on page 285
Troubleshooting the M320 Cooling System on page 287
Troubleshooting the M320 FPCs on page 289
Troubleshooting the M320 Fuses on page 290
Troubleshooting the M320 PICs on page 291
Troubleshooting the M320 Power System on page 292
To troubleshoot an M320 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 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 on the CIP—When a red or yellow
alarm occurs, it trips the corresponding alarm relay contact on the CIP.
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.
283