Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Understanding Chassis Alarms

Chassis Alarms

Table 1 and Table 2 list the chassis-related alarms that are displayed when you execute the show chassis alarms operational mode command on PTX Series or MX series routers.

Table 1: Chassis Alarms for PTX5000 series routers

Message displayed in the output of show chassis alarms Command

Description

Class

Solution

Mix of PDUs

Appears when AC PDUs and DC PDUs are installed. Also appears when zoning and non- zoning PDUs are installed.

Minor

Install same type of PDUs in all slots.

Power Manager Non Operational )

Appears when zoning and non- zoning PDUs are installed.

Minor

Install same type of PDUs in all slots.

No Redundant Power

When backup PDUs are absent or down

Minor

Install backup PDU.

PDU 0/1 Converter Failed

Appears when one or more 36V booster converter fails in PDU (PDU2-PTX-DC ).

Major

Check PDU and replace if required.

No redundant power for system

Appears when there is no backup PDUs in the router

Minor

Install backup PDU.

No Power for System

Appears when the router is powered on with only one PSM.

Major

Install backup PDU.

SIB 1 FPC Link Error

Appears when the indicated SIB is down.

Minor

Replace faulty SIB.

SIB 1 Absent

Appears when the indicated SIB is absent.

Major

Replace faulty SIB.

PDU 1 PSM 1 Not OK

Appears when the PSM in the displayed PDU is down.

Major

Replace faulty PSM.

Host x disk drive y smart error

Appears when there is an issue with the internal state of the disk such as, the disk life remaining is below the threshold.

  • x–0 for Host 0 (RE0) and 1 for Host 1 (RE1)

  • y–1 for disk 1 and 2 for disk 2

Minor

Replace the disk.

VMHost x Boot from alternate set

Appears when the Routing Engine is booted from the alternate set.

Minor

Verify logs. As required, recover the Routing Engine by using the command request vmhost snapshot

VMHost RE x host application failed

Appears when one of the vmhost daemon has failed.

Minor

Manual primary-role switchover followed by reboot using the command request vmhost reboot.

VMHost Boot from alternate disk

Appears when the primary disk is corrupted and unable to launch the guest.

Minor

Recover the disk by using the command request vmhost snapshot recovery.

Host 0/1 CPU Temperature Warm

Appears when the Routing Engine CPU temperature is above the TCONTROL threshold.

0 for Host 0 (RE0) and 1 for Host 1 (RE1)

Minor

No recovery action required from the user. Based on the temperature, the fan speed is changed to cool the system, thereby reducing the temperature.

Host 0/1 CPU Temperature Hot

Appears when the Routing Engine CPU temperature is above the PROCHOT threshold.

0 for Host 0 (RE0) and 1 for Host 1 (RE1)

Minor

No recovery action required from the user. Based on the temperature, the fan speed is changed to cool the system, thereby reducing the temperature.

Host 0/1 ECC single bit parity error

Appears when single bit ECC error is above the threshold value.

0 for Host 0 (RE0) and 1 for Host 1 (RE1)

Major

No recovery action required from the user. The count gets reset after 24 hours.

Host 0 ECC 53 parity error

Appears when multiple bit Error Checking and Correction (ECC) error is above the threshold value.

Major

Reboot the router.

VMHost RE x Disk y Missing

Appears when the disk in the Routing Engine is missing.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Check if there is missing or a defective disk. Insert healthy disk. Take a snapshot and recover the disk by using the command request vmhost snapshot.

See Disk Recovery Using the VM Host Snapshot in Installing, Upgrading, Backing Up, and Recovery of VM Host

VMHost RE x Disk y Label Missing

Appears when the labels on the disk in the Routing Engine is missing.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Reboot the Routing-Engine from healthy disk and recover the impacted disk using the command request vmhost snapshot.

VMHost RE x Disk y Wrong Slot

Appears when there is disk swap or pre-lablled disk inserted in wrong slot.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

If both the disks are in wrong slot, swap the disks and reboot. If only one disk is in wrong slot, recover the disk via snapshot after booting from healthy disk.

VMHost RE x Disk y File System Errors

Appears when there is a file system error.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Boot the Routing-engine from healthy disk and recover the impacted disk using the command request vmhost snapshot.

VMHost RE x Disk y Write Rate Threshold Cross

Appears if write rate threshold is crossed.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Identify the application that is generating excessive writes and apply configuration changes to prevent excessive writes.

VMHost RE x Disk y Size Incorrect

Appears if the size of the disk is not appropriate for the platform.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Insert an disk of the right size and reboot the Routing Engine.

VMHost RE x Disk y Usage Is Above Threshold

Appears when the usage of the disk partition is above the threshold limit.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Cleanup the disks using request vmhost cleanup command.

VMHost RE x Secure Boot Disabled

Appears when Secure Boot is not enforced in the BIOS.

Medium

Enable Secure Boot in the BIOS.

VMHost RE x Secure BIOS Version Mismatch

Appears when current BIOS version is older than the Last Known good BIOS version.

Medium

Upgrade the BIOS using the request system firmware command.

RE x Mismatch in total memory detected

Appears when total memory for the pair of Routing Engines does not match, possibly because a memory module has failed.

Medium

Check the available RAM size using show vmhost hardware command. If the RAM size for the pair of Routing Engines does not match, contact JTAC.

Table 2: Chassis Alarms for PTX10008 and PTX10016 routers

Message displayed in the output of show chassis alarms Command

Description

Class

Solution

FPC x need bounce

Appears when port speed configuration needs an FPC reboot for the new speed configuration to take effect.

  • x-FPC slot number.

Minor

Do one of the following to clear the alarm.

  • Manually reboot the FPC for the new port speed configuration to take effect.

  • Delete the new port speed configuration that has triggered the alarm. In this case, the new port speed configuration will not take effect.

PEM pem-slot No Power

Appears when both power supplies are not connected and the enable switch is not set correctly.

Major

Check power supply input connection and the enable switch setting.

See the dip switch and enable switch settings for your specific power supply model, Removing and Installing MX10000 Power System Components.

PEM pem-slot feed feed-slot no input

