This guide describes the complete integration of Didactum monitoring devices into AccelOps (also known as Fortinet FortiSIEM, starting from version 5.x). The objective is the centralized monitoring of all connected sensors - temperature, humidity, leakage, voltage, door contacts, and others - via SNMP polling and SNMP traps, including automatic device discovery, event correlation, alerting, and dashboards.

Note on Terminology: 

AccelOps was acquired by Fortinet in 2016 and has been marketed as FortiSIEM ever since. The underlying architecture and configuration concepts remain identical. Both designations are used throughout this guide.

AccelOps / FortiSIEM is a combined SIEM and IT operations platform. It unifies security monitoring (SIEM), network performance monitoring (NPM), and IT infrastructure monitoring in one solution. Didactum devices are integrated as network devices via SNMP and can be used for both performance monitoring (sensor values) and security events (door contact, motion).

AccelOps / FortiSIEM core components

Processing workflow for Didactum sensors

1. Discovery: AccelOps discovers the Didactum device automatically via SNMP discovery or through manual entry.
2. CMDB entry: The device is recorded in the CMDB as a device of type Environmental Monitor.
3. Credential assignment: SNMP community string is assigned to the device.
4. Monitoring template: An SNMP monitoring template defines which OIDs are queried at what interval.
5. Performance metrics: OID values are stored as performance metrics in the EventDB.
6. Rule engine: Configured rules check incoming metrics and generate incidents when thresholds are exceeded.
7. Notification: Incidents trigger notifications via email, SMS, or ticketing system.

• AccelOps 5.x or FortiSIEM 6.x / 7.x (current version)
• Supervisor node with administrator access to the web interface
• Collector node in the same network segment as the Didactum device (recommended)
• Didactum monitoring device reachable in the network, SNMP enabled
• UDP port 161 opened from the AccelOps collector to the Didactum device
• UDP port 162 opened on the AccelOps supervisor/collector for SNMP traps
• SNMP community string known (default: public)
• Didactum MIB file available (optional, for OID name resolution)

Example network configuration

3.1 Activate SNMP

