Didactum Monitoring & ManageEngine OpManager Integration

Complete step-by-step guide for integrating Didactum monitoring devices and sensors into ManageEngine OpManager via SNMP – including device discovery, MIB import, custom SNMP monitor (performance monitor), SNMP trap processors, device template, and email alerting[cite: 244].

OpManager Special Feature: OpManager provides SNMP monitoring for common device types out of the box[cite: 245]. For manufacturer-specific OIDs, OpManager allows the creation of custom SNMP monitors[cite: 246]. This is done by entering the desired OID and verifying it by querying a device[cite: 246]. The OIDs can be entered directly or selected via the integrated MIB browser[cite: 247].

• Software: ManageEngine OpManager (25.x / 2024) [cite: 248]
• Components: Custom SNMP Monitor, Performance Monitor, SNMP Trap Processor, Device Template, Alert Profiles [cite: 248]
• Protocol: SNMP v1 / v2c / v3 [cite: 248]
• Devices: Didactum Monitoring System 100T / 300T / 500T / 540T [cite: 248]
• Sensors: Temperature, leakage, humidity, door contact, smoke [cite: 249]

1. Prerequisites & System Overview [cite: 249, 250]

OpManager Server

• ManageEngine OpManager installed (Windows or Linux) [cite: 250]
• Web interface accessible: <Server> (Standard Port) [cite: 250]
• UDP port 161 outbound for SNMP polling [cite: 250]
• UDP port 162 inbound for SNMP traps [cite: 250]
• Network access to the Didactum device [cite: 250, 251]

Didactum Device

• Monitoring System 100T, 300T, 500T or 550T [cite: 251]
• SNMP enabled (v2c recommended) [cite: 251]
• Device reachable via ICMP (Ping) from the OpManager server [cite: 251]
• MIB file available in the web interface [cite: 251]

Important OpManager Directories

Windows: C:\Program Files\ManageEngine\OpManager\
Linux:   /opt/ManageEngine/OpManager/ [cite: 251, 252]

MIB directory: [OpManager-Home]\mibs\ [cite: 252]

Architecture & Data Flow

[OpManager Web Console]
       |
       v [cite: 252, 253]
[OpManager Server]   --SNMP Polling UDP 161-->  [Didactum 192.168.1.50] [cite: 253]
       ^             <--SNMP Traps  UDP 162--- [cite: 253]
       |
[Custom SNMP Monitors]: [cite: 254]
  - Didactum Temperature Sensor 01 [cite: 254]
  - Didactum Leakage Sensor 01 [cite: 254]
  - Didactum Humidity 01 [cite: 254]
  - Didactum Door Contact 01 [cite: 254]
  - Didactum Smoke Detector 01 [cite: 254]
[SNMP Trap Processors]: [cite: 254]
  - Didactum Enterprise Trap [cite: 254]
[Alert Profiles] → Email, Syslog, Webhook [cite: 254]

2. Enable SNMP on the Didactum Device

Step 1 – Open Web Interface

Open in browser: 192.168.1.50 (adjust the IP of the Didactum device)

Step 2 – Open SNMP Settings

System Settings → SNMP

Step 3 – Enter the Following Values

Field in Didactum Web Interface [cite: 255]	Value [cite: 255, 256]
Enable SNMP [cite: 256, 257]	Enabled [cite: 257]
SNMP Version [cite: 258]	v2c (recommended) [cite: 258]
Community String [cite: 259]	didactum_opm (do not use "public"!) [cite: 259, 260]
SNMP Port [cite: 260, 261]	161 [cite: 261]
Trap Receiver IP [cite: 261, 262]	192.168.1.10 (IP of the OpManager server) [cite: 262]
Trap Port [cite: 263]	162 [cite: 263, 264]
Trap Version [cite: 264]	v2c [cite: 265]

SNMPv3 Settings (optional)

Field [cite: 265, 266]	Value [cite: 266, 267]
Security Name [cite: 267]	opm_user [cite: 267, 268]
Auth Protocol [cite: 268, 269]	SHA [cite: 269]
Auth Password [cite: 269, 270]	min. 8 characters [cite: 270, 271]
Priv Protocol [cite: 271]	AES [cite: 271, 272]
Priv Password [cite: 272, 273]	min. 8 characters [cite: 273, 274]
Security Level [cite: 274]	authPriv [cite: 274, 275]

