This guide describes the complete integration of Didactum monitoring devices into AggreGate Network Manager. 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, context-based alerting, trend charts, and dashboards.

AggreGate Network Manager is a universal monitoring and management platform by Tibbo Technology. It is based on a context-oriented data model: Each monitored device is represented as a context, to which any variables, events, and functions can be assigned. SNMP-enabled devices such as the Didactum monitoring units are integrated as device contexts via the built-in SNMP driver.

AggreGate Core Concepts

Processing Workflow for Didactum Sensors

1. Create device: The Didactum device is created as an SNMP device context.
2. SNMP walk: AggreGate performs an SNMP walk and detects available OIDs.
3. Variable mapping: OIDs are configured as variables in the device context.
4. Polling: AggreGate queries the variables at configured intervals.
5. Alert check: Variable values are checked against alert conditions.
6. Event processing: When conditions are met, events and notifications are triggered.

Important Directories

• AggreGate Network Manager 6.x or newer (current stable version)
• AggreGate server on Linux (Debian/Ubuntu, RHEL/CentOS) or Windows Server
• Java Runtime Environment 11 or newer (included with AggreGate)
• AggreGate Client (Java application) or web interface for configuration
• SNMP tools (snmpwalk, snmpget) for preparation
• Didactum monitoring device reachable on the network, SNMP enabled
• UDP port 161 open from the AggreGate server to the Didactum device
• UDP port 162 open on the AggreGate server for SNMP traps
• TCP port 8080 (web interface) and TCP port 6060 (client connection) on the server
• SNMP community string known (default: public)

Example Network Configuration

3.1 Enable SNMP

1. Open the Didactum web interface: 192.168.1.100, log in with an 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 the IP of the AggreGate server (192.168.1.90)
   • SNMP trap receiver: IP of the AggreGate server, port 162
4. Save the settings.

Warning: Change the default community string public in production environments. Use the same string in the AggreGate SNMP configuration.

3.2 Test reachability from the AggreGate server

# 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 is taken into account in AggreGate using a formula in the variable configuration.

4.1 Start and verify AggreGate server

# Linux – start AggreGate service:
sudo systemctl start aggregate-server
sudo systemctl enable aggregate-server
sudo systemctl status aggregate-server
 
# Check logs:
sudo tail -f /opt/aggregate/server/logs/server.log
 
# Open web interface:
# 192.168.1.90/aggregate

4.2 Import Didactum MIB file

1. Start the AggreGate client or open the web interface.
2. Navigation: Administration → SNMP → MIB Repository → Import MIB.
3. Upload the Didactum MIB file (DIDACTUM-RACKMONI2-MIB.mib).
4. Ensure dependent MIBs are present: SNMPv2-SMI, SNMPv2-TC, RFC1213-MIB must already be available.
5. After successful import: OID names from the MIB are displayed in the SNMP browser.

Alternatively, copy the MIB manually into the server directory:

sudo cp DIDACTUM-RACKMONI2-MIB.mib /opt/aggregate/server/mibs/
sudo systemctl restart aggregate-server

4.3 Store SNMP community in AggreGate

1. Navigation: Administration → SNMP → Community Strings → Add.
2. Settings:
   • Name: Didactum Community
   • Community String: public
   • Version: v2c
   • IP Range: 192.168.1.100 (restrict to Didactum device)
3. Save.

4.4 Enable SNMP trap receiver

1. Navigation: Administration → SNMP → Trap Receiver.
2. Status: Enabled
3. Port: 162
4. Allowed sources: 192.168.1.100
5. Save and restart the AggreGate server.

5.1 Create device via AggreGate Client

1. Open AggreGate Client: File → Connect → 192.168.1.90:6060.
2. In the context browser: right-click on the desired folder → New → Device → SNMP Device.
3. Fill in the following fields:
   • Name: didactum-rack01
   • Description: Didactum Rack Monitoring Unit – Server Room A
   • IP address: 192.168.1.100
   • SNMP version: v2c
   • Community: public
   • Port: 161
   • Timeout: 2000 ms
   • Retries: 3
4. Click Run SNMP walk – AggreGate detects all available OIDs.
5. Click OK. The device appears as a context in the browser.

5.2 Create device via web interface

1. Open the web interface: 192.168.1.90/aggregate.
2. Navigation: Devices → New Device → SNMP Device.
3. Enter the same parameters as above.
4. Click Discover – AggreGate performs discovery.

