Didactum Monitoring Devices and Sensors – Integration in SevOne NMS / IBM SevOne NPM

This guide describes the complete integration of Didactum Monitoring Devices into SevOne Network Management System (NMS) or IBM SevOne Network Performance Management (NPM), versions 5.x to 8.x. The goal is centralized monitoring of all sensors – temperature, humidity, leak, voltage, door contacts, and more – via the integrated SNMP poller, custom Object Types and Indicator Types, Threshold Policies, and SNMP trap processing.

Note on product name: SevOne was acquired by IBM in 2018 and has since been marketed as IBM SevOne Network Performance Management (NPM). The core architecture and configuration logic are largely identical across all versions (5.7 through 8.x). This guide applies to both names and refers to the current version.

1. Fundamentals and architecture

SevOne NMS is a scalable network performance management platform that supports SNMP polling, NetFlow analysis, syslog, and other protocols. The SNMP integration for Didactum devices is based on a hierarchical configuration model with Device Types, Object Types, and Indicator Types.

SevOne concepts for Didactum integration

SevOne concept	Meaning	Relevance for Didactum
Device	Monitored network device with IP and SNMP settings	The Didactum Monitoring Device
Device Type	Device classification (hierarchical); determines which Object Types are recognized	Own type Didactum Environmental Monitor
Object Type	Definition of an OID group to be monitored (e.g. all temperature sensors)	One Object Type each for temperature, leak, humidity, etc.
Indicator Type	Single measured value within an Object Type (e.g. temperature value S1)	Each OID is defined as an Indicator Type
Object Subtype	Instance-specific configuration for table-based OIDs	For multiple sensors of the same type (Sensor 1, 2, 3 ...)
MIB Manager	Management of MIB files; enables OID name resolution	Import Didactum MIB
SNMP OID Browser	Interactive tool for exploring MIB OIDs; basis for Object Type definition	Explore and select Didactum OIDs
Threshold Policy	Threshold rules for Indicator values (Warning, Minor, Major, Critical, Fatal)	Temperature and leak alarms
Alert Rule	Link between threshold violations and notification actions	E-mail, SMS, SNMP trap on Didactum alarm
Peer	SevOne appliance responsible for polling	Peer assignment for the Didactum device

Processing flow for Didactum sensors

1. SevOne peer polls the Didactum device via SNMP based on configured Object Types.
2. OID values are stored as Indicator data in the SevOne database.
3. Threshold Policies check Indicator values against configured thresholds.
4. An alert is generated when a threshold is exceeded.
5. Alert Rules trigger notifications by e-mail, SNMP trap, or other methods.
6. Performance graphs and reports are automatically generated from the stored data.

SevOne directory structure and ports

Component	Port / path	Function
SevOne Web Interface	TCP 443 (HTTPS)	Configuration, dashboards, reports
SNMP Polling	UDP 161 (outbound)	OID queries to the Didactum device
SNMP Trap Receiver	UDP 162 (inbound)	Reception of Didactum traps
REST API	TCP 443 /api/	Programmatic configuration and data retrieval

2. Requirements

• SevOne NMS 5.7.x or IBM SevOne NPM 8.x with administrator access
• SevOne appliance hardware, virtual, or cloud with active SNMP polling peer
• Didactum Monitoring Device reachable on the network, SNMP enabled
• UDP port 161 from the SevOne peer to the Didactum device open
• UDP port 162 on the SevOne peer open for SNMP traps
• SNMP community string known, default public
• Didactum MIB file available, DIDACTUM-RACKMONI2-MIB.mib
• Administrator access to the SevOne web interface

Example network configuration

Device	IP address	Role
SevOne Peer Appliance	192.168.1.98	SNMP polling, trap receiver, web interface
Didactum Monitoring Unit	192.168.1.100	Monitored device, SNMP agent

3. SNMP preparation on the Didactum device

3.1 Enable SNMP

1. Open the Didactum web interface at 192.168.1.100, log in with the 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 SevOne peer IP (192.168.1.98)
   • SNMP Trap Receiver: SevOne peer IP, port 162
4. Save the settings.

Caution: Change the default community string public in production environments. Use the same string in the SevOne device settings.

3.2 Test reachability

# SNMP walk — all Didactum OIDs (from the SevOne peer):
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 value: 235 (= 23.5 °C)

