Common Operational Mode Commands To Monitor Router Components - Juniper M Series Monitoring And Troubleshooting Manual

M Series and T Series Routers Monitoring and Troubleshooting Guide
Related
Documentation

Common Operational Mode Commands To Monitor Router Components

56
Table 17: Basic Tools for Monitoring Router Components (continued)
Router Component Monitor
Tool
chassisd system log file
Swap test
JTAC
Basic Router Component Monitoring Method on page 51
NOTE: If the Forwarding Engine Board (FEB) on M5, M10 and M120 routers,
CFEB on M10i routers, SSB on M20 routers, SCB on M40 routers, SFM on
M40e and M160 routers, or SIB on M320 , T320 , T640, T1600, TX Matrix,
and TX Matrix Plus routers is not running and if you log in to the backup
Routing Engine, no information about chassis components is available through
the CLI.
To use the CLI to monitor routers:
Log in to the router.
1.
At the command prompt, type
2.
NOTE: You only need to type
the CLI should already be in operational mode.
Purpose
The chassis daemon ( chassisd
of each chassis component. To view the
the following command:
show log chassisd
To monitor the log file in real time, use the following
chassisd
command:
monitor start chassisd
To stop monitoring the
chassisd
command:
monitor stop chassisd
Remove the failed component. Replace it with one that you
know works. Check the component status. If the replacement
component works, it confirms that the original one failed.
For technical support, open a support case using the Case
Manager link at
http://www.juniper.net/support/
1-888-314-JTAC (within the United States) or 1-408-745-9500
(outside the United States). JTAC can do more extensive
testing to determine the root of the problem.
to start the Junos OS and enter operational mode.
cli
cli if you log in to the router as root. Otherwise,
Copyright © 2012, Juniper Networks, Inc.
) log file keeps track of the state
log file, use
chassisd
log file, use the following
or call