Appears when both power supplies are not connected but the enable switch is set to on.

Major

PEM pem-slot feed feed-slot Switch Cfg Wrong

Appears when either both power supplies are connected or one of the power supplies is connected but the enable switch is not set correctly.

Major

Mix of AC & DC Supplies

Mix of AC and DC power supplies.

Major

Ensure that the router has the same type of power supplies.

Table 3 lists the chassis-related alarms that are displayed when you execute the show chassis alarms operational mode command on MX Series routers

Table 3: Chassis Alarms for MX series routers

Message displayed in the output of show chassis alarms Command

Description

Class

Solution

Host x disk drive y smart error

Appears when there is an issue with the internal state of the disk such as, the disk life remaining is below the threshold.

  • x–0 for Host 0 (RE0) and 1 for Host 1 (RE1)

  • y–1 for disk 1 and 2 for disk 2

Minor

Replace the disk.

VMHost x Boot from alternate set

Appears when the Routing Engine is booted from the alternate set.

Minor

Verify logs. As required, recover the Routing Engine by using the command request vmhost snapshot

VMHost RE x host application failed

Appears when one of the vmhost daemon has failed.

Minor

Manual primary-role switchover followed by reboot using the command primary-role switchover followed by reboot using the command request vmhost reboot

VMHost Boot from alternate disk

Appears when the primary disk is corrupted and unable to launch the guest.

Minor

Recover the disk by using the command request vmhost snapshot recovery.

Host 0/1 CPU Temperature Warm

Appears when the Routing Engine CPU temperature is above the TCONTROL threshold.

0 for Host 0 (RE0) and 1 for Host 1 (RE1)

Minor

No recovery action required from the user. Based on the temperature, the fan speed is changed to cool the system thereby reducing the temperature

Host 0/1 CPU Temperature Hot

Appears when the Routing Engine CPU temperature is above the PROCHOT threshold.

0 for Host 0 (RE0) and 1 for Host 1 (RE1)

Minor

No recovery action required from the user. Based on the temperature, the fan speed is changed to cool the system thereby reducing the temperature

Host 0/1 ECC single bit parity error

Appears when single bit ECC error is above the threshold value.

0 for Host 0 (RE0) and 1 for Host 1 (RE1)

Major

No recovery action required from the user. The count gets reset after 24 hours.

Host 0 ECC 53 parity error

Appears when multiple bit ECC error is above the threshold value.

Major

Reboot the router.

Mixed Master and Backup RE types

Appears when dissimilar Routing Engines are present on the chassis.

Major

Both Routing Engines must be of the same model number. Replace one of the Routing Engines.

VMHost RE x Disk y Missing

Appears when the disk in the Routing Engine is missing.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Check if there is missing or a defective disk. Insert healthy disk. Take a snapshot and recover the disk by using the command request vmhost snapshot.

See Disk Recovery Using the VM Host Snapshot in Installing, Upgrading, Backing Up, and Recovery of VM Host

VMHost RE x Disk y Label Missing

Appears when the labels on the disk in the Routing Engine is missing.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Reboot the Routing-Engine from healthy disk and recover the impacted disk using the command request vmhost snapshot.

VMHost RE x Disk y Wrong Slot

Appears when there is disk swap or pre-lablled disk inserted in wrong slot.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

If both the disks are in wrong slot, swap the disks and reboot. If only one disk is in wrong slot, recover the disk via snapshot after booting from healthy disk.

VMHost RE x Disk y File System Errors

Appears when there is a file system error.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Boot the Routing-engine from healthy disk and recover the impacted disk using the command request vmhost snapshot.

VMHost RE x Disk y Write Rate Threshold Cross

Appears if write rate threshold is crossed.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Identify the application that is generating excessive writes and apply configuration changes to prevent the excessive writes.

VMHost RE x Disk y Size Incorrect

Appears if the size of the disk is not appropriate for the platform.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Insert an disk of the right size and reboot the Routing Engine.

VMHost RE x Disk y Usage Is Above Threshold

Appears when the usage of the disk partition is above the threshold limit.

  • x–0 for RE0 and 1 for RE1

  • y–1 for disk 1 and 2 for disk 2

Minor

Cleanup the disks using request vmhost cleanup command.

VMHost RE x Secure Boot Disabled

Appears when Secure Boot is not enforced in the BIOS.

Medium

Enable Secure Boot in the BIOS.

VMHost RE x Secure BIOS Version Mismatch

Appears when current BIOS version is older than the Last Known good BIOS version.

Medium

Upgrade the BIOS using the request system firmware command.

RE x Mismatch in total memory detected

Appears when total memory for the pair of Routing Engines does not match, possibly because a memory module has failed.

Medium

Check the available RAM size using show vmhost hardware command. If the RAM size for the pair of Routing Engines does not match, contact JTAC.

Mix of PDM types

Appears when the new high-voltage second-generation universal PDM is used along with older PDM variants.

Minor

Replace the old PDMs with the new universal PDMs.

Mix of PSM types

Appears if the new high-voltage second-generation universal PSM is used along with other AC/DC or DC/DC PSMs.

Minor

Install the same type of PSMs in all the slots.

Mix of PEMs

Applicable to the MX960 routers with high-voltage second-generation universal power supply module (PSM).

This alarm appears if the 5100 W power supply is used along with older power supplies in the MX960.

Minor

Install the same type of power supplies in all the slots.

Table 4: Chassis Alarms (PTP-Specific) for ACX710 Router

Message displayed in the output of show chassis alarms Command

Description

Class

Solution

PTP No Foreign Master

Raised if the external Precision Time Protocol (PTP) primary clock does not send announce packets.

Major

Ensure that the PTP configuration is correct. Also, ensure that external primary clock is working fine. This alarm gets cleared when the system recovers from the error state.

PTP Sync Fail

Raised if the PTP lock-status is not in Phase Aligned state.

Major

Ensure that the PTP configuration is correct. This alarm gets cleared when the PTP lock status moves to Phase Aligned state. Use the CLI 'show ptp lock-status' to view the PTP lock status.

Chassis Loss of all Equipment Clock Synch References