Note: Didactum returns temperature and voltage values with a factor of 10. In SevOne, this is taken into account via the formula function in the Indicator Type (Multiplier: 0.1 or Formula: value / 10).

4. MIB Manager – load Didactum MIB

The SevOne MIB Manager enables importing vendor MIBs so that OID numbers are displayed with readable names in the SNMP OID Browser.

4.1 Import MIB file into SevOne

1. Open the SevOne web interface at 192.168.1.98.
2. Navigation: Administration → Monitoring Configuration → MIB Manager.
3. Click Add MIB.
4. Select the Didactum MIB file: DIDACTUM-RACKMONI2-MIB.mib.
5. Click Upload.
6. After successful upload, the MIB appears in the MIB list with name, file size, and revision.
7. OIDs in the base 1.3.6.1.4.1.3854 range are now visible in the SNMP OID Browser with clear names.

4.2 Ensure dependent MIBs

Before importing the Didactum MIB, the following standard MIBs must be present in SevOne (usually preinstalled):

• SNMPv2-SMI
• SNMPv2-TC
• SNMPv2-MIB
• RFC1213-MIB (MIB-2)

Navigation: Administration → Monitoring Configuration → MIB Manager → check the list of existing MIBs.

4.3 Use SNMP OID Browser

1. Navigation: Administration → Monitoring Configuration → SNMP OID Browser.
2. Enter OID: 1.3.6.1.4.1.3854 → click Browse.
3. All Didactum OIDs are shown with clear names from the MIB.
4. OIDs can be taken directly from the browser into Object Type definitions.
5. SNMP walk directly in the browser: enter device 192.168.1.100 → click Walk.

5. Create Device Type for Didactum

Device Types classify devices hierarchically and determine which Object Types are automatically recognized and polled.

5.1 Create Device Type

1. Navigation: Administration → Monitoring Configuration → Device Types.
2. Click Add Device Type.
3. Fill in the following fields:
   • Name: Didactum Environmental Monitor
   • Description: Didactum Rack Monitoring Units – environmental sensor monitoring
   • Parent Device Type: Network Equipment or Root
4. Click Save.

5.2 Configure sysObjectID detection

1. In the Device Type tab: sysObjectID.
2. Click Add sysObjectID.
3. sysObjectID Prefix: .1.3.6.1.4.1.3854
4. Save. SevOne now automatically recognizes Didactum devices during discovery based on the sysObjectID.

6. Add Didactum device as a Device

6.1 Add device manually

1. Navigation: Devices → Add Device.
2. Fill in the following fields:
   • Name: didactum-rack01
   • IP Address: 192.168.1.100
   • Description: Didactum Rack Monitoring Unit – server room A
   • Peer: select the responsible SevOne appliance
   • Device Type: Didactum Environmental Monitor
3. Tab SNMP:
   • SNMP Capable: Enabled
   • Version: SNMPv2c
   • Community String: public
   • Port: 161
   • Timeout: 2000 ms
   • Retries: 3
4. Click Save and Discover.

6.2 Configure device for SNMP v3

1. In the device tab SNMP, set version SNMPv3.
2. Additional fields:
   • Security Name: SNMP v3 username
   • Auth Protocol: SHA
   • Auth Password: authentication password
   • Privacy Protocol: AES128
   • Privacy Password: encryption password

6.3 Start discovery after creation

1. Navigation: Devices → Device Manager → didactum-rack01.
2. Click Discover or Rediscover.
3. SevOne performs SNMP walk and detects existing Object Types.
4. Discovery result tab Objects shows detected objects.

6.4 Create device group

1. Navigation: Devices → Device Groups → Add Group.
2. Name: Didactum-Rack-Monitoring
3. Device Type Filter: Didactum Environmental Monitor.
4. All Didactum devices are automatically assigned to this group.

7. Configure Object Types and Indicator Types

Object Types and their Indicator Types define which SNMP OIDs SevOne queries and how the data is stored and visualized.

7.1 Create Object Type for temperature sensors

1. Navigation: Administration → Monitoring Configuration → Object Types.
2. Click Add Object Type.
3. The following settings:
   • Name: Didactum Temperature
   • Plugin: SNMP Poller
   • Description: Temperature sensors of the Didactum Rack Monitoring device
   • Device Type: Didactum Environmental Monitor
   • Polling Interval: 300 seconds (5 minutes)
   • Discovery: Enable Auto-Discovery when table OIDs are used
4. Save.

7.2 Add Indicator Types for temperature sensors

