Didactum Monitoring Devices and Sensors – Integration into HP Network Node Manager (NNMi)
This guide describes the complete integration of Didactum monitoring devices into HPE Network Node Manager i (NNMi), version 10.x and newer (also known as Micro Focus NNMi or OpenText NNMi). The goal is centralized monitoring of all sensors – temperature, humidity, leakage, voltage, door contacts, and others – via NNMi Spiral Discovery, Custom Poller Collections, Threshold Incidents, and SNMP trap processing.
Note on naming: Over the years, HP NNMi was transferred from HP to HPE to Micro Focus and most recently to OpenText. The core functionality and configuration logic are largely identical across all versions (9.x to 10.3x). This guide refers to NNMi 10.x.
1. Fundamentals and Architecture
HP NNMi is an enterprise network management solution with a unique Spiral Discovery mechanism that automatically discovers and maintains network topologies. For monitoring environmental sensors such as Didactum devices, NNMi offers the Custom Poller feature: any SNMP MIB OID can be defined as Custom Poller Collections, polled regularly, and checked against configurable thresholds or comparison values (Comparison Maps). When a state changes, NNMi automatically generates incidents.
NNMi core components for Didactum integration
| NNMi concept | Function | Relevance for Didactum |
|---|---|---|
| Spiral Discovery | Automatic network discovery via SNMP/ICMP, based on sysObjectID | Automatically detect Didactum devices and add them to the topology |
| Communication Configuration | SNMP community strings, timeouts, retries per IP/range | Configure SNMP access to the Didactum device |
| Device Profile | Device profile based on sysObjectID (vendor, model, icon) | Classify the Didactum device as an environmental monitor |
| Node Group | Logical grouping of nodes for monitoring rules | Group all Didactum devices together |
| Custom Poller Collection | MIB expression-based polling with threshold/comparison map | Query OID values for temperature, leakage, humidity, and more |
| MIB Variable / MIB Expression | Single OID or formula from multiple OIDs | e.g. tempValue.1 / 10 for temperature in °C |
| Threshold / Comparison Map | Threshold or value mapping for state calculation | OK/Warning/Critical depending on sensor value |
| Incident | Event when a Custom Polled Instance changes state | Alarm on leakage detection, temperature exceedance, etc. |
| SNMP Trap Receiver | Receive and process incoming SNMP traps | Proactive alarms from the Didactum device |
| MIB Browser | Interactive SNMP walk and GET tool | Explore and test Didactum OIDs |
NNMi Custom Poller – Processing flow
- The administrator defines a Custom Poller Collection with a MIB expression (OID or formula).
- A Policy links the collection to a node group (e.g. all Didactum devices).
- NNMi polls the MIB expression at configured intervals.
- The result is stored as a Custom Polled Instance.
- NNMi checks the value against Thresholds (numerical limits) or Comparison Maps (value-to-status mapping).
- When the state changes (Normal → High/Low State), NNMi generates an Incident.
- Notifications by email or external scripts are triggered.
2. Prerequisites
- HPE/Micro Focus NNMi 10.x or newer with administrator access
- Linux server (RHEL/CentOS 7+) or Windows Server 2016+ as NNMi server
- NNMi web console reachable (default: HTTPS port 443 or HTTP port 80)
- SNMP tools (snmpwalk, snmpget) for preparation
- Didactum monitoring device reachable in the network, SNMP enabled
- UDP port 161 from the NNMi server to the Didactum device allowed
- UDP port 162 on the NNMi server allowed for SNMP traps
- SNMP community string known (default: public)
- Didactum MIB file available (DIDACTUM-RACKMONI2-MIB.mib)
- Optional: NNM iSPI Performance for Metrics (for advanced performance trending graphs)
Check NNMi services
# Linux – NNMi service status: ovstatus -c # Show all NNMi processes: ovstatus # Restart NNMi: ovstop && ovstart # Open NNMi web interface: # <NNMi-SERVER>/nnm/
Example network configuration
| Device | IP address | Role |
|---|---|---|
| NNMi server | 192.168.1.88 | Monitoring server, web console, trap receiver |
| Didactum Monitoring Unit | 192.168.1.100 | Monitored device (SNMP agent) |
3. SNMP preparation on the Didactum device
3.1 Enable SNMP
- Open the Didactum web interface: 192.168.1.100, log in with an admin account.
- Navigation: Settings → Network → SNMP (or: Settings → Network → SNMP).
- 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 NNMi server (192.168.1.88)
- SNMP Trap Receiver: IP of the NNMi server, port 162
- Save the settings.
3.2 Test reachability from the NNMi server
# SNMP walk – all Didactum OIDs: snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854 # Temperature sensor 1: snmpget -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 # System OID for device profile: snmpget -v2c -c public 192.168.1.100 1.3.6.1.2.1.1.2.0 # 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 (235 = 23.5 °C). NNMi supports mathematical MIB expressions – the value can be converted directly to °C with the formula tempValue.1 / 10.
4. Prepare NNMi and load MIB
4.1 Load the Didactum MIB file into NNMi
NNMi requires the Didactum MIB so that OID numbers are displayed in the MIB Browser, in Custom Poller Collections, and in incident messages with readable names.
- Transfer the MIB file to the NNMi server.
- Place the MIB in the NNMi MIB directory:
# Linux: sudo cp DIDACTUM-RACKMONI2-MIB.mib /opt/OV/share/snmp_mibs/customer/ # Windows: copy DIDACTUM-RACKMONI2-MIB.mib "C:\Program Files\HP\HP BTO Software\share\snmp_mibs\customer\"
- Load the MIB into NNMi (as root / administrator):
# Linux: /opt/OV/bin/nnmloadmib.ovpl -load DIDACTUM-RACKMONI2-MIB.mib # Windows: "%OvInstallDir%\bin\nnmloadmib.ovpl" -load DIDACTUM-RACKMONI2-MIB.mib # List loaded MIBs: /opt/OV/bin/nnmloadmib.ovpl -list | grep -i didactum
- Alternatively via the NNMi console: Configuration → MIBs → Load/Upload MIB (available depending on NNMi version).
4.2 Check MIB load
# Check whether the MIB was loaded correctly: /opt/OV/bin/nnmsnmpwalk.ovpl -u admin -p adminpasswort \ -v 2c -c public 192.168.1.100 .1.3.6.1.4.1.3854 # With readable OID names (after MIB load): /opt/OV/bin/nnmsnmpwalk.ovpl -u admin -p adminpasswort \ -v 2c -c public -O s 192.168.1.100 .1.3.6.1.4.1.3854
4.3 Enable SNMP Trap Receiver in NNMi
- Navigation: Configuration → Incidents → SNMP Trap Incidents.
- Check that the trap receiver is active (default: port 162, UDP).
- Allow the firewall on the NNMi server:
# Linux (firewalld): sudo firewall-cmd --permanent --add-port=162/udp sudo firewall-cmd --reload # Linux (iptables): sudo iptables -A INPUT -p udp --dport 162 -j ACCEPT # Linux (ufw): sudo ufw allow 162/udp
5. Discover the Didactum device (Spiral Discovery)
5.1 Add discovery seed
NNMi uses Spiral Discovery, which explores the network starting from a seed device. The Didactum device is added as a seed:
- Navigation: Configuration → Discovery → Seeds.
- Click New.
- Hostname or IP Address: 192.168.1.100
- Click Save.
Alternatively via command line:
# Add seed IP to discovery: /opt/OV/bin/nnmloadseeds.ovpl -f /tmp/didactum_seeds.txt # Content of the seed file: echo "192.168.1.100" > /tmp/didactum_seeds.txt
5.2 Configure auto-discovery rules
- Navigation: Configuration → Discovery → Auto-Discovery Rules.
- New rule: Add Rule.
- Rule Name: Didactum Monitoring Devices
- IP Address Range: 192.168.1.100 – 192.168.1.110
- sysObjectID Prefix: .1.3.6.1.4.1.3854 (Didactum devices only)
- Action: Add to NNMi Management
- Save and restart discovery.
5.3 Check discovery result
- Navigation: Inventory → Nodes.
- Search for IP 192.168.1.100.
- The node appears with sysName, sysDescr, and management status.
- Right-click the node → Actions → Polling → Configuration Poll – forces immediate discovery.
5.4 Check node properties
- Double-click the Didactum node → node detail form opens.
- Tab General: check hostname, IP, sysDescr, sysObjectID.
- Tab SNMP: confirm SNMP version and community string.
- Tab MIB Information: click List Supported MIBs – the Didactum MIB should appear (after MIB load).
6. Communication Configuration and credentials
6.1 Configure SNMP community string
- Navigation: Configuration → Communication Configuration.
- Tab SNMP Community Strings.
- Click New:
- Read Community: public
- Ordering: 1 (highest priority)
- Specific Nodes: 192.168.1.100 (Didactum device only)
- Save.
Important: NNMi must know the community string before discovery starts. Otherwise, the device is classified as Non-SNMP.
6.2 Adjust SNMP version and timeouts
- Navigation: Configuration → Communication Configuration → Default SNMP Settings.
- Device-specific setting for Didactum:
- SNMP Version: SNMPv2c
- Timeout: 2000 ms
- Retries: 3
- Port: 161
6.3 For SNMP v3
- Tab SNMPv3 Settings in Communication Configuration.
- New SNMPv3 configuration:
- Security Name: SNMP v3 username
- Auth Protocol: SHA
- Auth Password: authentication password
- Privacy Protocol: AES128
- Privacy Password: encryption password
- Specific Nodes: 192.168.1.100
6.4 Communication test with the NNMi MIB Browser
- Select node → right-click → Actions → MIB Information → MIB Browser.
- Enter OID: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1.
- Click Get – the raw temperature value should appear (e.g. 235).
- Click Walk → complete SNMP walk of the Didactum device.
7. Create Device Profile for Didactum
NNMi uses Device Profiles (based on sysObjectID) to classify devices. Since Didactum does not have a preinstalled profile in NNMi, a custom one is created.
7.1 Determine the sysObjectID of the Didactum device
# Query sysObjectID: snmpget -v2c -c public 192.168.1.100 1.3.6.1.2.1.1.2.0 # Typical response for Didactum Rack Monitoring Unit: # SNMPv2-SMI::enterprises.3854.1.1.1 (or similar)
7.2 Create device profile
- Navigation: Configuration → Device Profiles.
- Click New.
- Fill in the following fields:
- sysObjectID: .1.3.6.1.4.1.3854.1.1.1 (adjust depending on model)
- Vendor: Didactum
- Model: Rack Monitoring Unit II
- Device Category: Environmental Monitor (or Other)
- Device Family: Environmental Sensors
- System OID Prefix Matching: Enabled (detects all Didactum variants)
- Save.
- Run discovery again: Actions → Polling → Configuration Poll on the Didactum node.
7.3 Create a node group for Didactum devices
- Navigation: Configuration → Node Groups.
- Click New:
- Name: Didactum Rack Monitoring
- Notes: All Didactum Rack Monitoring Units in the network
- Tab Additional Filters:
- Filter: Vendor = Didactum (after device profile configuration) OR
- Filter: sysObjectID starts with .1.3.6.1.4.1.3854
- Save – NNMi automatically assigns all Didactum nodes to this group.
8. Configure Custom Poller Collections
Custom Poller Collections are the central tool in NNMi for monitoring Didactum-specific sensor values. Each collection consists of a MIB expression, a policy (device assignment), and optional threshold or comparison map configurations.
8.1 Create Custom Poller Collection for temperature
- Navigation: Configuration → Custom Poller → Custom Poller Collections → New.
- Tab Basic Settings:
- Name: Didactum Temperature S1
- Description: Temperature Sensor 1 – Rack Front
- Collection Type: Instance
- Polling Interval: 300 seconds (5 minutes)
- Include in Node Status: Enabled (lets the sensor state influence node status)
- Tab MIB Variable:
- MIB Expression: tempValue.1 / 10 (raw value ÷ 10 for °C) OR, for a manual OID entry: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 / 10
- Display Unit: °C
- Variable Type: Gauge
- Tab Thresholds:
- High Threshold: 30 → High State: Warning
- High Threshold: 35 → High State: Critical
- Low Threshold: 5 → Low State: Warning
- Generate Incident: Enabled
- Save.
8.2 Create a policy for the collection (assign node group)
- In the Custom Poller Collection: tab Policies → New.
- Settings:
- Policy Name: Didactum Temp Policy
- Node Group: Didactum Rack Monitoring
- Active State: Active
- Save. NNMi begins polling all nodes in the group.
8.3 Custom Poller Collection for leakage (comparison map)
For binary sensor values such as leakage (0 = OK, 1 = alarm), a comparison map is the more suitable configuration – this allows NNMi to assign values directly to a status:
- New collection: Didactum Leakage S1
- MIB Variable: .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1 (leakage status sensor 1)
- Polling Interval: 60 seconds
- Tab Comparison Maps → New:
- Ordering: 1
- Comparison Operator: = (equals)
- Comparison Value: 1
- High State: Critical
- Generate Incident: Yes
- Incident Message: LEAKAGE detected on {node} – sensor 1! Immediate action required!
- Second comparison map entry for OK status:
- Ordering: 2
- Comparison Value: 0
- High State: Normal
- Save and assign policy: node group Didactum Rack Monitoring.
8.4 Configure Custom Poller via command line
NNMi provides the command-line tool nnmcustompollerconfig.ovpl for script-based configuration:
# Create a new Custom Poller Collection for temperature S1: /opt/OV/bin/nnmcustompollerconfig.ovpl \ -u admin -p adminpasswort \ -action addCollection \ -name "Didactum Temperature S1" \ -description "Temperature Sensor 1 Rack Front" \ -collectionType Instance \ -pollingInterval 300 \ -mibExpression ".1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 / 10" \ -generateIncident true # Add threshold: /opt/OV/bin/nnmcustompollerconfig.ovpl \ -u admin -p adminpasswort \ -action addThreshold \ -collectionName "Didactum Temperature S1" \ -highThreshold 30 \ -highState Warning \ -rearmThreshold 28 # List collections: /opt/OV/bin/nnmcustompollerconfig.ovpl \ -u admin -p adminpasswort \ -action listCollections
8.5 All recommended Custom Poller Collections at a glance
| Collection name | MIB Expression / OID | Type | Interval | Configuration |
|---|---|---|---|---|
| Didactum Temperature S1 | .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 / 10 | Gauge | 300 s | Threshold: Warn ≥ 30, Crit ≥ 35 |
| Didactum Temperature S2 | .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.2 / 10 | Gauge | 300 s | Threshold: Warn ≥ 30, Crit ≥ 35 |
| Didactum Temp Status S1 | .1.3.6.1.4.1.3854.1.2.2.1.16.1.4.1 | Gauge | 300 s | Comparison Map: 0=Normal, 1=Warning, 2=Critical |
| Didactum Leakage S1 | .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1 | Gauge | 60 s | Comparison Map: 0=Normal, 1=Critical |
| Didactum Leakage S2 | .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.2 | Gauge | 60 s | Comparison Map: 0=Normal, 1=Critical |
| Didactum Humidity S1 | .1.3.6.1.4.1.3854.1.2.2.1.17.1.3.1 | Gauge | 300 s | Threshold: Warn > 70 or < 20 |
| Didactum Voltage S1 | .1.3.6.1.4.1.3854.1.2.2.1.15.1.3.1 / 10 | Gauge | 300 s | Threshold: Warn < 207 or > 253 |
| Didactum Door Contact S1 | .1.3.6.1.4.1.3854.1.2.2.1.10.1.3.1 | Gauge | 60 s | Comparison Map: 0=Normal, 1=Warning |
| Didactum Smoke Detector S1 | .1.3.6.1.4.1.3854.1.2.2.1.14.1.3.1 | Gauge | 60 s | Comparison Map: 0=Normal, 1=Critical |
| Didactum Motion S1 | .1.3.6.1.4.1.3854.1.2.2.1.11.1.3.1 | Gauge | 60 s | Comparison Map: 0=Normal, 1=Warning |
8.6 Show Custom Polled Instances
- Navigation: Inventory → Custom Polled Instances.
- Filter by node: 192.168.1.100.
- Each instance shows: last value, state (Normal/Warning/Critical), last poll timestamp.
- Double-click an instance → detail view with state change history.
9. OID reference for NNMi Custom Poller
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.).
9.1 Temperature sensors
| OID | Description | Raw value | MIB Expression | NNMi Threshold / Comparison Map |
|---|---|---|---|---|
| 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.{n} | Temperature value sensor n | °C x 10 | OID / 10 | Threshold: Warn ≥ 30, Crit ≥ 35 |
| 1.3.6.1.4.1.3854.1.2.2.1.16.1.4.{n} | Temperature status sensor n | Enum 0/1/2 | Direct value | Comparison Map: 0→Normal, 1→Warning, 2→Critical |
| 1.3.6.1.4.1.3854.1.2.2.1.16.1.7.{n} | Upper limit sensor n | °C x 10 | OID / 10 | Informational (no threshold) |
| 1.3.6.1.4.1.3854.1.2.2.1.16.1.8.{n} | Lower limit sensor n | °C x 10 | OID / 10 | Informational (no threshold) |
| 1.3.6.1.4.1.3854.1.2.2.1.16.1.2.{n} | Sensor name n | Text | – | For incident messages |
9.2 Leakage sensors
| OID | Description | Raw value | MIB Expression | Comparison Map |
|---|---|---|---|---|
| 1.3.6.1.4.1.3854.1.2.2.1.18.1.4.{n} | Leakage status sensor n | 0=OK, 1=Leakage | Direct value | 0→Normal, 1→Critical |
| 1.3.6.1.4.1.3854.1.2.2.1.18.1.3.{n} | Leakage value sensor n | 0=dry | Direct value | 0→Normal, ≥ 1→Critical |
| 1.3.6.1.4.1.3854.1.2.2.1.18.1.2.{n} | Sensor name n | Text | – | – |
9.3 Humidity sensors
| OID | Description | Raw value | MIB Expression | NNMi Threshold |
|---|---|---|---|---|
| 1.3.6.1.4.1.3854.1.2.2.1.17.1.3.{n} | Humidity value sensor n | % RH | Direct value | High: > 70 (Warning), > 80 (Critical); Low: < 20 (Warning) |
| 1.3.6.1.4.1.3854.1.2.2.1.17.1.4.{n} | Humidity status n | Enum 0/1/2 | Direct value | Comparison Map: 0→Normal, 1→Warning, 2→Critical |
| 1.3.6.1.4.1.3854.1.2.2.1.17.1.7.{n} | Upper limit sensor n | % RH | Direct value | Informational |
| 1.3.6.1.4.1.3854.1.2.2.1.17.1.8.{n} | Lower limit sensor n | % RH | Direct value | Informational |
9.4 Other sensors
| OID | Description | Raw value | MIB Expression | NNMi configuration |
|---|---|---|---|---|
| 1.3.6.1.4.1.3854.1.2.2.1.15.1.3.{n} | Voltage value sensor n | V x 10 | OID / 10 | Threshold: Warn < 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 | Direct value | Comparison Map: 0→Normal, 1→Warning, 2→Critical |
| 1.3.6.1.4.1.3854.1.2.2.1.10.1.3.{n} | Door contact status n | 0=closed, 1=open | Direct value | Comparison Map: 0→Normal, 1→Warning |
| 1.3.6.1.4.1.3854.1.2.2.1.11.1.3.{n} | Shock / motion n | 0=none, 1=alarm | Direct value | Comparison Map: 0→Normal, 1→Warning |
| 1.3.6.1.4.1.3854.1.2.2.1.14.1.3.{n} | Smoke detector status n | 0=OK, 1=alarm | Direct value | Comparison Map: 0→Normal, 1→Critical |
| 1.3.6.1.2.1.1.3.0 | System uptime | Hundredths of seconds | Direct value | Informational |
10. Incidents and alerting
10.1 Incident configuration for Custom Poller
... NNMi automatically generates incidents when a Custom Polled Instance changes state (e.g. Normal → Critical). The incident template can be adjusted:
- Navigation: Configuration → Incidents → Custom Poller Incidents.
- Open an existing incident template for Custom Poller or create a new one.
- Adjustments:
- Incident Name: Didactum Leakage Critical
- Severity: Critical
- Message Format: LEAKAGE detected: {customPolledInstance.node.name} – sensor {customPolledInstance.name} – value: {customPolledInstance.value}
- Category: Environmental
- Priority: High
10.2 Use Incident Browser
- Navigation: Incident Browsing → Open Incidents.
- Filter: Source: 192.168.1.100 or Category: Environmental.
- Incident details: timestamp, severity, affected node, value, status.
- Acknowledge the incident: Actions → Acknowledge.
- Close the incident after remediation: Actions → Close.
10.3 Configure email notification
- Navigation: Configuration → Incidents → Incident Actions.
- New action: Email Notification for Critical incidents of the Didactum node group.
- Trigger: Incident Severity = Critical
- Node Group: Didactum Rack Monitoring
- Email Recipients: admin@example.com
- Subject: [NNMi CRITICAL] Didactum Alarm: {incident.name} on {node.name}
10.4 Recommended thresholds
| Collection | Warning threshold | Critical threshold | Rearm | Standard |
|---|---|---|---|---|
| IT rack temperature (°C) | ≥ 30 | ≥ 35 | 28 | ASHRAE A1: 15–32 °C |
| UPS room temperature (°C) | ≥ 25 | ≥ 30 | 23 | Manufacturer specification |
| High humidity (% RH) | ≥ 70 | ≥ 80 | 65 | ASHRAE: 20–80 % RH |
| Low humidity (% RH) | ≤ 20 | ≤ 10 | 25 | ASHRAE: 20–80 % RH |
| Leakage (0/1) | – | = 1 | = 0 | Immediate alarm |
| Voltage 230 V AC (V) | < 207 or > 253 | < 196 or > 260 | 210 | EN 50160 ±10 % |
| Door contact / smoke / motion | – | = 1 | = 0 | Policy-dependent |
11. SNMP trap integration
NNMi includes a native SNMP trap receiver. Didactum traps are automatically assigned to the sending node and displayed as SNMP trap incidents in the Incident Browser – without additional configuration, provided that the Didactum MIB is loaded.
11.1 Create SNMP Trap Incident Configurations
- Navigation: Configuration → Incidents → SNMP Trap Incidents → New.
- Definition for leakage trap:
- Name: Didactum Leakage Trap
- SNMP Object ID: .1.3.6.1.4.1.3854.1.7.2
- Severity: Critical
- Category: Environmental
- Message Format: LEAKAGE detected via SNMP trap from {trapSource}
- Enable this Incident: Enabled
- Save. NNMi now automatically classifies incoming traps of this OID as Didactum Leakage Trap.
11.2 Trap definitions for all Didactum trap OIDs
| Trap OID | Incident name | Severity | Category |
|---|---|---|---|
| 1.3.6.1.4.1.3854.1.7.1 | Didactum Temperature Alarm Trap | Major | Environmental |
| 1.3.6.1.4.1.3854.1.7.2 | Didactum Leakage Alarm Trap | Critical | Environmental |
| 1.3.6.1.4.1.3854.1.7.3 | Didactum Humidity Alarm Trap | Major | Environmental |
| 1.3.6.1.4.1.3854.1.7.4 | Didactum Voltage Alarm Trap | Major | Environmental |
| 1.3.6.1.4.1.3854.1.7.10 | Didactum Door Contact Trap | Warning | Security |
| 1.3.6.1.4.1.3854.1.7.14 | Didactum Smoke Detector Trap | Critical | Environmental |
| 1.3.6.1.4.1.3854.1.7.99 | Didactum Device Reboot Trap | Warning | Availability |
11.3 Forward SNMP trap forwarding
NNMi can forward Didactum traps to other management systems:
- Navigation: Configuration → Incidents → SNMP Trap Forwarding → New.
- Destination: IP and port of the target system.
- Filter: Forward only traps from the OID base .1.3.6.1.4.1.3854.
11.4 Perform trap test
# Send test trap for leakage to NNMi: snmptrap -v2c -c public 192.168.1.88 '' \ .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 # Trap appears in the NNMi Incident Browser: # Incident Browsing → Open Incidents → Filter: Source = 192.168.1.100
12. Maps, dashboards, and reports
12.1 Node Group Map for Didactum devices
- Navigation: View → Node Group Maps → Didactum Rack Monitoring.
- All Didactum nodes are shown as icons, with the color indicating the current status (green/yellow/orange/red).
- Upload background image: Edit Map → Background → Upload Image (server room floor plan).
- Position the Didactum icons on the floor plan.
12.2 Custom Polled Instances in the dashboard
- Navigation: Inventory → Custom Polled Instances.
- Filter by node group Didactum Rack Monitoring.
- All current sensor values and states at a glance.
- Sort by severity: Critical instances at the top.
12.3 Performance reports (with NNM iSPI Performance)
If the optional NNM iSPI Performance for Metrics is installed, Custom Poller values can be visualized as trend graphs:
- Select node → right-click → Actions → NNM iSPI Performance → Reporting.
- Select collection: Didactum Temperature S1.
- Time period: last 24 hours, 7 days, or 30 days.
- Report type: Line Graph, Table, Top-N Report.
12.4 Generate incident report
- Navigation: Incident Browsing → Closed Incidents.
- Filter: Category = Environmental, Node Group = Didactum.
- Time period: last month.
- Export as CSV or PDF.
13. Troubleshooting
| Problem | Possible cause / solution |
|---|---|
| Device is discovered as Non-SNMP | The community string must be configured in NNMi before discovery: Configuration → Communication Configuration → SNMP Community Strings. Then force a new Configuration Poll. |
| Node does not appear after discovery | Is the seed entered correctly? Is the auto-discovery rule active? Firewall: UDP 161 allowed? Community string correct? Check NNMi log: /var/opt/OV/log/nnm/. |
| MIB load fails | Check dependent MIBs (SNMPv2-SMI, SNMPv2-TC). Validate MIB file syntax with nnmloadmib.ovpl -validate. Read the error message in the log. |
| Custom Poller returns no values | Is the MIB expression correct? Is the OID prefixed with a leading dot? Is the policy active and the node group correct? Run another Configuration Poll on the node. Use nnmcustompollerconfig.ovpl -action listCollections to verify. |
| Temperature value is wrong (235 instead of 23.5) | Adjust the MIB expression: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 / 10. The divisor is supported by NNMi in the expression. Enter threshold values accordingly in °C (not x 10). |
| Incident is not generated | Is Generate Incident enabled in Threshold/Comparison Map? Is the incident configuration saved and active? Does the Custom Polled Instance show the correct state? Check the incident log. |
| SNMP traps do not appear in the Incident Browser | UDP port 162 allowed? Trap Incident Configuration created? Didactum MIB loaded (for OID name resolution)? Is the NNMi trap receiver active? Send a test trap and check the log. |
| No email notifications | Is the Incident Action configured and active? SMTP server entered in NNMi? Configuration → Server Configuration → SMTP. Does the incident severity match the action trigger? |
Diagnostic commands overview
# NNMi process status: ovstatus -c # Start / stop NNMi: ovstart ovstop # NNMi logs (Linux): ls /var/opt/OV/log/nnm/ tail -f /var/opt/OV/log/nnm/nnm.log # Load MIB: /opt/OV/bin/nnmloadmib.ovpl -load DIDACTUM-RACKMONI2-MIB.mib # Check MIB list: /opt/OV/bin/nnmloadmib.ovpl -list | grep -i didactum # SNMP walk from the NNMi server: /opt/OV/bin/nnmsnmpwalk.ovpl -u admin -p adminpasswort \ -v 2c -c public 192.168.1.100 .1.3.6.1.4.1.3854 # SNMP GET for a single OID: /opt/OV/bin/nnmsnmpget.ovpl -u admin -p adminpasswort \ -v 2c -c public 192.168.1.100 .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 # List Custom Poller Collections: /opt/OV/bin/nnmcustompollerconfig.ovpl \ -u admin -p adminpasswort -action listCollections # Start discovery manually: /opt/OV/bin/nnmdiscovery.ovpl -u admin -p adminpasswort # Send test trap to NNMi: snmptrap -v2c -c public 192.168.1.88 '' \ .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 (firewalld): sudo firewall-cmd --list-ports # Allow ports: sudo firewall-cmd --permanent --add-port=162/udp sudo firewall-cmd --reload
Appendix: NNMi configuration quick reference
| Task | Navigation path in NNMi |
|---|---|
| Add discovery seed | Configuration → Discovery → Seeds → New |
| Auto-discovery rule | Configuration → Discovery → Auto-Discovery Rules → New |
| SNMP community string | Configuration → Communication Configuration → SNMP Community Strings |
| Create device profile | Configuration → Device Profiles → New |
| Create node group | Configuration → Node Groups → New |
| Custom Poller Collection | Configuration → Custom Poller → Custom Poller Collections → New |
| Show Custom Polled Instances | Inventory → Custom Polled Instances |
| Incident Browser | Incident Browsing → Open Incidents |
| SNMP Trap Incident Config | Configuration → Incidents → SNMP Trap Incidents → New |
| Incident Actions (email) | Configuration → Incidents → Incident Actions → New |
| MIB Browser | Select node → Actions → MIB Information → MIB Browser |
| Force Configuration Poll | Select node → Actions → Polling → Configuration Poll |
| Node Group Map | View → Node Group Maps → Didactum Rack Monitoring |
| Configure SMTP | Configuration → Server Configuration → SMTP |
| Incident Acknowledgement | Select incident → Actions → Acknowledge |
For firmware-specific OIDs and supported sensor types, always consult the current Didactum device documentation. NNMi version-specific details should be taken from the HPE/Micro Focus/OpenText NNMi administrator documentation.