Didactum Monitoring & CA Nimsoft Monitor Integration

Complete step-by-step guide for integrating Didactum Monitoring devices and sensors into CA Nimsoft Monitor (CA UIM) via SNMP – including Nimsoft Probe configuration (snmpcollector / sngtw), MIB import into the MIB Browser, complete OID reference for all sensor types (Temperature, Leakage, Humidity, Door Contact, Smoke), alarm configuration as well as SNMP Trap processing via the sngtw Probe.

Architecture Note: CA Nimsoft Monitor (also known as CA UIM – Unified Infrastructure Management) communicates with monitored devices via specialized Probes. For the Didactum device, two Probes are used: snmpcollector for active SNMP polling of sensor measurement values and sngtw (SNMP Gateway) for receiving SNMP Traps. Both Probes run on a Nimsoft Robot in the same network segment as the Didactum device.

Software: CA Nimsoft Monitor / CA UIM 9.x or newer
Probes: snmpcollector (Polling), sngtw (Trap reception), net_connect (Reachability)
Protocol: SNMP v1 / v2c / v3
Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke

1. Prerequisites & System Overview

CA Nimsoft / CA UIM Infrastructure

Component	Requirement / Details
CA UIM Version	9.0 or newer (recommended: 20.x / current release)
Nimsoft Robot	Robot in the same network segment as the Didactum device; reachable via UDP 161 (SNMP polling) and UDP 162 (Trap reception)
Probe snmpcollector	Version 3.x or newer; installed and active on the Robot
Probe sngtw	For SNMP Trap reception; UDP Port 162 inbound opened on the Robot
Probe net_connect	For reachability monitoring (Ping / ICMP) of the Didactum device
CA UIM MIB Browser	Integrated in Infrastructure Manager or UMP (Unified Management Portal)
Network	UDP 161 outbound from the Robot to the Didactum device; UDP 162 inbound from the Didactum device to the Robot

Didactum Device

