Skip to main content

Management of alarms' occurrences

The ThingPark Enterprise platform manages the number of occurrences of alarms that are raised according to a classification of alarms.

  • State-driven alarms

  • Event-driven alarms

For a state-driven alarm, the number of occurrences is not applicable and always set to 1.

For an event-driven alarm, the number of occurrences increases each time the event associated with the alarm is detected. Hence, a high number of occurrences of an event-driven alarm can be considered as an aggravating factor of the severity of the alarm.

Note Existing alarms are not migrated. Hence, existing state-driven alarms with a number of occurrences greater than 1 will still exist after an upgrade. For these alarms, the number of occurrences will be reset to 1 when the alarm will be recycled (that is, updated from clear to non-clear state).

The following tables detail this categorization.

Device alarms triggered by a state

Alarm numberAlarm description
001Battery level threshold
004No uplink activity warning
005Node uses higher data rate than expected
006Node uses lower data rate than expected
012MAC command transmission blocked because of rejection
013MAC command transmission blocked because of no reply

Device alarms triggered by an event

Alarm numberAlarm description
002Traffic exceeds the downlink regulator settings
003Traffic exceeds the uplink regulator settings
007Join request replay detected (DevNonce replay)
008Wrong MIC detected in Join request
009Join request replay detected (wrong MIC correlation)
010Uplink frame replay detected (wrong FCnt)
011Uplink frame replay detected (repeated FCnt)
014Invalid AppEUI detected in Join request
015Join request replay detected (invalid DevNonce)
016Wrong MIC detected in Uplink frame