1. In the Object Type Didactum Temperature tab: Indicator Types → Add Indicator Type.
2. Indicator Type for Temperature Sensor 1:
   • Name: Temperature Sensor 1
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
   • Data Type: Gauge
   • Multiplier: 0.1 (raw value ÷ 10 for °C)
   • Units: °C
   • Description: Temperature Sensor 1 – rack front (raw value ÷ 10)
3. Repeat steps 2 for Sensor 2 and 3.

7.3 Object Type for leak sensors

1. New Object Type: Didactum Leak Status
2. Polling Interval: 60 seconds (time critical)
3. Indicator Types:
   • Name: Leak Sensor 1, OID: .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1, Multiplier: 1, Units: Status
   • Name: Leak Sensor 2, OID: .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.2, Multiplier: 1, Units: Status

7.4 All Object Types and Indicator Types at a glance

Object Type	Indicator Type	OID	Multiplier	Interval
Didactum Temperature	Temperature Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1	0.1	300 s
Didactum Temperature	Temperature Sensor 2	.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.2	0.1	300 s
Didactum Temperature	Temperature Sensor 3	.1.3.6.1.4.1.3854.1.2.2.1.16.1.3.3	0.1	300 s
Didactum Temp Status	Temp Status Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.16.1.4.1	1	300 s
Didactum Leak Status	Leak Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1	1	60 s
Didactum Leak Status	Leak Sensor 2	.1.3.6.1.4.1.3854.1.2.2.1.18.1.4.2	1	60 s
Didactum Humidity	Humidity Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.17.1.3.1	1	300 s
Didactum Humidity	Humidity Sensor 2	.1.3.6.1.4.1.3854.1.2.2.1.17.1.3.2	1	300 s
Didactum Voltage	Voltage Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.15.1.3.1	0.1	300 s
Didactum Door Status	Door Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.10.1.3.1	1	60 s
Didactum Smoke Status	Smoke Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.14.1.3.1	1	60 s
Didactum Motion Status	Motion Sensor 1	.1.3.6.1.4.1.3854.1.2.2.1.11.1.3.1	1	60 s

7.5 Assign Object Types to the device

1. Navigation: Devices → Device Manager → didactum-rack01 → Objects.
2. Click Add Objects.
3. Select Object Type Didactum Temperature → Add.
4. Add further Object Types (Didactum Leak Status, Didactum Humidity, etc.) in the same way.
5. SevOne begins data collection from the next polling cycle.

8. OID reference for SevOne

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.

8.1 Temperature sensors

OID	Description	Raw value	Multiplier	SevOne Threshold
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, Major ≥ 35
1.3.6.1.4.1.3854.1.2.2.1.16.1.4.{n}	Temperature status Sensor n	Enum 0/1/2	1	Minor ≥ 1, Major ≥ 2
1.3.6.1.4.1.3854.1.2.2.1.16.1.7.{n}	Upper limit Sensor n	°C × 10	0.1	Informative
1.3.6.1.4.1.3854.1.2.2.1.16.1.8.{n}	Lower limit Sensor n	°C × 10	0.1	Informative
1.3.6.1.4.1.3854.1.2.2.1.16.1.2.{n}	Sensor name n	Text	–	For indicator labeling

8.2 Leak and binary sensors

OID	Description	Raw value	Multiplier	SevOne Threshold
1.3.6.1.4.1.3854.1.2.2.1.18.1.4.{n}	Leak status Sensor n	0=OK, 1=Leak	1	Fatal ≥ 1
1.3.6.1.4.1.3854.1.2.2.1.10.1.3.{n}	Door contact status n	0=closed, 1=open	1	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	1	Fatal ≥ 1
1.3.6.1.4.1.3854.1.2.2.1.11.1.3.{n}	Vibration / motion n	0=none, 1=alarm	1	Major ≥ 1

8.3 Humidity and voltage

OID	Description	Raw value	Multiplier	SevOne 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	Minor ≥ 1, Major ≥ 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
1.3.6.1.4.1.3854.1.2.2.1.15.1.4.{n}	Voltage status Sensor n	Enum 0/1/2	1	Minor ≥ 1, Major ≥ 2
1.3.6.1.2.1.1.3.0	System Uptime	Hundredths of seconds	0.01	Informative

9. Threshold Policies and Alert Rules

9.1 Create Threshold Policy for temperature sensors

