Didactum Monitoring Devices and Sensors – Integration into Verax NMS & APM

This guide describes the complete integration of Didactum monitoring devices into Verax NMS & APM (Verax Systems Corp.). The goal is the centralized monitoring of all sensors – temperature, humidity, leakage, voltage, door contacts, and more – via SNMP polling, custom Managed Objects, Aspects for service-oriented representation, threshold alarms, and SNMP trap processing.

Platform Note: Verax NMS & APM is a service-oriented IT management platform by Verax Systems Corp. (USA/Poland). It supports SNMP v1/v2c/v3, standalone and distributed deployments on Windows and Linux, as well as a unique Aspect concept that groups monitoring elements into service-oriented units and displays the aggregated status of an IT service (e.g., "Data Center Server Room A"). The Free Edition supports up to 10 Managed Elements.

1. Basics and Architecture

Verax NMS & APM manages network devices and applications as Managed Objects. Monitoring parameters (SNMP OIDs, ping, port checks, etc.) are configured for each object. The unique Aspect system allows multiple Managed Objects to be grouped into a higher-level service – such as all Didactum devices under the Aspect "Server Room Environmental Monitoring".

Verax NMS Core Concepts

Concept	Meaning	Relevance for Didactum
Managed Object	Monitored element (device, application, service)	The Didactum monitoring device
Monitoring Parameter	Individual measurement point (OID, ping, port, etc.)	One parameter per Didactum OID
SNMP Monitor	Polling configuration for SNMP OIDs	Temperature, leakage, humidity, etc.
Threshold	Threshold configuration for alarms	Warning, Minor, Major, Critical for sensor values
Alarm	Event upon threshold breach or SNMP trap	Leakage alarm, temperature alarm, etc.
Aspect	Logical group of Managed Objects; shows aggregated status	"Server Room A – Environmental Monitoring" aggregates all Didactum devices
Dashboard	Customizable web interface with widgets and graphs	Real-time display of all sensor values
MIB Browser	Integrated SNMP MIB browser for OID exploration	Explore and configure Didactum OIDs
Forecasting	Prediction of future metrics based on trend analysis	Predict temperature development

Processing Workflow for Didactum Sensors

1. Verax NMS polls the Didactum device via SNMP at configured intervals.
2. OID values are stored as monitoring parameter measurements.
3. Thresholds are checked; if breached, an alarm is generated.
4. SNMP traps from the device are received and processed as alarms.
5. Aspects aggregate the status of all Didactum devices into an overall status.
6. Dashboards visualize real-time values and historical trends.

Verax NMS Directories and Ports

Component	Port / Path
Verax NMS Web Interface	HTTP TCP 8080 (default) or HTTPS 8443
SNMP Polling (outbound)	UDP 161
SNMP Trap Receiver (inbound)	UDP 162
Installation Directory (Windows)	C:\Program Files\Verax NMS
Installation Directory (Linux)	/opt/verax-nms
Configuration Directory	<install>/conf/
Log Directory	<install>/logs/

2. Prerequisites

• Verax NMS & APM (any edition: Free, Standard, Professional, Enterprise) on Windows or Linux
• Java Runtime Environment 8 or newer (bundled with Verax)
• Web interface accessible: <SERVER>/verax
• SNMP tools (snmpwalk, snmpget) for preparation
• Didactum monitoring device accessible in the network, SNMP enabled
• UDP port 161 opened from the Verax server to the Didactum device
• UDP port 162 opened on the Verax server for SNMP traps
• SNMP community string known (default: public)
• Didactum MIB file available (DIDACTUM-RACKMONI2-MIB.mib)

Comparison of Verax NMS Editions

Edition	Max. Managed Elements	SNMP Traps	Aspects	Forecasting
Free	10	Yes	Yes	No
Standard	100	Yes	Yes	Yes
Professional	1,000	Yes	Yes	Yes
Enterprise	Unlimited	Yes	Yes	Yes

Example Network Configuration

Device	IP Address	Role
Verax NMS Server	192.168.1.99	Monitoring server, web interface, trap receiver
Didactum Monitoring Unit	192.168.1.100	Monitored device (SNMP agent)

3. SNMP Preparation on the Didactum Device

3.1 Enable SNMP

