# Alarm Thresholds

Alarm thresholds set the lower limits of an alarm level. When the severity of an alarm (measured by the percentage of a device type that is faulted or unavailable) exceeds an alarm threshold, a new alarm level is reached.

- Use the Show Faults command to view current alarm thresholds.

- Use the Set Thresholds command to change alarm thresholds.

Default alarm thresholds are shown in the table below.

NOTE: The value ">0" indicates "greater than 0%".

Default Alarm Thresholds (% faulted or unavailable)
Alarm Category | Minor Alarm | Major Alarm | Critical Alarm
CESID | >0 | -- | --
Check Bootrom | 100 | -- | --
Check FPGA | 100 | -- | --
Check MSP430 | 100 | -- | --
CP Applications | >0 | -- | --
CP Channels | 10 | 25 | --
CP Devices | >0 | 100 | --
Database Status | -- | >0 | --
Digital Links | -- | >0 | --
DSP Card Status | 1 | -- | 100
DSP Status | 1 | -- | 100
E2T | -- | >0 | --
Fans | 50 | 100 | --
FSK Generator | >0 | 25 | 100
Gateway Trunks | >10 | >50 | 100
I2C Failure | 100 | 100 | --
ICP Comms Card | >0 | 25 | 100
Inactive Boot | -- | 100 | --
License Violation (see Note 1) | N/A | N/A | N/A
Lines | >0 | 20 | 100
CC Memory Avail | -- | >0 | --
SysMem Used (MB) (see Note 2) | If the amount of free system memory is less than 60 MB, the system raises a minor alarm and generates a warning maintenance log. | If the amount of free system memory is less than 45 MB, the system raises a major alarm and generates a warning maintenance log. If the amount of free system memory is less than 35 MB, the system raises a major alarm, generates a warning maintenance log, and schedules resource recovery reboot if programmed (usually set to happen around 2 AM). | If the amount of free system memory is less than 25 MB, the system raises a critical alarm and initiates immediate system reboot.
MG Comms | -- | 100 | --
MNMS Indication | -- | >0 | --
MSP430 | 100 | -- | --
NETSYNC Source | >0 | -- | --
Network Gateway | -- | >0 | --
PER MSG Link | -- | >0 | 100
PER Channels | 10 | 25 | 100
POST Memory Faults | -- | 1 | --
One PSU | -- | 100 | --
Two PSU (see Note 3) | 50 | 100 | --
Receivers | >0 | 25 | 100
RAID Hard Drive | -- | 50 | 100
SDS Sharing (see Note 4) | >100 | >1000 | --
Security | -- | >0 | --
SFT Zones | -- | >0 | 100
SIP Link | 10 | 50 | 100
SYSID Mismatch | -- | >0 | --
T38 Load Fail | 100 | 100 | --
T.38 Licenses | >0 | -- | --
TDM Clock | 50 | 100 | --
Temperature (see Note 5) | -- | -- | 100
Trunks | >0 | 10 | 100
VM Port Status | 1 | -- | --

NOTES

1. Alarm thresholds cannot be set or displayed for alarms that originate in "License Violation" events. These alarms escalate in severity if the underlying event is left unresolved. For details, see License Violation Handling.

2. Threshold percentage is calculated as the amount of free system memory—i.e., 60MB, 45MB, 35MB, 25MB— divided by total amount of system memory installed. For example, a minor alarm on a system with 1G of memory represents a threshold percentage of ~6%.

3. The Two PSU alarm may be cleared on a reboot. After the reboot, you must check the logs or the PSU LEDs to identify which PSU failed.

4. SDS Sharing alarm thresholds are hardcoded (fixed) at the values shown.

5. A major alarm is raised if the controller temperature exceeds 55 degrees Celsius. After the temperature in the controller drops below 50 degrees Celsius, the alarm is cleared.