Raised if both the primary and secondary SyncE references fail and the chassis PLL is in holdover.

Major

Use the show chassis synchronization command to view the ineligibility reason, and to debug further. This alarm gets cleared when the system recovers from the error state.

Chassis Loss of Equipment Clock Synch Reference 1

Raised if the primary SyncE reference fails and no secondary SyncE reference is configured or present.

Major

Use the show chassis synchronization command to view the ineligibility reason, and to debug further.

Chassis Loss of Equipment Clock Synch Reference 2

Raised if you have configured at least two or more SyncE sources and the secondary SyncE source has failed.

Major

Use the show chassis synchronization command to view the ineligibility reason, and to debug further.

Chassis Conditions That Trigger Alarms

Various conditions related to the chassis components trigger yellow and red alarms. You cannot configure these conditions.

Chassis Component Alarm Conditions on M5 and M10 Routers

Table 5 lists the alarms that the chassis components can generate on M5 and M10 routers.

Table 5: Chassis Component Alarm Conditions on M5 and M10 Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at

www.juniper.net/

or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Fan trays

One fan tray has been removed from the chassis.

Install missing fan tray.

Yellow

Two or more fan trays have been removed from the chassis.

Install missing fan trays.

Red

One fan in the chassis is not spinning or is spinning below required speed.

Replace failed fan tray.

Red

Forwarding Engine Board (FEB)

The control board has failed. If this occurs, the board attempts to reboot.

Replace failed FEB.

 

Red

Flexible PIC Concentrator (FPC)

An FPC has failed. If this occurs, the FPC attempts to reboot. If the FEB sees that an FPC is rebooting too often, it shuts down the FPC.

Replace failed FPC.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Routing Engine

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

Power supplies

A power supply has been removed from the chassis.

Install missing power supply.

Yellow

A power supply has failed.

Replace failed power supply.

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at

www.juniper.net/

or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Chassis Component Alarm Conditions on M7i and M10i Routers

Table 6 lists the alarms that the chassis components can generate on M7i and M10i routers.

Table 6: Chassis Component Alarm Conditions on M7i and M10i Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Compact FEB (CFEB)

For an M7i router, CFEB has failed. If this occurs, the board attempts to reboot.

Replace failed CFEB.

Red

For an M10i router, both control boards have been removed or have failed.

Replace failed or missing CFEB.

Red

Too many hard errors in CFEB memory.

Replace failed CFEB.

Red

Too many soft errors in CFEB memory.

Replace failed CFEB.

Red

A CFEB microcode download has failed.

Replace failed CFEB.

Red

Fan trays

A fan has failed.

Replace failed fan tray.

Red

For an M7i router, a fan tray has been removed from the chassis.

Install missing fan tray.

Red

For an M10i router, both fan trays are absent from the chassis.

Install missing fan tray.

Red

For a TX Matrix Plus router, fan tray is not matching the ST-SIB-Ls SIB.

Install a Rev.3 fan tray.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s midplane from the front is broken.

Replace failed component.

Red

Power supplies

A power supply has been removed.

Insert missing power supply.

Yellow

A power supply has failed.

Replace failed power supply.

Red

For an M10i router, only one power supply is operating.

Insert or replace secondary power supply.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

Yellow

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk. This alarm only applies, if you have an optional CompactFlash card.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Chassis Component Alarm Conditions on M20 Routers

Table 7 lists the alarms that the chassis components can generate on M20 routers.

Table 7: Chassis Component Alarm Conditions on M20 Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Fan trays

One fan tray has been removed from the chassis.

Install missing fan tray.

Yellow

Two or more fan trays have been removed from the chassis.

Install missing fan trays.

Red

One fan in the chassis is not spinning or is spinning below requires speed.

Replace fan tray.

Red

FPC

An FPC has failed. If this occurs, the FPC attempts to reboot. If the System and Switch Board (SSB) sees that an FPC is rebooting too often, it shuts down the FPC.

Replace failed FPC.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs in to the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

Yellow

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from default backup Routing Engine. If you manually switched mastership, ignore this alarm condition.

Install bootable image on default primary Routing Engine. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

Power supplies

A power supply has been removed from the chassis.

Insert power supply into empty slot.

Yellow

A power supply has failed.

Replace failed power supply.

Red

SSB

The control board has failed. If this occurs, the board attempts to reboot.

Replace failed control board.

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Chassis Component Alarm Conditions on M40 Routers

Table 8 lists the alarms that the chassis components can generate on M40 routers.

Table 8: Chassis Component Alarm Conditions on M40 Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Air filter

Change air filter.

Change air filter.

Yellow

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Fan trays

One fan tray has been removed from the chassis.

Install missing fan tray.

Yellow

Two or more fan trays have been removed from the chassis.

Install missing fan trays.

Red

One fan in the chassis is not spinning or is spinning below required speed.

Replace fan tray.

Red

FPC

An FPC has an out of range or invalid temperature reading.

Replace failed FPC.

Yellow

An FPC microcode download has failed.

Replace failed FPC.

Red

An FPC has failed. If this occurs, the FPC attempts to reboot. If the SCB sees that an FPC is rebooting too often, it shuts down the FPC.

Replace failed FPC.

Red

Too many hard errors in FPC memory.

Replace failed FPC.

Red

Too many soft errors in FPC memory.

Replace failed FPC.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Power supplies

A power supply has been removed from the chassis.

Insert power supply into empty slot.

Yellow

A power supply temperature sensor has failed.

Replace failed power supply or power entry module.

Yellow

A power supply fan has failed.

Replace failed power supply fan.

Yellow

A power supply has high temperature.

Replace failed power supply or power entry module.

Red

A 5-V power supply has failed.

Replace failed power supply or power entry module.

Red

A 3.3-V power supply has failed.

Replace failed power supply or power entry module.

Red

A 2.5-V power supply has failed.

Replace failed power supply or power entry module.

Red

A power supply input has failed.

Check power supply input connection.

Red

A power supply has failed.

Replace failed power supply or power entry module.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

Yellow

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from default backup Routing Engine. If you manually switched mastership, ignore this alarm condition.