1. Navigation: Administration → Alerting → Threshold Policies → Add Policy.
2. Policy settings:
   • Policy Name: Didactum Temperature Thresholds
   • Description: Thresholds for Didactum temperature sensors
3. Add threshold rules (click Add Threshold):
   • Indicator Type: Temperature Sensor 1
   • Warning: 28 °C
   • Minor: 30 °C
   • Major: 32 °C
   • Critical: 35 °C
   • Fatal: 40 °C
4. Assign the policy to the Device or Device Type.
5. Save.

9.2 Threshold Policy for binary leak sensors

1. New policy: Didactum Leak Thresholds
2. Threshold rule:
   • Indicator Type: Leak Sensor 1
   • Fatal: 1 (at value ≥ 1 immediate fatal alarm)
   • Warning/Minor/Major: leave blank (direct Fatal)
3. Object Type polling interval: 60 seconds (time critical).

9.3 Alert Rule for e-mail notification

1. Navigation: Administration → Alerting → Alert Rules → Add Rule.
2. Rule for leak alarm:
   • Rule Name: Didactum Leak Alarm E-Mail
   • Trigger: Threshold exceeded: Fatal
   • Policy: Didactum Leak Thresholds
   • Device Group: Didactum-Rack-Monitoring
   • Action: Send Email
   • To: admin@example.com
   • Subject: SevOne FATAL Didactum leak device indicator
3. Save and activate.

9.4 Configure e-mail server in SevOne

1. Navigation: Administration → System Settings → Email.
2. Enter SMTP server, port, sender address.
3. Send test e-mail.

9.5 SevOne Threshold severity levels

Severity	Color coding	Use for Didactum
Warning	Yellow	Temperature 28 °C, humidity > 65 % rH
Minor	Orange	Temperature 30 °C, humidity > 70 % rH
Major	Red	Temperature 32 °C, door contact open
Critical	Dark red	Temperature 35 °C, voltage outside ±10 %
Fatal	Black/Purple	Leak detected, smoke detector triggered

9.6 Recommended threshold settings

Indicator Type	Warning	Minor	Critical	Fatal	Norm
Temperature (°C)	28	30	35	40	ASHRAE A1: 15–32
Humidity high (% rH)	65	70	75	80	ASHRAE: 20–80
Humidity low (% rH)	< 20	< 15	< 12	< 10	ASHRAE: 20–80
Leak Status (0/1)	–	–	–	≥ 1	Immediate alarm
Voltage high (V)	250	253	256	260	EN 50160 ±10 %
Voltage low (V)	< 210	< 207	< 200	< 196	EN 50160 ±10 %
Door / Smoke (0/1)	–	–	–	≥ 1	Policy-dependent

10. SNMP trap integration

SevOne NMS includes an integrated SNMP trap receiver. Incoming Didactum traps are assigned to the sending device and displayed as events in the SevOne interface.

10.1 Configure SNMP trap events in SevOne

1. Navigation: Administration → Monitoring Configuration → SNMP OID Browser.
2. Enter trap OID: .1.3.6.1.4.1.3854.1.7.2 (leak trap).
3. Click Add Trap Event.
4. Settings:
   • Event Name: Didactum Leak Alarm
   • Severity: Fatal
   • Message: LEAK detected on {source} – immediate action required!
   • Device Type: Didactum Environmental Monitor
5. Save. Repeat for all other trap OIDs.

10.2 Test trap reception

# Send test leak trap to SevOne:
snmptrap -v2c -c public 192.168.1.98 '' \
  .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 in SevOne event log:
# Reports → Events → Filter: Source = 192.168.1.100

10.3 Important Didactum trap OIDs

Trap OID	Event	SevOne severity
1.3.6.1.4.1.3854.1.7.1	Temperature alarm	Critical
1.3.6.1.4.1.3854.1.7.2	Leak alarm	Fatal
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	Critical
1.3.6.1.4.1.3854.1.7.10	Door contact opened	Major
1.3.6.1.4.1.3854.1.7.14	Smoke detector alarm	Fatal
1.3.6.1.4.1.3854.1.7.99	Device restart	Warning

11. Dashboards and reports

11.1 Open Device Summary for Didactum

1. Navigation: Devices → Device Manager → didactum-rack01.
2. Device Summary shows all collected Indicator values in real time.
3. Tab Performance: graphs for all Object Types (temperature, humidity, leak).
4. Time ranges: last hour, 24 hours, 7 days, 30 days, 1 year.

