Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Gather Component Alarm Information

 

Purpose

When you obtain information about component alarms and error messages, you determine when a problem with a component first appeared and the details of the situation.

To gather component alarm information, follow these steps:



Display the Current Router Alarms

Purpose

To determine the details of the alarms and when they first appeared in the component.

Action

To display the current router component alarms, use the following CLI command:

The command output displays the number of alarms currently active, the time when the alarm began, the severity level, and an alarm description. Note the date and time of an alarm so that you can correlate it with error messages in the messages system log file.

For examples of sample output, see the Junos System Basics and Services Command Reference.



Display Error Messages in the Messages Log File

Purpose

To determine the details of the error messages in the Messages Log File.

Action

To display router component error messages in the messages system log file, use the following CLI command:

The messages system log file records the time the failure or event occurred, the severity level, a code, and a message description. Error messages in the messages system log file are logged at least 5 minutes before and after the alarm event.

To search for specific information in the log file, use the | match component-name command; for example, use show log messages | match fpc. If there is a space in the component name, enclose the component name in quotation marks; for example, | match “power supply”.

To search for multiple items in the log file, use the | match command followed by the multiple items, separated by the | (pipe), and enclosed in quotation marks; for example, | match “fpc | sfm | kernel | tnp”.

To monitor the messages file in real time, use the monitor start messages CLI command. This command displays the new entries in the file until you stop monitoring by using the monitor stop messages CLI command.

For more information about system log messages, see the Junos System Log Messages Reference.



Display Error Messages in the Chassis Process Log File

Purpose

To determine the details of the error messages in the Chassis Process Log File.

Action

To display router component errors in the chassis process (chassisd) system log file, use the following CLI command:

The chassis process (chassisd) log file tracks the state of each chassis component. For examples of sample output, see the Junos System Basics and Services Command Reference.

To search for specific information in the log file, use the | match component-name command; for example, show log messages | match fpc. If there is a space in the component name, enclose the component name in quotation marks; for example, | match “power supply”.

To search for multiple items in the log file, use the | match command followed by the multiple items, separated by the | (pipe), and enclosed in quotation marks; for example, | match “fpc | sfm | kernel | tnp”.

To monitor the chassisd file in real time, use the monitor start chassisd CLI command. This command displays the new entries in the file until you stop monitoring by using the monitor stop chassisd CLI command.