Install bootable image on default primary Routing Engine. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

SCB

The System Control Board (SCB) has failed. If this occurs, the board attempts to reboot.

Replace failed SCB.

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Chassis Component Alarm Conditions on M40e and M160 Routers

Table 9 lists the alarms that the chassis components can generate on M40e and M160 routers.

Table 9: Chassis Component Alarm Conditions on M40e and M160 Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Air filter

Change air filter.

Change air filter.

Yellow

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Connector Interface Panel (CIP)

A CIP is missing.

Insert CIP into empty slot.

Red

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Fan trays

One fan tray has been removed from the chassis.

Install missing fan tray.

Yellow

Two or more fan trays have been removed from the chassis.

Install missing fan trays.

Red

One fan in the chassis is not spinning or spinning below required speed.

Replace fan tray.

Red

FPC

An FPC has an out of range or invalid temperature reading.

Replace failed FPC.

Yellow

An FPC microcode download has failed.

Replace failed FPC.

Red

An FPC has failed. If this occurs, the FPC attempts to reboot. If the MCS sees that an FPC is rebooting too often, it shuts down the FPC.

Replace failed FPC.

Red

Too many hard errors in FPC memory.

Replace failed FPC.

Red

Too many soft errors in FPC memory.

Replace failed FPC.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Miscellaneous Control Subsystem (MCS)

An MCS has an out of range or invalid temperature reading.

Replace failed MCS.

Yellow

MCS0 has been removed.

Reinstall MCS0.

Yellow

An MCS has failed.

Replace failed MCS.

Red

Packet Forwarding Engine Clock Generator (PCG)

A backup PCG is offline.

Set backup PCG online.

Yellow

A PCG has an out of range or invalid temperature reading.

Replace failed PCG.

Yellow

A PCG has been removed.

Insert PCG into empty slot.

Yellow

A PCG has failed to come online.

Replace failed PCG.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

Yellow

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from default backup Routing Engine. If you manually switched mastership, ignore this alarm condition.

Install bootable image on default primary Routing Engine. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

Power supplies

A power supply has been removed from the chassis.

Insert power supply into empty slot.

Yellow

A power supply has failed.

Replace failed power supply.

Red

Switching and Forwarding Module (SFM)

An SFM has an out of range or invalid temperature reading on SPP.

Replace failed SFM.

Yellow

An SFM has an out of range or invalid temperature reading on SPR.

Replace failed SFM.

Yellow

An SFM is offline.

Set SFM online.

Yellow

An SFM has failed.

Replace failed SFM.

Red

An SFM has been removed from the chassis.

Insert SFM into empty slot.

Red

All SFMs are offline or missing from the chassis.

Insert SFMs into empty slots or set all SFMs online.

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Chassis Component Alarm Conditions on M120 Routers

Table 10 lists the alarms that the chassis components can generate on M120 routers.

Table 10: Chassis Component Alarm Conditions on M120 Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Air filters

Change air filter.

Change air filter.

Yellow

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Control Board (CB)

A CB Ethernet switch has failed.

Replace failed CB.

Yellow

A CB has been removed.

Insert CB into empty slot.

Red

A CB has failed.

Replace failed CB.

Red

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Fan trays

One fan tray has been removed from the chassis.

Install missing fan tray.

Yellow

Two or more fan trays have been removed from the chassis.

Install missing fan trays.

Red

One fan in the chassis is not spinning or is spinning below required speed.

Replace fan tray.

Red

Forwarding Engine Boards (FEBs)

A spare FEB has failed.

Replace failed FEB.

Yellow

A spare FEB has been removed.

Insert FEB into empty slot.

Yellow

A FEB is offline.

Check FEB. Remove and reinsert the FEB. If this fails, replace failed FEB.

Yellow

A FEB has failed.

Replace failed FEB.

Red

A FEB has been removed.

Insert FEB into empty slot.

Red

Host subsystem

A host subsystem has failed.

Replace the host subsystem.

Yellow

A host subsystem has been removed.

Insert host subsystem into empty slot.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Power supplies

A power supply has been removed from the chassis.

Insert power supply into empty slot.

Yellow

A power supply has a high temperature.

Replace failed power supply or power entry module.

Red

A power supply input has failed.

Check power supply input connection.

Red

A power supply output has failed.

Check power supply output connection.

Red

A power supply has failed.

Replace failed power supply.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

 

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from default backup Routing Engine. If you manually switched mastership, ignore this alarm condition.

Install bootable image on default primary Routing Engine. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

Chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Chassis Component Alarm Conditions on M320 Routers

Table 11 lists the alarms that the chassis components can generate on M320 routers.

Table 11: Chassis Component Alarm Conditions on M320 Routers

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Air filters

Change air filter.

Change air filter.

Yellow

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Control Board (CB)

A CB has been removed.

Insert CB into empty slot.

Yellow

A CB temperature sensor alarm has failed.

Replace failed CB.

Yellow

A CB has failed.

Replace failed CB.

Red

CIP

A CIP is missing.

Insert CIP into empty slot.

Red

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Fan trays

One fan tray has been removed from the chassis.

Install missing fan tray.

Yellow

Two or more fan trays have been removed from the chassis.

Install missing fan trays.

Red

One fan in the chassis is not spinning or is spinning below required speed.

Replace fan tray.

Red

FPC

An FPC has an out of range or invalid temperature reading.

Replace failed FPC.

Yellow

An FPC microcode download has failed.

Replace failed FPC.

Red

An FPC has failed. If this occurs, the FPC attempts to reboot. If the CB sees that an FPC is rebooting too often, it shuts down the FPC.

Replace failed FPC.

Red

Too many hard errors in FPC memory.

Replace failed FPC.

Red

Too many soft errors in FPC memory.

Replace failed FPC.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Power supplies

A power supply has been removed from the chassis.

Insert power supply into empty slot.

Yellow

A power supply has failed.

Replace failed power supply.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

Yellow

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from default backup Routing Engine. If you manually switched mastership, ignore this alarm condition.

Install bootable image on default primary Routing Engine. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

A spare SIB is missing.

Insert spare SIB in to empty slot.

Yellow

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

