Didactum Monitoring & OPNET AppResponse Xpert Integration
Complete step-by-step guide for integrating Didactum Monitoring devices and sensors into OPNET AppResponse Xpert via SNMP – including SNMP data source configuration, MIB import, complete OID reference for all sensor types (temperature, leakage, humidity, door contact, smoke), threshold and alarm configuration as well as SNMP Trap processing.
Architecture Note: OPNET AppResponse Xpert is primarily an Application Performance Management solution (APM). The integration of Didactum Monitoring devices is done via the integrated SNMP Poller functionality of AppResponse Xpert, which allows capturing any SNMP-enabled devices as external data sources. AppResponse Xpert sends SNMP-GET requests (UDP port 161) to the Didactum device. SNMP Traps are actively sent by the Didactum device to the AppResponse Xpert server (UDP port 162).
- Software: OPNET AppResponse Xpert (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
OPNET AppResponse Xpert Server
| Requirement | Details |
|---|---|
| Software | OPNET AppResponse Xpert (current version; also known as Riverbed AppResponse) |
| SNMP Poller | Integrated SNMP Poller must be enabled |
| Network (outbound) | UDP Port 161 to the Didactum device (SNMP polling) |
| Network (inbound) | UDP Port 162 from the Didactum device (SNMP Traps) |
| MIB Directory | Accessible MIB path on the AppResponse Xpert server |
| Network Access | IP reachability from the AppResponse Xpert server to the Didactum device required |
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 AppResponse Xpert server |
| 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_appresponse (do not use "public"!) |
| SNMP Port | 161 |
| Trap Destination | IP address of the AppResponse Xpert server |
| 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 AppResponse Xpert.
Save settings. The device will now send Traps to the AppResponse Xpert server.
3. Import MIB File into AppResponse Xpert
AppResponse Xpert uses MIB files to resolve SNMP OID numbers into readable symbolic names. This greatly simplifies the configuration of SNMP data sources and the readability of alarm messages.
Step 1 – Determine MIB Directory
Default path on Windows: C:\Program Files\OPNET\AppResponse Xpert\mibs\ Default path on Linux / Appliance: /opt/opnet/appresponse/mibs/ (Exact path depending on installation; check AppResponse Xpert documentation if necessary)
Step 2 – Copy MIB File
Copy didactum.mib to the MIB directory of AppResponse Xpert: → <appresponse-install-path>\mibs\didactum.mib
Step 3 – Load MIB in Web Interface
AppResponse Xpert Web Interface → Administration → SNMP Settings → MIB Management → "Upload MIB" or "Import MIB" → Select file didactum.mib → Confirm import → Reload page – DIDACTUM-MIB appears in the MIB list
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 MIB directory and import as described above:
-- ================================================================
-- DIDACTUM-MIB – Minimal MIB for AppResponse Xpert 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 as SNMP Data Source
In AppResponse Xpert, the Didactum device is registered as an external SNMP data source ("SNMP Device" or "Managed Device"). AppResponse Xpert then polls the device at configurable intervals and stores the measured values for trend analysis and alarms.
Step 1 – Add SNMP Device
AppResponse Xpert Web Interface → Administration → Managed Devices → Add Device Device Name: Didactum-Monitor-01 IP Address: 192.168.1.50 SNMP Version: v2c Community String: didactum_appresponse Port: 161 Timeout: 5 seconds Retries: 3 Description: Didactum Monitoring System – Server Room Device Group: Environmental (create new if not present)
Step 2 – Test SNMP Connection
→ Click "Test SNMP Connection" Expected result: "Connection successful – sysDescr: Didactum Monitoring System" If test fails: → Check Community String and IP address → Check firewall rule UDP 161 from AppResponse server to Didactum device → Test snmpwalk directly from the server (see Section 10)
Step 3 – Set SNMP Polling Interval
Poll Interval: 60 seconds (Temperature, Humidity)
30 seconds (Leakage, Door Contact, Smoke – time-critical sensors)
→ Save5. Configure SNMP Data Sources (OID Queries)
Important – Temperature Thresholds:
The Didactum device delivers temperature values as raw value × 10. 25.5 °C = OID value 255. All temperature thresholds in AppResponse Xpert must also be specified × 10.
Add SNMP Data Sources
AppResponse Xpert → Administration → SNMP Data Sources → Add Data Source
-- ================================================================
-- Data Source 1: Temperature Sensor (digital, Sensor-ID 101001)
-- ================================================================
Name: Temperature_Sensor_01
Device: Didactum-Monitor-01
OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
Data Type: Integer / Gauge
Description: Temperature sensor 01 – raw value x10; 235 = 23.5 °C
Poll Interval: 60 seconds
Unit: raw_x10
Threshold Warning High: 280 (= 28.0 °C)
Threshold Critical High: 350 (= 35.0 °C)
Alarm Message: Didactum Temp Alarm: Raw value ${value} corresponds to ${value/10} °C
-- ================================================================
-- Data Source 2: Temperature Status (0=OK / 1=Alarm / 2=No Signal)
-- ================================================================
Name: Temperature_Status_01
OID: .1.3.6.1.4.1.46501.5.1.1.6.101001
Data Type: Integer
Poll Interval: 60 seconds
Threshold Warning High: 1
Threshold Critical High: 2
Alarm Message: Didactum Temp Sensor Status: ${value} (0=OK, 1=Alarm, 2=No Signal)
-- ================================================================
-- Data Source 3: Water Sensor / Leakage (Sensor-ID 107001)
-- ================================================================
Name: Leakage_Sensor_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.107001
Data Type: Integer
Poll Interval: 30 seconds
Threshold Critical High: 1 (0 = dry / OK, 1 = Water detected / CRITICAL)
Alarm Message: CRITICAL: Didactum Leakage Alarm – Water detected!
-- ================================================================
-- Data Source 4: Humidity (Sensor-ID 102001)
-- ================================================================
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: %
Threshold Warning High: 80
Threshold Critical High: 90
Alarm Message: Didactum Humidity Alarm: ${value} %
-- ================================================================
-- Data Source 5: Door Contact (Sensor-ID 104001)
-- ================================================================
Name: DoorContact_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.104001
Data Type: Integer
Poll Interval: 30 seconds
Threshold Warning High: 1 (0 = closed / OK, 1 = open / Warning)
Alarm Message: Didactum Door Contact: Door opened!
-- ================================================================
-- Data Source 6: Smoke Detector (Sensor-ID 106001)
-- ================================================================
Name: SmokeDetector_01
OID: .1.3.6.1.4.1.46501.5.1.1.7.106001
Data Type: Integer
Poll Interval: 30 seconds
Threshold Critical High: 1 (0 = no smoke / OK, 1 = Alarm / CRITICAL)
Alarm Message: CRITICAL: Didactum Smoke Detector Alarm!Step – Save and Activate Configuration
→ Save all data sources → Restart SNMP Poller if necessary: Administration → Services → SNMP Poller → Restart → After the first poll interval, measured values appear under: Monitoring → SNMP Data → Didactum-Monitor-01
6. Configure SNMP Trap Reception
AppResponse Xpert can receive incoming SNMP Traps from the Didactum device and process them as events or alarms. This creates an event immediately on a sensor alarm – without waiting for the next polling cycle.
Step 1 – Activate SNMP Trap Receiver
AppResponse Xpert → Administration → SNMP Settings → Trap Receiver Trap Port: 162 Trap Community: didactum_trap SNMP Version: v2c MIB: DIDACTUM-MIB (previously imported) → Activate "Enable Trap Receiver" → Save
Step 2 – Authorize Trap Source (Didactum Device)
AppResponse Xpert → Administration → SNMP Settings → Allowed Trap Sources → "Add Source" → IP address of the Didactum device: 192.168.1.50 → Community: didactum_trap → Save
Step 3 – Configure Trap-to-Event Mapping
AppResponse Xpert → Administration → SNMP Trap Mappings → New Mapping
Trap OID: .1.3.6.1.4.1.46501.1.1
(didactumAlarmTrap – general alarm trap)
Event Name: Didactum Sensor Alarm
Severity: Critical
Message: Didactum Alarm: Sensor ${sensorName} – Status ${sensorStatus}
Device: Didactum-Monitor-01 (192.168.1.50)
→ Save
Second mapping for clear (optional):
Trap OID: .1.3.6.1.4.1.46501.1.2
Event Name: Didactum Sensor – Normal state
Severity: Informational / Clear
→ 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 AppResponse Xpert server) Trap Community: didactum_trap Trap Version: v2c Trap Port: 162 → Save
Recommendation:
Activate both SNMP polling (regular queries for trends and graphs) and SNMP Traps (immediate alarms) at the same time. Polling provides historical measurement data; Traps guarantee immediate notification in case of alarm events.
7. Configure Alarms and Notifications
Create Alarm Policy
AppResponse Xpert → Administration → Alert Policies → New Policy
Policy Name: Didactum Sensor Alarms
Applies to: Device Group "Environmental" or device "Didactum-Monitor-01"
Trigger: SNMP threshold exceeded OR SNMP Trap received
Critical Action: Send email
Warning Action: Send email
Clear Action: Send email "Alarm cleared"
Email Recipient: admin@yourdomain.com
Email Subject: [AppResponse] Didactum Alarm: ${device.name} – ${datasource.name}
Email Body:
Timestamp: ${alert.timestamp}
Device: ${device.name} (${device.ip})
Data Source: ${datasource.name}
Severity: ${alert.severity}
Value: ${alert.value}
Threshold: ${alert.threshold}
Message: ${alert.message}Configure Escalation Levels
AppResponse Xpert → Alert Policies → Didactum Sensor Alarms → Escalation Level 1 (Warning): Email to admin@yourdomain.com after 0 minutes Level 2 (Critical): Email to it-management@yourdomain.com after 5 minutes Level 3 (Critical): SNMP Trap forward to SIEM (optional) after 10 minutes
8. Set Up Dashboards and Reports
Step 1 – Create Dashboard
AppResponse Xpert → Dashboards → New Dashboard Dashboard Name: Server Room Monitoring Didactum Layout: Grid 2 x 3 (six widgets)
Step 2 – Configure Widgets
Widget 1: Temperature Trend (Line Chart) Type: Time Series Chart Data Source: Temperature_Sensor_01 (Didactum-Monitor-01) Time Range: Last 24 hours Y-Axis: Raw value (÷10 = °C) Threshold: Warning line at 280 / Critical line at 350 Widget 2: Leakage Status (Status Indicator) Type: Current Value / Status LED Data Source: Leakage_Sensor_01 OK Color: Green (value = 0) Alarm Color: Red (value >= 1) Widget 3: Humidity (Gauge) Type: Gauge / Dial Data Source: Humidity_Sensor_01 Min / Max: 0 / 100 % Warning: 80 % Critical: 90 % Widget 4: Door Contact Status Type: Current Value / Status LED Data Source: DoorContact_01 OK Color: Green (value = 0) Alarm Color: Yellow / Orange (value = 1) Widget 5: Smoke Detector Status Type: Current Value / Status LED Data Source: SmokeDetector_01 OK Color: Green (value = 0) Alarm Color: Red (value = 1) Widget 6: Active Alarms Type: Alert List Filter: Device = Didactum-Monitor-01 Shows all active alarms and trap events in real time
Step 3 – Create Report for Periodic Evaluation
AppResponse Xpert → Reports → New Report
Report Name: Didactum Server Room – Weekly Report
Content:
- Temperature Trend (7 days) with Min / Max / Average
- Humidity Trend (7 days)
- Alarm History: all Didactum alarms of the week
Schedule: Weekly, Monday 07:00 AM
Recipient: admin@yourdomain.com
Format: PDF9. 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 AppResponse Thresholds
| Sensor Type | Sensor ID | OID Measured Value | OID Status | AppResponse 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 AppResponse Xpert:
Didactum delivers temperature as raw value × 10. 28.0 °C = OID value 280. Enter AppResponse Xpert thresholds (Warning/Critical High) also as × 10 value. Note "÷10 = °C" in the dashboard label.
10. Test SNMP Connection
Test via Command Line (from AppResponse Xpert Server)
# snmpwalk – list all sensor values
snmpwalk -v 2c -c didactum_appresponse 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_appresponse 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_appresponse 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_appresponse 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_appresponse -m ALL 192.168.1.50 \
DIDACTUM-MIB::sensorValue
Test via AppResponse Xpert SNMP Test Function
AppResponse Xpert → Administration → Managed Devices → Didactum-Monitor-01 → "Test SNMP Connection" → Expected result: Connection OK – sysDescr appears AppResponse Xpert → Administration → SNMP Data Sources → Temperature_Sensor_01 → "Poll Now" / "Test Poll" → Expected result: Raw value (e.g. 235) appears
Test Trap Reception
Trigger a test trap in the Didactum Web Interface: System Settings → SNMP → "Send Test Trap" Check in AppResponse Xpert: → Dashboards → Server Room Monitoring → Widget "Active Alarms" → New event with Source 192.168.1.50 appears → Severity: Critical / Informational → Message: Didactum Alarm: …
11. Troubleshooting
| Problem | Cause & Solution |
|---|---|
| "Test SNMP Connection" fails | SNMP not enabled on Didactum device; Community String wrong; UDP Port 161 blocked by firewall → test snmpwalk directly from AppResponse server; check firewall rule |
| MIB import fails | Dependent MIBs missing (SNMPv2-SMI, RFC1213-MIB) → copy base MIBs to MIB directory first; 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. Configure thresholds as × 10 value (28 °C = Warning High 280). Adjust dashboard label to ÷10 = °C. |
| SNMP Traps do not arrive | Trap target IP in Didactum Web Interface does not point to AppResponse server; UDP Port 162 blocked by firewall; Trap Community does not match → check snmptrap / AppResponse log |
| Trap received but no alarm generated | Trap mapping missing in AppResponse Xpert or Trap OID does not match; Didactum IP not entered in Allowed Trap Sources → check trap definitions and allowed sources |
| Measured values do not appear in dashboard | SNMP Poller not started yet or first poll interval not yet elapsed → check Administration → Services → SNMP Poller Status; wait 60 seconds and reload page |
| No email on alarm | SMTP settings not configured in AppResponse Xpert; Alert Policy not assigned to device or device group → check Administration → Mail Settings |
| Sensor value always remains 0 (Leakage / Door Contact) | Normal in uncritical state (0 = OK). Test sensor by briefly triggering it; verify OID directly with snmpget from server. |
| AppResponse Xpert cannot reach Didactum device | Routing problem between AppResponse server and Didactum device; firewall blocks UDP 161 → ping test; traceroute from server; check network segment routing if necessary |
12. Final Checklist
Didactum Device
- SNMP enabled (v2c)
- Community String set (not "public"): didactum_appresponse
- Trap target set to IP of AppResponse Xpert server
- Trap Community set: didactum_trap
- MIB file downloaded (didactum.mib)
- snmpwalk from AppResponse Xpert server successful
AppResponse Xpert Server
- DIDACTUM-MIB copied to MIB directory and imported
- Didactum device added as Managed Device (IP, Community String, SNMP version)
- "Test SNMP Connection" successful
- All 6 SNMP data sources 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 mappings created for Didactum alarm traps
- Alert Policy "Didactum Sensor Alarms" configured and email sending enabled
Tests & Verification
- First measured values visible in SNMP data sources 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 → Alarm appears in AppResponse Xpert
- Email received on test alarm
- Weekly report scheduled and test export created