Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

show chassis alarms

 

List of Syntax

Syntax

Syntax (MX Series Routers)

Syntax (TX Matrix Routers)

Syntax (TX Matrix Plus Routers)

Syntax (MX104, MX2010, MX2020, and MX2008 Universal Routing Platforms)

Syntax (MX10003, MX204, MX10008, OCX Series, PTX Series, ACX Series, EX9251, and EX9253)

Syntax (QFX Series)

Syntax

Syntax (MX Series Routers)

Syntax (TX Matrix Routers)

Syntax (TX Matrix Plus Routers)

Syntax (MX104, MX2010, MX2020, and MX2008 Universal Routing Platforms)

Syntax (MX10003, MX204, MX10008, OCX Series, PTX Series, ACX Series, EX9251, and EX9253)

Syntax (QFX Series)

Release Information

Command introduced before Junos OS Release 7.4.

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

sfc option introduced in Junos OS Release 9.6 for the TX Matrix Plus router.

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

Command introduced in Junos OS Release 12.1 for the PTX Series Packet Transport Routers.

Command introduced in Junos OS Release 12.2 for the ACX Series Universal Metro Routers.

Command introduced in Junos OS Release 12.3 for MX 2010 and MX2020 Universal Routing Platforms.

Command introduced in Junos OS Release 13.2 for MX104 Universal Routing Platforms.

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

satellite option introduced in Junos OS Release 14.2R3 for Junos Fusion.

Command introduced in Junos OS Release 17.2 for MX2008 and PTX10008 Routers.

Command introduced in Junos OS Release 17.3 for MX150 Router Appliance and MX10003 Universal Routing Platforms.

Command introduced in Junos OS Release 17.4 for MX204 Universal Routing Platforms.

Command introduced in Junos OS Release 18.1R1 for EX9251 Switches.

Command introduced in Junos OS Release 18.2R1 for EX9253 Switches and MX10008 Universal Routing Platforms.

Description

Display information about the conditions that have been configured to trigger alarms.

Options

noneDisplay 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.
lcc number(TX Matrix router and TX Matrix Plus router only) (Optional) Line-card chassis number.

Replace number with the following values depending on the LCC configuration:

  • 0 through 3, when T640 routers are connected to a TX Matrix router in a routing matrix.

  • 0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a routing matrix.

  • 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.

  • 0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.

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.
scc(TX Matrix router only) (Optional) Show information about the TX Matrix router (switch-card chassis).
sfc number(TX Matrix Plus router only) (Optional) Show information about the respective TX Matrix Plus router, which is the switch-fabric chassis. Replace number variable with 0.

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.

Note

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:

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:

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:

Actual Error Code = (257-1)/2 = 128. Similarly, for minor alarms, Actual Error Code = (Error Code)/2

Note

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

List of Sample Output

show chassis alarms (Alarms Active)

show chassis alarms (No Alarms Active)

show chassis alarms (Fan Tray)

show chassis alarms (MX150)

show chassis alarms (MX104 Router)

show chassis alarms (MX2010 Router)

show chassis alarms (MX2020 Router)

show chassis alarms (MX10003 Router)

