Alarms
System Alarms
Switches provide predefined system alarms that can be
triggered by a missing rescue configuration, failure to install a
license for a licensed software feature, or high disk usage. You can
display alarm messages by issuing the show system alarms operational mode command.
For example: The switch might trigger an alarm when disk usage in the /var partition exceeds 75 percent. A usage level between 76 and 90 percent indicates high usage and raises a minor alarm condition, whereas a usage level above 90 percent indicates that the partition is full and raises a major alarm condition.
The following sample output shows the system alarm messages that are displayed when disk usage is exceeded on the switch.
user@host> show system alarms 4 alarms currently active Alarm time Class Description 2013-10-08 20:08:20 UTC Minor RE 0 /var partition usage is high 2013-10-08 20:08:20 UTC Major RE 0 /var partition is full 2013-10-08 20:08:08 UTC Minor FPC 1 /var partition usage is high 2013-10-08 20:08:08 UTC Major FPC 1 /var partition is full
We recommend that you regularly request a system file storage cleanup to optimize the performance of the switch and prevent generating system alarms.
Configuring Junos OS to Determine Conditions That Trigger Alarms on Different Interface Types
For the different types of PICs, you can configure which conditions trigger alarms and whether they trigger a red or yellow alarm. Red alarm conditions light the RED ALARM LED and trigger an audible alarm if one is connected. Yellow alarm conditions light the YELLOW ALARM LED and trigger an audible alarm if one is connected.
By default, any failure condition on the integrated-services interface (Adaptive Services PIC) triggers a red alarm.
To configure conditions that trigger alarms and
that can occur on any interface of the specified type, include the alarm statement at the [edit chassis] hierarchy
level.
[edit chassis] alarm { interface-type { alarm-name (red | yellow | ignore); } }
alarm-name is the name of an alarm.
System-Wide Alarms and Alarms for Each Interface Type
Table 1 lists the system-wide alarms and the alarms for each interface type.
Interface/System |
Alarm Condition |
Configuration Option |
|---|---|---|
| SONET/SDH and ATM | Link alarm indication signal |
ais-l |
Path alarm indication signal |
ais-p |
|
Signal degrade (SD) |
ber-sd |
|
Signal fail (SF) |
ber-sf |
|
Loss of cell delineation (ATM only) |
locd |
|
Loss of framing |
lof |
|
Loss of light |
lol |
|
Loss of pointer |
lop-p |
|
Loss of signal |
los |
|
Phase-locked loop out of lock |
pll |
|
Synchronous transport signal (STS) payload label (C2) mismatch |
plm-p |
|
Line remote failure indication |
rfi-l |
|
Path remote failure indication |
rfi-p |
|
STS path (C2) unequipped |
uneq-p |
|
| E3/T3 | Alarm indicator signal |
ais |
Excessive numbers of zeros |
exz |
|
Failure of the far end |
ferf |
|
Idle alarm |
idle |
|
Line code violation |
lcv |
|
Loss of frame |
lof |
|
Loss of signal |
los |
|
Phase-locked loop out of lock |
pll |
|
Yellow alarm |
ylw |
|
| Ethernet | Link has gone down |
link-down |
| DS1 | Alarm indicator signal |
ais |
Yellow alarm |
ylw |
|
| Integrated services | Hardware or software failure |
failure |
| Management Ethernet | Link has gone down |
link-down |