Alarms & Events Reference
Overview
This reference lists every event name that TEKTELIC KONA Core Network Server can record for your LoRaWAN® network. For each event, you see its source, its type, its severity where a source confirms it, what it reports and what to do. Use it when an alarm appears on the Alarms page, or when you choose triggers for an alarm rule.
For the difference between events and alarms, and how an alarm is raised and cleared, see Events & Alarms.
How it works
What each event record holds
Every record on the Alarms page and on a gateway's Events tab has these values:
| UI label | Values |
|---|---|
| Entity | Gateway, Device or Integration: the source of the event. |
| Label | The name or ID of that gateway, device or integration. |
| Type | Alarm, Fault, Offline or Event. The Event types filter on the Alarms page uses the plural: Alarms, Faults, Events and Offline. |
| Event name | A fixed code from the tables below. The UI shows the code as it is, for example GATEWAY_MAC_MISMATCH. |
| Severity | Critical, Major or Minor. |
| State | Raised or Clear. |
| Event ITU type | COMMUNICATION, QOS, EQUIPMENT, SERVICE, PERFORMANCE, ENVIRONMENTAL or SECURITY. confirm where the UI shows the Event ITU type: the Alarms page has no column for it. |
The description of a record tells you the cause, and sometimes the payload involved. For example, an INTEGRATION_DISCONNECTED record names the failed HTTP request and the HTTP status it got. Always read the description before you act on an event.
The API also returns a probable cause and corrective actions for each event: see Get all enhanced events. confirm for which event names KONA Core fills in the corrective actions. The records checked on the live NS had none.
How to read the tables
- The table an event is in shows its source. The UI source marks every gateway event. For device and integration events, the source comes from the event name or from records on the live NS.
- Type and Severity come with the event: you don't choose them in an alarm rule. The device and integration tables show them where a record on the live NS confirms them, and — where no source does yet. The other tables leave both columns out until a source confirms them.
- What it reports describes what the event name says. Where the name doesn't make the meaning clear, a
TODOmarks it. - What to do is the TEKTELIC recommendation for a first check.
confirm the type and severity of every event name with the network-server source. Then add the Type and Severity columns to the other tables and fill in every —.
Gateway events
KONA Core records these events for gateways. You see them on the Alarms page with Entity set to Gateway, and on the gateway's Events tab. See Monitor Gateways.
GATEWAY_AUTHENTICATION_ERROR and GATEWAY_MAC_MISMATCH have the type Events. Select Events in the Event type filter to find them.
| Event name | What it reports | What to do |
|---|---|---|
GATEWAY_MQTT_CONNECTION_LOST | The gateway's MQTT connection to KONA Core is lost. | Check the gateway's power and internet connection. See Onboard a KONA Gateway via MQTT. |
GATEWAY_DATA_REPORTING_INTERVAL_EXCEEDED | The gateway didn't send data within its reporting interval. | Check that the gateway is online and its radio works. Check its timeouts in Configure Gateways. |
GATEWAY_AUTHENTICATION_ERROR | KONA Core rejected the gateway's credentials. | Check that the username and password on the gateway match Manage credentials in KONA Core. |
GATEWAY_MAC_MISMATCH | The gateway ID that the gateway reports doesn't match the one in KONA Core. | Compare the GW-ID in KONA Core with the gateway's sticker. |
GATEWAY_MQTT_RATE_EXCEEDED | The gateway sends MQTT messages faster than KONA Core allows. Contact your Provider if the event persists. | Check the gateway's configuration and logs. |
GATEWAY_EVENTS_REPORTING_RATE_EXCEEDED | The gateway reports events faster than KONA Core allows. Contact your Provider if the event persists. | Check the gateway's logs for repeated alarms. |
GATEWAY_MQTT_INVALID_FIRMWARE_REPORTED_JSON | The firmware report the gateway sent over MQTT isn't valid JSON. | Check the gateway's firmware version. See Upgrade Gateway Firmware. |
GATEWAY_MQTT_INVALID_CONFIGURATION_REPORTED_JSON | The configuration report the gateway sent over MQTT isn't valid JSON. | Check the gateway's configuration. See Configure Gateways. |
GATEWAY_SHUTDOWN_ALARM | The gateway reports a shutdown. | Check the power at the gateway site, then the gateway's logs. |
GATEWAY_HIGH_TEMP_SHUTDOWN_ALARM | The gateway reports a shutdown because of high temperature. | Check the temperature at the site and the gateway's ventilation and sun exposure. |
GATEWAY_SWITCHED_TO_BATTERY_POWER | The gateway runs on its battery. | Check the main power supply at the site. |
GATEWAY_LOW_BATTERY_ALARM | The gateway's battery is low. | Restore the main power supply before the battery runs out. |
GATEWAY_SWITCH_TO_SECONDARY_NETWORK_INTERFACE_ALARM | The gateway switched to its secondary network interface. | Check the gateway's primary backhaul connection. |
GATEWAY_INTERFACE_ALARM | The gateway reports a problem with an interface. confirm which interfaces this alarm covers. | Check the gateway's cables and its logs. |
GATEWAY_PERFORMANCE_DEGRADE_ALARM | The gateway reports degraded performance. | Check the gateway's logs and its CPU, RAM and disk events. |
GATEWAY_HIGH_CPU_UTILISATION | The gateway's CPU use is high. | Check the gateway's logs. If the alarm stays raised, restart the gateway. See Gateway Commands & Management. |
GATEWAY_HIGH_RAM_UTILISATION | The gateway's RAM use is high. | Check the gateway's logs. If the alarm stays raised, restart the gateway. |
GATEWAY_HIGH_DISK_UTILISATION | The gateway's disk use is high. | Check the gateway's logs and its stored files. |
SECURITY_ALARM | The gateway reports a security alarm. confirm what raises it. | Check the gateway's logs. Report it to your Provider. |
STATUS_UPDATE_ALARM | confirm what this alarm reports. | Check the gateway's logs. |
To get notified about the alarms and faults that a gateway reports, add the triggers Gateway alarm and Gateway fault to a gateway group rule. See Configure Gateway Group Alarm Rules.
Device events
| Event name | Type | Severity | What it reports | What to do |
|---|---|---|---|---|
DEVICE_DATA_REPORTING_INTERVAL_EXCEEDED | Offline | Major | The device didn't send an uplink within its reporting interval. | Check the device's battery and radio coverage, and that a gateway near it is online. See Device Activity & Status. |
DEVICE_CANNOT_JOIN | — | — | Repeated join requests aren't followed by uplinks. | Check the DevEUI, JoinEUI and AppKey against the values delivered with the device. See Onboard a TEKTELIC Device. |
DEVICE_JOIN_PROCEDURE_ERROR | — | — | An error occurred during the device's join request processing. | Check the device keys, as for DEVICE_CANNOT_JOIN. Read the description for the cause. |
DEVICE_DATA_PROCESSING_ERROR | — | — | KONA Core couldn't process data from the device. confirm what this error covers. | Read the description for the cause. |
Integration events
| Event name | Type | Severity | What it reports | What to do |
|---|---|---|---|---|
INTEGRATION_DISCONNECTED | Offline | Critical | The integration can't deliver data to your system. The description names the cause, for example an HTTP status. When the connection works again, KONA Core adds a Clear record. | Check that your endpoint or broker is reachable and answers. Data likely isn't reaching your system. See Integration Monitoring. |
INTEGRATION_FIRST_UL | Event | Minor | The first successful uplink after the integration connects. | None. It confirms that data flows again. |
INTEGRATION_UL_DECODING_FAILURE | — | — | The data converter failed to decode an uplink. | Check the decoder against the payload in the description. See Write a Decoder. |
INTEGRATION_DL_ENCODING_FAILURE | — | — | The data converter failed to encode a downlink. | Check the encoder. See Write an Encoder. |
Device or integration events
The UI source doesn't mark these events as gateway events, and the name doesn't give the source. confirm the source (device or integration), the type and the severity of each event in this table.
| Event name | What it reports | What to do |
|---|---|---|
DL_QUEUE_SIZE_EXCEEDED | The device's downlink queue holds more downlinks than the recommended threshold. | Send fewer downlinks, or check that the device receives them. See Send Downlinks. |
DL_QUEUE_IS_FULL | The device's downlink queue is full. New downlinks are lost. | Stop sending downlinks to the device until the queue empties. See Send Downlinks. |
TOO_FREQUENT_UPLINKS | The device sends uplinks more often than KONA Core allows. | Check the device's reporting settings. |
UNKNOWN_DEVICE | KONA Core received data from a device it doesn't know. | If the device is yours, add it to an application. Otherwise, ignore the event. |
LORA_MIC_FAILURE | The MIC check of a message failed. | Check the device's keys. For an ABP device, check its session keys. |
INVALID_UL_FREQUENCY | An uplink arrived on a frequency that isn't valid for the device. | Check that the device and the gateway use the same frequency plan. See Regions & Frequency Plans. |
INVALID_DL_PAYLOAD | A downlink payload isn't valid. | Check the payload format of the downlink you sent. See Send Downlinks. |
DECODER_BANNED | KONA Core stopped running the decoder of a data converter. The UI states the rule: if the code exceeds its execution timeout 5 times within 600 seconds, KONA Core bans it for 30 minutes. | Fix the decoder errors. See Write a Decoder. |
ENCODER_BANNED | KONA Core stopped running the encoder of a data converter, by the same rule as DECODER_BANNED. | Fix the encoder errors. See Write an Encoder. |
Application alarm rules have trigger pairs for these conditions. Examples are Downlink Queue is full (new DLs are lost) and Downlink Queue is not full (can accept new DLs), or Decoder is banned and Decoder is unbanned. See Configure Application Alarm Rules.
Event names only in the API
The API lists these event names, but the UI's list of event names doesn't include them. confirm whether KONA Core records these events, their source, type and severity, and how the Alarms page shows them.
| Event name | What it reports |
|---|---|
LARGE_DL_DROPPED | A large downlink was dropped. Application alarm rules have the triggers Large DL dropped and Large DL dropping stopped. Its size exceeds the allowed MACPayload size even without MAC commands. |
RADIO_STARTUP_FAULT | A radio fault at startup. |
RADIO_OPERATIONAL_FAULT | A radio fault during operation. |
GPS_HOLDOVER_EXPIRY | The GPS holdover time expired. The gateway has gone too long without GPS lock; transmit and receive performance may be affected. |
CELLULAR_BACKHAUL_FAULT | A fault of the cellular backhaul. |
GATEWAY_TEMPERATURE_WARNING | A temperature warning from the gateway. |
GATEWAY_TEMPERATURE_SHUTDOWN | A shutdown because of temperature. |
NETWORK_SERVER_CONNECTION | The gateway has no connection to the Network Server. |
BATTERY_ON_DISCHARGE_OR_GPS_ANTENNA_FAULT | The battery is discharging, or the GPS antenna has a fault. |
LOW_BATTERY_WARNING | A low battery warning. |
To filter the Alarms page by event name and read the full description of a record, see Work with Alarms. To receive events in your own system, see Events over MQTT.