11.2 Customize performance graphs

1. In device Performance → Indicators → didactum-rack01.
2. Select Indicator Temperature Sensor 1.
3. The graph shows temperature trend (correctly in °C after multiplier application).
4. Overlay multiple Indicators in one graph: Overlay → Add Indicator.
5. Show threshold lines in graph: Show Thresholds.

11.3 Create dashboard for Didactum sensors

1. Navigation: Dashboards → Add Dashboard.
2. Name: Didactum Rack Monitoring
3. Add widgets:
   • Performance Chart: Temperature Sensor 1 and 2, last 24 hours
   • Performance Chart: Humidity Sensor 1, last 24 hours
   • Status Widget: Leak status of all Didactum devices
   • Alert Widget: Current alarms of the group Didactum-Rack-Monitoring
4. Save the dashboard and mark it as a favorite.

11.4 Configure automatic reports

1. Navigation: Reports → Scheduled Reports → Add Report.
2. Report type: Performance Report.
3. Device Group: Didactum-Rack-Monitoring.
4. Indicators: Temperature Sensor 1, Humidity Sensor 1, Leak Sensor 1.
5. Period: last month.
6. Format: PDF.
7. Delivery: monthly by e-mail to administrators.

12. Troubleshooting

Problem	Possible cause / solution
Device shows “SNMP Down” status	Community string wrong? UDP port 161 open? Allowed Managers on the Didactum device: SevOne peer IP entered? Test: snmpget -v2c -c public 192.168.1.100 sysDescr.0
Object Types are not discovered	Device Type assigned correctly? Rediscover performed? Assign Object Types manually to the Device: Devices → Objects → Add Objects.
Temperature value wrong (235 instead of 23.5)	Set multiplier in the Indicator Type to 0.1. Edit the Indicator Type multiplier field. Data will be displayed correctly from the next polling cycle.
MIB import fails	Check dependent MIBs (SNMPv2-SMI, SNMPv2-TC). Read the error message in MIB Manager. MIB file encoding: UTF-8 without BOM.
Threshold alarm is not triggered	Threshold Policy assigned to the device or device type? Alert Rule active and linked to policy? E-mail server configured? Check alert log.
SNMP traps do not arrive	UDP port 162 open on the SevOne peer? Trap receiver enabled in SevOne? Correct SevOne IP set as trap receiver in the Didactum device? Community string correct?
Graphs show no data	Polling has not yet taken place (wait for the first cycle). Object Type active and correct OID? Check SevOne peer status. Indicator data: Devices → didactum-rack01 → Performance.
Discovery takes a very long time	Increase timeout settings. SNMP walk too extensive (all OIDs are searched). Restrict Device Type with sysObjectID filter to the Didactum base.

Diagnostic commands and navigation paths

# Test SNMP reachability (from the SevOne peer):
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 SevOne:
snmptrap -v2c -c public 192.168.1.98 '' \
  .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

# Open firewall port for SNMP traps (Linux):
sudo firewall-cmd --permanent --add-port=162/udp
sudo firewall-cmd --reload

Appendix: SevOne configuration quick reference

Task	Navigation path in SevOne
Import MIB	Administration → Monitoring Configuration → MIB Manager → Add MIB
SNMP OID Browser	Administration → Monitoring Configuration → SNMP OID Browser
Create Device Type	Administration → Monitoring Configuration → Device Types → Add
Create Device	Devices → Add Device
Create Device Group	Devices → Device Groups → Add Group
Create Object Type	Administration → Monitoring Configuration → Object Types → Add
Create Indicator Type	Object Type → Indicator Types → Add Indicator Type
Assign Object Types to the device	Devices → Device Manager → Device → Objects → Add Objects
Create Threshold Policy	Administration → Alerting → Threshold Policies → Add Policy
Create Alert Rule	Administration → Alerting → Alert Rules → Add Rule
Configure trap event	Administration → Monitoring Configuration → SNMP OID Browser → Add Trap Event
E-mail settings	Administration → System Settings → Email
Create dashboard	Dashboards → Add Dashboard
Show performance graphs	Devices → Device Manager → Device → Performance
Create scheduled report	Reports → Scheduled Reports → Add Report
Rediscover device	Devices → Device Manager → Device → Discover

For firmware-specific OIDs and supported sensor types, always consult the current Didactum device documentation. SevOne documentation: ibm.com/docs/en/sevone-npm.