Switch Interface Board (SIB)

A SIB has failed.

Replace failed SIB.

Yellow

A spare SIB has failed.

Replace failed SIB.

Yellow

A SIB has an out of range or invalid temperature reading.

Replace failed SIB.

Yellow

A SIB is missing.

Insert SIB into empty slot.

Red

A SIB has failed.

Replace failed SIB.

Red

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

Temperature

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

Chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

     

Chassis Component Alarm Conditions on MX Series 5G Universal Routing Platforms

Table 12 lists the alarms that the chassis components can generate on MX Series 5G Universal Routing Platforms.

Table 12: Chassis Component Alarm Conditions on MX Series 5G Universal Routing Platforms

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Air filters

Change air filter.

Change air filter.

Yellow

Alternative media

The router boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Craft interface

The craft interface has failed.

Replace failed craft interface.

Red

Dense Port Concentrators (DPC)s

A DPC is offline.

Check DPC. Remove and reinsert the DPC. If this fails, replace failed DPC.

Yellow

A DPC has failed.

Replace failed DPC.

Red

A DPC has been removed.

Insert DPC into empty slot.

Red

Fan trays

A fan tray has been removed from the chassis.

Install missing fan tray.

Red

One fan in the chassis is not spinning or is spinning below required speed.

Replace fan tray.

Red

A higher-cooling capacity fan tray is required when an MPC is installed on the chassis.

Upgrade to a high-capacity fan tray.

Yellow

Host subsystem

A host subsystem has been removed.

Insert host subsystem into empty slot.

Yellow

A host subsystem has failed.

Replace failed host subsystem.

Red

Hot swapping

Too many hot-swap interrupts are occurring. This message generally indicates that a hardware component that plugs into the router’s backplane from the front (generally, an FPC) is broken.

Replace failed component.

Red

Power supplies

A power supply has been removed from the chassis.

Insert power supply into empty slot.

Yellow

A power supply has a high temperature.

Replace failed power supply or power entry module.

Red

A power supply input has failed.

Check power supply input connection.

Red

A power supply output has failed.

Check power supply output connection.

Red

A power supply has failed.

Replace failed power supply.

Red

Invalid AC power supply configuration.

When two AC power supplies are installed, insert one power supply into an odd-numbered slot and the other power supply into an even-numbered slot.

Red

Invalid DC power supply configuration.

When two DC power supplies are installed, insert one power supply into an odd-numbered slot and the other power supply into an even-numbered slot.

Red

Mix of AC and DC power supplies.

Do not mix AC and DC power supplies. For DC power, remove the AC power supply. For AC power, remove the DC power supply.

Red

Not enough power supplies.

Install an additional power supply.

Red

Routing Engine

Excessive framing errors on console port.

An excessive framing error alarm is triggered when the default framing error threshold of 20 errors per second on a serial port is exceeded.

This might be caused by a faulty serial console port cable connected to the device.

Replace the serial cable connected to the device.

If the cable is replaced and no excessive framing errors are detected within 5 minutes from the last detected framing error, the alarm is cleared automatically.

Yellow

Error in reading or writing hard disk.

Reformat hard disk and install bootable image. If this fails, replace failed Routing Engine.

Yellow

Error in reading or writing CompactFlash card.

Reformat CompactFlash card and install bootable image. If this fails, replace failed Routing Engine.

Yellow

System booted from default backup Routing Engine. If you manually switched mastership, ignore this alarm condition.

Install bootable image on default primary Routing Engine. If this fails, replace failed Routing Engine.

Yellow

System booted from hard disk.

Install bootable image on CompactFlash card. If this fails, replace failed Routing Engine.

Yellow

CompactFlash card missing in boot list.

Replace failed Routing Engine.

Red

Hard disk missing in boot list.

Replace failed Routing Engine.

Red

Routing Engine failed to boot.

Replace failed Routing Engine.

Red

The Ethernet management interface (fxp0 or em0) on the Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Red

System Control Board (SCB)

An SCB has been removed.

Insert SCB into empty slot.

Yellow

An SCB temperature sensor alarm has failed.

Replace failed SCB.

Yellow

An SCB has failed.

Replace failed SCB.

Red

Temperature

The chassis temperature has exceeded 55 degrees C (131 degrees F), the fans have been turned on to full speed, and one or more fans have failed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and the fans have been turned on to full speed.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Yellow

The chassis temperature has exceeded 65 degrees C (149 degrees F), and a fan has failed. If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

Chassis temperature has exceeded 75 degrees C (167 degrees F). If this condition persists for more than 4 minutes, the router shuts down.

  • Check room temperature.

  • Check air filter and replace it.

  • Check airflow.

  • Check fan.

Red

The temperature sensor has failed.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Flexible PIC Concentrator (FPC)

FPC <slot number> Major Errors

On MX Series routers with MPC1 and MPC2 line cards, a major chassis alarm is raised when the following transient hardware errors occur

  • CPQ Sram parity error

  • CPQ RLDRAM double bit ECC error

By default, these errors result in the Packet Forwarding Engine interfaces on the FPC being disabled. You can use the show chassis fpc errors command to view the default or user-configured action that resulted from the error.

You can check the syslog messages to know more about the errors.

To resolve the error, restart the line card. If the error is still not resolved, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Red

Backup Routing Engine Alarms

For routers with primary and backup Routing Engines, a primary Routing Engine can generate alarms for events that occur on a backup Routing Engine. Table 13 lists chassis alarms generated for a backup Routing Engine.

Note:

Because the failure occurs on the backup Routing Engine, alarm severity for some events (such as Ethernet interface failures) is yellow instead of red.

Note:

For information about configuring redundant Routing Engines, see the Junos OS High Availability Library for Routing Devices.

Table 13: Backup Routing Engine Alarms

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Alternative media

The backup Routing Engine boots from an alternate boot device, the hard disk. The CompactFlash card is typically the primary boot device. The Routing Engine boots from the hard disk when the primary boot device fails.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Boot Device

The boot device (CompactFlash or hard disk) is missing in boot list on the backup Routing Engine.

Replace failed backup Routing Engine.

