show chassis alarms
Syntax
show chassis alarms
Syntax (MX Series Routers)
show chassis alarms <all-members> <local> <member member-id>
Syntax (SRX1500, SRX4100, and SRX4200)
show chassis alarms 1 alarms currently active Alarm time Class Description 2020-02-28 10:07:16 CST Major FPC0: PEM 0 Not Present
Syntax (SRX4600)
show chassis alarms node0: -------------------------------------------------------------------------- 2 alarms currently active Alarm time Class Description 2020-10-08 19:42:06 UTC Major FPC 0 BITS CPLD Version Mismatch 2020-10-08 19:42:06 UTC Minor PEM 1 Not Present
Syntax (SRX5400)
show chassis alarms 1 alarms currently active Alarm time Class Description 2021-04-16 17:21:02 PDT Major Too Few AC PEMs
Syntax (MX104, MX2010, MX2020, and MX2008 Universal Routing Platforms)
show chassis alarms <satellite [slot-id slot-id]>
Syntax (QFX Series)
show chassis alarms <interconnect-device name> <node-device name>
Description
Display information about the conditions that have been configured to trigger alarms.
In Junos, the chassis alarms are different from the system alarms (viewed by using
the show system alarms command). The system alarms indicate a
missing rescue configuration or software license, where valid. For more information,
see Alarm Overview.
Options
| none |
Display information about the conditions that have been configured to trigger alarms. |
| all-members |
(MX Series routers only) (Optional) Display information about alarm conditions for all the member routers of the Virtual Chassis configuration. |
| interconnect-device name |
(QFabric systems only) (Optional) Display information about alarm conditions for the Interconnect device. |
| local |
(MX Series routers only) (Optional) Display information about alarm conditions for the local Virtual Chassis member. |
| member member-id |
(MX Series routers only) (Optional) Display information about alarm conditions for the specified member of the Virtual Chassis configuration. Replace member-id variable with a value of 0 or 1. |
| node-device name |
(QFabric systems only) (Optional) Display information about alarm conditions for the Node device. |
| satellite [slot-id slot-id] |
(Junos Fusion only)(Optional) Display information about alarm conditions for the specified satellite device in a Junos Fusion, or for all satellite devices in the Junos Fusion if no satellite devices are specified. |
Additional Information
Chassis alarms are preset. You cannot modify them.
You cannot clear the alarms for chassis components. Instead, you must remedy the cause of the alarm. When a chassis alarm LED is lit, it indicates that you are running the router or switch in a manner that we do not recommend.
On routers, you can manually silence external devices connected to the alarm relay contacts by pressing the alarm cutoff button, located on the craft interface. Silencing the device does not remove the alarm messages from the display (if present on the router) or extinguish the alarm LEDs. In addition, new alarms that occur after you silence an external device reactivate the external device.
MX10003 routers do not support craft interface.
In Junos OS release 11.1 and later, alarms for fans also show the slot number of the fans in the CLI output.
In Junos OS Release 11.2 and later, the command output on EX8200 switches shows the
detailed location (Plane/FPC/PFE) for link errors in the
chassis.
In Junos OS Release 10.2 and later, an alarm is shown on T Series routers for a standby SONET Clock Generator (SCG) that is offline or absent.
You may often see the following error messages, in which only the error code is shown and no other information is provided:
Apr 12 08:04:10 send: red alarm set, device FPC 6, reason FPC 6 Major Errors - Error code: 257 Apr 12 08:04:19 send: red alarm set, device FPC 1, reason FPC 1 Major Errors - Error code: 559
To understand what CM_ALARM error codes mean, you need to first identify the structure of the CM Alarm codes. A CM_ALARM code has the following structure:
|
Bits: |
Error type: |
|
1-31 |
Major (1) |
|
0 |
Minor (0) |
According to the table above, the LSB (bit 0) identifies the Error Type (major alarm, if the bit is set and minor alarm if the bit is unset). The rest of the bits (1 - 31) identify the actual error code.
Take an example of the following error code, which was logged on a T1600:
Apr 12 08:04:10 send: red alarm set, device FPC 1, reason FPC 1 Major Errors - Error code: 559
First, you have to convert 559 to binary; that is 1000101111. The LSB in this case is 1, which means that this is a major alarm. After removing the LSB, you are left with 100010111, which is equal to 279 in decimal. This is the actual error code, its meaning can be found from the following list:
|
Chip Type: L Chip |
Code |
|
CMALARM_LCHIP_LOUT_DESRD_PARITY_ERR |
1 |
|
CMALARM_LCHIP_LOUT_DESRD_UNINIT_ERR |
2 |
|
CMALARM_LCHIP_LOUT_DESRD_ILLEGALLINK_ERR |
3 |
|
CMALARM_LCHIP_LOUT_DESRD_ILLEGALSIZE_ERR |
4 |
|
CMALARM_LCHIP_LOUT_HDRF_TOERR_ERR |
5 |
|
CMALARM_LCHIP_LOUT_HDRF_PARITY_ERR |
6 |
|
CMALARM_LCHIP_LOUT_HDRF_UCERR_ERR |
7 |
|
CMALARM_LCHIP_LOUT_NLIF_CRCDROP_ERR |
8 |
|
CMALARM_LCHIP_LOUT_NLIF_CRCERR_ERR |
9 |
|
CMALARM_LCHIP_UCODE_TIMEOUT_ERR |
10 |
|
CMALARM_LCHIP_LIN_SRCTL_ACCT_DROP_ERR |
11 |
|
CMALARM_LCHIP_LIN_SRCTL_ACCT_ADDR_SIZE_ERR |
12 |
|
CMALARM_LCHIP_SRAM_PARITY_ERR |
13 |
|
CMALARM_LCHIP_UCODE_OVFLW_ERR |
14 |
|
CMALARM_LCHIP_LOUT_HDRF_MTU_ERR |
15 |
|
Chip Type: M Chip |
Code |
|
CMALARM_MCHIP_ECC_UNCORRECT_ERR |
128 |
|
Chip Type: N Chip |
Code |
|
CMALARM_NCHIP_RDDMA_JBUS_TIMEOUT_ERR |
256 |
|
CMALARM_NCHIP_RDDMA_FIFO_OVFLW_ERR |
257 |
|
CMALARM_NCHIP_RDDMA_FIFO_UNFLW_ERR |
258 |
|
CMALARM_NCHIP_RDDMA_SIZE_ERR |
259 |
|
CMALARM_NCHIP_RDDMA_JBUS_CRC_ERR |
260 |
|
CMALARM_NCHIP_WRDMA_PKTR_ERR |
261 |
|
CMALARM_NCHIP_WRDMA_PKT_CRC_ERR |
262 |
|
CMALARM_NCHIP_WRDMA_JBUS_TIMEOUT_ERR |
263 |
|
CMALARM_NCHIP_WRDMA_FIFO_OVFLW_ERR |
264 |
|
CMALARM_NCHIP_WRDMA_FIFO_UNFLW_ERR |
265 |
|
CMALARM_NCHIP_WRDMA_PKT_LEN_ERR |
266 |
|
CMALARM_NCHIP_WRDMA_JBUS_CRC_ERR |
267 |
|
CMALARM_NCHIP_PKTR_DMA_AGE_ERR |
268 |
|
CMALARM_NCHIP_PKTR_ICELLSIG_ERR |
269 |
|
CMALARM_NCHIP_PKTR_FTTL_ERR |
270 |
|
CMALARM_NCHIP_RODR_OFFSET_OVFLW_ERR |
271 |
|
CMALARM_NCHIP_PKTR_TMO_CELL_ERR |
272 |
|
CMALARM_NCHIP_PKTR_TMO_OUTRANGE_ERR |
273 |
|
CMALARM_NCHIP_PKTR_MD_REQUEST_Q_OVFLW_ERR |
274 |
|
CMALARM_NCHIP_PKTR_DMA_BUFFER_OVFLW_ERR |
275 |
|
CMALARM_NCHIP_PKTR_GRT_OVFLW_ERR |
276 |
|
CMALARM_NCHIP_FRQ_ERR |
277 |
|
CMALARM_NCHIP_RODR_IN_Q_OVFLW_ERR |
278 |
|
CMALARM_NCHIP_DBUF_CRC_ERR |
279 |
|
Chip Type: R Chip |
Code |
|
CMALARM_RCHIP_SRAM_PARITY_ERR |
512 |
|
Chip Type: R Chip |
Code |
|
CMALARM_ICHIP_WO_DESRD_ID_ERR |
601 |
|
CMALARM_ICHIP_WO_DESRD_DATA_ERR |
602 |
|
CMALARM_ICHIP_WO_DESRD_OFLOW_ERR |
603 |
|
CMALARM_ICHIP_WO_HDRF_UCERR_ERR |
604 |
|
CMALARM_ICHIP_WO_HDRF_MTUERR_ERR |
605 |
|
CMALARM_ICHIP_WO_HDRF_PARITY_ERR |
606 |
|
CMALARM_ICHIP_WO_HDRF_TOERR_ERR |
607 |
|
CMALARM_ICHIP_WO_IP_CRC_ERR |
608 |
|
CMALARM_ICHIP_WO_IP_INTER_ERR |
609 |
|
CMALARM_ICHIP_WI_WAN_TIMEOUT_ERR |
625 |
|
CMALARM_ICHIP_WI_FAB_TIMEOUT_ERR |
626 |
|
CMALARM_ICHIP_RLDRAM_BIST_ERR |
630 |
|
CMALARM_ICHIP_SDRAM_BIST_ERR |
631 |
|
CMALARM_ICHIP_RLDRAM_PARITY_ERR |
632 |
|
CMALARM_ICHIP_SDRAM_UNCORRECT_ERR |
633 |
|
CMALARM_ICHIP_SDRAM_CORRECT_ERR |
634 |
|
CMALARM_ICHIP_FUSE_DONE_ERR |
635 |
According to the table above, the 279 error code corresponds to CMALARM_NCHIP_DBUF_CRC_ERR; this means that new CRC errors were seen on the NCHIP of this particular FPC, which is FPC as per the logs.
If you do not want to convert decimal to binary and vice versa, you may use the following shortcut:
For major alarms, the Actual Error Code = (Error Code - 1)/2, where Error Code is the code that you get in the log message. For example, if you get the following log:
Apr 12 08:04:10 send: red alarm set, device FPC 6, reason FPC 6 Major Errors - Error code: 257
Actual Error Code = (257-1)/2 = 128. Similarly, for minor alarms, Actual Error Code = (Error Code)/2
Starting in Junos OS Release 18.2R1, on MX Series routers, the show
chassis alarms output does not display error codes for PFE-related
errors. You can use the following commands to view more details of the errors
that caused the alarms:
-
show chassis errors active -
show chassis errors active detail
Required Privilege Level
view
Output Fields
Table 7 lists the
output fields for the show chassis 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. When optics are connected to the device, the output displays the transceiver name instead of interface name. |
Sample Output
- show chassis alarms (Alarms Active)
- show chassis alarms (No Alarms Active)
- show chassis alarms (Fan Tray)
- show chassis alarms (MX2010 Router)
- show chassis alarms (MX2020 Router)
- show chassis alarms (MX10004 Router)
- show chassis alarms (MX2008 Router)
- show chassis alarms (MX960, MX480, and MX240 Routers showing Major CB Failure)
- show chassis alarms (PTX10008 Router)
- show chassis alarms (Unreachable Destinations Present on a T Series Router)
- show chassis alarms (FPC Offline Due to Unreachable Destinations on a T Series Router)
- show chassis alarms (SCG Absent on a T Series Router)
- show chassis alarms (Backup Routing Engine)
- show chassis alarms (EX Series Switch)
- show chassis alarms (Alarms Active on the QFX Series and OCX Series Switches)
- show chassis alarms node-device (Alarms Active on the QFabric System)
- show chassis alarms (Alarms Active on the QFabric System)
- show chassis alarms (Alarms Active on an EX8200 Switch)
- show chassis alarms (EX9251 Switch)
- show chassis alarms (EX9253 Switch)
- show chassis alarms (MX Series for PFE reset)
- show chassis alarms (MX Series for PFE reset error)
- show chassis alarms (MX2010, MX10008, MX10016 and MX10004)
show chassis alarms (Alarms Active)
user@host> show chassis alarms 3 alarms are currently active Alarm time Class Description 2000-02-07 10:12:22 UTC Major fxp0: ethernet link down 2000-02-07 10:11:54 UTC Minor YELLOW ALARM - PEM 1 Removed 2000-02-07 10:11:03 UTC Minor YELLOW ALARM - Lower Fan Tray Removed
show chassis alarms (No Alarms Active)
user@host> show chassis alarms No alarms are currently active
show chassis alarms (Fan Tray)
user@host> show chassis 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 Failure
show chassis alarms (MX2010 Router)
user@host> show chassis alarms 7 alarms currently active Alarm time Class Description 2012-08-07 00:46:06 PDT Major Fan Tray 2 Failure 2012-08-06 18:24:36 PDT Minor Redundant feed missing for PSM 6 2012-08-06 07:41:04 PDT Minor Redundant feed missing for PSM 8 2012-08-04 02:42:06 PDT Minor Redundant feed missing for PSM 5 2012-08-03 21:14:24 PDT Minor Loss of communication with Backup RE 2012-08-03 12:26:03 PDT Minor Redundant feed missing for PSM 4 2012-08-03 10:40:18 PDT Minor Redundant feed missing for PSM 7
show chassis alarms (MX2020 Router)
user@host> show chassis alarms 1 alarms currently active Alarm time Class Description 2012-10-03 12:14:59 PDT Minor Plane 0 not online
show chassis alarms (MX10004 Router)
user@host> show chassis alarms 2 alarms currently active Alarm time Class Description 2022-07-05 20:34:40 PDT Major Fan Tray 0 EEPROM Read Error 2021-17-05 11:06:47 PST Minor Check plane 0 Fabric Chip
user@host> show chassis alarms | match PEM 2021-11-12 13:19:35 UTC Major PEM 2 Not Supported
user@host> show system alarms | match Fan 2021-09-27 19:13:15 PDT Major Fan Tray 0 Model Not Supported
show chassis alarms (MX2008 Router)
user@host>show chassis alarms No alarms currently active
show chassis alarms (MX960, MX480, and MX240 Routers showing Major CB Failure)
A major CB 0 failure alarm occurs in the event of a bad CB (unknown or mismatched CBs do not trigger this alarm in Junos Release OS 12.3R9 and later). Following GRES or recovery, if the hardware issue persists, the traffic moves to the good CB and continues. If the alarm was triggered by something transient like a power zone budget on GRES, bringing the CB back online can clear the alarm. Otherwise, replace the bad CB. Note that fabric link speed is not impacted by an offline SCB. The alarm migh be raised on CB0, CB1, and CB2.
user@host> show chassis alarms 6 alarms currently active Alarm time Class Description 2014-10-31 16:49:41 EDT Major PEM 3 Not OK 2014-10-31 16:49:41 EDT Major PEM 2 Not OK 2014-10-31 16:49:31 EDT Major CB 0 Failure 2014-10-31 16:49:31 EDT Minor CB 0 Fabric Chip 0 Not Online 2014-10-31 16:49:31 EDT Minor CB 0 Fabric Chip 1 Not Online 2014-10-31 16:49:31 EDT Minor Backup RE Active
show chassis alarms (PTX10008 Router)
user@host>show chassis alarms 12 alarms currently active Alarm time Class Description 2017-05-09 01:38:55 PDT Minor Loss of communication with Backup RE 2017-05-05 06:49:57 PDT Major FPC 5 LCPU Temp Sensor Access Failed 2017-05-05 06:49:57 PDT Major FPC 5 PE2 Temp Sensor Hot 2017-05-05 06:49:57 PDT Major FPC 5 PE1 Temp Sensor Hot 2017-05-05 06:49:57 PDT Major FPC 5 PE0 Temp Sensor Hot 2017-05-05 06:49:57 PDT Major FPC 5 Exhaust-C Temp Sensor Hot 2017-05-05 06:49:57 PDT Major FPC 5 Exhaust-B Temp Sensor Hot 2017-05-05 06:49:57 PDT Major FPC 5 Exhaust-A Temp Sensor Hot 2017-05-05 06:49:57 PDT Major FPC 5 Intake-B Temp Sensor Access Failed 2017-05-05 06:49:57 PDT Major FPC 5 Intake-A Temp Sensor Access Failed 2017-05-05 06:49:57 PDT Major Fan Tray 0 Fan 5 running at lower speed 2017-05-05 06:49:57 PDT Major Fan Tray 0 Fan 4 running at lower speed
show chassis alarms (Unreachable Destinations Present on a T Series Router)
user@host> show chassis alarms 10 alarms currently active Alarm time Class Description 2011-08-30 18:43:53 PDT Major FPC 7 has unreachable destinations 2011-08-30 18:43:53 PDT Major FPC 5 has unreachable destinations 2011-08-30 18:43:52 PDT Major FPC 3 has unreachable destinations 2011-08-30 18:43:52 PDT Major FPC 2 has unreachable destinations 2011-08-30 18:43:52 PDT Minor SIB 0 Not Online 2011-08-30 18:43:33 PDT Minor SIB 4 Not Online 2011-08-30 18:43:28 PDT Minor SIB 3 Not Online 2011-08-30 18:43:05 PDT Minor SIB 2 Not Online 2011-08-30 18:43:28 PDT Minor SIB 1 Not Online 2011-08-30 18:43:05 PDT Major PEM 1 Not Ok
show chassis alarms (FPC Offline Due to Unreachable Destinations on a T Series Router)
user@host> show chassis alarms 10 alarms currently active Alarm time Class Description 2011-08-30 18:43:53 PDT Major FPC 7 offline due to unreachable destinations 2011-08-30 18:43:53 PDT Major FPC 5 offline due to unreachable destinations 2011-08-30 18:43:52 PDT Major FPC 3 offline due to unreachable destinations 2011-08-30 18:43:52 PDT Major FPC 2 offline due to unreachable destinations 2011-08-30 18:43:52 PDT Minor SIB 0 Not Online 2011-08-30 18:43:33 PDT Minor SIB 4 Not Online 2011-08-30 18:43:28 PDT Minor SIB 3 Not Online 2011-08-30 18:43:05 PDT Minor SIB 2 Not Online 2011-08-30 18:43:28 PDT Minor SIB 1 Not Online 2011-08-30 18:43:05 PDT Major PEM 1 Not Ok
show chassis alarms (SCG Absent on a T Series Router)
user@host> show chassis alarms 4 alarms currently active Alarm time Class Description 2011-01-23 21:42:46 PST Major SCG 0 NO EXT CLK MEAS-BKUP SCG ABS
show chassis alarms (Backup Routing Engine)
user@host> show chassis alarms 2 alarms are currently active Alarm time Class Description 2005-04-07 10:12:22 PDT Minor Host 1 Boot from alternate media 2005-04-07 10:11:54 PDT Major Host 1 compact-flash missing in Boot List
show chassis alarms (EX Series Switch)
user@switch> show chassis alarms 4 alarms currently active Alarm time Class Description 2014-03-12 15:36:09 UTC Minor Require a Fan Tray upgrade 2014-03-12 15:00:02 UTC Major PEM 0 Input Failure 2014-03-12 15:00:02 UTC Major PEM 0 Not OK 2014-03-12 14:59:51 UTC Minor Host 1 Boot from alternate media
show chassis alarms (Alarms Active on the QFX Series and OCX Series Switches)
user@switch> show chassis alarms 1 alarms currently active Alarm time Class Description 2012-03-05 2:10:24 UTC Major FPC 0 PEM 0 Airflow not matching Chassis Airflow
show chassis alarms node-device (Alarms Active on the QFabric System)
user@switch> show chassis alarms node-device Test node-device ED3694 3 alarms currently active Alarm time Class Description 2011-08-24 16:04:15 UTC Major Test:fte-0/1/2: Link down 2011-08-24 16:04:14 UTC Major Test:fte-0/1/0: Link down 2011-08-24 14:21:14 UTC Major Test PEM 0 is not supported/powered
show chassis alarms (Alarms Active on the QFabric System)
user@switch> show chassis alarms IC-1: -------------------------------------------------------------------------- 1 alarms currently active Alarm time Class Description 2011-08-24 16:04:15 UTC Minor Backup RE Active Test: -------------------------------------------------------------------------- 3 alarms currently active Alarm time Class Description 2011-08-24 16:04:15 UTC Major Test:fte-0/1/2: Link down 2011-08-24 16:04:14 UTC Major Test:fte-0/1/0: Link down 2011-08-24 14:21:14 UTC Major Test PEM 0 is not supported/powered SNG-0: -------------------------------------------------------------------------- NW-NG-0: -------------------------------------------------------------------------- 1 alarms currently active Alarm time Class Description 2011-08-24 15:49:27 UTC Major Test PEM 0 is not supported/powered
show chassis alarms (Alarms Active on an EX8200 Switch)
user@switch> show chassis alarms 6 alarms currently active Alarm time Class Description 2010-12-02 19:15:22 UTC Major Fan Tray Failure 2010-12-02 19:15:22 UTC Major Fan Tray Failure 2010-12-02 19:15:14 UTC Minor Check CB 0 Fabric Chip 1 on Plane/FPC/PFE: 1/5/0, 1/5/1, 1/5/2, 1/5/3, 1/7/0, 1/7/1, 1/7/2, 1/7/3, 2/5/0, 2/5/1, ... 2010-12-02 19:15:14 UTC Minor Check CB 0 Fabric Chip 0 on Plane/FPC/PFE: 1/5/0, 1/5/1, 1/5/2, 1/5/3, 1/7/0, 1/7/1, 1/7/2, 1/7/3, 2/5/0, 2/5/1, ... 2010-12-02 19:14:18 UTC Major PSU 1 Output Failure 2010-12-02 19:14:18 UTC Minor Loss of communication with Backup RE
show chassis alarms (EX9251 Switch)
user@switch> show chassis alarms 2 alarms currently active Alarm time Class Description 2018-03-08 05:13:10 PST Major PEM 0 Not Powered 2018-03-08 05:13:10 PST Major Fan Tray 2 is not present
show chassis alarms (EX9253 Switch)
user@switch> show chassis alarms 6 alarms currently active Alarm time Class Description 2018-03-07 01:09:01 PST Major Power Budget:Insufficient Power 2018-03-06 23:56:34 PST Minor Loss of communication with Backup RE 2018-02-15 00:48:10 PST Minor PEM 3 Not Present 2018-02-15 00:48:10 PST Minor PEM 2 Not Present 2018-02-15 00:48:07 PST Major PEM 4 Not Powered 2018-02-15 00:48:07 PST Major PEM 1 Not Powered
show chassis alarms (MX Series for PFE reset)
user@host> show chassis alarms 1 alarm currently active Alarm time Class Description 2021-01-04 11:20:42 PST Major FPC 0 PFE 0 reset initiated
show chassis alarms (MX Series for PFE reset error)
user@host> show chassis alarms 1 alarm currently active Alarm time Class Description 2021-01-04 11:20:42 PST Major FPC 0 PFE 0 reset error
show chassis alarms (MX2010, MX10008, MX10016 and MX10004)
An optics configuration mismatch alarm may be triggered when there is a discrepancy between the configured speed of an interface and the supported speed of the optic. This alarm indicates that the optic installed in the specified FPC is incompatible with the speed configured on the interface. This can be observed through the following output:
root@user> run show chassis alarms 2 alarms currently active Alarm time Class Description 2024-10-14 21:54:38 PDT Minor FPC 5 Optics does not support configured speed 2024-10-14 17:07:23 PDT Minor FPC 0 Optics does not support configured speed
- show chassis alarms (Active Alarm to Indicate Status of the Bad SCB Clock on MX Series)
- show chassis alarms (MX10003 Router)
- show chassis alarms (Alarms active on a MX10008 Router)
- show chassis alarms (ACX Series)
show chassis alarms (Active Alarm to Indicate Status of the Bad SCB Clock on MX Series)
user@host> show chassis alarms 1 alarm currently active Alarm time Class Description 2013-08-06 07:48:35 PDT Major CB 0 19.44 MHz clock failure
show chassis alarms (MX10003 Router)
If LCMD is down on the backup RE, then the following alarm is seen on the primary.
user@host> show chassis alarms 1 alarm currently active Alarm time Class Description 2017-05-09 13:26:27 PDT Major VMHost RE 1 host application failed
If LCMD is down on the primary, then following alarms are displayed.
user@host> show chassis alarms 3 alarms currently active Alarm time Class Description 2017-05-10 14:12:21 PDT Major VMHost RE 0 host application failed 2017-05-10 14:12:16 PDT Minor LCM Peer Absent 2017-05-09 13:26:27 PDT Major VMHost RE 1 host application failed
If the LCMD process is crashing on the primary, the system will switchover after one minute provided the backup RE LCMD connection is stable. The system will not switchover under the following conditions: if the backup RE LCMD connection is unstable or if the current primary just gained primary role. When the primary has just gained primary role, the switchover happens only after four minutes.
The LCM peer connection un-stable alarm is raised when the LCMD-CHASD IPC communication flaps three times within a small interval of two to three minutes. Once LCM peer connection un-stable alarm is raised, the connection status is monitored for two minutes.
user@host> show chassis alarms 7 alarms currently active Alarm time Class Description 2017-05-29 10:12:17 PDT Minor LCM Peer Connection un-stable 2017-05-29 09:04:17 PDT Minor PEM 8 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 9 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 7 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 3 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 0 Not Powered 2017-05-29 09:04:08 PDT Minor Loss of communication with Backup RE
If there are no more connection flaps within this two minutes time interval, the LCM peer connection un-stable alarm is cleared.
6 alarms currently active Alarm time Class Description 2017-05-29 09:04:17 PDT Minor PEM 8 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 9 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 7 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 3 Not Powered 2017-05-29 09:04:17 PDT Minor PEM 0 Not Powered 2017-05-29 09:04:08 PDT Minor Loss of communication with Backup RE
A major alarm is raised even if there is on one PLL lock error, and this alarm can be cleared only through an FPC restart.
user@host> show chassis alarms 4 alarms currently active Alarm time Class Description 2017-02-16 09:06:06 PDT Major FPC 0 Major Errors 2017-02-16 09:08:40 PDT Major FPC 1 Major Errors 2017-02-16 09:11:47 PST Minor Fan Tray 3 Pair 1 Outer Fan running at over speed 2017-02-16 09:11:47 PST Minor Fan Tray 3 Pair 1 Inner Fan running at over speed
show chassis alarms (Alarms active on a MX10008 Router)
user@host> show chassis alarms 13 alarms currently active Alarm time Class Description 2018-07-17 05:48:08 PDT Major FPC 2 I2C Failure 2018-07-17 05:47:02 PDT Minor Mixed Master and Backup RE types 2018-07-17 05:47:01 PDT Major Fan Tray 0 Fan 5 Failed 2018-07-17 05:47:01 PDT Major Fan Tray 0 Fan 4 Failed 2018-07-17 05:47:01 PDT Minor PEM 5 Not Powered 2018-07-17 05:47:01 PDT Minor PEM 5 Feed 2 has no input source 2018-07-17 05:47:01 PDT Minor PEM 5 Feed 1 has no input source 2018-07-17 05:47:01 PDT Minor PEM 4 Not Powered 2018-07-17 05:47:01 PDT Minor PEM 4 Feed 2 has no input source 2018-07-17 05:47:01 PDT Minor PEM 4 Feed 1 has no input source 2018-07-17 05:47:01 PDT Minor PEM 3 Not Powered 2018-07-17 05:47:01 PDT Minor PEM 3 Feed 2 has no input source 2018-07-17 05:47:01 PDT Minor PEM 3 Feed 1 has no input source 2018-07-17 05:47:01 PDT Major CB 0 external-1 LOS
show chassis alarms (ACX Series)
user@host> show chassis alarms Alarm time Class Description 2011-01-23 21:42:46 PST Major PTP Local Clock OOS 2011-01-23 21:42:46 PST Major PTP No Foreign Master 2011-01-23 21:42:46 PST Major Chassis Loss of all Equipment Clock Synch References 2011-01-23 21:42:46 PST Major Chassis Loss of Equipment Clock Synch Reference 1 2011-01-23 21:42:46 PST Major Chassis Loss of Equipment Clock Synch Reference 2 2011-01-23 21:42:46 PST Major Equipment Clock QL Below Threshold 2011-01-23 21:42:46 PST Major TOD Input A Signal Fail 2011-01-23 21:42:46 PST Major 1PPS lost 2011-01-23 21:42:46 PST Major SyncE Port incompatible Media Type
show chassis alarms (MX10008, MX10016, PTX10008, PTX10016, QFX10008,QFX10016) (Junos OS Release)
Starting Junos OS Evolved Release 21.2R1, if PEM or FET Failure detected, a major
alarm is raised, and the identified PSM will shutdown or raise alarms as per
predefined configuration in the set chassis thermal-events
fet-failure-check command.
For FET failure detection and action, the show chassis alarm
output displays a major alarm and information if PSM is shutdown.
For example, for the show chassis configuration:
user@root> show chassis thermal-health-check
{
fet-failure-check;
action-onfail auto-shutdown;
}The output is displayed as follows:
user@root> show chassis alarms Alarm time Class Description 2007-04-10 02:33:11 PDT Minor No Redundant Power for System 2007-04-10 02:33:08 PDT Minor PDU 1 PSM 4 Thermal Check brought it Down 2007-04-10 02:33:08 PDT Major PDU 1 PSM 4 Not OK 2007-04-10 02:33:08 PDT Minor PDU 0 PSM 4 Thermal Check brought it Down 2007-04-10 02:33:08 PDT Major PDU 0 PSM 4 Not OK 2007-04-10 02:32:03 PDT Minor PDU 1 PSM 3 Thermal Check brought it Down 2007-04-10 02:32:03 PDT Major PDU 1 PSM 3 Not OK ... ...
show chassis alarms (ACX7024)
On ACX7024 device, when edit chassis pem minimum is set to 1, The
following output is displayed. The PSM absent alarm is removed only after a
reboot:
user@root> show chassis alarms 4 alarms currently active Alarm time Class Description 2022-05-15 09:12:31 PDT Major No Redundant Power for System 2022-05-15 09:12:31 PDT Major PSM 1 Input1 Failed 2022-05-15 09:12:31 PDT Major PSM 1 Input Failed 2022-05-15 09:12:34 PDT Major PSM 0 Absent 2022-06-04 05:30:11 PDT Minor RE 0 Secure boot disabled or not enforced
When the default PSU 1+1 redundancy mode is active, the following output is displayed:
user@root> show chassis alarms 6 alarms currently active Alarm time Class Description 2022-05-15 09:12:31 PDT Major No Redundant Power for System 2022-05-15 09:12:31 PDT Major PSM 1 Input1 Failed 2022-05-15 09:12:31 PDT Major PSM 1 Input Failed 2022-06-04 05:30:19 PDT Major PSM 0 Absent 2022-06-04 05:30:11 PDT Minor RE 0 Secure boot disabled or not enforced 2022-06-04 05:31:54 PDT Major chassis No Redundant Power
show chassis alarms (MX304 with Optic Modules)
user@host> show chassis alarms 4 alarms currently active Alarm time Class Description 2024-12-13 05:51:00 UTC Minor FPC 0 xcvr-0/0/0 Temp Sensor Warm 2024-12-12 22:37:43 UTC Minor FPC 0 Optics does not support configured speed 2024-12-11 16:07:10 UTC Major SFB 0 I2CS CPLD image outdated 2024-12-11 16:04:52 UTC Major PEM 0 is Absent
show chassis alarms (PTX10008 with Optic Modules)
user@host> show chassis alarms 30 alarms currently active Alarm time Class Description 2024-10-17 08:06:28 PDT Major FPM 0 Ideeprom read failure 2024-10-17 08:09:42 PDT Minor FPC 4 Secure boot disabled or not enforced 2024-10-17 17:02:56 PDT Minor 1 VRF Scale(273) requires a license 2024-10-17 17:02:56 PDT Minor gre_tunnel(278) usage requires a license 2024-10-17 17:02:41 PDT Major xcvr-4/0/1: Optics Temperature Hot ...
Release Information
Command introduced before Junos OS Release 7.4.
satellite option introduced in Junos OS Release 14.2R3 for Junos
Fusion.
Command introduced in Junos OS Release 18.2R1 for EX9253 Switches and MX10008 Universal Routing Platforms.