show chassis alarms (MX204 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 (T4000 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 (Alarms Active on a TX Matrix Router)

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

show chassis alarms (Alarms on a T4000 Router After the enhanced-mode Statement is Enabled)

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 (Alarms Active on a PTX5000 Packet Transport Router)

show chassis alarms (Mix of PDUs Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)

show chassis alarms (PDU Converter Failed Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)

show chassis alarms (No Power for System Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)

show chassis alarms (Alarms Active on an ACX2000 Universal Metro Router)

show chassis alarms (Active Alarm to Indicate Status of the Bad SCB Clock on MX Series)

show chassis alarms (Alarms active on a PTX1000 Packet Transport Router)

show chassis alarms (MX10003 Router)

show chassis alarms (Alarms active on a MX10008 Router)

Output Fields

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

Table 1: show chassis 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 chassis alarms (Alarms Active)

user@host> show chassis alarms

show chassis alarms (No Alarms Active)

user@host> show chassis alarms

show chassis alarms (Fan Tray)

user@host> show chassis alarms

show chassis alarms (MX150)

user@host > show chassis alarms

show chassis alarms (MX104 Router)

user@host >show chassis alarms

show chassis alarms (MX2010 Router)

user@host> show chassis alarms

show chassis alarms (MX2020 Router)

user@host> show chassis alarms

show chassis alarms (MX10003 Router)

user@host> show chassis alarms

Starting in Junos OS Release 19.2R1, the MX10003 routers do not raise an alarm if a Power Entry Module (PEM) slot is empty. However, when the number of operational PEMs goes below 2, the router raises a major alarm. This alarm is cleared when the required number of PEMs are made available.

show chassis alarms (MX204 Router)

user@host> show chassis alarms

show chassis alarms (MX2008 Router)

user@host>show chassis alarms

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

show chassis alarms (PTX10008 Router)

user@host>show chassis alarms

show chassis alarms (T4000 Router)

user@host> show chassis alarms

show chassis alarms (Unreachable Destinations Present on a T Series Router)

user@host> show chassis alarms

show chassis alarms (FPC Offline Due to Unreachable Destinations on a T Series Router)

user@host> show chassis alarms

show chassis alarms (SCG Absent on a T Series Router)

user@host> show chassis alarms

show chassis alarms (Alarms Active on a TX Matrix Router)

user@host> show chassis alarms

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

user@host> show chassis alarms

show chassis alarms (Alarms on a T4000 Router After the enhanced-mode Statement is Enabled)

To enable improved virtual private LAN service (VPLS) MAC address learning on T4000 routers, you must include the enhanced-mode statement at the [edit chassis network-services] hierarchy level and reboot the router. When router reboots, only the T4000 Type 5 FPCs are required to be present on the router. If there are any other FPCs (apart from T4000 Type 5 FPCs) on the T4000 router, such FPCs become offline, and FPC misconfiguration alarms are generated. The show chassis alarm command output displays FPC misconfiguration (FPC fpc-slot misconfig) as the reason for the generation of the alarms.

user@host> show chassis alarms

show chassis alarms (Backup Routing Engine)

user@host> show chassis alarms

show chassis alarms (EX Series Switch)

user@switch> show chassis alarms

show chassis alarms (Alarms Active on the QFX Series and OCX Series Switches)

user@switch> show chassis alarms

show chassis alarms node-device (Alarms Active on the QFabric System)

user@switch> show chassis alarms node-device Test

show chassis alarms (Alarms Active on the QFabric System)

user@switch> show chassis alarms

show chassis alarms (Alarms Active on an EX8200 Switch)

user@switch> show chassis alarms

show chassis alarms (EX9251 Switch)

user@switch> show chassis alarms

show chassis alarms (EX9253 Switch)

user@switch> show chassis alarms

show chassis alarms (Alarms Active on a PTX5000 Packet Transport Router)

user@host> show chassis alarms

show chassis alarms (Mix of PDUs Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)

All PDUs installed on a PTX5000 router must be of the same type. The Mix of PDUs or Power Manager Non Operational alarm is raised when different types of PDUs are installed on a PTX5000 router.

user@host> show chassis alarms

show chassis alarms (PDU Converter Failed Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)

The PDU Converter Failed alarm is raised when one or more 36 V booster converter of a DC PDU fails. If two or more 36 V booster converter fails, fan trays fail and the router might get over heated. Therefore, when this alarm is raised, check the PDU and replace it, if required.

user@host> show chassis alarms

show chassis alarms (No Power for System Alarm on a PTX5000 Packet Transport Router with FPC2-PTX-P1A)

user@host> show chassis alarms

show chassis alarms (Alarms Active on an ACX2000 Universal Metro Router)

user@host> show chassis alarms

show chassis alarms (Active Alarm to Indicate Status of the Bad SCB Clock on MX Series)

user@host> show chassis alarms

show chassis alarms (Alarms active on a PTX1000 Packet Transport Router)

user@host> show chassis alarms

show chassis alarms (MX10003 Router)

If LCMD is down on the backup RE, then the following alarm is seen on the Master.

user@host> show chassis alarms

If LCMD is down on the master, then following alarms are displayed.

user@host> show chassis alarms

If the LCMD process is crashing on the master, 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 master just gained mastership. When the master has just gained mastership, 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

If there are no more connection flaps within this two minutes time interval, the LCM peer connection un-stable alarm is cleared.

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

show chassis alarms (Alarms active on a MX10008 Router)

user@host> show chassis alarms