Red

       
Ethernet

The Ethernet management interface (fxp0 or em0) on the backup Routing Engine is down.

  • Check the interface cable connection.

  • Reboot the system.

  • If the alarm recurs, open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States)

Yellow

FRU Offline

The backup Routing Engine has stopped communicating with the master Routing Engine.

Open a support case using the Case Manager link at https://www.juniper.net/support/ or call 1-888-314-JTAC (within the United States) or 1-408-745-9500 (from outside the United States).

Yellow

Hard Disk

Error in reading or writing hard disk on the backup Routing Engine.

Reformat hard disk and install bootable image. If this fails, replace failed backup Routing Engine.

Yellow

Multibit Memory ECC

The backup Routing Engine reports a multibit ECC error.

  • Reboot the system with the board reset button on the backup Routing Engine.

  • If the alarm recurs, open a support case using the Case Manager link at

    www.juniper.net/support/ or

    call 1-888-314-JTAC

    (within the United States) or 1-408-745-9500 (from outside the United States)

Yellow

Chassis Component Alarm Conditions for Guest Network Functions (GNFs)

Table 14 lists the Chassis conditions that trigger alarms on guest network functions (GNFs).

Read more about GNFs in this Junos Node Slicing article.

Table 14: GNF Alarms

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Routing Engine

Mixed Master and Backup RE types

This alarm is raised when the GNF primary Routing Engine and GNF Backup Routing Engine have been assigned either mismatching frequencies ( with difference above 100 MHz), mismatching numbers of cores, or DRAM.

Correct the differences and then relaunch the corrected GNF Routing Engine.

Yellow

Routing Engine

System Incompatibility with BSYS

The alarm is shown when any incompatibilities between BSYS and GNF software versions cause the GNF to go offline.

Make the required changes to the BSYS or GNF software through upgrade.

Red

Routing Engine

Feature Incompatibility with BSYS

Indicates a minor incompatibility between BSYS and GNF software versions. This could result in a:

  • A warning error for the GNF.

  • A FRU going offline.

    Note:

    Minor incompatibilities do not cause the GNF to go offline.

Make the required changes to the BSYS or GNF software through upgrade.

Yellow

Chassis Component Alarm Conditions on SRX1500, SRX4100, SRX4200 and SRX4600 devices

Table 15 lists the alarms that the chassis components can generate on SRX1500, SRX4100, SRX4200 and SRX4600 devices. Execute show chassis alarms operational mode command on SRX1500, SRX4100, SRX4200 and SRX4600 devices to view the alarm.

Table 15: Chassis Component Alarm Conditions on SRX1500, SRX4100, SRX4200 and SRX4600 devices

Chassis Component

Alarm Condition

Remedy

Alarm Severity

Power supply unit (PSU)

Appears when one among the two PSU is not available or not energized for SRX1500, SRX4100, and SRX4200.

Install the missing PSU or refer pem-absence

Red

Power supply unit (PSU)

Appears when one among the two PSU is not available or not energized for SRX4600.

Install the missing PSU or refer pem-absence

Yellow

MX204 LED Scheme Overview

LEDs on the interface cards display the status of the ports. In MX204 router, there are four port LEDs per port. Each port provides an individual status LED with four states signaled by the color/LED state: OFF, GREEN, AMBER, RED.

The following port LED display modes are defined:

  • Normal—Represents the normal working mode of the LED. By default, the port status display mode is Normal.

  • Port location—The port location mode is ON when a remote operator initiates a port location command for a port or a group of ports.

The following factors trigger a change in the port LED color:

  • Change in the port state. For example, loss of signal (LOS) to no LOS, remote fault, or local fault

  • Pluggable insertion or removal

  • Change in configuration

  • Activation or deactivation of port location feature

Table 16 summarizes the state and color rules for the port LEDs. These rules help in determining the port LED color. When port location mode is activated, the port LED state or color can be determined from the Port Location ON column.

Note:

In MX204 router, there are four port LEDs per port. On PIC 0, if the port operates at the speed of 40-Gbps or 100-Gbps, then the first LED of PIC 1 will be ON and the other three LEDs will be OFF. And, if the port operates at the speed of 10-Gbps, then all the LEDs will be ON.

Table 16: Port LED State and Color Rules

Pluggable Inserted

Explicitly Disabled

Port State

Normal

Port Location ON

Yes

No

Up

Green

Blinking green

Yes

No

Down; loss of signal (LOS) detected

Off

Blinking green

Yes

No

Down; transceiver hardware failure

Red

Blinking red

Yes

No

Down; any other fault other than LOS and transceiver hardware failure

Amber

Blinking amber

ANY

Yes

Port disabled by CLI

Amber

Blinking amber

No

No

Anything except disabled port; however, transceiver not present

Off

Blinking green

MPC and MIC Lane LED Scheme Overview

LEDs on the interface cards display the status of the ports. On some MICs and MPC that have multiple ports and supports multiple port speed, it is not feasible to have an individual LED display for each port on an interface card. Hence, a shared LED display is introduced—the lane LEDs.

The MX10003 MPC includes this new LED lane display. The Multi-Rate 12xQFSP28 MIC and the fixed-port PIC (6xQFSPP) have separate lane LEDs.

The lane LEDs of the MIC are located on the MIC itself, whereas the lane LEDs of the PIC are located on the MPC.

The following interface cards support lane LEDs:

You can select a port operating in a breakout mode for an individual lane display, either periodically or when the request chassis port-led command is executed. Similar to the port status LEDs, the lane LED supports 4 states defined by the color or the LED status—OFF, GREEN, AMBER, and RED.

Figure 1 illustrates the port LED and lane LED displays on the MPC.

Figure 1: Port LED and Lane LED display on the MPCPort LED and Lane LED display on the MPC
  1

Port LEDs

  2

Lane display LEDs

Figure 2 illustrates the port LED and lane LED displays for the MPC.

Figure 2: Port LED and Lane LED display on the JNP10K-LC2101 MPCPort LED and Lane LED display on the JNP10K-LC2101 MPC
  1

Lane display LEDs

  2

Port LEDs