3. Import MIB File into OpManager

The SNMP management system in the device sends traps with varbinds (OID-value pairs) generated based on the MIBs[cite: 275, 276]. To convert the varbinds in OpManager into quantifiable values, the relevant MIB file must be selected[cite: 276, 277]. The MIB file must be stored in the MIBs folder of OpManager[cite: 277].

Step 1 – Download MIB from the Didactum Web Interface

System Settings → SNMP → "Download MIB file" → didactum.mib

Step 2 – Copy MIB File into OpManager Directory

# Windows:
copy didactum.mib "C:\Program Files\ManageEngine\OpManager\mibs\"

# Linux:
cp didactum.mib /opt/ManageEngine/OpManager/mibs/

Step 3 – Load MIB in OpManager Web Interface

OpManager Web Console → Settings → Monitoring → SNMP Trap Processors
→ click "Trap Settings"
→ click "Click here" button (open MIB list)
→ select "didactum.mib" from the list → Load

Step 4 – Verify MIB in MIB Browser

Settings → Monitoring → Performance Monitors
→ "Add Monitor" → SNMP Monitor → click "Choose OID" button [cite: 277, 278]
→ MIB Browser opens
→ navigate to enterprises → 46501 → Sensor table
→ Didactum OIDs appear with clear names

4. Add Didactum Device (Discovery)

Option A – Single Device via „Quick Add"

OpManager Web Console → Discovery → Add Device
→ select "Add a Single Device"
  IP Address:         192.168.1.50
  Device Name:        Didactum-Monitor-01
  SNMP Community:     didactum_opm
  SNMP Version:       v2c
  SNMP Port:          161 [cite: 278, 279]
→ click "Discover"

Option B – Discovery Rule for Automatic Detection

Discovery → Discovery Rules → Add
  Rule Name:          Didactum Devices
  IP Range:           192.168.1.50 – 192.168.1.55
  SNMP Community:     didactum_opm
  SNMP Version:       v2c
→ click "Discover" or "Schedule"

Step 3 – Verify Device in Device Inventory

Inventory → Devices → All Devices
→ look for device "Didactum-Monitor-01" (192.168.1.50)
→ Status icon shows green if ICMP + SNMP reachable [cite: 279, 280]

Step 4 – Verify / Set SNMP Community on Device

Click device "Didactum-Monitor-01" → "Edit Device"
→ SNMP tab: Community String = didactum_opm, Version = v2c
→ click "Test SNMP" → Green success message
→ Save

5. Custom SNMP Monitor for All Sensor Types

OpManager allows the creation of custom SNMP monitors for manufacturer-specific OIDs[cite: 280, 281]. Initially, the desired OIDs are entered and verified by querying a device[cite: 281, 282]. OIDs can be conveniently selected from the MIB database via the integrated MIB browser[cite: 282, 283].

Navigation

Settings → Monitoring → Performance Monitors → Add Monitor → SNMP Monitor

Custom SNMP Monitor: Temperature Sensor

Step 1 – Enter and test OID:

Field [cite: 283, 284]	Value [cite: 284]
Monitor Name [cite: 285]	Didactum Temperature Sensor 01 [cite: 285, 286]
Device Name (Test) [cite: 286]	Didactum-Monitor-01 (for OID test) [cite: 286, 287]
SNMP OID [cite: 287, 288]	.1.3.6.1.4.1.46501.5.1.1.7.101001 [cite: 288]
Display Name [cite: 288, 289]	Temperature Sensor 01 [cite: 289, 290]

Click on „Query device" → Raw value appears (e.g., 235 = 23.5 °C)[cite: 290, 291]. Click on „Next".

Step 2 – Configure graph details:

Field [cite: 291]	Value [cite: 291, 292]
Graph Title [cite: 292, 293]	Didactum Temperature Sensor 01 [cite: 293]
Y-Axis Label [cite: 294]	0.1 Degrees C (Raw value) [cite: 294, 295]
Unit [cite: 295, 296]	0.1°C [cite: 296]
Enable Graphing [cite: 296, 297]	Yes [cite: 297]
Polling Interval [cite: 298]	5 Minutes [cite: 298, 299]

