Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show system alarms

 

Syntax

Release Information

Command introduced before Junos OS Release 7.4.

Command introduced in Junos OS Release 9.0 for EX Series switches.

Command introduced in Junos OS Release 11.1 for the QFX Series.

Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

Description

Display active system alarms.

Options

This command has no options.

Additional Information

System alarms are preset. You cannot modify them, although you can configure them to appear automatically in the J-Web user interface or CLI. They include a configuration alarm that appears when no rescue configuration alarm is set and a license alarm that appears when a software feature is configured and no valid license is configured for the feature. You can also determine when a license will expire from syslog messages that appear starting from four weeks before expiry of the license. On EX6200 switches, an alarm can be triggered by an internal link error.

The the logic for multiple feature licenses is based on the highest validity among the licenses. Also, for capacity non-cumulative, exclusive type licenses (such as for scale), the logic is based on the highest validity of the license.

Note

As of Junos OS Release 17.3R1, the logic for multiple capacity type licenses and when their expiry raises alarms was changed. Before, the behavior had alarms and syslog messages for expiring licenses raised based on the highest validity, which would mislead users in the case of a license expiring earlier than the highest validity license. The newer behavior has the about-to-expire logic based on the first expiring license.

In Junos OS release 11.1 and later, alarms for fans also show the slot number of the malfunctioning fans in the CLI output.

Starting with Junos OS Release 13.2, you can view degraded fabric alarms on a routing matrix based on TX Matrix Plus router with 3D SIBs. The alarm indicates that the source FPC is running with a degraded fabric condition. This alarm is an early warning of a possible fabric black-hole condition. When the degraded fabric alarm is raised on the source FPC, you can take remedial action to avoid a fabric black-hole condition. The degraded fabric alarm is raised on the source FPC if both the following conditions are met:

  • The active Packet Forwarding Engine destinations are reachable on one or no active switching planes.

  • At least one of the inactive switching planes has a fault that causes the destination Packet Forwarding Engine to become unreachable.

Note

On Junos OS Evolved, the show system alarms command does not display the error number. Instead, you can use the show chassis fpc errors detail and the show system errors commands to list the errors that contribute to a failure.

Required Privilege Level

view

Related Documentation

List of Sample Output

show system alarms

show system alarms (Fan Tray)

show system alarms (QFX Series and OCX Series)

show system alarms (EX6200)

show system alarms (TX Matrix Plus router with 3D SIBs)

show system alarms (Junos OS Evolved)

Output Fields

Table 1 lists the output fields for the show system alarms command. Output fields are listed in the approximate order in which they appear.

Table 1: show system alarms Output Fields

Field Name

Field Description

Alarm time

Date and time the alarm was first recorded.

Class

Severity class for this alarm: Minor or Major.

Description

Information about the alarm.

Sample Output

show system alarms

user@host> show system alarms

show system alarms (Fan Tray)

user@host> show system alarms

show system alarms (QFX Series and OCX Series)

user@switch> show system alarms

show system alarms (EX6200)

user@switch> show system alarms

show system alarms (TX Matrix Plus router with 3D SIBs)

user@router> show system alarms

show system alarms (Junos OS Evolved)

user@router> show system alarms

Starting in Junos OS Evolved Release 19.1R1, the alarm string for PCI Corrected error is shown as PCI Corrected error on dev 0000:00:01.0. Also, a PCI uncorrectable error does not cause a reboot, but only raises an alarm.