Figure 3 illustrates the port LED and lane LED displays for the MIC.

Figure 3: Port LED and Lane LED display on the MICPort LED and Lane LED display on the MIC
  1

Lane display LEDs

  2

Port LEDs

The following port LED display modes are defined:

  • Normal—The port status LED represents port state or a breakout port state. By default, the port status display mode is Normal.

  • Lane display—An array of lane status LEDs displays the status of each individual lane for the selected port. The lane display is ON when the software cycles through ports for lane status display. One port is selected at a time, and the display mode for that particular port switches to lane display mode. The other ports remain in normal display mode.

  • Port location—The port location mode is ON when a remote operator initiates a port location command for a port or a group of ports. The request chassis port-led command temporarily overrides periodic software port selection for the lane display; all ports on an interface card that are not selected for port location switch to Normal mode, and selected ports switch to port location mode. If only one port is selected for port location, then the corresponding lane LEDs are applicable. However, if the selected port is in breakout mode, then all lane LEDs are applicable. If not in breakout mode, only lane 0 LED displays the port status. If more than one port is selected for port location, then the lane LEDs are disabled.

The following factors trigger a change in the port LED color:

  • Change in the port state. For example, loss of signal (LOS) to no LOS, remote fault, or local fault

  • Pluggable insertion or removal

  • Change in configuration

  • Activation or deactivation of port location feature

  • Selection of breakout port for lane display

Note:

Ports with all individual links in Up state are skipped and are not considered for lane display, thereby reducing the time needed to cycle through all the ports.

Table 17 summarizes the state and color rules for the port LEDs. These rules help in determining the port LED color. When port location mode is activated, the port LED state or color can be determined from the Port Location ON column. If the breakout port is selected for the lane status display, then port LED state or color can be determined from the Lane Display column.

Table 17: Port LED State and Color Rules

Pluggable Inserted

Breakout Configuration State

Explicitly Disabled

Port State

Normal

Port Location ON

Lane Display

Yes

No breakout

No

Up

Green

Blinking green

-

Yes

No breakout

No

Down; loss of signal (LOS) detected

Off

Blinking green

-

Yes

No breakout

No

Down; transceiver hardware failure

Red

Blinking red

-

Yes

No breakout

No

Down; any other fault other than LOS and transceiver hardware failure

Amber

Blinking amber

-

ANY

No breakout

Yes

Port disabled by CLI

Amber

Blinking amber

-

No

Any

No

Anything except disabled port; however, transceiver not present

Off

Blinking green

-

Yes

Breakout

No

All breakout ports are UP

Green

Blinking green

Blinking green

Yes

Breakout

No

All breakout ports are down with LOS

Off

Blinking green

Blinking green

Yes

Breakout

No

Hardware failure; transceiver initialization error at the port level (not individual lane)

Red

Blinking red

Blinking red

Yes

Breakout

Any

In all other cases the port LED color is amber

Amber

Blinking amber

Blinking amber

The following factors trigger a change in the lane LED color:

  • A breakout port is selected for a lane display.

  • Port location mode is activated for a port on a given interface card.

Table 18 summarizes the state and color rules for the lane LEDs.

Table 18: Lane LED Color Rules

Pluggable Inserted

Breakout Configuration State

Explicitly Disabled

Port State

Order

LED Color

Yes

Breakout

No

Up

1

Green

Yes

Breakout

No

Down; loss of signal (LOS) detected

2

Off

Yes

Breakout

No

Down; transceiver hardware failure

3

Red

Yes

Breakout

No

Down; fault other than LOS and transceiver hardware failure

4

Amber

Yes

Breakout

Yes

Breakout port is disabled in the CLI

5

Amber

Configuring Slow Packet Forwarding Engine Alarm

On an M Series, an MX Series, a T Series, or an SRX Series device, the Packet Forwarding Engine might not send a resource acknowledgment message to the Routing Engine within a predetermined time of 360 seconds. This delay in receiving resource acknowledgment could be due to a slow or stuck Packet Forwarding Engine on the M Series, MX Series, T Series, or SRX Series device, or on one of the LCCs connected to a TX Matrix, TX Matrix Plus, or TX Matrix Plus router with 3D SIBs.

Starting with Junos OS Release 13.2R1 (also applicable in Junos OS Releases 12.1R6, 12.2R5, 12.3R3, 13.1R2 and later), to display the issue as an alarm in the show chassis alarms command output and to append the alarm to the system log messages file, you must enable the slow Packet Forwarding Engine alarm on the router.

The following sections provide more information about the slow Packet Forwarding Engine alarm:

Enabling Slow Packet Forwarding Engine Alarm

To enable the slow Packet Forwarding Engine alarm, perform the following steps:

Note:

By default, the slow Packet Forwarding Engine alarm is disabled.

  1. In configuration mode, go to the [edit chassis] hierarchy level:
  2. Enable the slow Packet Forwarding Engine alarm by configuring the slow-pfe-alarm statement.

Disabling Slow Packet Forwarding Engine Alarm

To disable the slow Packet Forwarding Engine alarm, perform the following steps:

  1. In configuration mode, go to the [edit chassis] hierarchy level:
  2. Disable the slow Packet Forwarding Engine alarm by deleting the slow-pfe-alarm statement.

Verifying That the Alarm Output and System Log Messages are Updated

Purpose

To verify that the output of the show chassis alarms operational mode command and the system log messages file are updated with the slow Packet Forwarding Engine alarm when:

  • The slow-pfe-alarm statement is enabled in the [edit chassis] hierarchy.

  • The Packet Forwarding Engine resource acknowledgment is not received by the Routing Engine within a predetermined time of 360 seconds.

Action

To check the output on an M Series, MX Series, T Series, or an SRX Series device:

  1. Verify that the alarm is displayed in the output of the show chassis alarms operational mode command.

    show chassis alarms

    For field descriptions, see show chassis alarms.

  2. Verify that the alarm is appended to the system log messages file.

To check the output on a TX Matrix, TX Matrix Plus, or a TX Matrix Plus with 3D SIBs router:

  1. Verify that the alarm is displayed in the output of the show chassis alarms operational mode command.

    show chassis alarms

    For field descriptions, see show chassis alarms.

  2. Verify that the alarm is appended to the system log messages file.

