How do I monitor devices in the network via SNMP and read specific values?
This guide briefly explains what SNMP is, how to activate SNMP in KentixONE, and how to use OID glossary, MIB structure and trap information for integration into external systems.
Prerequisites
- Access to the KentixONE web interface
- Role with rights to edit the configuration
- Optional: MIB browser (e.g. iReasoning) for testing OIDs
Overview
- SNMP (Simple Network Management Protocol) is used for monitoring and querying devices via OIDs described in a MIB.
- KentixONE supports SNMP v2c and v3. Additionally, SNMP traps (events) can be sent to external systems.
- The OID glossary can be downloaded directly from KentixONE and lists all available query values of the system.
Step-by-Step Guide
1. Open SNMP in Configuration
Navigate to Configuration → Communication → SNMP.
2. Activate SNMP and Set Options
Enable SNMP and optionally select "Immediate query after trap reception". Download the "OID Glossary" if needed.
You must save after activation to make the "OID Glossary" visible.
SNMP versions: Use v3 if possible, as authentication/encryption is available here. v2c is sufficient for simple tests.
3. Create Access Credentials
Under "SNMP Credentials" you can store query accounts for external systems (e.g. community for v2c or user/pass/priv for v3).
| SNMP Type | Description |
|---|---|
| Provide data | Data can be queried by an external device |
| Retrieve data | The Kentix device retrieves data from external systems |
| Send trap | Alarm messages are sent to external devices |
4. Download OID Glossary
Via "Download OID Glossary" you get a CSV overview of all OIDs. Use this for monitoring systems and MIB browsers.
5. Understanding MIB Structure
- Kentix OIDs start below the enterprise branch. Common areas are "system", "sensors", "zones", "logbook", "event".
- Tables (...Table) contain row-based measurement and status values such as temperature, humidity, CO, motion, vibration etc.
MIB Structure
The OIDs of Kentix devices can best be read with a MIB browser (e.g. https://ireasoning.com/mibbrowser.shtml).
The basic structure for an AlarmManager looks like this:
| OID | Name |
|---|---|
| .1.3.6.1.4.1.37954.5 | kentixdevices |
| .1.3.6.1.4.1.37954.5.1 | system |
| .1.3.6.1.4.1.37954.5.1.1 | valuemultiplier |
| .1.3.6.1.4.1.37954.5.1.2 | alarmstate |
| .1.3.6.1.4.1.37954.5.1.3 | energy |
| .1.3.6.1.4.1.37954.5.2 | sensors |
| .1.3.6.1.4.1.37954.5.2.1 | generalTable |
| .1.3.6.1.4.1.37954.5.2.2 | temperatureTable |
| .1.3.6.1.4.1.37954.5.2.3 | humidityTable |
| .1.3.6.1.4.1.37954.5.2.4 | dewpointTable |
| .1.3.6.1.4.1.37954.5.2.5 | coTable |
| .1.3.6.1.4.1.37954.5.2.6 | motionTable |
| .1.3.6.1.4.1.37954.5.2.7 | vibrationTable |
| .1.3.6.1.4.1.37954.5.2.8 | latencyTable |
| .1.3.6.1.4.1.37954.5.2.100 | inputs |
| .1.3.6.1.4.1.37954.5.2.101 | outputs |
| .1.3.6.1.4.1.37954.5.2.102 | pdus |
| .1.3.6.1.4.1.37954.5.3 | zones |
| .1.3.6.1.4.1.37954.5.3.1 | zoneTable |
| .1.3.6.1.4.1.37954.5.4 | logbook |
| .1.3.6.1.4.1.37954.5.4.1 | systemLogbookTable |
| .1.3.6.1.4.1.37954.5.4.2 | accessLogbookTable |
| .1.3.6.1.4.1.37954.5.4.3 | eventLogbookTable |
| .1.3.6.1.4.1.37954.5.100 | event |
AlarmManager Example Table MIB
6. Correctly Interpreting Trap Types
Traps contain among others a unique device ID (eventGlobalIndex), a timestamp, the trap type (eventTraptype) and detailed information (source, device, measurement value, alarm zone). This allows alarms to be uniquely correlated.
Trap Description (Variables)
Below are the most important trap variables including OIDs and their meaning. The values correspond to the Kentix MIB and are used for evaluation in external systems.
AlarmManager / PowerManager / PDU
| Name | OID | Description | Possible Values |
|---|---|---|---|
| eventGlobalIndex | .1.3.6.1.4.1.37954.5.100.1 | Unique device identification number | e.g. 5 (AlarmManager) |
| eventTimestamp | .1.3.6.1.4.1.37954.5.100.2 | Timestamp at the time of alarm/acknowledgeable status in Unix time | |
| format | e.g. 1600438199 (Friday September 18, 2020) | ||
| eventTraptype | .1.3.6.1.4.1.37954.5.100.3 | Alarm type is entered as integer | 1=Temperature, 2=Humidity, 3=Dew |
| point, 4=Fire (DI as fire alarm), 5=Burglary, 6=Vibration, 7=Latency, 8=Service connection lost, 9=SNMP, 11=Heat, | |||
| 12=Air quality, 14=TI-Fire, 15=PeopleCount, 16=Fire-Air quality, 18=CO2, 21=Power deviation, 24=Active power | |||
| exceedance, 30=Fuse, 31=RCM (AC), 32=RCM (DC), 33=Power failure, 51=Sabotage (e.g. Tilt/DI), 52=Connection lost | |||
| (camera/device), 53=Voltage failure, 54=Battery, 101=Digital input (no fire/sabotage alarm) | |||
| eventAlarmState | .1.3.6.1.4.1.37954.5.100.4 | Alarm status | 0=No alarm, 1=Pending alarm (even if |
| acknowledgeable) | |||
| eventAlarmDescription | .1.3.6.1.4.1.37954.5.100.5 | The following values are output depending on the alarm | |
| assignment | Sabotage alarm (for sabotage alarm); System message (for battery alarm); Alarm (for remaining alarms - | ||
| permanent active, armed active etc.) | |||
| eventSource | .1.3.6.1.4.1.37954.5.100.6 | Which alarm was triggered | Battery; CO/Carbon dioxide; Thermal image; |
| People counting; Air quality; Heat detector; Dew point; Power; Room temperature; Rel. humidity; Reed; Motion; | |||
| Latency; Connection; Sabotage; Vibration; SNMP; Name of digital input (if triggered via DI) | |||
| eventDevice | .1.3.6.1.4.1.37954.5.100.7 | Device name that triggered the alarm | e.g. MultiSensor Office 1 |
| eventMeasurement | .1.3.6.1.4.1.37954.5.100.8 | Measured value at which the alarm/recovery trap was triggered | |
| e.g. 30.2 °C | |||
| eventAlarmzone | .1.3.6.1.4.1.37954.5.100.9 | Name of the alarm zone where the alarm occurred | e.g. Server room |
AccessManager
| Name | OID | Description | Possible Values |
|---|---|---|---|
| eventGlobalIndex | .1.3.6.1.4.1.37954.5.100.1 | Unique device identification number | e.g. 7 (AccessManager) |
| eventTimestamp | .1.3.6.1.4.1.37954.5.100.2 | Timestamp at the time of alarm/acknowledgeable status in Unix time | |
| format | e.g. 1600438199 | ||
| eventTraptype | .1.3.6.1.4.1.37954.5.100.3 | Trap type | 151 = Access |
| eventTrapstate | .1.3.6.1.4.1.37954.5.100.4 | Trap status | 0 = no access, 1 = access granted |
| eventDoor | .1.3.6.1.4.1.37954.5.100.5 | Door name | e.g. Rack 01 |
| eventUser | .1.3.6.1.4.1.37954.5.100.6 | Name of the user who booked | e.g. admin |
| eventDetail | .1.3.6.1.4.1.37954.5.100.7 | Booking details | e.g. no door authorization |
| eventAlarmzone | .1.3.6.1.4.1.37954.5.100.8 | Zone name | — |
Note: Depending on firmware version, additional fields may be present. The OID glossary/MIB supplied with KentixONE is authoritative.
More detailed information can also be found here SNMP.
Tips & Tricks
- Start with v3 (authPriv) if your system supports it; set strong passwords/keys.
- Use the OID glossary as the "source of truth" for queries; check for changes after firmware updates.
- For testing: poll specific OIDs via MIB browser and compare with the KentixONE interface.
- Download a MIB file (SNMP V2/3) directly from our website (Resources -> Software Downloads).
Query Examples
Battery Level Query for DoorLocks
The battery level in the SNMP query returns the following values:
- 0 = Battery OK
- 1 = Warning, battery will be empty soon (but usually lasts several more days)
- 2 = Critical, battery almost empty (should be replaced "immediately")
- 3 = Battery empty
GSM Signal
The query for the GSM signal returns the following values:
- 0 = no reception
- 1 = 25% reception
- 2 = 50% reception
- 3 = 75% reception
- 4 = 100% reception
Troubleshooting
- No values via query: Check SNMP version, community/user, firewall and whether SNMP is activated in KentixONE.
- Wrong measurements: Compare OID and index (for tables); use the current OID glossary.
- Traps not arriving: Check target host/port, network accessibility and whether traps are activated in the system.
Glossary
- OID: Object Identifier – unique identifier of a value in the MIB.
- MIB: Management Information Base – structure that describes all OIDs of a manufacturer/functional area.
- Trap: Asynchronous event message that a device sends to an SNMP manager.
- v2c/v3: Protocol versions. v3 supports authentication/privacy (auth/priv).