Table 104: Control Board Leds - Juniper M Series Monitoring And Troubleshooting Manual

M Series and T Series Routers Monitoring and Troubleshooting Guide
Display Control Board Error Messages in the System Log File
Purpose
Action
Sample Output
Meaning
Display Control Board Error Messages in the Chassis Daemon Log File
Purpose
Action
Sample Output
392

Table 104: Control Board LEDs

Label Color
Green
OK
FAIL Amber
MASTER Blue
To determine the details of the Control Board error messages in the system log file.
To check for Control Board error messages in the system log
following command:
user@host> show log messages | match cb
Check for messages at least 5 minutes before and after a Control Board alarm occurs.
user@host> show log messages | match cb
May 18 16:04:06 routerhost chassisd[4836]: CHASSISD_FRU_OFFLINE_NOTICE: CB 1
offline: Offlined
The messages system log file records the time the failure or event occurred, the severity
level, a code, and a message description. You can also use the
command to see error messages that are generated when a Control Board fails or is
cb
offline. Use this information to diagnose a Control Board problem and to let the Juniper
Networks Technical Assistance Center (JTAC) know what error messages were generated
and the router events that occurred before and after the problem. For more information
about system log messages, see the Junos OS System Log Messages Reference.
To determine the details of the Control Board error messages in the chassis daemon log
file.
To display Control Board error messages in the
command:
user@host> show log chassisd | match cb
user@host> show log chassisd | match cb
May 18 16:04:06 CHASSISD_FRU_OFFLINE_NOTICE: Taking CB 1 offline: Offlined
May 18 16:04:06 GBUS cmd to CB#1 [0x9], Green LED Off [0x1a]
State Description
On steadily Control Board is online and functioning
normally.
On steadily Control Board has failed.
On steadily Control Board is functioning as master.
messages
log file, use the following
chassisd
Copyright © 2012, Juniper Networks, Inc.
file, use the
show log messages | match