Meaning

The output of show chassis alarms operational mode command and the system log messages file are updated as expected when the slow Packet Forwarding Engine alarm is enabled and when the Packet Forwarding Engine resource acknowledgment is not received by the Routing engine within a predetermined time of 360 seconds.

User-Defined Alarm Relay Overview

The ACX Series router alarm contact port—labeled ALARM on the front panel—allows you to manage sensors and external devices connected to the router in remote unstaffed facilities.

Note:

Alarm contact port is not applicable on ACX5048 and ACX5096 routers.

Alarm Contact Port

The ACX Series router alarm contact port is a 15-pin D-type dry contact connector for alarms. The alarm contact port is used to generate LED alarms on the router and to turn external devices on or off. You can connect up to four input alarms and two output alarms. The alarm setting is open or closed.

Alarm Input

Alarm input provides dry contacts to connect to security sensors such as door or window monitors. The alarm input—open or closed—is sensed and reported to the management software. You can configure up to four alarm input relay ports (0 through 3) to operate as normally open or normally closed, and to trigger a red alarm condition or a yellow alarm condition or to ignore alarm conditions.

Alarm Output

Alarm output provides dry contacts to connect to external equipment, such as an audible or visual alarm that switches on or off–for example, a bell or a light. The four alarm output relay ports—0 through 3—are set up as follows:

  • Ports 0 and 1—These ports can be configured to trigger an alarm when the system temperature goes to the red alarm status and when an alarm input port is triggered.

  • Ports 2 and 3—These ports are not configured. They are used to indicate system major and minor alarms and are normally open. When a condition triggers an alarm, an alarm message is displayed.

To view the alarm input and output relay information, issue the show chassis craft-interface command from the Junos OS command line interface.

Configuring Chassis Alarm Relays

On ACX Series routers, you can configure alarm relays that can trigger alarms and turn external devices on or off. For example, if the router heats up to more than the critical temperature, the output port is activated and a device connected to the output port—such as a fan—is turned on.

To configure conditions that trigger alarms, include the relay statement with the input and output options at the [edit chassis alarm] hierarchy level.

The following output shows an example configuration of a chassis relay alarm:

Configuring Chassis Alarm Input

The ACX Series router alarm contact port—labeled ALARM on the front panel—allows you to manage sensors and external devices connected to the router in remote unstaffed facilities. You can configure up to four alarm input ports (0 through 3) to operate as normally open or normally closed, and to trigger a red alarm condition or a yellow alarm condition or to ignore alarm conditions.

To configure an input alarm:

  1. Configure the input port:

    For example, to configure input port zero (0):

  2. Configure the mode in which the input alarm is not active:

    For example, to configure open mode:

  3. Configure the trigger to set off the alarm:

    For example, to set off the yellow alarm:

  4. Verify the configuration with the show command:
  5. Commit the configuration with the commit command.

To view the alarm input relay information, issue the show chassis alarms or show chassis craft-interface commands from the Junos OS command line interface.

Configuring Chassis Alarm Output

The ACX Series router alarm contact port—labeled ALARM on the front panel—allows you to manage sensors and external devices connected to the router in remote unstaffed facilities. You can configure up to two alarm output relay ports (0 and 1) to operate as normally open or normally closed, and to trigger an alarm when the system temperature goes to the red alarm status and when an alarm input port is triggered.

Note:

Ports 2 and 3 are not configured. They are used to indicate system major and minor alarms and are normally open. When a condition triggers an alarm, an alarm message is displayed, and the corresponding LED turns on.

To configure an output alarm:

  1. Configure the output port:

    For example, to configure output port zero (0):

  2. Configure the trigger to set off the alarm:

    For example, to set off the alarm when the system temperature goes into the red status:

  3. Verify the configuration with the show command:
  4. Commit the configuration with the commit command.

To view the alarm output relay information, issue the show chassis alarms or show chassis craft-interface command from the Junos OS command line interface.

Configuring Chassis Alarm Input and Output (ACX710 Routers)

The alarm interface port, an RJ45 port on the front panel of the ACX710 router, provides user-configurable input and output signals. You can configure the alarm input to receive alarm inputs from the external devices (such as sensors) connected to the router through the alarm port. You can configure the alarm output to relay the alarms in the router to external alarm devices (for example, bells and bulbs) connected to the router through the alarm port. You can configure up to three alarm inputs and one alarm output.

The router supports configuration of up to three alarm inputs and one alarm output, using the command alarm-port at the [edit chassis] hierarchy. You can configure the alarm input signals independent of the alarm output signal, and vice versa.

Table 19: Alarm Port Pin-out Information

Pin Number of the Connector on the Device

Signal Definition

IN/OUT

CLI Mapping

1

ALARM_IN0_Sig

IN

port 1

2

ALARM_IN0_Return

IN

port 1

3

ALARM_IN1_Sig

IN

port 2

4

ALARM_IN2_Sig

IN

port 3

5

ALARM_IN1_Return

IN

port 2

6

ALARM_IN2_Return

IN

port 3

7

ALARM_OUT_Sig

OUT

port 1

8

ALARM_OUT_Return

OUT

port 1

To configure an alarm input:

  1. Specify the input port number by using the command set chassis alarm-port input port port-number. The router supports three input ports (1 to 3).
  2. Configure a signal polarity for the alarm input based on the user environment.
  3. Set the administrative state of the alarm input as enabled.
  4. Provide a description to the alarm input. For example, FAN.
  5. Specify an alarm severity. The following are the available options: critical, major, minor, and warning.
  6. Commit the configuration with the commit command.

To view the input alarms, by using the show chassis alarms command.

To configure an alarm output:

  1. Specify the output port number by using the command set chassis alarm-port output port port-number. The router supports only one output port (port number: 1).

  2. Set the administrative state of the alarm output as enabled.

  3. Provide a description to the alarm input.

  4. Commit the configuration with the commit command.

For more information, see alarm-port.

You can use the command show chassis craft-interface to view the alarm port configuration details.