Skip to main content

Management of alarms' occurrences

The ThingPark 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.

Base station alarms triggered by a state

Alarm numberAlarm description
102Base station connection status
103Unusually low uplink traffic level
104Unusually high level of invalid uplink physical CRC
105Downlink frame rate exceeds the RF cell capacity
106Unusually high CPU usage level
107Unusually high RAM usage level
108Unusually high file system usage level
109Time synchronization lost
110Power failure detected
111Beacon transmission failure
112Abnormal log activation
121Backhaul network interface status

Base station alarms triggered by an event

Alarm numberAlarm description
101LRR software restarted by watchdog
114Wrong MIC detected in Join request
115Join request replay detected (wrong MIC correlation)
116Uplink frame replay detected (wrong FCnt)
117Wrong MIC detected in Uplink frame
118Uplink frame replay detected (repeated FCnt)
119Invalid AppEUI detected in Join request
120Join request replay detected (invalid DevNonce)