Didactum Monitoring & PacketTrap Integration
Complete step-by-step guide for integrating Didactum Monitoring devices and sensors into PacketTrap MSP / PacketTrap Network Management via SNMP – including device discovery, MIB import, SNMP Monitor configuration for all sensor types (temperature, leakage, humidity, door contact, smoke), threshold and alarm configuration, SNMP Trap processing as well as dashboard and report setup.
Architecture Note: PacketTrap communicates directly via SNMP with the Didactum device. The PacketTrap server sends SNMP-GET requests (UDP port 161) to the Didactum device and receives SNMP Traps (UDP port 162) from the Didactum device. PacketTrap MSP uses a central server with optional Remote Probes for distributed environments. The Didactum device must be reachable via the network from the PacketTrap server (or the responsible Remote Probe).
- Software: PacketTrap MSP / PacketTrap Network Management (current version)
- Protocol: SNMP v1 / v2c / v3
- Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
- Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke
1. Prerequisites & System Overview
PacketTrap Server
| Component | Requirement / Details |
|---|---|
| PacketTrap Version | PacketTrap MSP or Network Management, current version recommended |
| Operating System | Windows Server 2016 / 2019 / 2022 |
| SNMP Poller | Integrated in PacketTrap; UDP port 161 outbound to the Didactum device open |
| SNMP Trap Receiver | UDP port 162 inbound open on the PacketTrap server |
| MIB Compiler | Integrated in PacketTrap; for importing the Didactum MIB |
| Remote Probe (optional) | If the Didactum device is in a different network segment; install Remote Probe there |
| Network Access | IP reachability from the PacketTrap server (or Remote Probe) to the Didactum device |
Didactum Device
| Requirement | Details |
|---|---|
| Model | Monitoring System 100T, 300T, 500T or 550T |
| SNMP | SNMP enabled (v2c recommended) |
| Community String | Individual Community String (do not use "public") |
| Trap Target | IP address of the PacketTrap server (or the Remote Probe) |
| MIB File | Downloadable under System Settings → SNMP |
Enterprise OIDs by 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: Determine which Enterprise OID your device uses with: snmpwalk -v 2c -c public 192.168.1.50 .1.3.6.1.2.1.1.2.0
2. Enable SNMP on the Didactum Device
Step 1 – Open Web Interface
192.168.1.50 (adjust IP of the Didactum device)
Step 2 – Access SNMP Settings
System Settings → SNMP
Step 3 – Enter the following values
| Field in Didactum Web Interface | Recommended Value |
|---|---|
| Enable SNMP | Enabled |
| SNMP Version | v2c (recommended) |
| Community String (Read) | didactum_packettrap (do not use "public"!) |
| SNMP Port | 161 |
| Trap Destination | IP address of the PacketTrap server (or Remote Probe) |
| Trap Community | didactum_trap |
| Trap Port | 162 |
Step 4 – Download MIB File
System Settings → SNMP → "Download MIB File" File is saved as didactum.mib. This file is imported in Step 3 into PacketTrap.
Save settings. The device will now send Traps to the PacketTrap server.
3. Import MIB File into PacketTrap
PacketTrap includes an integrated MIB Compiler through which the Didactum MIB is loaded. After import, OID numbers are displayed with symbolic names throughout the PacketTrap interface – both in SNMP Monitor configurations and in Trap events and reports.
Step 1 – Determine MIB Directory
Default path on Windows: C:\Program Files (x86)\PacketTrap\MSP\mibs\ C:\Program Files\PacketTrap\Network Management\mibs\ (Exact path depending on PacketTrap version and installation path)
Step 2 – Copy MIB File
Copy didactum.mib to the PacketTrap MIB directory: → <packettrap-install-path>\mibs\didactum.mib
Step 3 – Import MIB via PacketTrap Interface
PacketTrap → Administration → MIB Manager → Import MIB → Alternatively: Tools → MIB Compiler → Load MIB → Select file didactum.mib → Click "Compile" / "Import" → Success message: "DIDACTUM-MIB compiled successfully" → In the MIB tree appears: enterprises → didactum (.1.3.6.1.4.1.46501)
Step 4 – Verify MIB Import
PacketTrap → Tools → 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 correctly resolved
Completed MIB Import Configuration (DIDACTUM-MIB.txt)
If no MIB file is available from the device, save the following minimal MIB structure as DIDACTUM-MIB.txt, copy it to the PacketTrap MIB directory and import as described above:
-- ================================================================
-- DIDACTUM-MIB – Minimal MIB for PacketTrap 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. Add Didactum Device in PacketTrap
Variant A – Automatic Device Discovery
Step 1 – Create Discovery Job
PacketTrap → Discovery → New Discovery Job Job Name: Didactum-Discovery IP Range: 192.168.1.50 – 192.168.1.50 SNMP Version: v2c Community String: didactum_packettrap SNMP Port: 161 Timeout: 5 seconds Retries: 3 → Click "Run Discovery"
Step 2 – Check Discovery Result
→ Device appears in the result list: Name: Didactum Monitoring System (from sysName / sysDescr) IP: 192.168.1.50 Status: SNMP reachable → Click "Add to Monitoring" → Device is added to the device list
Variant B – Manual Creation
PacketTrap → Devices → Add Device Device Name: Didactum-Monitor-01 IP Address: 192.168.1.50 Device Type: SNMP Device / Environmental Monitor SNMP Version: v2c Community String: didactum_packettrap SNMP Port: 161 Timeout: 5 seconds Retries: 3 Location: Server Room Description: Didactum Monitoring System 300T – Server Room Device Group: Environmental Monitoring (create new if not present) → Save
Step 3 – Test SNMP Connection
PacketTrap → Devices → Didactum-Monitor-01 → Test SNMP → Expected result: "SNMP connection successful" → sysDescr: Didactum Monitoring System → sysUpTime: (device uptime) If test fails: → Check Community String and IP address → Check firewall UDP 161 from PacketTrap server to Didactum device → Test snmpwalk directly from the server (see Section 10)
5. Configure SNMP Monitors for Didactum Sensors
Important – Temperature Thresholds:
The Didactum device delivers temperature values as raw value × 10. 25.5 °C = OID value 255. All temperature thresholds in PacketTrap must also be specified × 10.
Add SNMP Monitors
PacketTrap → Devices → Didactum-Monitor-01 → Monitors → Add Monitor → SNMP Monitor
-- ================================================================
-- Monitor 1: Temperature Sensor Measured Value (Sensor-ID 101001)
-- ================================================================
Monitor Name: Temperature_Sensor_01
Monitor Type: SNMP Get
OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
SNMP Version: v2c
Community: didactum_packettrap
Poll Interval: 60 seconds
Data Type: Integer / Gauge
Description: Temperature sensor 01 – raw value x10; 235 = 23.5 °C
Threshold Warning High: 280 (= 28.0 °C)
Threshold Critical High: 350 (= 35.0 °C)
Alarm Message: Didactum Temp Alarm: Raw value ${value} (= ${value/10} °C)
Auto-Clear: Yes
→ Save
-- ================================================================
-- Monitor 2: Temperature Sensor Status (0=OK / 1=Alarm / 2=No Signal)
-- ================================================================
Monitor Name: Temperature_Status_01
OID: .1.3.6.1.4.1.46501.5.1.1.6.101001
Poll Interval: 60 seconds
Data Type: Integer
Threshold Warning High: 1
Threshold Critical High: 2
Alarm Message: Didactum Temp Status: ${value} (0=OK, 1=Alarm, 2=No Signal)
→ Save
-- ================================================================
-- Monitor 3: Water Sensor / Leakage (Sensor-ID 107001)
-- ================================================================
Monitor Name: Leakage_Sensor_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.107001
Poll Interval: 30 seconds
Data Type: Integer
Threshold Critical High: 1 (0 = dry / OK, 1 = Water detected / CRITICAL)
Alarm Message: CRITICAL: Didactum Leakage Alarm – Water detected!
Auto-Clear: Yes
→ Save
-- ================================================================
-- Monitor 4: Humidity (Sensor-ID 102001)
-- ================================================================
Monitor Name: Humidity_Sensor_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.102001
Poll Interval: 60 seconds
Data Type: Integer / Gauge
Unit: %
Threshold Warning High: 80
Threshold Critical High: 90
Alarm Message: Didactum Humidity Alarm: ${value} %
Auto-Clear: Yes
→ Save
-- ================================================================
-- Monitor 5: Door Contact (Sensor-ID 104001)
-- ================================================================
Monitor Name: DoorContact_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.104001
Poll Interval: 30 seconds
Data Type: Integer
Threshold Warning High: 1 (0 = closed / OK, 1 = open / Warning)
Alarm Message: Didactum Door Contact: Door opened – ${device.name}
Auto-Clear: Yes
→ Save
-- ================================================================
-- Monitor 6: Smoke Detector (Sensor-ID 106001)
-- ================================================================
Monitor Name: SmokeDetector_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.106001
Poll Interval: 30 seconds
Data Type: Integer
Threshold Critical High: 1 (0 = no smoke / OK, 1 = Alarm / CRITICAL)
Alarm Message: CRITICAL: Didactum Smoke Detector Alarm! – ${device.name}
Auto-Clear: Yes
→ SaveActivate Monitoring
PacketTrap → Devices → Didactum-Monitor-01
→ Ensure "Enable Monitoring" (all monitors active)
→ After the first poll interval, measured values appear under:
Devices → Didactum-Monitor-01 → Monitor Results6. Configure SNMP Trap Reception
PacketTrap receives SNMP Traps from the Didactum device and processes them as immediate alert events. Combined with SNMP polling, this covers both trend data and immediate alarm notifications.
Step 1 – Activate SNMP Trap Receiver
PacketTrap → Administration → SNMP Trap Receiver Listen Port: 162 Community: didactum_trap SNMP Version: v2c MIB: DIDACTUM-MIB (previously imported) → Activate "Enable Trap Receiver" → Save
Step 2 – Authorize Trap Source
PacketTrap → Administration → SNMP Trap Receiver → Allowed Sources → "Add Source" → IP Address: 192.168.1.50 (Didactum device) → Community: didactum_trap → Device: Didactum-Monitor-01 (assign from device list) → Save
Step 3 – Create Trap Definitions
PacketTrap → 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: 192.168.1.50
Community: didactum_trap
Severity: Critical
Alarm Message: Didactum Trap Alarm: ${varbind[sensorName]} –
Status ${varbind[sensorStatus]} –
Value ${varbind[sensorValue]}
Action: Create Alert + Send Email
→ Save
-- Trap Definition 2: Clear --
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 Alert + Send Email
→ SaveStep 4 – Check Trap Forwarding in Didactum Web Interface
Didactum Web Interface → System Settings → SNMP → Trap Targets Trap Destination: 192.168.1.100 (IP of the PacketTrap server) Trap Community: didactum_trap Trap Version: v2c Trap Port: 162 → Save
7. Configure Alerts and Notifications
Create Alert Policy
PacketTrap → Alerts → Alert Policies → New Policy
Policy Name: Didactum Sensor Alarms
Applies to: Device Group "Environmental Monitoring"
or individual device "Didactum-Monitor-01"
Trigger: Monitor threshold exceeded OR SNMP Trap receivedConfigure Email Notification
PacketTrap → Alerts → Alert Policies → Didactum Sensor Alarms → Actions
Action Type: Send Email
Trigger on: Warning, Critical
Recipients: admin@yourdomain.com
Subject: [PacketTrap] Didactum Alarm: ${device.name} – ${monitor.name}
Body:
Timestamp: ${alert.time}
Device: ${device.name} (${device.ip})
Monitor: ${monitor.name}
Severity: ${alert.severity}
Value: ${monitor.value}
Threshold: ${monitor.threshold}
Location: ${device.location}
Message: ${alert.message}
→ Save
Second action – Alarm cleared:
Action Type: Send Email
Trigger on: Clear / Recovery
Subject: [PacketTrap] Didactum OK: ${device.name} – ${monitor.name} back to normal
→ SaveConfigure Escalation Levels
PacketTrap → Alerts → Alert Policies → Didactum Sensor Alarms → Escalation
Level 1 – Immediate (0 minutes):
Action: Email to admin@yourdomain.com
Condition: Severity Warning or Critical
Level 2 – After 5 minutes (alarm not acknowledged):
Action: Email to it-management@yourdomain.com
Condition: Severity Critical
Level 3 – After 15 minutes (alarm not acknowledged):
Action: SNMP Trap forward to another NMS / SIEM
Condition: Severity Critical
→ Save8. Set Up Dashboard and Reports
Step 1 – Create Dashboard
PacketTrap → Dashboards → New Dashboard Dashboard Name: Server Room Monitoring Didactum Layout: Grid 2 x 3
Step 2 – Configure Widgets
Widget 1: Temperature Trend (Line Chart) Type: Time Series / Line Chart Device: Didactum-Monitor-01 Monitor: Temperature_Sensor_01 Time Range: Last 24 hours Y-Axis: Raw value (÷10 = °C) Threshold: Warning line 280 / Critical line 350 Widget 2: Leakage Status (Status LED) Type: Current Value / Status Indicator Monitor: Leakage_Sensor_01 Green: Value = 0 (dry) Red: Value = 1 (Water detected) Widget 3: Humidity (Gauge) Type: Gauge / Dial Monitor: Humidity_Sensor_01 Min / Max: 0 / 100 % Warning: 80 % Critical: 90 % Widget 4: Door Contact Status (Status LED) Type: Current Value / Status Indicator Monitor: DoorContact_01 Green: Value = 0 (closed) Yellow: Value = 1 (open) Widget 5: Smoke Detector Status (Status LED) Type: Current Value / Status Indicator Monitor: SmokeDetector_01 Green: Value = 0 (no smoke) Red: Value = 1 (Alarm) Widget 6: Active Alarms (Alert List) Type: Alert List Filter: Device = Didactum-Monitor-01 Shows: All active alarms and trap events in real time
Step 3 – Create Automated Report
PacketTrap → Reports → New Report
Report Name: Didactum Server Room – Weekly Report
Devices: Didactum-Monitor-01
Content:
- Temperature Trend 7 days (Min / Max / Average / raw value)
- Humidity Trend 7 days
- Alarm Summary: all Didactum alarms of the week
- Monitor Availability (Uptime of sensor queries)
Schedule: Weekly, Monday 07:00 AM
Recipient: admin@yourdomain.com
Format: PDF
→ Save9. 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 at 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 | .1.3.6.1.4.1.46501.5.1.1.3.101001 |
| Sensor Name | .5.1.1.5.SENSOR_ID | Designation (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 Complete OIDs and PacketTrap Thresholds
| Sensor Type | Sensor ID | OID Measured Value | OID Status | PacketTrap 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 %) |
| Potential-free 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 identical sensors, the last digit increases: 101001, 101002, 101003 etc.
Temperature Thresholds in PacketTrap:
Didactum delivers temperature as raw value × 10. 28.0 °C = OID value 280. Enter PacketTrap thresholds (Warning/Critical High) also as × 10 value. Indicate "÷10 = °C" in alarm messages and dashboard labels.
10. Test SNMP Connection
Test via Command Line (from PacketTrap Server)
# snmpwalk – list all sensor values
snmpwalk -v 2c -c didactum_packettrap 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_packettrap 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_packettrap 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_packettrap 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_packettrap -m ALL 192.168.1.50 \
DIDACTUM-MIB::sensorValue
Test via PacketTrap MIB Browser
PacketTrap → Tools → MIB Browser Host: 192.168.1.50 Community: didactum_packettrap 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
Check Monitor Result
PacketTrap → Devices → Didactum-Monitor-01 → Monitor Results → Temperature_Sensor_01: last value + timestamp appears → Status: OK (green) / Warning (yellow) / Critical (red)
Test Trap Reception
Trigger test trap in Didactum Web Interface: System Settings → SNMP → "Send Test Trap" Check in PacketTrap: → Alerts → Active Alerts → New alert with Source 192.168.1.50 appears → Severity: Critical → Message: Didactum Trap Alarm: … → Email received
11. Troubleshooting
| Problem | Cause & Solution |
|---|---|
| Discovery does not find device | SNMP not enabled on Didactum device; Community String wrong; UDP port 161 blocked by firewall → test snmpwalk directly from PacketTrap server; match Community String in device and PacketTrap |
| MIB Compiler reports error | Dependent MIBs missing (SNMPv2-SMI, RFC1213-MIB) → copy base MIBs to MIB directory first and import; alternatively use DIDACTUM-MIB.txt from Section 3 |
| OID returns "No Such Object" | Wrong Enterprise OID (46501 vs. 39052) → check sysObjectID with 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 delivers raw value × 10. Set PacketTrap thresholds as × 10 value (28 °C = Warning High 280). Adjust dashboard label to ÷10 = °C. |
| Monitor shows no value after poll interval | Monitor not enabled; restart PacketTrap service; test SNMP connection via MIB Browser; check OID entry for typos |
| SNMP Traps do not arrive | Trap target IP in Didactum Web Interface does not point to PacketTrap server; UDP port 162 blocked by firewall; Trap Community does not match → check PacketTrap Trap Receiver log |
| Trap received but no alert generated | Trap definition missing in PacketTrap or Trap OID does not match; Didactum IP not in Allowed Sources → check trap definitions and allowed sources |
| No email on alarm | SMTP settings not configured in PacketTrap; Alert Policy not assigned to device; check spam folder → check Administration → Email Settings |
| Sensor value always remains 0 (Leakage / Door Contact / Smoke) | Normal in uncritical state (0 = OK). Test sensor by briefly triggering it; verify OID directly with snmpget from server. |
| Remote Probe cannot reach device | Remote Probe not in the same network segment as the Didactum device; routing missing → install Remote Probe in the Didactum device segment; assign monitor to the correct probe |
12. Final Checklist
Didactum Device
- SNMP enabled (v2c)
- Community String set (not "public"): didactum_packettrap
- Trap target set to IP of the PacketTrap server
- Trap Community set: didactum_trap
- MIB file downloaded (didactum.mib)
- snmpwalk from PacketTrap server successful
PacketTrap Server
- DIDACTUM-MIB copied to MIB directory and imported via MIB Compiler
- MIB resolution verified in MIB Browser
- Didactum device found via Discovery or created manually
- SNMP connection test successful
- All 6 SNMP Monitors 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
- SNMP Trap Receiver enabled (Port 162)
- Didactum IP entered in Allowed Trap Sources
- Trap definitions for Didactum alarm traps created
- Alert Policy "Didactum Sensor Alarms" configured
- Email notification and escalation levels activated
Tests & Verification
- First monitor results visible after one poll interval
- Dashboard "Server Room Monitoring Didactum" configured with all widgets
- Temperature trend graph shows historical measured values
- Test trap triggered via Didactum Web Interface → Alert appears in PacketTrap
- Email received on test alarm
- Weekly report scheduled and test export successfully created
- Auto-Clear tested: value back in OK range → Alert automatically cleared