Alarms and Events Description
TYPE - ALARM, FAULT, EVENT, OFFLINE.
STATE - RAISED, CLEARED
Online and Offline events are represented by a single Event Type “OFFLINE” and different Event State (RAISED or CLEARED).
- When Entity is Offline - NS creates OFFLINE event in the RAISED state
- When Entity is Online - NS creates OFFLINE event in the CLEARED state. This is similar to Alarms/Faults.
SEVERITY - CRITICAL, MAJOR, MINOR.
Event Name | Description | |
---|---|---|
1 | Gateway shutdown Alarm | Check environmental conditions at the Gateway site. |
2 | Gateway Interface Alarm | There is no downlink network traffic for about 10min. |
3 | Gateway Performance Degrade Alarm | Gateway’s temperature is higher than the radio shutdown treshold. |
4 | Gateway high temp shutdown Alarm | -Reset the GW. -Execute BIST. -Check software versions and upgrade if required. -If condition does not clear, replace the GW. |
5 | Gateway switched to Battery Power | If battery is present in the Gateway and Gateway switched to it for some reasons |
6 | Gateway Low Battery Alarm | If a battery is present in the gateway and it has a low charge level |
7 | Gateway Switch to Secondary Network Interface Alarm | If cellular backhaul is the backup link, this condition could be communicated to the customer |
Event Name | Description | |
---|---|---|
1 | Gateway Authentication error | Gateway MQTT Password does not match the one in Database/ GatewayAuthorizationFailedEvent (GW connection failed because not TLS MQTT) |
2 | Gateway Events Reporting Rate Exceeded | Depends on the Threshold configuration set: -Gateway parameter: -eventThresholdGatewayEventsPerMinute |
3 | Gateway MQTT Rate Exceeded | Depends on the Threshold configuration set: -GW parameter: -eventThresholdMqttMsgPerMinute |
4 | DL_QUEUE_SIZE_EXCEEDED | Threshold configuration: Device parameter: eventThresholdDownlinkQueueSize values range: >0 /null default: 100 |
5 | DEVICE_CANNOT_JOIN | Threshold configuration: Device parameter: eeventThresholdJoinRequestWithoutUl values range: >0 /null default: 100 |
6 | TOO_FREQUENT_UPLINKS | Threshold configuration: Device parameter: eventThresholdUlPerMinuteCounter values range: >0 /null default: 100 |
7 | INVALID_DL_PAYLOAD | Validation of Invalid downlink |
8 | LARGE_DL_DROPPED | LargeDownlinkDroppedEvent The DL size does not fit into the Max MacPayload size (even without MAC commands). MacPayload includes FHdr, FPort and FRMPayload |
9 | DEVICE_DATA_PROCESSING_ERROR | <…>.Packets are lost. |
Event Name | Description | |
---|---|---|
1 | Gateway MQTT Connection Lost | Gateway MQTT Connection is Lost |
2 | Gateway Data Reporting interval Exceed | Depends on the Threshold configuration set: GW parameter: inactivityTimeout |
3 | DEVICE_DATA_REPORTING_INTERVAL_EXCEEDED | Threshold configuration: Device parameter: inactivityTimeout default: 3600 (seconds) |
4 | INTEGRATION_DISCONNECTED | MQTT Integration: Connection lost HTTP Integration: non 2XX response received |
5 | DECODER_BANNED | Javascript function for decoding binary UL payload to JSON is banned due to too long execution time |
6 | ENCODER_BANNED | Javascript function for encoding JSON DL into binary payload is banned due to too long execution time |
ID | Event Name | Description |
---|---|---|
1 | Radio Startup Fault | HAL configuration alarms ported to the customer visible interface. Asserted prior to the start of the packet forwarder or other LoRa utilities. |
2 | Radio Operational Fault | HAL initialization alarms ported to the customer visible interface. Asserted after the packet forwarder, or other LoRa utility, has been started. |
3 | GPS Holdover Expiry | Too much time has elapsed since the GPS was last in the locked state. Transmit and Receive performance may be degraded. |
4 | Cellular Backhaul Fault | If cellular backhaul is the backup link, this condition could be communicated to the customer. |
5 | Gateway Temperature Warning | Gateway temperature exceeds warning threshold |
6 | Gateway Temperature Shutdown | Gateway temperature exceeds shutdown threshold |
7 | Network Server Connection | No Network Server Connection. Gateway Interface Alarm and NS Connection Alarm usually follow one another. The HAL uses this method to detect whether not there are network problems. |