Step 3 – Configure threshold values:

Field [cite: 299, 300]	Value [cite: 300]
Warning (High) [cite: 301]	280 (= 28.0 °C – Raw value × 10) [cite: 301, 302]
Critical (High) [cite: 302, 303]	350 (= 35.0 °C – Raw value × 10) [cite: 303]
Warning (Low) [cite: 303, 304]	50 (= 5.0 °C) [cite: 304]
Critical (Low) [cite: 305]	20 (= 2.0 °C) [cite: 305, 306]
Rearm Value (High) [cite: 306, 307]	270 (Alarm cleared when value drops below 27.0 °C) [cite: 307]

Important – Temperature Thresholds: Didactum delivers temperatures as raw value × 10[cite: 307, 308]. 28.0 °C = OID value 280[cite: 308]. Therefore, all thresholds must be entered × 10[cite: 308].

Click on „Save"[cite: 309].

Custom SNMP Monitor: Leakage Sensor

Field [cite: 309]	Value [cite: 310]
Monitor Name [cite: 310, 311]	Didactum Leakage Sensor 01 [cite: 311]
SNMP OID [cite: 312]	.1.3.6.1.4.1.46501.5.1.1.7.107001 [cite: 312, 313]
Unit [cite: 313]	0=OK, 1=Water [cite: 314]
Warning (High) [cite: 314, 315]	empty (no warning for leakage) [cite: 315]
Critical (High) [cite: 316]	0 (Value > 0 = Water = Critical) [cite: 316, 317]
Rearm Value (High) [cite: 317]	0 [cite: 318]
Polling Interval [cite: 318, 319]	2 Minutes [cite: 319]

Custom SNMP Monitor: Temperature Sensor Status

Field [cite: 320]	Value [cite: 321]
Monitor Name [cite: 321, 322]	Didactum Temp-Status Sensor 01 [cite: 322]
SNMP OID [cite: 323]	.1.3.6.1.4.1.46501.5.1.1.6.101001 [cite: 323, 324]
Unit [cite: 324]	0=OK, 1=Alarm, 2=No Signal [cite: 325]
Critical (High) [cite: 325, 326]	0 (Status > 0 = Problem) [cite: 326, 327]
Polling Interval [cite: 327]	5 Minutes [cite: 328]

Custom SNMP Monitor: Humidity

Field [cite: 329]	Value [cite: 329, 330]
Monitor Name [cite: 330, 331]	Didactum Humidity Sensor 01 [cite: 331]
SNMP OID [cite: 331, 332]	.1.3.6.1.4.1.46501.5.1.1.7.102001 [cite: 332]
Unit [cite: 332, 333]	% [cite: 333, 334]
Warning (High) [cite: 334]	80 [cite: 335]
Critical (High) [cite: 335, 336]	90 [cite: 336]
Warning (Low) [cite: 336, 337]	20 [cite: 337, 338]
Polling Interval [cite: 338]	5 Minutes [cite: 339]

Custom SNMP Monitor: Door Contact

Field [cite: 340]	Value [cite: 340, 341]
Monitor Name [cite: 341]	Didactum Door Contact 01 [cite: 341, 342]
SNMP OID [cite: 342, 343]	.1.3.6.1.4.1.46501.5.1.1.7.104001 [cite: 343]
Unit [cite: 344]	0=closed, 1=open [cite: 344, 345]
Warning (High) [cite: 345, 346]	0 (Value > 0 = Door open = Warning) [cite: 346, 347]
Polling Interval [cite: 347]	1 Minute [cite: 348]

Custom SNMP Monitor: Smoke Detector

Field [cite: 349]	Value [cite: 349, 350]
Monitor Name [cite: 350, 351]	Didactum Smoke Detector 01 [cite: 351]
SNMP OID [cite: 351, 352]	.1.3.6.1.4.1.46501.5.1.1.7.106001 [cite: 352, 353]
Unit [cite: 353]	0=OK, 1=Alarm [cite: 354]
Critical (High) [cite: 354]	0 (Value > 0 = Smoke = Critical) [cite: 355, 356]
Polling Interval [cite: 356]	1 Minute [cite: 357]