1. Access the Didactum web interface: 192.168.1.100, log in with an administrator account.
2. Navigation: Settings → Network → SNMP (or: Einstellungen → Netzwerk → 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 Verax server (192.168.1.99)
   • SNMP Trap Receiver: IP of the Verax server, port 162
4. Save settings.

3.2 Test Connectivity

# SNMP Walk – all Didactum OIDs:
snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854

# Temperature Sensor 1 (raw value × 10):
snmpget -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
# Expected return value: 235 (= 23.5 °C)

# System description:
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. In Verax NMS, this is taken into account using the Multiplier (0.1) in the monitoring parameter.

4. Prepare Verax NMS and Load MIB

4.1 Start Verax NMS and Access Web Interface

# Linux – start Verax NMS:
sudo /opt/verax-nms/bin/verax-nms.sh start

# Check service status:
sudo /opt/verax-nms/bin/verax-nms.sh status

# Access web interface:
# 192.168.1.99/verax
# Default login: admin / admin (please change immediately)

:: Windows – start Verax NMS as a Windows service:
net start "Verax NMS"
:: Web interface: 192.168.1.99/verax

4.2 Import Didactum MIB File into Verax NMS

1. Verax NMS web interface: Navigation: Administration → MIB Management → Upload MIB.
2. Select MIB file: DIDACTUM-RACKMONI2-MIB.mib.
3. Click on Upload.
4. After successful import: OIDs of the Didactum base (1.3.6.1.4.1.3854) are visible with clear names in the MIB browser.

Alternatively, copy the MIB file manually into the Verax MIB directory:

# Linux:
sudo cp DIDACTUM-RACKMONI2-MIB.mib /opt/verax-nms/mibs/

# Windows:
copy DIDACTUM-RACKMONI2-MIB.mib "C:\Program Files\Verax NMS\mibs\"

# Restart Verax NMS to load the MIB:
sudo /opt/verax-nms/bin/verax-nms.sh restart

4.3 Use MIB Browser

1. Navigation: Tools → MIB Browser.
2. Host: 192.168.1.100, Community: public, Version: v2c.
3. Enter OID: 1.3.6.1.4.1.3854 → click Walk.
4. All Didactum OIDs with clear names are displayed.
5. Transfer the OID directly from the browser into a new monitoring parameter.

4.4 Open Firewall for SNMP Traps

# Linux (firewalld):
sudo firewall-cmd --permanent --add-port=162/udp
sudo firewall-cmd --reload

# Linux (ufw):
sudo ufw allow 162/udp

# Windows (as administrator):
netsh advfirewall firewall add rule name="Verax NMS SNMP Trap" ^
  protocol=UDP dir=in localport=162 action=allow

5. Create Didactum as a Managed Object

5.1 Add Managed Object Manually

1. Verax NMS web interface: Navigation: Inventory → Add Managed Object.
2. Fill in the following fields:
   • Name: didactum-rack01
   • Display Name: Didactum Rack Monitoring – Server Room A
   • Category: Network Device (or your own category Environmental Monitor)
   • IP Address: 192.168.1.100
   • Description: Didactum Rack Monitoring Unit II – Server Room A, Rack 03
   • Location: Server Room A
   • SNMP Version: v2c
   • SNMP Community: public
   • SNMP Port: 161
3. Click on Save.

5.2 Network Discovery for Automated Detection

1. Navigation: Inventory → Network Discovery → Add IP Range.
2. IP Range: 192.168.1.100 – 192.168.1.110.
3. SNMP Community: public, Version: v2c.
4. Click on Discover – found devices will be listed.
5. Select Didactum device and import it as a Managed Object.

5.3 Configure SNMP v3

1. Edit Managed Object: Inventory → didactum-rack01 → Edit.
2. SNMP Version: v3.
3. Additional fields:
   • Security Name: SNMP v3 username from the Didactum device
   • Auth Protocol: SHA
   • Auth Password: Authentication password
   • Privacy Protocol: AES128
   • Privacy Password: Encryption password
4. Save.

5.4 Create Managed Object Group

1. Navigation: Inventory → Groups → Add Group.
2. Name: Didactum-Monitoring-Geraete
3. Description: All Didactum Rack Monitoring Units
4. Members: add didactum-rack01 and other Didactum devices.
5. The group is used for threshold rules and notifications.

6. Configure SNMP Monitoring Parameters

A separate monitoring parameter is created for each Didactum OID to be monitored.

6.1 SNMP Monitor for Temperature Sensor 1

1. Open Managed Object: Inventory → didactum-rack01.
2. Tab Monitoring → Add Monitor.
3. Monitor Type: select SNMP Get.
4. Following parameters:
   • Monitor Name: Temperature Sensor 1 – Rack Front
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
   • Data Type: Gauge / Float
   • Multiplier: 0.1 (raw value ÷ 10 for °C)
   • Unit: °C
   • Polling Interval: 300 seconds
   • Description: raw value ÷ 10 = °C (Didactum factor × 10)
5. Click on Save.

6.2 SNMP Monitor for Leakage Sensor 1

1. New monitor on the Managed Object: Add Monitor → SNMP Get.
2. Settings:
   • Monitor Name: Leakage Sensor 1 – Floor Area
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1
   • Multiplier: 1
   • Unit: Status (0=OK, 1=Alarm)
   • Polling Interval: 60 seconds (time-critical)

6.3 Overview of All Recommended SNMP Monitors

Monitor Name	OID	Multiplier	Unit	Interval
Temperature Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1	0.1	°C	300 s
Temperature Sensor 2	.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.2	0.1	°C	300 s
Temperature Sensor 3	.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.3	0.1	°C	300 s
Temp Status Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.16.1.4.1	1	Enum	300 s
Leakage Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1	1	0/1	60 s
Leakage Sensor 2	.1.3.6.1.4.1.3854.1.2.2.1.18.1.4.2	1	0/1	60 s
Humidity Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.17.1.3.1	1	% RH	300 s
Humidity Sensor 2	.1.3.6.1.4.1.3854.1.2.2.1.17.1.3.2	1	% RH	300 s
Voltage Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.15.1.3.1	0.1	V	300 s
Door Contact Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.10.1.3.1	1	0/1	60 s
Smoke Detector Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.14.1.3.1	1	0/1	60 s
Motion Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.11.1.3.1	1	0/1	60 s
System Uptime	.1.3.6.1.2.1.1.3.0	0.01	Seconds	3600 s

7. OID Reference for Verax NMS

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.

7.1 Temperature Sensors

OID	Description	Raw Value	Verax Multiplier	Threshold (after Multiplier)
1.3.6.1.4.1.3854.1.2.2.1.16.1.3.{n}	Temperature value sensor n	°C × 10	0.1	Warning ≥ 30, Critical ≥ 35 °C
1.3.6.1.4.1.3854.1.2.2.1.16.1.4.{n}	Temperature status sensor n	Enum 0/1/2	1	Warning ≥ 1, Critical ≥ 2
1.3.6.1.4.1.3854.1.2.2.1.16.1.7.{n}	Upper threshold limit sensor n	°C × 10	0.1	Informational
1.3.6.1.4.1.3854.1.2.2.1.16.1.8.{n}	Lower threshold limit sensor n	°C × 10	0.1	Informational
1.3.6.1.4.1.3854.1.2.2.1.16.1.2.{n}	Sensor name n	Text	–	For monitor labeling

7.2 Leakage and Binary Sensors

OID	Description	Raw Value	Verax Threshold
1.3.6.1.4.1.3854.1.2.2.1.18.1.4.{n}	Leakage status sensor n	0=OK, 1=Leakage	Critical ≥ 1 (Immediate alarm)
1.3.6.1.4.1.3854.1.2.2.1.10.1.3.{n}	Door contact status n	0=closed, 1=open	Major ≥ 1
1.3.6.1.4.1.3854.1.2.2.1.14.1.3.{n}	Smoke detector status n	0=OK, 1=Alarm	Critical ≥ 1 (Immediate alarm)
1.3.6.1.4.1.3854.1.2.2.1.11.1.3.{n}	Shock / Motion n	0=none, 1=Alarm	Major ≥ 1

7.3 Humidity and Voltage

OID	Description	Raw Value	Multiplier	Verax Threshold
1.3.6.1.4.1.3854.1.2.2.1.17.1.3.{n}	Humidity value sensor n	% RH	1	Warning > 70 or < 20
1.3.6.1.4.1.3854.1.2.2.1.17.1.4.{n}	Humidity status n	Enum 0/1/2	1	Warning ≥ 1, Critical ≥ 2
1.3.6.1.4.1.3854.1.2.2.1.15.1.3.{n}	Voltage value sensor n	V × 10	0.1	Warning < 207 or > 253 V
1.3.6.1.4.1.3854.1.2.2.1.15.1.4.{n}	Voltage status n	Enum 0/1/2	1	Warning ≥ 1, Critical ≥ 2
1.3.6.1.2.1.1.3.0	System Uptime	Centiseconds	0.01	Informational

8. Thresholds and Alerting

8.1 Configure Threshold for Temperature

1. Open monitor: Inventory → didactum-rack01 → Monitoring → Temperatur Sensor 1 → Edit.
2. Tab Thresholds → Add Threshold.
3. Warning threshold:
   • Severity: Warning
   • Condition: Greater than or equal
   • Value: 30 (°C, after multiplier application)
4. Critical threshold:
   • Severity: Critical
   • Condition: Greater than or equal
   • Value: 35
5. Lower warning threshold:
   • Severity: Warning
   • Condition: Less than
   • Value: 5
6. Save.

8.2 Threshold for Leakage (Immediate Alarm)

1. Monitor Leckage Sensor 1 → Thresholds → Add.
2. Settings:
   • Severity: Critical
   • Condition: Greater than or equal
   • Value: 1
   • Message: LEAKAGE DETECTED on {device} – Immediate action required!
3. Set the monitor's polling interval to 60 seconds.

8.3 Configure Email Notification

1. Navigation: Administration → Notifications → Email Settings.
2. Enter SMTP server, port, and sender address.
3. Send test email.
4. Create alert rule: Administration → Alert Rules → Add Rule:
   • Rule Name: Didactum-Leakage-Alarm
   • Trigger: Severity Critical, Group: Didactum-Monitoring-Geraete
   • Action: Send E-Mail to admin@example.com
   • Repeat: Every 5 minutes as long as the alarm is active

8.4 Recommended Thresholds

Monitor	Warning	Major	Critical	Norm
Temperature IT Rack (°C)	≤ 28 or < 5	≥ 30	≥ 35	ASHRAE A1: 15–32 °C
Temperature UPS Room (°C)	≥ 23	≥ 25	≥ 30	Manufacturer specification
Humidity high (% RH)	≥ 65	≥ 70	≥ 80	ASHRAE: 20–80 % RH
Humidity low (% RH)	< 20	< 15	< 10	ASHRAE: 20–80 % RH
Leakage (0/1)	–	–	≥ 1	Immediate alarm
Voltage 230 V AC (V)	< 210 or > 250	< 207 or > 253	< 196 or > 260	EN 50160 ±10 %
Door Contact / Smoke / Motion	–	≥ 1	–	Policy-dependent

9. Aspects for Service-Oriented Representation

The Aspect system is one of the most important features of Verax NMS. It allows grouping multiple Managed Objects into a higher-level service object – such as "Data Center Server Room A" – which displays the aggregated status of all elements it contains.

9.1 Create Aspect for Server Room Environmental Monitoring

1. Navigation: Inventory → Aspects → Add Aspect.
2. Following fields:
   • Name: Serverraum-A-Umgebungsmonitoring
   • Display Name: Server Room A – Environmental Monitoring
   • Description: Aggregated status of all Didactum environmental sensors in Server Room A
   • Status Aggregation: Worst-Case (worst individual status determines overall status)
3. Add Managed Objects:
   • Click on Add Element → select didactum-rack01
   • Select Monitors: all leakage, temperature, and status monitors
4. Save.

9.2 Hierarchical Aspects for Location Overview

1. Higher-level Aspect: Total Data Center
2. Contains: Serverraum-A-Umgebungsmonitoring, Serverraum-B-Umgebungsmonitoring, etc.
3. The higher-level Aspect shows the worst status of all server rooms.
4. In the Dashboard: click on Total Data Center → drill down to the individual rooms and sensors.

9.3 Display Aspect in the Dashboard

1. Navigation: Dashboards → Add Widget → Aspect Status.
2. Select Aspect: Serverraum-A-Umgebungsmonitoring.
3. Widget shows traffic light status: green (OK), yellow (Warning), orange (Major), red (Critical).
4. Clicking the widget opens a detailed view with all monitors and current values.

10. SNMP Trap Integration

Verax NMS includes an integrated SNMP trap receiver. Incoming Didactum traps are mapped to the sending Managed Object and processed as alarms.

10.1 Enable SNMP Trap Receiver

1. Navigation: Administration → System Settings → SNMP Trap Receiver.
2. Status: Enabled, Port: 162.
3. Accepted Communities: add public.
4. Save and restart Verax NMS.

10.2 Configure Trap Event Rules for Didactum

1. Navigation: Administration → SNMP Trap Rules → Add Rule.
2. Rule for leakage trap:
   • Trap OID: .1.3.6.1.4.1.3854.1.7.2
   • Alarm Name: Didactum Leakage Alarm
   • Severity: Critical
   • Message: LEAKAGE detected on {sourceIP} via SNMP Trap!
   • Notification: email to administrators
3. Create additional rules analogously for temperature, smoke detectors, door contacts, etc.

10.3 Important Didactum Trap OIDs

Trap OID	Event	Verax Severity
1.3.6.1.4.1.3854.1.7.1	Temperature Alarm	Major
1.3.6.1.4.1.3854.1.7.2	Leakage Alarm	Critical
1.3.6.1.4.1.3854.1.7.3	Humidity Alarm	Major
1.3.6.1.4.1.3854.1.7.4	Voltage Alarm	Major
1.3.6.1.4.1.3854.1.7.10	Door Contact Opened	Warning
1.3.6.1.4.1.3854.1.7.14	Smoke Detector Alarm	Critical
1.3.6.1.4.1.3854.1.7.99	Device Reboot	Warning

10.4 Perform Trap Test

# Send test trap for leakage to Verax NMS:
snmptrap -v2c -c public 192.168.1.99 '' \
  .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 alarm in Verax NMS:
# Alarms → Active Alarms → Filter: Source = 192.168.1.100

11. Dashboards and Reports

11.1 Create Dashboard for Didactum Sensors

1. Navigation: Dashboards → Add Dashboard.
2. Name: Didactum Rack Monitoring
3. Add Widgets:
   • Aspect Status Widget: Aspect Serverraum-A-Umgebungsmonitoring
   • Performance Chart: Temperature Sensor 1 and 2, last 24 hours
   • Performance Chart: Humidity Sensor 1
   • Indicator Widget: Leakage Sensor 1 (traffic light: green/red)
   • Indicator Widget: Leakage Sensor 2
   • Alarm Widget: Active alarms of the group Didactum-Monitoring-Geraete
4. Save dashboard and set as homepage.

11.2 Access Performance Charts

1. Open Managed Object: Inventory → didactum-rack01.
2. Tab Performance → Temperature Sensor 1.
3. Time ranges: Last hour, 24 hours, 7 days, 30 days, 1 year.
4. Chart shows values after multiplier application (correctly in °C).
5. Multiple monitors in one graph: Overlay → Add Monitor.

11.3 Use Forecasting Feature (from Standard Edition)

1. Open monitor: Temperature Sensor 1 → Forecasting.
2. Prediction horizon: 7 days.
3. Verax NMS calculates the predicted temperature trend based on historical data.
4. Checkpoint: Warning if the prediction exceeds a threshold within the next X days.

11.4 Automated Reports

1. Navigation: Reports → Scheduled Reports → Add Report.
2. Settings:
   • Report Type: Performance Summary
   • Managed Object Group: Didactum-Monitoring-Geraete
   • Metrics: Temperature Min/Max/Avg, leakage events, alarm overview
   • Time period: Last month
   • Format: PDF or HTML
   • Dispatch: Monthly via email

11.5 Geo-Map Representation with Didactum Devices

1. Navigation: Maps → Add Map.
2. Map type: OpenStreetMap or custom floor plan.
3. Place the Didactum Managed Object as an icon on the map.
4. Icon color automatically shows the current alarm status (green/yellow/red).
5. Clicking the icon opens a detailed view with all monitors.

12. Troubleshooting

Problem	Possible Cause / Solution
Managed Object shows "Unreachable"	Check ping connectivity. UDP port 161 opened? Community string correct? Allowed Managers on the Didactum device: Verax server IP entered?
Sensor values are too high by a factor of 10	Multiplier in the monitor configuration is set incorrectly. Ensure it is set to 0.1 for temperature and voltage.
SNMP traps are not received	Check UDP port 162 on the Verax server firewall. Didactum configuration: Trap receiver IP and port correct? Trap receiver service enabled in Verax?
Alarms are not cleared automatically	Ensure that the Didactum device sends a corresponding "Clear Trap" or that the Verax threshold condition evaluates back to normal.
MIB upload fails	Check the syntax of the MIB file. Dependencies (e.g., RFC-MIBs) must be imported beforehand or be present in the MIB directory.

13. Quick Reference: Most Important Paths and Commands

Action / Component	Path / Command
Start Verax NMS (Linux)	sudo /opt/verax-nms/bin/verax-nms.sh start
Stop Verax NMS (Linux)	sudo /opt/verax-nms/bin/verax-nms.sh stop
Log files (Linux)	/opt/verax-nms/logs/wrapper.log & nms.log
Log files (Windows)	C:\Program Files\Verax NMS\logs\
Main configuration file	<install>/conf/nms.properties
Create dashboard	Dashboards → Add Dashboard
Display performance chart	Inventory → <Object> → Performance
Forecasting	Inventory → <Object> → Monitoring → <Monitor> → Forecasting
Scheduled Report	Reports → Scheduled Reports → Add Report
Geo-Map	Maps → Add Map
Active Alarms	Alarms → Active Alarms

Always consult the current Didactum device documentation for firmware-specific OIDs and supported sensor types. Verax NMS documentation: veraxsystems.com.