Description

 This document explains how to find out why ALARM LED lit Amber on Secondary Node. It could happen on any Standalone SRX device as well.

Amber and steadily on indicates a major alarm, such as low memory (less than 10% remaining), session full, maximum number of VPN tunnels reached, HA status change, or redundant group member not found.

Symptoms

root@MSt-Primary> show chassis craft-interface 
node0:
--------------------------------------------------------------------------
show chassis environment
Front Panel Fan LEDs:
------------------------
AMBER LED .
GREEN LED *
RED LED .
LED OFF .

Front Panel Alarm Indicators:
-----------------------------
AMBER LED .
GREEN LED .
RED LED .
LED OFF *

Front Panel HA Indicators:
-----------------------------
AMBER LED .
GREEN LED *
RED LED .
LED OFF .
PS LEDs:
PS 0
--------------------
AMBER LED .
GREEN LED *
RED LED .
LED OFF .
show system alarms

node1:
--------------------------------------------------------------------------
Front Panel Fan LEDs:
------------------------
AMBER LED .
GREEN LED *
RED LED .
LED OFF .

Front Panel Alarm Indicators:
-----------------------------
AMBER LED *
GREEN LED .
RED LED .
LED OFF .

Front Panel HA Indicators:
-----------------------------
AMBER LED .
GREEN LED *
RED LED .
LED OFF .

PS LEDs:
PS 0
--------------------
AMBER LED .
GREEN LED *
RED LED .
LED OFF .




{secondary:node1}
root@MSt-Secondary> show system alarms
node0:
--------------------------------------------------------------------------
No alarms currently active

node1:
--------------------------------------------------------------------------
1 alarms currently active
Alarm time Class Description
2012-05-14 19:51:02 EDT Minor Rescue configuration is not set

Solution

Run the following Operational mode command on Secondary Node to save Rescue Configuration and Clear the ALARM LED: 

request system configuration rescue save

Modification History

19-11-2025: Minor, non-technical edit