5.3 Automatically detect device via discovery

1. Navigation: Administration → Network Discovery → New Scan.
2. IP range: 192.168.1.100 – 192.168.1.110
3. Protocol: SNMP, Community: public
4. Click Start Scan.
5. Import discovered devices from the results list.

5.4 Create device group

1. In the context browser: right-click → New → Group.
2. Name: Didactum Monitoring Devices
3. Move all Didactum devices into the group via drag & drop.
4. Group description: All Didactum Rack Monitoring Units

5.5 Check device status after discovery

1. In the context browser: double-click on didactum-rack01.
2. Tab Status – SNMP reachability should show Online.
3. Tab Variables – detected OIDs are listed.
4. Tab Events – SNMP events are displayed here.

6.1 Use SNMP browser for Didactum OIDs

1. Navigation: Tools → SNMP Browser.
2. IP address: 192.168.1.100, Community: public.
3. Click Walk – all available Didactum OIDs are displayed.
4. OIDs can be transferred directly from the browser into the variable configuration.

6.2 Configure SNMP version and security

For SNMP v3 in the device properties:

1. Right-click on the Didactum context → Properties → SNMP.
2. SNMP version: v3
3. Additional fields:
   • Security Name: SNMP v3 username
   • Auth Protocol: SHA
   • Auth Password: authentication password
   • Privacy Protocol: AES128
   • Privacy Password: encryption password
4. Save.

6.3 Polling configuration

1. Right-click on the Didactum context → Properties → Polling.
2. Settings:
   • Polling enabled: Yes
   • Default polling interval: 300 seconds (5 minutes)
   • Timeout: 2000 ms
   • Retries: 3
3. For time-critical sensors (leakage, door contact), set a shorter interval directly on the variable: 60 seconds.

7.1 Create variables for sensors

Each OID to be monitored is configured as a variable in the Didactum device context:

1. Right-click on the Didactum context → New → Variable.
2. Variable for temperature sensor 1:
   • Name: temperatur_s1
   • Description: Temperature Sensor 1 – Rack Front
   • Type: SNMP Variable
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
   • Data type: Float
   • Formula: value / 10.0 (raw value ÷ 10 for °C)
   • Unit: °C
   • Polling interval: 300 seconds
   • History: Enabled, retention: 90 days
3. Click OK.

7.2 Formula transformation for measured values

AggreGate supports formulas in the variable configuration that transform the raw value:

7.3 Overview of all variables for Didactum

7.4 Create device template (for multiple Didactum devices)

Instead of creating variables individually for each device, it is recommended to use a device template:

1. Navigation: Administration → Templates → New Template.
2. Name: Didactum Rack Monitoring Template
3. Create all variables from section 7.3 in the template.
4. Apply the template to new Didactum devices: right-click on the device context → Apply Template → Didactum Rack Monitoring Template.
5. Variables are automatically applied and assigned to the device.

7.5 History and data storage

1. For each variable: tab History.
2. Recommended settings:
   • History enabled: Yes
   • Retention period: 90 days (raw data), 365 days (aggregated data)
   • Aggregation: hourly (avg, min, max), daily (avg, min, max)
   • Compression: Enabled (saves storage space)

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 Create alert for temperature

1. Right-click on the Didactum context → New → Alert.
2. Settings for temperature warning:
   • Name: Temperature-Warning-S1
   • Description: Temperature sensor 1 above 30 °C
   • Variable: temperatur_s1
   • Condition: Value greater than 30
   • Severity: WARNING
   • Message: Temperature sensor 1 on {deviceName}: {value} °C – threshold 30 °C exceeded
   • Repeat: 600 seconds (every 10 minutes while active)
3. Add critical alert:
   • Name: Temperature-Critical-S1
   • Condition: Value greater than 35
   • Severity: CRITICAL
4. Link action: email notification (see 9.4).

9.2 Alert for leakage (instant alert)

1. New alert on the Didactum context.
2. Settings:
   • Name: Leakage-CRITICAL-S1
   • Variable: leckage_status_s1
   • Condition: Value greater than or equal 1
   • Severity: CRITICAL
   • Message: LEAKAGE DETECTED on {deviceName}! Immediate action required!
   • Repeat: 300 seconds (every 5 minutes)
   • Notify immediately: Yes (no delay)

9.3 Combined alert (multiple conditions)

AggreGate supports formulas as alert conditions that allow combining multiple variables:

1. New alert: Critical-Combination
2. Condition formula:

/* Alert when leakage AND temperature are critical at the same time */
({leckage_status_s1} >= 1) AND ({temperatur_s1} > 35)

1. Severity: CRITICAL
2. Message: CRITICAL: simultaneous leakage AND temperature alarm on {deviceName}!

9.4 Configure email notification

1. Navigation: Administration → Email → SMTP Server.
2. Enter SMTP server settings (host, port, sender, authentication).
3. Send test email.
4. Create notification rule: Administration → Notifications → New Rule.
   • Trigger: alert severity CRITICAL or WARNING
   • Device / Group: Didactum Monitoring Devices
   • Method: Email
   • Recipient: admin@example.com
   • Subject: [AggreGate] {severity}: {alertName} on {deviceName}

9.5 Recommended alert thresholds

AggreGate receives SNMP traps natively on UDP port 162. Incoming traps are automatically assigned to the sending device and stored as events in the context.

10.1 Check SNMP trap reception

# Check firewall port on the AggreGate server:
sudo ufw status | grep 162
# or:
sudo iptables -L -n | grep 162
 
# Open port:
sudo ufw allow 162/udp
 
# Is AggreGate trap receiver running? Check log:
sudo tail -f /opt/aggregate/server/logs/server.log | grep -i trap

10.2 Configure trap event handler

1. Navigation: Administration → SNMP → Trap Handler → New Handler.
2. Handler for leakage trap:
   • Trap OID: .1.3.6.1.4.1.3854.1.7.2
   • Event name: Didactum-Leakage-Trap
   • Severity: CRITICAL
   • Message: LEAKAGE detected on {sourceIP} via SNMP trap!
   • Update variable: leckage_status_s1 = 1
3. Handler for temperature alarm trap:
   • Trap OID: .1.3.6.1.4.1.3854.1.7.1
   • Event name: Didactum-Temperature-Trap
   • Severity: HIGH
4. Analogously for all other trap OIDs.

10.3 Perform trap test

# Send test trap for leakage:
snmptrap -v2c -c public 192.168.1.90 '' \\
  .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 reception in AggreGate:
# Context didactum-rack01 → Events → trap appears here

10.4 Important Didactum trap OIDs

11.1 Create dashboard for Didactum sensors

1. Navigation: Dashboards → New Dashboard.
2. Name: Didactum Rack Monitoring
3. Add dashboard widgets:

11.2 Recommended dashboard widgets

11.3 Floor plan with sensor overlay

1. Navigation: Dashboards → New Dashboard → Type: Floor Plan.
2. Background image: upload server room floor plan (PNG or SVG).
3. Place Didactum device as an icon on the floor plan.
4. Icon color: automatically based on the highest alert severity of the device.
5. Tooltip: display current temperature and leakage status.
6. Click on icon: opens detailed dashboard with all sensors.

11.4 Historical analysis

1. Right-click on a variable (e.g. temperatur_s1) → Show history.
2. Select time range: 7 days, 30 days, 90 days.
3. Display statistics: minimum, maximum, average, standard deviation.
4. Export as CSV or PDF for reports.

11.5 Automatic reports

1. Navigation: Administration → Reports → New Report.
2. Report: Didactum Monthly Report
3. Content: temperature min/max/avg, humidity min/max/avg, number of alarms by type
4. Time range: last month
5. Format: PDF
6. Delivery: automatically on the 1st of each month via email

# AggreGate server status:
sudo systemctl status aggregate-server
 
# Restart AggreGate server:
sudo systemctl restart aggregate-server
 
# Follow server log in real time:
sudo tail -f /opt/aggregate/server/logs/server.log
 
# Show only errors:
sudo grep -i "error\\|warn\\|snmp" /opt/aggregate/server/logs/server.log | tail -50
 
# Test SNMP reachability:
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:
snmptrap -v2c -c public 192.168.1.90 '' \\
  .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 firewall ports (ufw):
sudo ufw status verbose
 
# Open ports 161 and 162:
sudo ufw allow 161/udp
sudo ufw allow 162/udp
 
# Open port 6060 (client) and 8080 (web):
sudo ufw allow 6060/tcp
sudo ufw allow 8080/tcp

For firmware-specific OIDs and supported sensor types, always consult the current Didactum device documentation. Version-specific differences in AggreGate should be checked in the Tibbo Technology documentation.