1. Open Didactum web interface: [http://192.168.1.100](http://192.168.1.100), log in with admin account.
2. Navigation: Settings → Network → SNMP (or: Settings → Network → SNMP).
3. Set the following parameters:
   • SNMP enabled: Yes
   • SNMP version: v2c (recommended) or v3
   • Community string: public (change in production)
   • SNMP port: 161
   • Allowed Managers: enter IP of AccelOps collector (192.168.1.81) and supervisor (192.168.1.80)
   • SNMP trap receiver: IP of AccelOps supervisor, port 162
4. Save settings.

Attention:

Change the default community string public in production environments. Use the same string in the AccelOps credentials.

3.2 Test reachability from collector

# SNMP Walk – list all Didactum OIDs:
snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854
 
# Query temperature sensor 1 directly:
snmpget -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
 
# System description (basic test):
snmpget -v2c -c public 192.168.1.100 1.3.6.1.2.1.1.1.0

Note:

Didactum returns temperature and voltage values with a factor of 10 (235 = 23.5°C). This must be taken into account in the performance monitor configuration and in the rule parameters.

4.1 Import Didactum MIB file

1. Open AccelOps web interface: [https://192.168.1.80](https://192.168.1.80).
2. Navigation: Admin → Device Support → MIBs → Upload MIB.
3. Upload Didactum MIB file (DIDACTUM-RACKMONI2-MIB.mib).
4. Click Compile – AccelOps processes the MIB and makes OID names usable in the interface.
5. Check result: Admin → Device Support → MIBs → Didactum should now appear.

4.2 Create SNMP credentials

1. Navigation: Admin → Setup → Credentials → Add.
2. Select credential type: SNMP v2c.
3. Fill in the following fields:
   • Name: Didactum-SNMP-v2c
   • Community string: public
   • SNMP port: 161
   • Description: SNMP credentials for Didactum Rack Monitoring devices
4. Save.

For SNMP v3:

1. Credential type: SNMP v3.
2. Additional fields:
   • Security name: SNMP-v3 username
   • Auth protocol: SHA
   • Auth password: Authentication password
   • Privacy protocol: AES128
   • Privacy password: Encryption password

4.3 Prepare IP range for discovery

1. Navigation: Admin → Setup → Discovery → IP Range.
2. Enter IP range: 192.168.1.100 – 192.168.1.110 (or specific IP).
3. Assign credentials: Didactum-SNMP-v2c
4. Assign collector: AccelOps collector in the same subnet.

5.1 Start automatic discovery

1. Navigation: Admin → Setup → Discovery → Discover.
2. Select IP range: 192.168.1.100/32 (only the Didactum device).
3. Enable protocols: SNMP, ICMP.
4. Click Discover Now.
5. AccelOps performs an SNMP walk and detects device properties (sysDescr, sysOID, Interfaces).
6. Upon completion, the device appears under CMDB → Devices.

5.2 Add device manually

1. Navigation: CMDB → Devices → Add Device.
2. Fill in the following fields:
   • Name: didactum-rack01
   • IP address: 192.168.1.100
   • Device type: Environmental Monitor (or Network Device → Other)
   • Vendor: Didactum
   • Model: Rack Monitoring Unit II
   • Location: Server room A, Rack 03
3. Under Credentials: assign Didactum-SNMP-v2c.
4. Under Collector: select the responsible collector.
5. Save.

5.3 Create device group for Didactum devices

1. Navigation: CMDB → Device Groups → Add Group.
2. Name: Didactum Rack Monitoring
3. Members: add all Didactum nodes.
4. Alternatively: automatic grouping by device type Environmental Monitor.

5.4 Check device status after discovery

1. Navigation: CMDB → Devices → didactum-rack01.
2. Open tab Monitor Status.
3. SNMP status should show Up.
4. Under Device Properties → SNMP: sysDescr and sysOID displayed from the SNMP walk.

6.1 Create Performance Monitor template for Didactum

Performance Monitor templates define which OIDs AccelOps polls regularly and stores as metrics.

1. Navigation: Admin → Device Support → Performance Monitors → Add.
2. Following basic settings:
   • Name: Didactum-Rack-Monitoring
   • Type: SNMP Performance Monitor
   • Polling interval: 300 seconds (5 minutes)
3. Add monitoring objects (one entry for each OID):

6.2 Configure monitoring objects

Click Add Object and create the following entries one after another:

Note on multiplier:

The multiplier 0.1 divides the raw value by 10 and thus corrects the Didactum-specific scaling factor for temperature and voltage. The displayed value is then correct in °C or V.

6.3 Assign Performance Monitor to the device

1. Navigation: CMDB → Devices → didactum-rack01 → Monitor.
2. Click Add Monitor.
3. Monitor type: select Didactum-Rack-Monitoring.
4. Confirm polling interval: 300 seconds.
5. For leakage and door contact: create a separate monitor object with interval 60 seconds.
6. Save and activate.

6.4 Polling intervals by priority

7.1 Create own device type profile for Didactum

AccelOps uses device type profiles to automatically assign device properties and event parsing.

1. Navigation: Admin → Device Support → Device Types → Add.
2. Settings:
   • Device type: Didactum-RackMonitor
   • Vendor: Didactum
   • Model: Rack Monitoring Unit
   • SNMP sysOID: .1.3.6.1.4.1.3854
   • Category: Environmental Monitor
3. Assign Performance Monitor: Didactum-Rack-Monitoring
4. Save.

7.2 Create event parser for SNMP trap events

To enable AccelOps to correctly classify incoming Didactum traps, an event parser is created:

1. Navigation: Admin → Device Support → Event Parsers → Add.
2. Parser settings:
   • Name: Didactum-SNMP-Trap-Parser
   • Device type: Didactum-RackMonitor
   • Event type: SNMP Trap
3. Pattern mapping for leakage trap:
   • OID match: 1.3.6.1.4.1.3854.1.7.2
   • Event name: DIDACTUM-LEAK-ALARM
   • Severity: CRITICAL
   • Category: Environmental
4. Pattern mapping for temperature alarm trap:
   • OID match: 1.3.6.1.4.1.3854.1.7.1
   • Event name: DIDACTUM-TEMP-ALARM
   • Severity: HIGH
5. Save.

7.3 Register custom event types

1. Navigation: Admin → Device Support → Event Types → Add.
2. Create event types:

All OIDs are based on the Didactum enterprise OID base 1.3.6.1.4.1.3854. The placeholder {n} stands for the sensor index (1 = first sensor, etc.).

8.1 Temperature sensors

8.2 Leakage sensors

8.3 Humidity sensors

8.4 Other sensors

9.1 Rule for temperature exceedance

1. Navigation: Rules → Add Rule.
2. Rule settings:
   • Name: Didactum-temperature-warning
   • Group: Environmental Monitoring
   • Severity: HIGH
   • Active period: Always
3. Under Conditions:
   • Event type: Performance metric
   • Metric name: Temperature_S1
   • Device: group Didactum Rack Monitoring
   • Condition: Greater than 30 (°C, after multiplier application)
   • Duration: 2 samples (avoids false alarms for single outliers)
4. Under Actions:
   • Create incident: activate
   • Incident title: Temperature alarm: $deviceName – $metricValue °C
   • Send notification: email to IT administrators
5. Save and activate.

9.2 Rule for leakage (immediate alarm)

1. New rule: Didactum-leakage-CRITICAL
2. Severity: CRITICAL
3. Conditions:
   • Metric name: Leak_Status_S1
   • Condition: Greater than or equal to 1
   • Duration: 1 sample (no delay – immediate alarm)
4. Actions:
   • Create incident
   • Email to all administrators and management level
   • Repeat notification every: 5 minutes as long as alarm is active

9.3 Correlation rule: multi-event detection

A special advantage of AccelOps / FortiSIEM is event correlation. The following rule detects critical combinations:

1. New rule: Didactum-critical-combination
2. Severity: CRITICAL
3. Conditions (multiple events within time window):
   • Event 1: Leak_Status_S1 >= 1 AND
   • Event 2: Temperature_S1 > 35 (simultaneously or within 10 minutes)
   • Time window: 600 seconds
   • Same device: activate
4. Incident title: CRITICAL: Simultaneous leakage AND temperature alarm on $deviceName!

9.4 Recommended thresholds in AccelOps rules

9.5 Configure notification policy

1. Navigation: Admin → General Settings → Notification Policy.
2. Enter email server: SMTP host, port, sender address.
3. Create notification groups:
   • Didactum-admins: IT administrators (all severities)
   • Didactum-management: management level (CRITICAL only)
   • Didactum-OnCall: on-call service (CRITICAL outside working hours)
4. Link rules with notification groups.

AccelOps / FortiSIEM receives SNMP traps natively on UDP port 162. Traps are automatically assigned to the sending device in the CMDB and classified via the configured event parser.

10.1 Check SNMP trap receiver

# AccelOps listens on UDP 162 by default.
# Check firewall allowance:
sudo iptables -L -n | grep 162
# or:
sudo ufw status | grep 162
 
# Open port (if necessary):
sudo ufw allow 162/udp

10.2 Trap receiver configuration in AccelOps

1. Navigation: Admin → Setup → Phishing & Traps → SNMP Trap Receiver.
2. Status: check Enabled.
3. Port: 162
4. Community: public
5. Accepted hosts: enter 192.168.1.100 (IP of the Didactum device).

10.3 Perform trap test

# Send test trap for leakage from the Didactum device:
snmptrap -v2c -c public 192.168.1.80 '' \\
  .1.3.6.1.4.1.3854.1.7.2 \\
  .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1 i 1
 
# Check trap reception in AccelOps:
# Analytics → Events → Filter: Event Type = DIDACTUM-LEAK-ALARM

10.4 Important Didactum trap OIDs for AccelOps

11.1 Create dashboard for Didactum sensors

1. Navigation: Dashboards → Add Dashboard.
2. Name: Didactum Rack Monitoring
3. Add dashboard widgets:
   • Line chart – temperature trend: metrics Temperature_S1 and Temperature_S2, last 24 hours
   • Gauge – current temperature S1: min 0, max 50 °C, color scale green/yellow/red
   • Line chart – humidity: metric Humidity_S1, last 24 hours
   • Bar chart – leakage status: metrics Leak_Status_S1 and Leak_Status_S2
   • Incident table: current open incidents of device group Didactum Rack Monitoring
   • Event table: last 10 events with type DIDACTUM-*
4. Set dashboard as start page.

11.2 Analytics queries for long-term evaluation

1. Navigation: Analytics → Search.
2. Create saved queries:

# Query 1: temperature overview last 7 days
eventType = "PH_DEV_MON_PERF_METRIC" AND
deviceName IN GROUP("Didactum Rack Monitoring") AND
metricName = "Temperature_S1"
| Chart AVG(metricValue) AS "Average", MAX(metricValue) AS "Maximum",
  MIN(metricValue) AS "Minimum" BY deviceName, metricName
TIMERANGE LAST 7 DAYS
 
# Query 2: all leakage events
eventType CONTAIN "DIDACTUM-LEAK"
| GROUP COUNT(*) AS count BY deviceName
TIMERANGE LAST 30 DAYS
 
# Query 3: door contact openings by time of day
eventType = "DIDACTUM-DOOR-OPEN"
| GROUP COUNT(*) AS openings BY HOUR(deviceTime), deviceName
TIMERANGE LAST 7 DAYS

11.3 Configure automatic reports

1. Navigation: Reports → Schedule → Add.
2. Report: Didactum monthly report
3. Content:
   • Temperature statistics (min/max/avg) per sensor
   • Humidity statistics
   • Number of alarm events by type
   • Availability of monitoring units
4. Format: PDF
5. Distribution: monthly, email to management level

# Test SNMP reachability from collector / supervisor:
snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854
 
# Query single OID:
snmpget -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
 
# Send test trap to AccelOps:
snmptrap -v2c -c public 192.168.1.80 '' \\
  .1.3.6.1.4.1.3854.1.7.2 \\
  .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1 i 1
 
# Collector service status (on the collector node):
sudo systemctl status phCollector
 
# Supervisor service status:
sudo systemctl status phSupervisor
 
# AccelOps logs (depending on installation):
sudo tail -f /opt/phoenix/log/phoenix.log
sudo tail -f /opt/phoenix/log/collector.log

Always consult the current Didactum device documentation for firmware-specific OIDs and supported sensor types. AccelOps / FortiSIEM version specifics can be looked up in the respective Fortinet documentation.