6. Assign Monitor to Device

Step 1 – Assign Monitor via Device Profile

Inventory → Devices → Didactum-Monitor-01 → "Monitors" Tab
→ click "Associate Monitors" [cite: 357, 358]
→ Select all Didactum monitors:
  ✅ Didactum Temperature Sensor 01
  ✅ Didactum Leakage Sensor 01
  ✅ Didactum Temp-Status Sensor 01
  ✅ Didactum Humidity Sensor 01
  ✅ Didactum Door Contact 01
  ✅ Didactum Smoke Detector 01
→ click "Associate"

Step 2 – Verify Monitoring Data

Device "Didactum-Monitor-01" → "Performance" Tab
→ All assigned monitors appear with current values
→ Graphs will be displayed after the next polling cycle
→ Temperature raw value e.g., 235 (= 23.5 Degrees C) [cite: 358, 359]

Step 3 – Monitor for Bulk Assignment (multiple devices)

Settings → Monitoring → Performance Monitors
→ Select monitor "Didactum Temperature Sensor 01"
→ click "Associate to Devices"
→ Select all Didactum devices from the list
→ click "Associate"

7. Create Device Template for Didactum

A Device Template bundles all monitors for Didactum devices[cite: 359, 360]. During discovery, the template is automatically applied to detected Didactum devices[cite: 360, 361].

Step 1 – Create Device Template

Settings → Configuration → Device Templates → Add Template
  Template Name:  Didactum Monitoring System
  Description:    Template for Didactum Environmental Monitoring devices
  Device Type:    Other
  Vendor:         Didactum

Step 2 – Set SNMP Detection OID

Template → "SNMP Properties":
  SysObjectID: .1.3.6.1.4.1.46501
  (Newer models: .1.3.6.1.4.1.39052)

Step 3 – Add Monitors to Template

Template → "Monitors" Tab → "Add Monitor":
  Add all Didactum Custom SNMP Monitors
→ Save Template

Step 4 – Link Discovery Rule with Template [cite: 361, 362]

Discovery → Discovery Rules → edit "Didactum Devices"
→ Device Template: select "Didactum Monitoring System"
→ Save
→ Monitors will be automatically assigned at the next discovery

8. Configure SNMP Trap Processor

Before traps can be processed, trap processing must be enabled in OpManager[cite: 362, 363]. Navigation: Settings → Monitoring → SNMP Trap Processors. Click on „Trap Settings" and enable Trap Processing (disabled by default)[cite: 363, 364].

Step 1 – Enable Trap Processing

Settings → Monitoring → SNMP Trap Processors → Trap Settings
→ enable "Enable Trap Processing" (check the box)
→ Trap Port: 162 (Standard)
→ Save

Step 2 – Load MIB for Trap Processing

Trap Settings → "Click here" (MIB list)
→ select "didactum.mib" from the list
→ Didactum trap OIDs appear for selection

Step 3 – Trap Processor: Leakage

Settings → Monitoring → SNMP Trap Processors → Add Trap Processor

Field [cite: 365]	Value [cite: 365, 366]
Processor Name [cite: 366]	Didactum Leakage Trap [cite: 367]
SNMP Trap Version [cite: 367, 368]	SNMP V2c [cite: 368]
Trap OID [cite: 369]	.1.3.6.1.4.1.46501.5.1.1.7.107001 (select from MIB via "Select") [cite: 369, 370]
Severity [cite: 370]	Critical [cite: 370, 371]
Failure Component [cite: 371, 372]	Leakage Sensor [cite: 372]
Message [cite: 372, 373]	LEAKAGE ALARM: Didactum water sensor – Water detected! Value: $v1 [cite: 373, 374]
Match Criteria [cite: 374]	Variable Binding $v1 (Value) = 1 [cite: 375]
Rearm Criteria [cite: 375, 376]	Variable Binding $v1 = 0 [cite: 376]

Click on Save[cite: 377].

Step 4 – Trap Processor: Temperature Alarm