Requirement	Details
Model	Monitoring System 100T, 300T, 500T or 550T
SNMP	SNMP enabled (v2c recommended)
Community String	Individual Community String (not „public")
Trap Destination	IP address of the Nimsoft Robot (not the UIM Server)
MIB File	Downloadable under System Settings → SNMP

Enterprise OIDs by Firmware Generation

Device / Firmware	Enterprise OID (Base)
Older models / older firmware	.1.3.6.1.4.1.46501
Newer models / current firmware	.1.3.6.1.4.1.39052

Note: Determine which Enterprise OID your device uses with:
snmpwalk -v 2c -c public 192.168.1.50 .1.3.6.1.2.1.1.2.0

2. Enable SNMP on the Didactum Device

Step 1 – Open Web Interface

192.168.1.50 (adjust Didactum device IP)

Step 2 – Access SNMP Settings

System Settings → SNMP

Step 3 – Enter the following values

Field in Didactum Web Interface	Recommended Value
Enable SNMP	Enabled
SNMP Version	v2c (recommended)
Community String (Read)	didactum_nimsoft (do not use „public"!)
SNMP Port	161
Trap Destination	IP address of the Nimsoft Robot (not the UIM Server!)
Trap Community	didactum_trap
Trap Port	162

Step 4 – Download MIB File

System Settings → SNMP → "Download MIB File"
File is saved as didactum.mib.
This file will be imported into Nimsoft in step 3.

Save settings. The device will now send Traps to the Nimsoft Robot.

3. Import MIB File into CA Nimsoft

The MIB file is imported into the Nimsoft Infrastructure Manager (IM) so that OID numbers can be resolved into readable names – both in snmpcollector and for Trap events via sngtw.

Step 1 – Determine the Robot's MIB Directory

Standard path on Windows:
  C:\Program Files (x86)\Nimsoft\probes\network\snmpcollector\mibs\
Standard path on Linux:
  /opt/nimsoft/probes/network/snmpcollector/mibs/
MIB directory for sngtw (Trap reception):
  C:\Program Files (x86)\Nimsoft\probes\network\sngtw\mibs\ (Windows)
  /opt/nimsoft/probes/network/sngtw/mibs/ (Linux)

Step 2 – Copy MIB File

Copy didactum.mib to both MIB directories:
  → snmpcollector\mibs\didactum.mib
  → sngtw\mibs\didactum.mib

Step 3 – Load MIB in Infrastructure Manager

CA UIM Infrastructure Manager → Probes → snmpcollector
  → Right-click → Configure
  → Tab "MIBs"
  → "Load MIB" → select didactum.mib
  → Confirm import
Same procedure for sngtw:
  CA UIM Infrastructure Manager → Probes → sngtw
  → Configure → MIBs → Load MIB → didactum.mib

Ready MIB Import Configuration (DIDACTUM-MIB.txt)

If no MIB file is available from the device, save the following minimal MIB structure as DIDACTUM-MIB.txt, copy it to the MIB directories of both Probes and import as described above:

-- ================================================================
-- DIDACTUM-MIB – Minimal MIB for Nimsoft snmpcollector / sngtw
-- File: DIDACTUM-MIB.txt
-- For older devices: enterprises.46501
-- For newer devices: enterprises.39052 (adjust OID)
-- ================================================================
DIDACTUM-MIB DEFINITIONS ::= BEGIN
IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32, enterprises
        FROM SNMPv2-SMI
    NOTIFICATION-TYPE
        FROM SNMPv2-SMI;
didactum MODULE-IDENTITY
    LAST-UPDATED "202401010000Z"
    ORGANIZATION "Didactum Security GmbH"
    CONTACT-INFO "support@didactum-security.com"
    DESCRIPTION "Didactum Monitoring System MIB"
    ::= { enterprises 46501 }
sensorTable OBJECT-TYPE
    SYNTAX SEQUENCE OF SensorEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION "Table of all connected sensors"
    ::= { didactum 5 1 1 }
sensorEntry OBJECT-TYPE
    SYNTAX SensorEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION "Single sensor entry"
    INDEX { sensorIndex }
    ::= { sensorTable 1 }
SensorEntry ::= SEQUENCE {
    sensorIndex Integer32,
    sensorID Integer32,
    sensorType Integer32,
    sensorName OCTET STRING,
    sensorStatus Integer32,
    sensorValue Integer32
}
sensorIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Index" ::= { sensorEntry 1 }
sensorID OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Sensor ID" ::= { sensorEntry 2 }
sensorType OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Sensor Type" ::= { sensorEntry 3 }
sensorName OBJECT-TYPE SYNTAX OCTET STRING MAX-ACCESS read-only STATUS current
    DESCRIPTION "Sensor Name" ::= { sensorEntry 5 }
sensorStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "0=OK 1=Alarm 2=No Signal" ::= { sensorEntry 6 }
sensorValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current
    DESCRIPTION "Measured value (Temperature: x10)" ::= { sensorEntry 7 }
didactumAlarmTrap NOTIFICATION-TYPE
    OBJECTS { sensorName, sensorStatus, sensorValue }
    STATUS current
    DESCRIPTION "Alarm Trap on sensor status change"
    ::= { didactum 1 1 }
END

4. Configure snmpcollector Probe

The snmpcollector Probe handles active SNMP polling of the Didactum sensor values at configurable intervals and stores the measurement data as QoS metrics (Quality of Service) in the Nimsoft database.

Step 1 – Open snmpcollector

CA UIM Infrastructure Manager
  → Robot (in the same network segment as the Didactum device)
  → Probes → network → snmpcollector
  → Double-click → Probe configuration opens

Step 2 – Create New SNMP Device

snmpcollector → Tab "Devices" → "New Device"
  Device Name: Didactum-Monitor-01
  IP Address: 192.168.1.50
  SNMP Version: v2c
  Community String: didactum_nimsoft
  Port: 161
  Timeout: 5 seconds
  Retries: 3
  Description: Didactum Monitoring System – Server Room

Step 3 – Test SNMP Connection

snmpcollector → Devices → Didactum-Monitor-01
  → "Test Connection" / "SNMP Walk"
  → OID: .1.3.6.1.4.1.46501.5.1.1
  → Result: List of all sensor OIDs and raw values appears

Step 4 – Create Checkpoints (OID Queries)

Important – Temperature Thresholds: The Didactum device delivers temperature values as raw value × 10. 25.5 °C = OID value 255. All temperature thresholds in snmpcollector must also be specified × 10!

snmpcollector → Devices → Didactum-Monitor-01 → "Add Checkpoint"
-- ================================================================
-- Checkpoint 1: Temperature Sensor (digital, Sensor ID 101001)
-- ================================================================
  Checkpoint Name: Temperature_Sensor_01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
  Description: Temperature Sensor 01 (raw value x10; 235 = 23.5 °C)
  Data Type: Integer / Gauge
  Poll Interval: 60 seconds
  QoS: Enabled
  QoS Name: temperature_sensor_01
  QoS Unit: raw_x10
  Alarm active: Yes
  Warning High: 280 (= 28.0 °C)
  Critical High: 350 (= 35.0 °C)
  Alarm Message: Didactum Temperature Alarm: Value ${value} (= ${value/10} °C)
-- ================================================================
-- Checkpoint 2: Temperature Status (0=OK / 1=Alarm / 2=No Signal)
-- ================================================================
  Checkpoint Name: Temperature_Status_01
  OID: .1.3.6.1.4.1.46501.5.1.1.6.101001
  Data Type: Integer
  Poll Interval: 60 seconds
  Warning High: 1
  Critical High: 2
  Alarm Message: Didactum Temp Sensor Status: ${value} (0=OK, 1=Alarm, 2=No Signal)
-- ================================================================
-- Checkpoint 3: Water Sensor / Leakage (Sensor ID 107001)
-- ================================================================
  Checkpoint Name: Leakage_Sensor_01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.107001
  Data Type: Integer
  Poll Interval: 30 seconds
  Critical High: 1 (0 = dry / OK, 1 = water detected / CRITICAL)
  Alarm Message: CRITICAL: Didactum Leakage Alarm – Water detected!
-- ================================================================
-- Checkpoint 4: Humidity (Sensor ID 102001)
-- ================================================================
  Checkpoint Name: Humidity_Sensor_01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.102001
  Data Type: Integer / Gauge
  Poll Interval: 60 seconds
  QoS: Enabled
  QoS Unit: %
  Warning High: 80
  Critical High: 90
  Alarm Message: Didactum Humidity Alarm: ${value} %
-- ================================================================
-- Checkpoint 5: Door Contact (Sensor ID 104001)
-- ================================================================
  Checkpoint Name: DoorContact_01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.104001
  Data Type: Integer
  Poll Interval: 30 seconds
  Warning High: 1 (0 = closed / OK, 1 = open / Warning)
  Alarm Message: Didactum Door Contact: Door opened!
-- ================================================================
-- Checkpoint 6: Smoke Detector (Sensor ID 106001)
-- ================================================================
  Checkpoint Name: SmokeDetector_01
  OID: .1.3.6.1.4.1.46501.5.1.1.7.106001
  Data Type: Integer
  Poll Interval: 30 seconds
  Critical High: 1 (0 = no smoke / OK, 1 = Alarm / CRITICAL)
  Alarm Message: CRITICAL: Didactum Smoke Detector Alarm!

Step 5 – Save Configuration and Restart Probe

snmpcollector → File → Save Configuration
  → Restart Probe: Right-click on snmpcollector → Restart Probe
  → First QoS measurement values appear in the database after approx. 60 seconds

5. Configure sngtw Probe for SNMP Trap Reception

The sngtw Probe (SNMP Gateway) receives incoming SNMP Traps from the Didactum device and converts them into Nimsoft alarms. This creates an immediate alarm in UIM on a sensor alarm – without waiting for the next polling cycle of the snmpcollector.

Step 1 – Open sngtw

CA UIM Infrastructure Manager
  → Robot → Probes → network → sngtw
  → Double-click → Probe configuration opens

Step 2 – Enable Trap Reception

sngtw → Tab "Setup"
  Listen Port: 162
  Community: didactum_trap
  SNMP Version: v2c
  MIB Directory: (path to the mibs folder, see section 3)
  → Enable "Enable Trap Receiver"
  → Save

Step 3 – Configure Trap-to-Alarm Mapping

sngtw → Tab "Trap Definitions" → "New Trap Definition"
  Trap OID: .1.3.6.1.4.1.46501.1.1
                    (didactumAlarmTrap – general alarm trap)
  Alarm Message: Didactum Alarm: ${sensorName} – Status ${sensorStatus}
  Severity: Critical
  Subsystem: /Environmental/Didactum
  Source: ${trapSourceIP}
  → Save
  Second Trap Definition for status return (optional):
  Trap OID: .1.3.6.1.4.1.46501.1.2
  Alarm Message: Didactum: ${sensorName} – State back to normal
  Severity: Clear / Informational
  → Save

Step 4 – Allow Trap Source (Didactum Device)

sngtw → Tab "Allowed Sources"
  → "Add Source"
  → IP address of the Didactum device: 192.168.1.50
  → Save
  → Restart Probe

6. net_connect Probe for Reachability Monitoring

In addition to SNMP monitoring, monitoring the IP reachability of the Didactum device via the net_connect Probe is recommended. This immediately detects a device or network connection failure.

CA UIM Infrastructure Manager
  → Robot → Probes → network → net_connect
  → Configure → "New Profile"
  Profile Name: Didactum-Monitor-01-Ping
  IP Address: 192.168.1.50
  Check Type: Ping (ICMP)
  Interval: 60 seconds
  Timeout: 5 seconds
  Retries: 3
  Alarm on: No response after 3 attempts
  Alarm Message: Didactum Monitoring System 192.168.1.50 not reachable!
  Severity: Critical
  → Save

7. Configure Alarms in CA UIM

Alarm Configuration in snmpcollector (Repeat / Escalation)

snmpcollector → Devices → Didactum-Monitor-01 → Checkpoint → Alarm Settings
  Alarm Repeat: Every 15 minutes (while alarm is active)
  Auto-Clear: Yes (alarm is automatically cleared when value returns to OK range)
  Suppression: Enable when device is unreachable (net_connect alarm active)
  Alarm Subsystem: /Environmental/Didactum/Serverroom
  Alarm Key: didactum_${devicename}_${checkpointname}
                      (unique key for alarm deduplication)

Alarm Policy in UMP (Unified Management Portal)

CA UMP → Administration → Alarm Policies → New Policy
  Policy Name: Didactum Sensor Alarms
  Filter: Subsystem contains "/Environmental/Didactum"
  Critical Action: Email to admin@yourdomain.com
  Warning Action: Email to monitoring@yourdomain.com
  Clear Action: Email "Alarm cleared" to admin@yourdomain.com
  Email Subject: [Nimsoft] Didactum Alarm: ${alarm.hostname} – ${alarm.message}
  Email Body:
    Timestamp: ${alarm.time}
    Device: ${alarm.hostname} (${alarm.source})
    Sensor: ${alarm.supp_key}
    Severity: ${alarm.severity}
    Message: ${alarm.message}
    Raw Value: ${alarm.value}
    Subsystem: ${alarm.subsystem}

8. Set Up QoS Metrics and Dashboards in UMP

Step 1 – Check QoS Data

CA UMP → Performance → QoS Explorer
  Search for: Robot = "didactum-robot-01"
              Probe = "snmpcollector"
              QoS Name = "temperature_sensor_01"
  → Time series graph appears with raw values (÷10 = degrees Celsius)
  → Same procedure for all other QoS names (humidity_sensor_01 etc.)

Step 2 – Create Dashboard in UMP

CA UMP → Dashboards → New Dashboard
  Dashboard Name: Server Room Monitoring Didactum
  Widget 1: Line Chart – Temperature Trend
    QoS: temperature_sensor_01
    Robot: didactum-robot-01
    Time Range: Last 24 hours
    Y-Axis: Raw value (÷10 = °C)
  Widget 2: Current Value – Leakage Status
    QoS: leakage_sensor_01
    Threshold: 0 = green, ≥1 = red
  Widget 3: Gauge – Humidity
    QoS: humidity_sensor_01
    Min / Max: 0 / 100 %
    Warning: 80 %
    Critical: 90 %
  Widget 4: Alarm List
    Filter: Subsystem = /Environmental/Didactum
    Shows all active Didactum alarms in real time
  Widget 5: Availability – Reachability
    Probe: net_connect
    Profile: Didactum-Monitor-01-Ping

9. SNMP OID Reference for Didactum Sensors

All Didactum OIDs start with .1.3.6.1.4.1.46501 (older firmware) or .1.3.6.1.4.1.39052 (newer models). The sensor ID is appended at the end.

OID fields per sensor

Field	OID Suffix	Meaning	Example (Sensor 101001)
Sensor Index	.5.1.1.1.SENSOR_ID	Internal index	.1.3.6.1.4.1.46501.5.1.1.1.101001
Sensor ID	.5.1.1.2.SENSOR_ID	Numeric sensor ID	.1.3.6.1.4.1.46501.5.1.1.2.101001
Sensor Type	.5.1.1.3.SENSOR_ID	Type identifier	.1.3.6.1.4.1.46501.5.1.1.3.101001
Sensor Name	.5.1.1.5.SENSOR_ID	Designation (String)	.1.3.6.1.4.1.46501.5.1.1.5.101001
Sensor Status	.5.1.1.6.SENSOR_ID	0=OK, 1=Alarm, 2=No Signal	.1.3.6.1.4.1.46501.5.1.1.6.101001
Sensor Measured Value	.5.1.1.7.SENSOR_ID	Current measured value	.1.3.6.1.4.1.46501.5.1.1.7.101001

Sensor types with complete OIDs and Nimsoft thresholds

Sensor Type	Sensor ID	OID Measured Value	OID Status	Nimsoft Threshold
Temperature Sensor (digital)	101001	.1.3.6.1.4.1.46501.5.1.1.7.101001	.1.3.6.1.4.1.46501.5.1.1.6.101001	Warning High 280 / Critical High 350 (raw value × 10)
Temperature Sensor (analog)	201001	.1.3.6.1.4.1.39052.5.2.1.7.201001	.1.3.6.1.4.1.39052.5.2.1.6.201001	Warning High 280 / Critical High 350 (× 10)
Water Sensor / Leakage	107001	.1.3.6.1.4.1.46501.5.1.1.7.107001	.1.3.6.1.4.1.46501.5.1.1.6.107001	Critical High ≥ 1 (0 = dry / OK)
Humidity	102001	.1.3.6.1.4.1.46501.5.1.1.7.102001	.1.3.6.1.4.1.46501.5.1.1.6.102001	Warning High 80 / Critical High 90 (direct %)
Dry Contact	101003	.1.3.6.1.4.1.39052.5.1.1.7.101003	.1.3.6.1.4.1.39052.5.1.1.6.101003	Warning High ≥ 1 (0 = open / inactive)
Door Contact	104001	.1.3.6.1.4.1.46501.5.1.1.7.104001	.1.3.6.1.4.1.46501.5.1.1.6.104001	Warning High ≥ 1 (0 = closed / OK)
Smoke Detector	106001	.1.3.6.1.4.1.46501.5.1.1.7.106001	.1.3.6.1.4.1.46501.5.1.1.6.106001	Critical High ≥ 1 (0 = no smoke / OK)

Determine Sensor ID: In the Didactum Web Interface under System Tree → Select Sensor → Details. The displayed sensor ID is appended as the last element to the OID. For multiple sensors of the same type, the last digit increases: 101001, 101002, 101003 etc.

Temperature Thresholds: Didactum delivers temperature as raw value × 10. 28.0 °C = OID value 280. Enter snmpcollector thresholds (Warning/Critical High) also as × 10 value.

10. Test SNMP Connection

Test via Command Line (from the Nimsoft Robot)

# snmpwalk – list all sensor values
snmpwalk -v 2c -c didactum_nimsoft 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1
# snmpget – query temperature value (raw value ÷ 10 = °C)
snmpget -v 2c -c didactum_nimsoft 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.7.101001
# Expected output: INTEGER: 235 (= 23.5 °C)
# snmpget – query leakage status
snmpget -v 2c -c didactum_nimsoft 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.7.107001
# Expected output (dry): INTEGER: 0
# snmpget – query sensor status
snmpget -v 2c -c didactum_nimsoft 192.168.1.50 \
    .1.3.6.1.4.1.46501.5.1.1.6.101001
# Expected output (OK): INTEGER: 0

Test via snmpcollector – SNMP Walk

snmpcollector → Devices → Didactum-Monitor-01
  → "Test Connection" → OK appears
  → "SNMP Walk" → enter OID .1.3.6.1.4.1.46501.5.1.1
  → All sensor OIDs and raw values are listed

Test Trap Reception

Trigger a test trap in the Didactum Web Interface:
  System Settings → SNMP → "Send Test Trap"
Check in Nimsoft Infrastructure Manager:
  → Alarm Console → New alarm with Source 192.168.1.50 appears
  → Subsystem: /Environmental/Didactum
  → Message: Didactum Alarm: …

11. Troubleshooting

Problem	Cause & Solution
snmpcollector shows „Connection failed"	SNMP not enabled on Didactum device; Community String wrong; UDP Port 161 blocked by firewall between Robot and device → check firewall rule, test snmpwalk directly from the Robot
MIB import fails (snmpcollector / sngtw)	Dependent MIBs missing (SNMPv2-SMI, RFC1213-MIB) → copy base MIBs to MIB directory first and import; alternatively use DIDACTUM-MIB.txt from section 3
OID returns „No Such Object"	Wrong Enterprise OID (46501 vs. 39052) → check sysObjectID with snmpwalk -v 2c -c COMMUNITY IP .1.3.6.1.2.1.1.2.0
Temperature value appears 10× too high	Not an error – Didactum delivers raw value × 10. Set thresholds as × 10 value (28 °C = Warning High 280). Indicate ÷10 in dashboard label.
SNMP Traps do not arrive in sngtw	Trap destination IP in Didactum Web Interface set to IP of the Robot (not UIM Server)? UDP Port 162 blocked by firewall on Robot? Trap Community matches? → check sngtw log: sngtw.log in Nimsoft log directory
Trap received but no alarm generated	Trap definition missing in sngtw or Trap OID does not match → verify Trap OID with snmpcollector SNMP Walk; check Allowed Sources in sngtw
QoS data does not appear in UMP	QoS not enabled in Checkpoint configuration → snmpcollector → Checkpoint → enable QoS; Data Engine Probe running? → check Infrastructure Manager
No email on alarm	SMTP configured in CA UIM Administration? Alarm Policy assigned to correct subsystem? → UMP → Administration → Alarm Policies check
Sensor value always remains 0 (Leakage / Door Contact)	Normal in non-critical state (0 = OK). Test sensor by briefly triggering it; verify OID with snmpget directly from the Robot.
Robot cannot reach Didactum device	Robot not in the same network segment; routing issue → test net_connect Ping; if necessary install a second Robot in the Didactum device's segment

12. Final Checklist

Didactum Device

SNMP enabled (v2c)
Community String set (not „public"): didactum_nimsoft
Trap destination set to IP of the Nimsoft Robot (not UIM Server!)
Trap Community set: didactum_trap
MIB file downloaded (didactum.mib)
snmpwalk from Nimsoft Robot successful

CA Nimsoft / CA UIM

DIDACTUM-MIB copied to MIB directory of snmpcollector and sngtw
MIB imported in snmpcollector Probe
MIB imported in sngtw Probe
Didactum device created in snmpcollector as Device (IP, Community, Version)
Connection test in snmpcollector successful
All 6 Checkpoints (OIDs) created: Temperature, Temp Status, Leakage, Humidity, Door Contact, Smoke
Temperature thresholds set as raw value × 10 (Warning 280 / Critical 350)
QoS enabled for temperature and humidity
sngtw: Trap Receiver enabled on Port 162
sngtw: Trap definitions created for Didactum alarm traps
sngtw: Didactum IP entered as Allowed Source
net_connect: Ping profile created for Didactum device
Alarm Policy configured in UMP and email delivery enabled

Tests & Verification

snmpcollector: First QoS measurement values present after one polling interval
UMP QoS Explorer: Temperature and humidity graphs visible
Trap test triggered via Didactum Web Interface → Alarm appears in Alarm Console
Email received on test alarm
UMP Dashboard "Server Room Monitoring" configured with all widgets
net_connect: Didactum device reported as „up"

Didactum Monitoring & CA Nimsoft Monitor Integration

1. Prerequisites & System Overview

CA Nimsoft / CA UIM Infrastructure

Didactum Device

Enterprise OIDs by Firmware Generation

2. Enable SNMP on the Didactum Device

Step 1 – Open Web Interface

Step 2 – Access SNMP Settings

Step 3 – Enter the following values

Step 4 – Download MIB File

3. Import MIB File into CA Nimsoft

Step 1 – Determine the Robot's MIB Directory

Step 2 – Copy MIB File

Step 3 – Load MIB in Infrastructure Manager

Ready MIB Import Configuration (DIDACTUM-MIB.txt)

4. Configure snmpcollector Probe

Step 1 – Open snmpcollector

Step 2 – Create New SNMP Device

Step 3 – Test SNMP Connection

Step 4 – Create Checkpoints (OID Queries)

Step 5 – Save Configuration and Restart Probe

5. Configure sngtw Probe for SNMP Trap Reception

Step 1 – Open sngtw

Step 2 – Enable Trap Reception

Step 3 – Configure Trap-to-Alarm Mapping

Step 4 – Allow Trap Source (Didactum Device)

6. net_connect Probe for Reachability Monitoring

7. Configure Alarms in CA UIM

Alarm Configuration in snmpcollector (Repeat / Escalation)

Alarm Policy in UMP (Unified Management Portal)

8. Set Up QoS Metrics and Dashboards in UMP

Step 1 – Check QoS Data

Step 2 – Create Dashboard in UMP

9. SNMP OID Reference for Didactum Sensors

OID fields per sensor

Sensor types with complete OIDs and Nimsoft thresholds

10. Test SNMP Connection

Test via Command Line (from the Nimsoft Robot)

Test via snmpcollector – SNMP Walk

Test Trap Reception

11. Troubleshooting

12. Final Checklist

Didactum Device

CA Nimsoft / CA UIM

Tests & Verification

Related Links

Powered by

Hint

This website uses cookies