show system alarms
Syntax
show system alarms
Description
Display active system alarms. System alarms are software or operating system software related alarms. System alarms indicate a missing rescue configuration or software license, where valid. 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.
Chassis alarms indicate a failure on the device or one of its components. For example, chassis alarms include an alarm for fan tray failure on a device, or if an FPC on a device is unreachable. Chassis alarms are preset and cannot be modified.
Options
This command has no options.
Additional Information
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.
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 null route condition. When the degraded fabric alarm is raised on the source FPC, you can take remedial action to avoid a fabric null route 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.
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
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.
Field Name |
Field Description |
|---|---|
|
Date and time the alarm was first recorded. |
|
Severity class for this alarm: |
|
Information about the alarm. |
Sample Output
- show system alarms
- show system alarms
- show system alarms (Fan Tray)
- show system alarms (QFX Series and OCX Series)
- show system alarms (EX6200)
- show system alarms (SRX5400, SRX5600, and SRX5800)
- show system alarms (TX Matrix Plus router with 3D SIBs)
- show system alarms (Junos OS Evolved with PCI corrected error)
- show system alarms (Junos OS Evolved when FEB is absent)
show system alarms
user@host> show system alarms
2 alarms currently active
Alarm time Class Description
2005-02-24 17:29:34 UTC Minor IPsec VPN tunneling usage requires a license
2005-02-24 17:29:34 UTC Minor Rescue configuration is not sent
show system alarms
user@host> show system alarms 5 alarms currently active Alarm time Class Description 2012-05-29 16:47:18 UTC Major /var partition usage crossed critical threshold 2012-05-29 16:47:18 UTC Minor /var partition usage crossed high threshold 2012-05-29 16:47:18 UTC Major /root partition usage crossed critical threshold 2012-05-29 16:47:18 UTC Minor /root partition usage crossed high threshold 2012-05-29 16:47:18 UTC Minor Rescue configuration is not set
show system alarms (Fan Tray)
user@host> show system alarms
4 alarms currently active
Alarm time Class Description
2010-11-11 20:27:38 UTC Major Side Fan Tray 7 Failure
2010-11-11 20:27:13 UTC Minor Side Fan Tray 7 Overspeed
2010-11-11 20:27:13 UTC Major Side Fan Tray 5 Failure
2010-11-11 20:27:13 UTC Major Side Fan Tray 0 Failureshow system alarms (QFX Series and OCX Series)
user@switch> show system alarms 2 alarms currently active Alarm time Class Description 2005-02-24 17:29:34 UTC Minor Rescue configuration is not sent
show system alarms (EX6200)
user@switch> show system alarms 2 alarms currently active Alarm time Class Description 2013-04-05 16:51:41 PDT Major FPC 8 internal link errors detected 2013-04-04 18:05:35 PDT Minor Rescue configuration is not set
show system alarms (SRX5400, SRX5600, and SRX5800)
This command displays the active alarms due to L2 channel error.
user@switch> show system alarms 1 alarm currently active Alarm time Class Description 2021-01-16 20:42:40 PST Minor NSD l2 channel error on physical interfaces
show system alarms (TX Matrix Plus router with 3D SIBs)
user@router> show system alarms sfc0-re0: -------------------------------------------------------------------------- 2 alarms currently active Alarm time Class Description 2013-05-08 18:13:58 UTC Major LCC 0 Major Errors 2013-05-08 17:48:46 UTC Major LCC 7 Major Errors lcc0-re1: -------------------------------------------------------------------------- 1 alarm currently active Alarm time Class Description 2013-05-08 18:19:24 UTC Major FPC 1 degraded fabric condition detected lcc7-re0: -------------------------------------------------------------------------- 1 alarm currently active Alarm time Class Description 2013-05-08 18:19:24 UTC Major FPC 7 degraded fabric condition detected
show system alarms (Junos OS Evolved with PCI corrected error)
user@router> show system alarms 10 alarms currently active Alarm time Class Description 2019-02-01 02:20:09 PST Major PCI Corrected error on dev 0000:00:01.0
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.
show system alarms (Junos OS Evolved when FEB is absent)
user@router> show system alarms 31 alarms currently active Alarm time Class Description 2023-01-31 11:25:49 UTC Major FEB 1 Absent 2023-01-31 10:09:26 UTC Major Chassis No Redundant Power
Starting in Junos OS Evolved Release 23.1R1, an alarm will be raised when a RCB is present but its mated FEB is absent.
Release Information
Command introduced before Junos OS Release 7.4.