Field [cite: 378]	Value [cite: 379]
Processor Name [cite: 379, 380]	Didactum Temperature Trap [cite: 380]
Trap OID [cite: 381]	.1.3.6.1.4.1.46501.5.1.1.6.101001 [cite: 381, 382]
Severity [cite: 382]	Critical [cite: 383]
Message [cite: 383, 384]	TEMPERATURE ALARM: Didactum Sensor Status = $v1 (1=Alarm, 2=No Signal) [cite: 384]
Match Criteria [cite: 385]	Variable Binding $v1 >= 1 [cite: 385, 386]
Rearm Criteria [cite: 386]	Variable Binding $v1 = 0 [cite: 387]

Step 5 – Trap Processor: Smoke Detector

Field [cite: 388]	Value [cite: 388, 389]
Processor Name [cite: 389, 390]	Didactum Smoke Detector Trap [cite: 390]
Trap OID [cite: 390, 391]	.1.3.6.1.4.1.46501.5.1.1.7.106001 [cite: 391]
Severity [cite: 392]	Critical [cite: 392, 393]
Message [cite: 393]	SMOKE DETECTOR ALARM: Didactum – Smoke detected! Immediate actions required! [cite: 394, 395]
Match Criteria [cite: 395]	Variable Binding $v1 = 1 [cite: 396]
Rearm Criteria [cite: 396, 397]	Variable Binding $v1 = 0 [cite: 397]

Step 6 – Trap Processor: Door Contact [cite: 397, 398]

Field [cite: 398]	Value [cite: 399]
Processor Name [cite: 400]	Didactum Door Contact Trap [cite: 400]
Trap OID [cite: 401]	.1.3.6.1.4.1.46501.5.1.1.7.104001 [cite: 401, 402]
Severity [cite: 402]	Warning [cite: 403]
Message [cite: 403, 404]	DOOR ALARM: Didactum – Door opened! Value: $v1 [cite: 404, 405]
Match Criteria [cite: 405]	Variable Binding $v1 = 1 [cite: 406]
Rearm Criteria [cite: 406, 407]	Variable Binding $v1 = 0 [cite: 407]

Step 7 – SNMP Trap Viewer

The SNMP Trap Viewer is a powerful diagnostic tool that displays all incoming traps in real time – regardless of whether the device is managed in OpManager[cite: 408].

Settings → Monitoring → SNMP Trap Processors → open "Trap Viewer" [cite: 409]
→ Incoming traps from the Didactum device are displayed here in real time [cite: 409]
→ Traps from unmanaged devices also appear here [cite: 409]

9. Alert Profile & Email Notification [cite: 409, 410]

Step 1 – Configure Mail Server

Settings → General Settings → Mail Server Settings
  Mail Server:      mail.yourdomain.com
  Port:             587
  Use SSL/TLS:      Yes (STARTTLS)
  Username:         opmanager@yourdomain.com
  Password:         YourPassword
  From Address:     opmanager@yourdomain.com
→ "Send Test Mail" → check inbox → Save

Step 2 – Create Alert Profile

Settings → Notifications → Add Notification Profile [cite: 410, 411]

Field [cite: 411]	Value [cite: 412]
Profile Name [cite: 413]	Didactum Alarm Email [cite: 413]
Notification Type [cite: 414]	Email [cite: 414, 415]
To Address [cite: 415]	admin@yourdomain.com [cite: 416]
Subject [cite: 416, 417]	[OpManager Didactum] $alarmMessage – $deviceName [cite: 417]
Message [cite: 418]	Time: $strModifiedTime\nDevice: $deviceName ($strIPAddress)\nAlarm: $alarmMessage\nSeverity: $severity\nMonitor: $displayName\nValue: $strValue [cite: 418, 419]
Notify on Severity [cite: 419]	Warning, Critical [cite: 420]

Click on Save[cite: 421].

Step 3 – Enable Alert Profile for Device

Inventory → Didactum-Monitor-01 → "Alert Profiles" Tab
→ "Add Alert Profile": select "Didactum Alarm Email"
→ Trigger On: Threshold Violation, Trap Alarm
→ Save

Step 4 – Alert Profile for All Monitors (global)

Settings → Notifications → Notification Profiles
→ "Didactum Alarm Email" → "Devices" Tab
→ Add all Didactum devices (or Device Group)
→ Save

10. SNMP OID Reference

