Didactum Monitoring & Zyrion Traverse Integration
Complete step-by-step guide for integrating Didactum monitoring devices and sensors into Zyrion Traverse via SNMP – including device discovery, MIB import, test configuration for all sensor types (temperature, leakage, humidity, door contact, smoke), threshold and alarm configuration, SNMP trap processing via the Traverse trap receiver, as well as dashboard and report setup.
Architecture Note: Zyrion Traverse operates with a test-based monitoring concept. Each monitored metric (OID query) is defined as an independent test, to which thresholds, notification profiles, and actions are directly assigned. The Didactum device is created as a device in Traverse and receives a series of SNMP tests. Traverse sends SNMP GET requests (UDP port 161) to the Didactum device; SNMP traps are actively sent by the Didactum device to the Traverse server (UDP port 162).
- Software: Zyrion Traverse (current version)
- Components: Traverse Web UI, Traverse DGE (Data Gathering Engine), Trap Receiver
- Protocol: SNMP v1 / v2c / v3
- Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
- Sensors: Temperature, leakage, humidity, door contact, smoke
1. Prerequisites & System Overview
Zyrion Traverse Server
| Component | Requirement / Details |
|---|---|
| Zyrion Traverse Version | Current version recommended; DGE (Data Gathering Engine) must be active |
| Operating System | Linux (RHEL / CentOS / Ubuntu) or Windows Server |
| DGE (Data Gathering Engine) | Responsible for SNMP polling; must be reachable in the same network segment as the Didactum device |
| Traverse Trap Receiver | UDP port 162 inbound opened on the Traverse server |
| Network (outbound) | UDP port 161 from DGE to the Didactum device (SNMP polling) |
| Network (inbound) | UDP port 162 from the Didactum device to the Traverse server (SNMP traps) |
| MIB Directory | Accessible MIB path on the Traverse server for MIB import |
| Remote DGE (optional) | If the Didactum device is in a different network segment; deploy a Remote DGE there |
Didactum Device
| Requirement | Details |
|---|---|
| Model | Monitoring System 100T, 300T, 500T or 550T |
| SNMP | SNMP activated (v2c recommended) |
| Community String | Individual community string (do not use "public") |
| Trap Destination | IP address of the Zyrion Traverse server |
| MIB File | Downloadable under System Settings → SNMP |
Enterprise OIDs per Firmware Generation
| Device / Firmware | Enterprise OID (Base) |
|---|---|
| Older models / older firmware | .1.3.6.1.4.1.46501 |
| Newer models / current firmware | .1.3.6.1.4.1.39052 |
Note: You can determine which enterprise OID your device uses via:
snmpwalk -v 2c -c public 192.168.1.50 .1.3.6.1.2.1.1.2.0
2. Activate SNMP on the Didactum Device
Step 1 – Open the Web Interface
192.168.1.50 (adjust IP of the Didactum device)
Step 2 – Open SNMP Settings
System Settings → SNMP
Step 3 – Enter the Following Values
| Field in the Didactum Web Interface | Recommended Value |
|---|---|
| Enable SNMP | Enabled |
| SNMP Version | v2c (recommended) |
| Community String (Read) | didactum_traverse (do not use "public"!) |
| SNMP Port | 161 |
| Trap Destination | IP address of the Zyrion Traverse server |
| Trap Community | didactum_trap |
| Trap Port | 162 |
Step 4 – Download MIB File
System Settings → SNMP → "Download MIB file" File will be saved as didactum.mib. This file will be imported into Traverse in step 3.
Save settings. The device will send SNMP traps to the Traverse server from now on.
3. Import MIB File into Zyrion Traverse
Zyrion Traverse uses MIB files for symbolic resolution of OID numbers in the web interface, during test configurations, and in trap events.
Step 1 – Determine MIB Directory
Standard path on Linux: /usr/local/traverse/mibs/ /opt/traverse/mibs/ Standard path on Windows: C:\Program Files\Zyrion\Traverse\mibs\ (Exact path depends on installation; look up the parameter mib_path in the Traverse configuration file traverse.cfg)
Step 2 – Copy MIB File
Copy didactum.mib into the Traverse MIB directory:
Linux:
cp didactum.mib /usr/local/traverse/mibs/
Windows:
copy didactum.mib "C:\Program Files\Zyrion\Traverse\mibs\"Step 3 – Load MIB via the Traverse Web Interface
Zyrion Traverse Web UI → Administration → MIB Management → Load MIB → Alternatively: Administration → SNMP → MIB Browser → Import → Select file didactum.mib from the MIB directory → Click "Load" / "Import" → Success message: "DIDACTUM-MIB loaded successfully" → In the MIB tree appears: enterprises → didactum (.1.3.6.1.4.1.46501)
Step 4 – Verify MIB Import
Traverse Web UI → Administration → MIB Browser → Enter OID: .1.3.6.1.4.1.46501.5.1.1.7.101001 → Expected result: DIDACTUM-MIB::sensorValue.101001 → Symbolic name is resolved correctly
Ready-made MIB Import Configuration (DIDACTUM-MIB.txt)
If no MIB file is available from the device, copy the following minimal MIB structure as DIDACTUM-MIB.txt into the Traverse MIB directory and import it as described above:
-- ================================================================
-- DIDACTUM-MIB – Minimal MIB for Zyrion Traverse Import
-- File: DIDACTUM-MIB.txt
-- For older
devices: enterprises.46501
-- For newer devices: enterprises.39052 (adjust OID)
-- ================================================================
DIDACTUM-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Integer32, enterprises
FROM SNMPv2-SMI
NOTIFICATION-TYPE
FROM SNMPv2-SMI;
didactum MODULE-IDENTITY
LAST-UPDATED "202401010000Z"
ORGANIZATION "Didactum Security GmbH"
CONTACT-INFO "support@didactum-security.com"
DESCRIPTION "Didactum Monitoring System MIB"
::= { enterprises 46501 }
sensorTable OBJECT-TYPE
SYNTAX SEQUENCE OF SensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Table of all connected sensors"
::= { didactum 5 1 1 }
sensorEntry OBJECT-TYPE
SYNTAX SensorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Single sensor entry"
INDEX { sensorIndex }
::= { sensorTable 1 }
SensorEntry ::= SEQUENCE {
sensorIndex Integer32,
sensorID Integer32,
sensorType Integer32,
sensorName OCTET STRING,
sensorStatus Integer32,
sensorValue Integer32
}
sensorIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
DESCRIPTION "Index"
::= { sensorEntry 1 }
sensorID OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
DESCRIPTION "Sensor ID" ::= { sensorEntry 2 }
sensorType OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
DESCRIPTION "Sensor Type"
::= { sensorEntry 3 }
sensorName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current
DESCRIPTION "Sensor Name" ::= { sensorEntry 5 }
sensorStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
DESCRIPTION "0=OK 1=Alarm 2=No Signal" ::= { sensorEntry 6 }
sensorValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
DESCRIPTION "Measured Value (Temperature: x10)" ::= { sensorEntry 7 }
didactumAlarmTrap NOTIFICATION-TYPE
OBJECTS { sensorName, sensorStatus, sensorValue }
STATUS current
DESCRIPTION "Alarm trap on sensor status change"
::= { didactum 1 1 }
END
4. Create Didactum Device in Zyrion Traverse
Option A – Automatic Device Discovery
Step 1 – Create Discovery Job
Traverse Web UI → Devices → Discovery → New Discovery Discovery Name: Didactum-Discovery IP Range: 192.168.1.50 – 192.168.1.50 DGE: Local DGE (or Remote DGE in the network segment of the device) SNMP Version: v2c Community String: didactum_traverse SNMP Port: 161 Timeout: 5 seconds Retries: 3 → Click "Start Discovery"
Step 2 – Check Discovery Result and Add Device
→ Device appears in the result list:
Name: Didactum Monitoring System (from sysName)
IP: 192.168.1.50
SNMP: Reachable
→ Click "Add to Monitoring"
→ Select Container: Environmental / Server Room
→ Device is added to the Traverse device listOption B – Manual Creation
Traverse Web UI → Devices → Add Device Device Name: Didactum-Monitor-01 IP Address: 192.168.1.50 Device Type: SNMP Device Container: /Environmental/Server Room (create new if not present) DGE: Local DGE or Remote DGE SNMP Version: v2c Community String: didactum_traverse SNMP Port: 161 Timeout: 5 seconds Retries: 3 Description: Didactum Monitoring System 300T – Server Room → Save
Step 3 – Test SNMP Connectivity
Traverse Web UI → Devices → Didactum-Monitor-01 → Test SNMP Connectivity → Expected result: "SNMP connection successful" → sysDescr: Didactum Monitoring System → sysUpTime appears If test fails: → Check community string and IP address → Check firewall UDP 161 from DGE to Didactum device → Test snmpwalk directly from the DGE server (see section 10)
5. Configure SNMP Tests for Didactum Sensors
In Zyrion Traverse, each monitored metric is defined as an independent test. For the Didactum device, SNMP tests are created for all sensor OIDs. Each test receives its own thresholds (Warning / Critical), a polling interval, and a notification profile.
Important – Temperature Thresholds: The Didactum device provides temperature values as raw value × 10. 25.5 °C = OID value 255. All temperature thresholds in Traverse tests must also be specified × 10.
Create SNMP Tests
Traverse Web UI → Devices → Didactum-Monitor-01 → Tests → Add Test → SNMP OID
-- ================================================================
-- Test 1: Temperature Sensor Measured Value (Sensor ID 101001)
-- ================================================================
Test Name: Temperature_Sensor_01
Test Type: SNMP OID
OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
Data Type: Integer / Gauge
Poll Interval: 60 seconds
Description: Temperature sensor 01 – raw value x10;
235 = 23.5 degrees C
Container: /Environmental/Server Room/Didactum-Monitor-01
Thresholds:
Warning High: 280 (= 28.0 degrees C)
Critical High: 350 (= 35.0 degrees C)
Warning Low: (empty)
Critical Low: (empty)
Alarm Message: Didactum Temp Alarm: raw value ${value} (= ${value/10} degrees C)
Recovery Message: Didactum temperature back to normal: raw value ${value}
Notification: Didactum Alarm Profile (create in step 8)
→ Save
-- ================================================================
-- Test 2: Temperature Sensor Status (0=OK / 1=Alarm / 2=No Signal)
-- ================================================================
Test Name: Temperature_Status_01
OID: .1.3.6.1.4.1.46501.5.1.1.6.101001
Data Type: Integer
Poll Interval: 60 seconds
Thresholds:
Warning High: 1
Critical High: 2
Alarm Message: Didactum Temp Status: ${value} (0=OK, 1=Alarm, 2=No Signal)
→ Save
-- ================================================================
-- Test 3: Water Sensor / Leakage
(Sensor ID 107001)
-- ================================================================
Test Name: Leakage_Sensor_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.107001
Data Type: Integer
Poll Interval: 30 seconds
Thresholds:
Critical High: 1 (0 = dry / OK, 1 = water detected / CRITICAL)
Alarm Message: CRITICAL: Didactum Leakage Alarm – water detected!
Device: ${device}
Recovery Message: Didactum Leakage: No water detected anymore
→ Save
-- ================================================================
-- Test 4: Humidity (Sensor ID 102001)
-- ================================================================
Test Name: Humidity_Sensor_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.102001
Data Type: Integer / Gauge
Poll Interval: 60 seconds
Unit: %
Thresholds:
Warning High: 80
Critical High:
90
Alarm Message: Didactum Humidity Alarm: ${value} %
Recovery Message: Didactum humidity back to normal: ${value} %
→ Save
-- ================================================================
-- Test 5: Door Contact (Sensor ID 104001)
-- ================================================================
Test Name: Door_Contact_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.104001
Data Type: Integer
Poll Interval: 30 seconds
Thresholds:
Warning High: 1 (0 = closed / OK, 1 = open
/ Warning)
Alarm Message: Didactum Door Contact: Door opened – Device: ${device}
Recovery Message: Didactum Door Contact: Door closed again
→ Save
-- ================================================================
-- Test 6: Smoke Detector (Sensor ID 106001)
-- ================================================================
Test Name: Smoke_Detector_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.106001
Data Type: Integer
Poll Interval: 30 seconds
Thresholds:
Critical High: 1 (0 = no smoke / OK,
1 = alarm / CRITICAL)
Alarm Message: CRITICAL: Didactum Smoke Detector Alarm!
Device: ${device}
Recovery Message: Didactum Smoke Detector: No smoke detected anymore
→ SaveActivate All Tests
Traverse Web UI → Devices → Didactum-Monitor-01 → Tests
→ Set all tests to "Enabled"
→ Measured values appear after the first poll interval under:
Devices → Didactum-Monitor-01 → Test Results / Performance6. Configure Test Groups and Containers
Zyrion Traverse organizes devices and tests into containers (hierarchical groups). For a clear structure, a separate container is created for the Didactum device.
Traverse Web UI → Containers → New Container
Container Name: Server Room Monitoring
Parent: /Environmental (or Root)
Description: Didactum environmental sensors server room
Icon: Server Room / Environmental
→ Save
Traverse Web UI → Devices → Didactum-Monitor-01 → Move to Container
→ Container: /Environmental/Server Room Monitoring
→ Save
Traverse Web UI → Containers → Server Room Monitoring → Test Groups
→ New Test Group: Didactum Temperature Sensors
Tests: Temperature_Sensor_01,
Temperature_Status_01
→ New Test Group: Didactum Environmental Sensors
Tests: Leakage_Sensor_01, Humidity_Sensor_01,
Door_Contact_01, Smoke_Detector_01
→ Save7. Configure SNMP Trap Reception
The Traverse trap receiver receives inbound SNMP traps from the Didactum device and translates them into Traverse alarms. This creates an event in Traverse immediately upon a sensor alarm – independently of the polling interval.
Step 1 – Activate Trap Receiver
Traverse Web UI → Administration → SNMP Trap Receiver Listen Port: 162 Community: didactum_trap SNMP Version: v2c MIB: DIDACTUM-MIB (previously imported) → Activate "Enable Trap Receiver" → Save → Restart Traverse trap service if required
Step 2 – Authorize Trap Source
Traverse Web UI → Administration → SNMP Trap Receiver → Allowed Sources → Add Source → IP Address: 192.168.1.50 (Didactum device) → Community: didactum_trap → Device: Assign Didactum-Monitor-01 (from device list) → Save
Step 3 – Create Trap Definitions and Mappings
Traverse Web UI → Administration → SNMP Trap Definitions → New Definition
-- Trap Definition 1: General Alarm Trap --
Definition Name: Didactum_Alarm_Trap
Trap OID: .1.3.6.1.4.1.46501.1.1 (didactumAlarmTrap)
Source IP: 192.168.1.50
Community: didactum_trap
Severity:
Critical
Container: /Environmental/Server Room Monitoring
Alarm Message: Didactum Trap Alarm: ${varbind[sensorName]} –
Status ${varbind[sensorStatus]} –
Value ${varbind[sensorValue]}
Action: Create Alarm + Send Notification
→ Save
-- Trap Definition 2: Clear Trap --
Definition Name:
Didactum_Clear_Trap
Trap OID: .1.3.6.1.4.1.46501.1.2
Severity: Informational
Alarm Message: Didactum: ${varbind[sensorName]} – state back to normal
Action: Clear Alarm + Send Notification
→ Save
-- Trap Definition 3: Newer Devices (Enterprise OID 39052) --
Definition Name: Didactum_Alarm_Trap_39052
Trap OID: .1.3.6.1.4.1.39052.1.1
Severity: Critical
Alarm Message:
Didactum (39052) Trap Alarm: ${varbind[sensorName]}
→ SaveStep 4 – Verify Trap Forwarding in Didactum Web Interface
Didactum Web Interface → System Settings → SNMP → Trap Destinations Trap Destination: 192.168.1.100 (IP of the Zyrion Traverse server) Trap Community: didactum_trap Trap Version: v2c Trap Port: 162 → Save
8. Configure Notification Profiles
Zyrion Traverse uses Notification Profiles that are assigned directly to one or several tests. The profile defines who gets notified on which events (Warning / Critical / Recovery).
Step 1 – Create Notification Profile
Traverse Web UI → Administration → Notification Profiles → New Profile
Profile Name: Didactum-Alarm-Profile
Description: Notifications for Didactum sensor alarms
Notify on: Warning, Critical, Unknown
Re-notify every: Every 15 minutes (as long as alarm is active)
Recovery: Yes (Notification on alarm clearance)
Method 1 – Email:
To: admin@yourdomain.com
Subject:
[Traverse] Didactum Alarm: ${device} – ${test} – ${severity}
Body:
Time: ${alert_time}
Device: ${device} (${device_ip})
Test: ${test}
Container: ${container}
Severity: ${severity}
Value: ${current_value}
Threshold: ${threshold}
Message: ${message}
→ SaveStep 2 – Configure Escalation Levels
Traverse Web UI → Administration → Notification Profiles
→ Didactum-Alarm-Profile → Escalation
Level 1 – Immediate (0 minutes):
Method: Email to admin@yourdomain.com
Condition: Warning or Critical
Level 2 – After 5 minutes (alarm still active):
Method: Email to it-management@yourdomain.com
Condition: Critical
Level 3 – After 15 minutes
(alarm still active):
Method: SNMP Trap Forward or script
Condition: Critical
→ SaveStep 3 – Assign Profile to All Didactum Tests
Traverse Web UI → Devices → Didactum-Monitor-01 → Tests For each test (Temperature_Sensor_01, Leakage_Sensor_01 etc.): → Open test → Notification Profile: "Didactum-Alarm-Profile" → Save Alternatively: Batch assignment via container: Containers → Server Room Monitoring → Apply Notification Profile → Profile: Didactum-Alarm-Profile → Apply to all tests in container → Save
9. Configure Dashboard and Reports
Step 1 – Create Dashboard
Traverse Web UI → Dashboards → New Dashboard Dashboard Name: Server Room Monitoring Didactum Layout: Grid 2 x 3
Step 2 – Configure Dashboard Widgets
Widget 1: Temperature Trend (Performance Chart) Type: Performance Graph / Time Series Device: Didactum-Monitor-01 Test: Temperature_Sensor_01 Timeframe: Last 24 hours Y-Axis: Raw value (÷10 = degrees C) Threshold: Warning line 280 / Critical line 350 Widget 2: Leakage Status (Current Value) Type: Current Value / Status LED Test: Leakage_Sensor_01 OK Color: Green (value = 0) Alarm Color: Red (value = 1) Widget 3: Humidity (Gauge) Type: Gauge / Dial Test: Humidity_Sensor_01 Min / Max: 0 / 100 % Warning: 80 % Critical: 90 % Widget 4: Door Contact Status (Current Value) Type: Current Value / Status LED Test: Door_Contact_01 OK Color: Green (value = 0) Alarm Color: Yellow (value = 1) Widget 5: Smoke Detector Status (Current Value) Type: Current Value / Status LED Test: Smoke_Detector_01 OK Color: Green (value = 0) Alarm Color: Red (value = 1) Widget 6: Active Alarms (Alarm Summary) Type: Alarm List / Alert Summary Filter: Container = /Environmental/Server Room Monitoring Shows: All active alarms in real time
Step 3 – Use Container Status View
Traverse Web UI → Containers → Server Room Monitoring → Shows overall status of all tests in the container → Color coding: Green (OK) / Yellow (Warning) / Red (Critical) / Gray (Unknown) → Drill-Down: Click on device → all test results with current value
Step 4 – Create Automated Report
Traverse Web UI → Reports → New Report
Report Name: Didactum Server Room –
Weekly Report
Container: /Environmental/Server Room Monitoring
Tests: All Didactum tests
Content:
- Temperature trend 7 days (Min / Max / Average)
- Humidity trend 7 days
- Alarm summary: all Didactum alarms of the week
- Test availability (% time in OK state)
Schedule: Weekly, Monday 07:00 AM
Recipient: admin@yourdomain.com
Format: PDF
→ Save10. SNMP OID Reference for Didactum Sensors
All Didactum OIDs start with .1.3.6.1.4.1.46501 (older firmware) or .1.3.6.1.4.1.39052 (newer models). The sensor ID is appended to the end.
OID Fields per Sensor
| Field | OID Suffix | Meaning | Example (Sensor 101001) |
|---|---|---|---|
| Sensor Index | .5.1.1.1.SENSOR_ID | Internal index | .1.3.6.1.4.1.46501.5.1.1.1.101001 |
| Sensor ID | .5.1.1.2.SENSOR_ID | Numeric sensor ID | .1.3.6.1.4.1.46501.5.1.1.2.101001 |
| Sensor Type | .5.1.1.3.SENSOR_ID | Type identifier code | .1.3.6.1.4.1.46501.5.1.1.3.101001 |
| Sensor Name | .5.1.1.5.SENSOR_ID | Label (String) | .1.3.6.1.4.1.46501.5.1.1.5.101001 |
| Sensor Status | .5.1.1.6.SENSOR_ID | 0=OK, 1=Alarm, 2=No Signal | .1.3.6.1.4.1.46501.5.1.1.6.101001 |
| Sensor Measured Value | .5.1.1.7.SENSOR_ID | Current measured value | .1.3.6.1.4.1.46501.5.1.1.7.101001 |
Sensor Types with Full OIDs and Traverse Thresholds
| Sensor Type | Sensor ID | OID Measured Value | OID Status | Traverse Threshold |
|---|---|---|---|---|
| Temperature Sensor (digital) | 101001 | .1.3.6.1.4.1.46501.5.1.1.7.101001 | .1.3.6.1.4.1.46501.5.1.1.6.101001 | Warning High 280 / Critical High 350 (raw value × 10) |
| Temperature Sensor (analog) | 201001 | .1.3.6.1.4.1.39052.5.2.1.7.201001 | .1.3.6.1.4.1.39052.5.2.1.6.201001 | Warning High 280 / Critical High 350 (× 10) |
| Water Sensor / Leakage | 107001 | .1.3.6.1.4.1.46501.5.1.1.7.107001 | .1.3.6.1.4.1.46501.5.1.1.6.107001 | Critical High 1 (0 = dry / OK) |
| Humidity | 102001 | .1.3.6.1.4.1.46501.5.1.1.7.102001 | .1.3.6.1.4.1.46501.5.1.1.6.102001 | Warning High 80 / Critical High 90 (direct %) |
| Dry Contact | 101003 | .1.3.6.1.4.1.39052.5.1.1.7.101003 | .1.3.6.1.4.1.39052.5.1.1.6.101003 | Warning High 1 (0 = open / inactive) |
| Door Contact | 104001 | .1.3.6.1.4.1.46501.5.1.1.7.104001 | .1.3.6.1.4.1.46501.5.1.1.6.104001 | Warning High 1 (0 = closed / OK) |
| Smoke Detector | 106001 | .1.3.6.1.4.1.46501.5.1.1.7.106001 | .1.3.6.1.4.1.46501.5.1.1.6.106001 | Critical High 1 (0 = no smoke / OK) |
Determine Sensor ID: In the Didactum Web Interface under System Tree → Select Sensor → Details. The displayed sensor ID is appended as the last element to the OID. For multiple sensors of the same type, the last digit increases: 101001, 101002, 101003 etc.
Temperature Thresholds in Traverse: Didactum provides temperature as raw value × 10. 28.0 °C = OID value 280. Enter Traverse test thresholds (Warning/Critical High) likewise as a × 10 value. Point out "÷10 = °C" in alarm messages and dashboard labels.
11. Test SNMP Connection
Test via Command Line (from Traverse Server or DGE)
# snmpwalk – list all sensor values
snmpwalk -v 2c -c didactum_traverse 192.168.1.50 \
.1.3.6.1.4.1.46501.5.1.1
# snmpget – query temperature value (raw value ÷ 10 = °C)
snmpget -v 2c -c didactum_traverse 192.168.1.50 \
.1.3.6.1.4.1.46501.5.1.1.7.101001
# Expected output: INTEGER: 235 (= 23.5 °C)
# snmpget – query leakage status
snmpget -v 2c -c didactum_traverse 192.168.1.50 \
.1.3.6.1.4.1.46501.5.1.1.7.107001
# Expected output (dry): INTEGER: 0
# snmpget – query sensor status
snmpget -v 2c -c didactum_traverse 192.168.1.50 \
.1.3.6.1.4.1.46501.5.1.1.6.101001
# Expected output (OK): INTEGER: 0
# Test with MIB names (after MIB import)
snmpwalk -v 2c -c didactum_traverse -m ALL 192.168.1.50 \
DIDACTUM-MIB::sensorValue
Test via Traverse MIB Browser
Traverse Web UI → Administration → MIB Browser Host: 192.168.1.50 Community: didactum_traverse Version: v2c OID: .1.3.6.1.4.1.46501.5.1.1.7.101001 → Click "Get" → raw value appears (e.g. 235 = 23.5 °C) MIB Browser → Walk → OID: .1.3.6.1.4.1.46501.5.1.1 → All sensor OIDs and raw values are listed
Verify Test Results
Traverse Web UI → Devices → Didactum-Monitor-01 → Tests → All tests appear with status "OK" and current value → Last poll timestamp is displayed Traverse Web UI → Containers → Server Room Monitoring → Overall Status: All traffic lights green (normal operation)
Test Trap Reception
Trigger a test trap in the Didactum Web Interface: System Settings → SNMP → "Send Test Trap" Verify in Traverse: → Traverse Web UI → Alarms → Active Alarms → New alarm with device 192.168.1.50 appears → Severity: Critical → Message: Didactum Trap Alarm: … → Email received from notification profile
12. Troubleshooting and Solutions
| Problem | Cause & Solution |
|---|---|
| Discovery does not find device | SNMP not activated on Didactum device; community string incorrect; UDP port 161 blocked by firewall between DGE and device → test snmpwalk directly from DGE; verify community string |
| MIB import fails | Dependent MIBs missing (SNMPv2-SMI, RFC1213-MIB) → copy base MIBs into Traverse MIB directory first; alternatively use DIDACTUM-MIB.txt from section 3 |
| OID returns "No Such Object" | Incorrect enterprise OID (46501 vs. 39052) → check sysObjectID via snmpwalk: snmpwalk -v 2c -c COMMUNITY IP .1.3.6.1.2.1.1.2.0 |
| Temperature value appears 10× too high | Not an error – Didactum provides raw value × 10. Set Traverse test thresholds as a × 10 value (28 °C = Warning High 280). Adjust dashboard label to ÷10 = °C. |
| Test shows no value after poll interval | DGE not reachable or not active; test not activated; check OID input for typos → check DGE status in Traverse Administration; test snmpget directly from DGE |
| SNMP traps do not arrive | Trap destination IP in Didactum device does not point to the Traverse server; UDP port 162 blocked by firewall; trap community does not match; trap receiver not activated → check Traverse trap receiver log |
| Trap received, but no alarm created | Trap definition missing or trap OID does not match; Didactum IP not in Allowed Sources → check trap definitions and Allowed Sources in Administration |
| No email on alarm | SMTP settings not configured in Traverse; notification profile not assigned to the test; escalation policy not active → check Administration → SMTP Settings; check Test → Notification Profile |
| Sensor value always remains 0 (leakage / door contact / smoke) | Normal for non-critical state (0 = OK). Test sensor by triggering it briefly; verify OID via snmpget directly from DGE. |
| DGE does not reach device (Remote DGE) | Remote DGE not in the same network segment as the Didactum device; routing issue → assign test to the correct DGE; check network route; if necessary, install Remote DGE in the segment of the Didactum device |
| Test status remains "Unknown" | First poll not yet conducted; DGE connection interrupted; SNMP timeout too short → wait for poll interval; increase timeout from 5 to 10 seconds; check DGE status |
13. Final Checklist
Didactum Device
- SNMP activated (v2c)
- Community string set (not "public"): didactum_traverse
- Trap destination set to IP of the Zyrion Traverse server
- Trap community set: didactum_trap
- MIB file downloaded (didactum.mib)
- snmpwalk from Traverse server / DGE successful
Zyrion Traverse Server
- DIDACTUM-MIB copied into Traverse MIB directory and imported
- MIB resolution verified in MIB Browser
- Container /Environmental/Server Room Monitoring created
- Didactum device found via discovery or manually created
- Device assigned to container Server Room Monitoring
- SNMP connectivity test successful
- All 6 SNMP tests created (temperature, temp status, leakage, humidity, door contact, smoke)
- Temperature thresholds set as raw value × 10 (Warning High 280 / Critical High 350)
- Leakage and smoke detector critical threshold set to 1
- Test groups created (Temperature Sensors / Environmental Sensors)
- SNMP Trap Receiver activated (Port 162)
- Didactum IP added to Allowed Trap Sources
- Trap definitions for Didactum alarm traps created (46501 and 39052)
- Notification profile "Didactum-Alarm-Profile" created
- Profile assigned to all 6 tests
- SMTP settings configured in Traverse
Tests & Verification
- All tests show status OK and current value after first poll interval
- Container Status: Server Room Monitoring shows green (normal operation)
- Dashboard "Server Room Monitoring Didactum" configured with all widgets
- Temperature trend graph shows historical measured values
- Test trap triggered via Didactum Web Interface → alarm appears in Traverse
- Email received from notification profile on test alarm
- Weekly Report planned and test export successfully generated
- Recovery tested: sensor returns to OK state → alarm cleared, recovery email received