All Didactum OIDs start with .1.3.6.1.4.1.46501 (older firmware) or .1.3.6.1.4.1.39052 (newer models)[cite: 421, 422]. The sensor ID is appended to the end[cite: 422].

OID Fields per Sensor

Field [cite: 422]	Meaning [cite: 423]	Example [cite: 423]
.1.x.SENSOR_ID [cite: 424]	Sensor ID [cite: 425]	.1.3.6.1.4.1.46501.5.1.1.1.101001 [cite: 425, 426]
.5.x.SENSOR_ID [cite: 426]	Sensor Name [cite: 427]	.1.3.6.1.4.1.46501.5.1.1.5.101001 [cite: 427]
.6.x.SENSOR_ID [cite: 428]	Status (0=OK, 1=Alarm, 2=No Signal) [cite: 428, 429]	.1.3.6.1.4.1.46501.5.1.1.6.101001 [cite: 429]
.7.x.SENSOR_ID [cite: 430]	Measured value (current) [cite: 430]	.1.3.6.1.4.1.46501.5.1.1.7.101001 [cite: 431]

Sensor Types with OIDs and OpManager Thresholds

Sensor Type [cite: 432]	Sensor ID [cite: 432, 433]	OID Measured Value [cite: 433]	OID Status [cite: 433, 434]	OpManager Threshold [cite: 434]
Temperature sensor (digital) [cite: 435]	101001 [cite: 435, 436]	.1.3.6.1.4.1.46501.5.1.1.7.101001 [cite: 436]	.1.3.6.1.4.1.46501.5.1.1.6.101001 [cite: 436, 437]	Warning: 280 / Critical: 350 (Raw value × 10) [cite: 437]
Temperature sensor (analog) [cite: 438]	201001 [cite: 438]	.1.3.6.1.4.1.39052.5.2.1.7.201001 [cite: 439]	.1.3.6.1.4.1.39052.5.2.1.6.201001 [cite: 439, 440]	Warning: 280 / Critical: 350 (× 10) [cite: 440]
Water sensor / Leakage [cite: 441]	107001 [cite: 441]	.1.3.6.1.4.1.46501.5.1.1.7.107001 [cite: 442]	.1.3.6.1.4.1.46501.5.1.1.6.107001 [cite: 442]	Critical: > 0 (from 1 = water) [cite: 443, 444]
Humidity [cite: 444]	102001 [cite: 445]	.1.3.6.1.4.1.46501.5.1.1.7.102001 [cite: 445, 446]	.1.3.6.1.4.1.46501.5.1.1.6.102001 [cite: 446]	Warning: 80 / Critical: 90 (directly %) [cite: 446, 447]
Dry contact [cite: 447]	101003 [cite: 448]	.1.3.6.1.4.1.39052.5.1.1.7.101003 [cite: 448]	.1.3.6.1.4.1.39052.5.1.1.6.101003 [cite: 449]	Warning: > 0 (from 1 = active) [cite: 449, 450]
Door contact [cite: 450]	104001 [cite: 451]	.1.3.6.1.4.1.46501.5.1.1.7.104001 [cite: 451, 452]	.1.3.6.1.4.1.46501.5.1.1.6.104001 [cite: 452]	Warning: > 0 (from 1 = open) [cite: 452, 453]
Smoke detector [cite: 453]	106001 [cite: 454]	.1.3.6.1.4.1.46501.5.1.1.7.106001 [cite: 454, 455]	.1.3.6.1.4.1.46501.5.1.1.6.106001 [cite: 455]	Critical: > 0 (from 1 = alarm) [cite: 455, 456]

How to find the Sensor ID: [cite: 457]

In the Didactum web interface under System Tree → Select Sensor → Details[cite: 458]. This ID is appended to the end of the OID[cite: 458].

Temperature Thresholds in OpManager: [cite: 459]

Didactum delivers temperatures as raw value × 10[cite: 459, 460]. 28.0 °C = OID value 280[cite: 460]. Custom SNMP Monitor thresholds must be entered × 10 (280 / 350)[cite: 460]. The graph shows the raw value; the description (Unit) indicates the conversion[cite: 460].

MIB Prefix per Model: [cite: 461]

Older devices use .1.3.6.1.4.1.46501, newer models might use .1.3.6.1.4.1.39052[cite: 461, 462]. Please obtain the exact OIDs from the MIB file of your device[cite: 462].

11. Testing & Troubleshooting [cite: 462, 463]

SNMP Test via OpManager Web Console

Inventory → Devices → Didactum-Monitor-01 → "Edit Device"
→ click "Test SNMP" button
→ Green message: "SNMP Community String is valid"

Test Custom Monitor Directly (Query Device)

Settings → Monitoring → Performance Monitors
→ Monitor "Didactum Temperature Sensor 01" → Edit
→ In the "Device Name" field: enter Didactum-Monitor-01
→ click "Query device"
→ Raw value appears: e.g., 235 (= 23.5 Degrees C) [cite: 463, 464]

SNMP Trap Viewer for Diagnostics

Settings → Monitoring → SNMP Trap Processors → "Trap Viewer"
→ Shows all incoming traps in real time
→ Also traps from unconfigured devices
→ Trap from Didactum device appears after triggering an alarm

Error Messages and Solutions

Problem [cite: 465]	Cause & Solution [cite: 465, 466]
„SNMP Community String is invalid" [cite: 467]	Community string incorrect; SNMP not active on Didactum; UDP 161 blocked [cite: 467, 468]
Monitor shows „No Data" [cite: 468, 469]	Monitor not assigned to the device; OID not supported → test Query Device [cite: 469, 470]
Temperature value 10× too high [cite: 470, 471]	No problem – raw value × 10. Enter thresholds × 10 (280 / 350) [cite: 471]
Alert does not trigger [cite: 472]	Threshold values incorrect; Alert Profile not assigned to the device; Monitor interval too long [cite: 472, 473]
Trap not in Alarms view [cite: 474]	Trap processing disabled → Settings → Trap Settings → enable Enable [cite: 474]
Trap appears as „Unsolicited Trap" [cite: 475]	No trap processor created for this OID → create processor for .1.3.6.1.4.1.46501 [cite: 475, 476]
No email on alarm [cite: 476]	Check mail server settings; Alert Profile not configured; send test mail [cite: 477, 478]
MIB Import Error [cite: 478]	MIB dependencies missing → copy standard MIBs (SNMPv2-SMI) to mibs directory first [cite: 479]

View OpManager Logs

# Windows:
C:\Program Files\ManageEngine\OpManager\logs\OpManager.log

# Linux:
/opt/ManageEngine/OpManager/logs/OpManager.log

# Via Web Console:
Settings → General Settings → Diagnostics → View Logs [cite: 479, 480]

12. Final Checklist

Didactum Device

• SNMP enabled (v2c or v3)
• Community String set (not „public"): didactum_opm
• Device reachable via Ping from OpManager server
• Trap receiver IP set to OpManager server
• MIB file downloaded [cite: 480, 481]

OpManager Configuration

• MIB file copied to OpManager mibs directory
• MIB loaded in OpManager web interface
• Device Didactum-Monitor-01 added via discovery or „Add Device"
• SNMP test on device successful (green message)
• UDP 161 outbound, UDP 162 inbound opened [cite: 481, 482]

Custom SNMP Monitors

• Temperature sensor monitor created (Warning 280, Critical 350)
• Temp-Status monitor created (Critical > 0) [cite: 482, 483]
• Leakage sensor monitor created (Critical > 0)
• Humidity monitor created (Warning 80, Critical 90)
• Door contact monitor created (Warning > 0)
• Smoke detector monitor created (Critical > 0)
• All monitors assigned to the device [cite: 483, 484]
• Query Device: Sensor values appear correctly
• Device Template created with all monitors

SNMP Trap Processors

• Trap Processing enabled (Settings → Trap Settings)
• MIB loaded for trap processing
• Trap Processor for leakage (Critical) created [cite: 484, 485]
• Trap Processor for temperature alarm created
• Trap Processor for smoke detector (Critical) created
• Trap Processor for door contact (Warning) created
• Test trap received → visible in Trap Viewer [cite: 485, 486]

Alerting & Notification

• Mail server configured, test email received
• Alert Profile „Didactum Alarm Email" created
• Alert Profile assigned to the device
• Test alarm triggered and email received