Didactum Monitoring & NetCrunch Integration

Complete step-by-step guide for integrating Didactum Monitoring devices and sensors into NetCrunch (AdRem Software) via SNMP – including device discovery, MIB compiler, SNMP Views (YAML), performance counter alarms, SNMP Trap integration and email notification.

NetCrunch Special Feature: NetCrunch includes over 8700 precompiled MIBs with a MIB compiler and extensive alarm functions. The unique SNMP Views feature enables the creation of custom views for any SNMP devices via YAML configuration. For Didactum devices, a Custom SNMP View is created that summarizes all sensors in one overview.

Software: NetCrunch 10.x / 12.x (AdRem Software)
Minimum Edition: NetCrunch PRO (for full SNMP functionality)
Protocol: SNMP v1 / v2c / v3
Devices: Didactum Monitoring System 100T / 300T / 500T / 5T
Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke

1. Prerequisites & System Overview

NetCrunch Server

NetCrunch Server installed (Windows Server 2016/2019/2022)
NetCrunch Console (Desktop App) or Web Console accessible
UDP Port 161 outbound for SNMP Polling
UDP Port 162 inbound for SNMP Traps
Network access to the Didactum device

Didactum Device

Monitoring System 100T, 300T, 500T or 550T
SNMP enabled (v2c recommended)
Device reachable via ICMP from the NetCrunch Server
MIB file available in the Web Interface

Architecture & Data Flow

[NetCrunch Console / Web Console]
       |
       v
[NetCrunch Server] --SNMP Polling UDP 161--> [Didactum 192.168.1.50]
       ^ <--SNMP Traps UDP 162---
       |
[Network Atlas (Map)]
[Monitoring Packs]
[Alert Scripts (Email)]

2. Enable SNMP on the Didactum Device

Step 1 – Open Web Interface

Open in browser: 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	Value
Enable SNMP	Enabled
SNMP Version	v2c (recommended)
Community String	didactum_netcrunch (do not use „public"!)
SNMP Port	161
Trap Receiver IP	192.168.1.10 (IP of NetCrunch Server)
Trap Port	162
Trap Version	v2c

SNMPv3 Settings (optional)

Field	Value
Security Name	netcrunch_user
Auth Protocol	SHA
Auth Password	min. 8 characters
Priv Protocol	AES
Priv Password	min. 8 characters
Security Level	authPriv

3. Import MIB File into NetCrunch MIB Compiler

NetCrunch offers the functionality to import MIB files into a usable database. A MIB provides two basic elements: an OID-to-metric mapping (for variables/counters) and an OID-to-event description mapping (for traps).

Step 1 – Download MIB from Didactum Web Interface

System Settings → SNMP → "Download MIB File" → didactum.mib

Step 2 – Import MIB into NetCrunch

NetCrunch Console → Menu: Tools → MIB Browser / MIB Compiler
→ Click "Import MIB" (or drag & drop file)
→ Select file didactum.mib → Open
→ NetCrunch compiles the MIB automatically
→ Success message: "MIB compiled successfully"

Step 3 – Check MIB in MIB Browser

MIB Browser → Navigation Panel:
  enterprises → 46501 → Sensor Table → 5 → 1 → 1
    → 7 (sensorValue) → Measurement values of all sensors
    → 6 (sensorStatus) → Status values of all sensors
    → 5 (sensorName) → Sensor names

Click on an OID entry → right side shows OID description and current value (if device is configured).

Step 4 – Query single OID value in MIB Browser

MIB Browser → Enter IP address: 192.168.1.50
→ Community: didactum_netcrunch
→ SNMP Version: v2c
→ OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
→ Click "Get" → Result: e.g. 235 (= 23.5 °C; raw value ÷ 10)

4. Add Didactum Device to NetCrunch (Discovery)

Step 1 – Store SNMP credentials before discovery

NetCrunch Console → Settings → SNMP Settings
→ Click "Add Community"
  Community String: didactum_netcrunch
  SNMP Version: SNMPv2c
  Port: 161
→ Set IP Range filter:
  IP Range: 192.168.1.50 – 192.168.1.55
→ Save

Step 2 – Start Network Discovery

NetCrunch Console → Network Atlas
→ Right-click on network segment → "Discover Network"
  IP Range: 192.168.1.50
  Or: enter single IP
→ Click "Start Discovery"

Step 3 – Add device manually (alternative)

Network Atlas → Right-click on Map → "Add Node"
→ "Add by IP address"
  IP Address: 192.168.1.50
  Node name: Didactum-Monitor-01
→ SNMP Tab:
  SNMP Version: v2c
  Community: didactum_netcrunch
→ Click OK

Step 4 – Configure Node Properties

Right-click on Didactum-Monitor-01 → "Node Settings"
→ Tab "General":
  Name: Didactum Monitoring System 01
  Comment: Server room monitoring, IP 192.168.1.50
→ Tab "SNMP":
  Enable SNMP: Yes
  Version: SNMPv2c
  Community: didactum_netcrunch
  Port: 161
  Timeout: 5 seconds
  Retries: 3
→ Click OK

Step 5 – Test SNMP connection

Right-click on Didactum-Monitor-01 → "Test SNMP Connection"
→ Green success message appears: "SNMP connection OK"

5. Create Custom SNMP View for Didactum (YAML)

The YAML-based customization feature enables the creation of Custom Views perfectly tailored to specific monitoring requirements, offering both clarity and detailed monitoring.

Step 1 – Create Custom SNMP View file

Save as didactum-view.yaml:

# ================================================================
# NetCrunch Custom SNMP View – Didactum Monitoring System
# Filename: didactum-view.yaml
# Import: NetCrunch Console → Tools → SNMP Views → Import
#
# Enterprise OID (older devices): .1.3.6.1.4.1.46501
# Enterprise OID (newer devices): .1.3.6.1.4.1.39052
#
# IMPORTANT – Temperature thresholds:
# Didactum delivers temperature as raw value x10.
# 25.5 °C = OID value 255.
# All numeric thresholds must therefore be specified x10.
# ================================================================
name: Didactum Monitoring System
sysObjectID:
  - 1.3.6.1.4.1.46501
  - 1.3.6.1.4.1.39052
sections:
  - name: Temperature Sensors
    icon: thermometer
    rows:
      - name: Temperature Sensor 01
        oid: 1.3.6.1.4.1.46501.5.1.1.7.101001
        type: integer
        description: "Room temperature (raw value; ÷10 = degrees Celsius)"
        unit: "x0.1 °C"
        chart: line
        thresholds:
          warning_high: 280
          critical_high: 350
          warning_low: 50
          critical_low: 20
      - name: Temperature Status Sensor 01
        oid: 1.3.6.1.4.1.46501.5.1.1.6.101001
        type: integer
        description: "0=OK, 1=Alarm, 2=No Signal"
        values:
          0: OK
          1: Alarm
          2: No Signal
        thresholds:
          critical_high: 1
      - name: Temp Sensor Name
        oid: 1.3.6.1.4.1.46501.5.1.1.5.101001
        type: string
        description: "Configured name of the temperature sensor"
  - name: Leakage Sensors
    icon: water
    rows:
      - name: Leakage Sensor 01
        oid: 1.3.6.1.4.1.46501.5.1.1.7.107001
        type: integer
        description: "Water sensor: 0=dry, 1=water detected"
        values:
          0: Dry (OK)
          1: WATER DETECTED!
        thresholds:
          critical_high: 1
      - name: Leakage Status Sensor 01
        oid: 1.3.6.1.4.1.46501.5.1.1.6.107001
        type: integer
        description: "0=OK, 1=Alarm, 2=No Signal"
        thresholds:
          critical_high: 1
  - name: Humidity
    icon: humidity
    rows:
      - name: Humidity Sensor 01
        oid: 1.3.6.1.4.1.46501.5.1.1.7.102001
        type: integer
        description: "Relative humidity in percent"
        unit: "%"
        chart: line
        thresholds:
          warning_high: 80
          critical_high: 90
          warning_low: 20
          critical_low: 10
  - name: Contacts and Security
    icon: security
    rows:
      - name: Door Contact 01
        oid: 1.3.6.1.4.1.46501.5.1.1.7.104001
        type: integer
        description: "Door contact: 0=closed, 1=open"
        values:
          0: Closed (OK)
          1: OPEN
        thresholds:
          warning_high: 1
      - name: Smoke Detector 01
        oid: 1.3.6.1.4.1.46501.5.1.1.7.106001
        type: integer
        description: "Smoke detector: 0=no smoke, 1=alarm"
        values:
          0: No Smoke (OK)
          1: SMOKE DETECTED!
        thresholds:
          critical_high: 1

Step 2 – Import Custom View into NetCrunch

NetCrunch Console → Tools → SNMP Views → "Import View"
→ Select file didactum-view.yaml → Open
→ View appears in the list as "Didactum Monitoring System"

Step 3 – Assign View to the device

Right-click on Didactum-Monitor-01 → "Node Settings"
→ Tab "SNMP Views"
→ "Add" → Select "Didactum Monitoring System" → OK

The Didactum sensor view now appears in the node's detail view with all configured sensor values.

6. Configure Performance Counter Alarms

Alarms for numeric values can be set quickly by using one of the many threshold types available in NetCrunch. Click on "Custom" and add a "Performance Counter Alarm". Then an SNMP variable can be selected as a performance counter – via the MIB library or by direct OID entry.

Navigation

Right-click on Didactum-Monitor-01 → "Node Settings"
→ Tab "Monitoring" → "Alerts" → "Add Alert" → "Custom"
→ Select "Performance Counter Alarm"

Performance Counter Alarm: Temperature Sensor

Field	Value
Alert Name	Didactum Temperature Warning
Counter Type	SNMP
OID	.1.3.6.1.4.1.46501.5.1.1.7.101001
Threshold Type	Over threshold
Warning Threshold	280 (= 28.0 °C; raw value × 10)
Critical Threshold	350 (= 35.0 °C; raw value × 10)
Alert Message	Didactum Temperature: {VALUE} (raw value; ÷10=°C) exceeds threshold!

Create a second alarm for critical temperatures (same OID, higher threshold 350).

Performance Counter Alarm: Leakage Sensor

Field	Value
Alert Name	Didactum LEAKAGE ALARM
OID	.1.3.6.1.4.1.46501.5.1.1.7.107001
Threshold Type	Over threshold
Critical Threshold	0 (value > 0 = water detected)
Alert Message	LEAKAGE ALARM: Water detected at Didactum sensor! Value: {VALUE}
Severity	Critical

Performance Counter Alarm: Humidity

Field	Value
Alert Name	Didactum High Humidity
OID	.1.3.6.1.4.1.46501.5.1.1.7.102001
Warning Threshold	80
Critical Threshold	90

SNMP Variable Value Alarm (for text values and status)

Text values from the SNMP agent can be monitored by selecting the alert type "New Event for SNMP Variable Value".

Add Alert → Custom → "SNMP Variable Value Event"
  OID: .1.3.6.1.4.1.46501.5.1.1.6.101001
  Match Value: 1 (Alarm Status)
  Alert Msg: Temp Sensor Status = 1 (Alarm!)
  OID: .1.3.6.1.4.1.46501.5.1.1.7.104001
  Match Value: 1 (Door open)
  Alert Msg: Door Contact: Door opened!

7. Create Monitoring Pack for Didactum

A Monitoring Pack bundles all alarms and settings for Didactum devices and can be applied to multiple nodes simultaneously.

Step 1 – Create Monitoring Pack

NetCrunch Console → Settings → Monitoring Packs → "New Pack"
  Pack Name: Didactum Monitoring System
  Description: SNMP Monitoring for Didactum Environmental Sensors
  Icon: Select appropriate icon

Step 2 – Add Alarms to the Pack

In the new Monitoring Pack → "Add Alert" → select all previously created
Performance Counter Alarms:
  ✅ Didactum Temperature Warning
  ✅ Didactum Temperature Critical
  ✅ Didactum LEAKAGE ALARM
  ✅ Didactum High Humidity
  ✅ Didactum Door Contact ALARM
  ✅ Didactum Smoke Detector ALARM
→ Save

Step 3 – Add SNMP View to the Pack

Monitoring Pack → "SNMP Views" → Add → Select "Didactum Monitoring System"
→ Save

Step 4 – Apply Monitoring Pack to devices

Right-click on Didactum-Monitor-01 → "Assign Monitoring Pack"
→ Select "Didactum Monitoring System" → Apply
# For multiple devices at once:
Select multiple nodes (Ctrl+Click) → Right-click → "Assign Monitoring Pack"
→ "Didactum Monitoring System" → Apply to all selected

8. Receive & Process SNMP Traps

NetCrunch automatically receives SNMP Traps from the Didactum device on UDP port 162. Traps are decoded and displayed in the Event Log.

Step 1 – Check Trap Reception

NetCrunch Console → Settings → SNMP Traps Settings
→ "Enable SNMP Trap Receiver" must be activated
→ Port: 162 (default)
→ Supported versions: enable v1, v2c, v3

Step 2 – Configure Trap Community

SNMP Traps Settings → "Accepted Communities"
→ "Add" → Community String: didactum_netcrunch → OK

Step 3 – Create Trap Alarm for Didactum

Right-click on Didactum-Monitor-01 → "Node Settings"
→ Alerts → Add Alert → "SNMP Trap Alert"

Field	Value
Alert Name	Didactum SNMP Trap
Enterprise OID	.1.3.6.1.4.1.46501
Trap Source	192.168.1.50 (Didactum IP)
Severity	Critical
Alert Message	SNMP Trap received from Didactum: {TRAP_OID} – Value: {TRAP_VALUE}

Step 4 – Trap-specific rules for individual sensors

For more granular trap processing, create additional Trap Alarms with specific OIDs:

Alarm Name	Trap OID	Expected Value
Didactum Leakage Trap	.1.3.6.1.4.1.46501.5.1.1.7.107001	1
Didactum Temperature Trap	.1.3.6.1.4.1.46501.5.1.1.6.101001	1
Didactum Smoke Detector Trap	.1.3.6.1.4.1.46501.5.1.1.7.106001	1

Step 5 – Check incoming Traps

NetCrunch Console → Events → Event Log
→ Filter: Source = 192.168.1.50
→ Incoming traps appear after reception

9. Configure Email Notification

Step 1 – Configure SMTP Server

NetCrunch Console → Settings → Notification Methods → Email
→ Click "Configure Email"
  SMTP Server: mail.yourdomain.com
  SMTP Port: 587
  Use TLS: Yes
  From Address: netcrunch@yourdomain.com
  Auth Username: netcrunch@yourdomain.com
  Auth Password: YourPassword
→ "Send Test E-Mail" → Check inbox → Save

Step 2 – Create Alert Script (Recipient)

Settings → Alert Scripts → "New Script"
  Script Name: Didactum Email Admin
  Script Type: Send E-Mail
  To: admin@yourdomain.com
  Subject: [NetCrunch Didactum ALARM] ${NodeName}: ${AlertName} – ${Status}
  Message:
    Timestamp: ${DateTime}
    Device: ${NodeName} (${NodeAddress})
    Alert: ${AlertName}
    Status: ${Status}
    Message: ${Message}
    Details: ${Details}
→ Save

Step 3 – Assign Alert Script to Didactum Alarms

Right-click on Didactum-Monitor-01 → "Node Settings"
→ Tab "Alerts" → Select alert (e.g. "Didactum LEAKAGE ALARM")
→ "Actions" Tab → "Add Action"
→ "Run Script": Select "Didactum Email Admin"
→ Trigger: "When alert activates" and "When alert recovers"
→ OK → configure all other Didactum alarms the same way

Step 4 – Assign Email Action via Monitoring Pack (for all devices)

Settings → Monitoring Packs → "Didactum Monitoring System"
→ Select each alert → Actions → Add → "Didactum Email Admin"
→ Save Pack → Re-apply Pack to all Didactum devices

10. SNMP OID Reference

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	Meaning	Example
.1.x.SENSOR_ID	Sensor ID	.1.3.6.1.4.1.46501.5.1.1.1.101001
.5.x.SENSOR_ID	Sensor Name	.1.3.6.1.4.1.46501.5.1.1.5.101001
.6.x.SENSOR_ID	Status (0=OK, 1=Alarm, 2=No Signal)	.1.3.6.1.4.1.46501.5.1.1.6.101001
.7.x.SENSOR_ID	Measurement value (current)	.1.3.6.1.4.1.46501.5.1.1.7.101001

Sensor types with OIDs and NetCrunch thresholds

Sensor Type	Sensor ID	OID Measurement Value	OID Status	NetCrunch 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	Warn: 280 / Crit: 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	Warn: 280 / Crit: 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	Crit: > 0 (from 1 = water detected)
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	Warn: 80 / Crit: 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	Warn: > 0 (from 1 = active)
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	Warn: > 0 (from 1 = open)
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	Crit: > 0 (from 1 = alarm)

Find Sensor ID: In the Didactum Web Interface under System Tree → Select Sensor → Details. This ID is appended to the end of the OID.

Temperature thresholds in NetCrunch: Didactum delivers temperatures as raw value × 10. 28.0 °C = OID value 280. Performance Counter Alarms and the SNMP View YAML file must therefore specify thresholds × 10 (280 / 350).

MIB Prefix per model: Older devices use .1.3.6.1.4.1.46501, newer ones possibly .1.3.6.1.4.1.39052. Take the exact OIDs from your device's MIB file. Enter both prefixes in the YAML View file under sysObjectID.

11. Test & Troubleshooting

Test SNMP connection in MIB Browser

NetCrunch Console → Tools → MIB Browser
→ IP: 192.168.1.50 / Community: didactum_netcrunch / Version: v2c
→ OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
→ "Get" → Raw value appears (e.g. 235 = 23.5 °C)
→ OID: .1.3.6.1.4.1.46501.5.1.1 → "Walk" → all sensor values appear

Check SNMP View status on the node

Right-click on Didactum-Monitor-01 → "Open SNMP View"
→ Didactum Monitoring System View opens
→ All sensor values are displayed in real time
→ Colored indicator next to each value shows OK/Warning/Critical status

Check active alarms

NetCrunch Console → Events → Active Alerts
→ Filter: Node = Didactum-Monitor-01
→ Active alarms are displayed here

Error messages and solutions

Problem	Cause & Solution
"Test SNMP Connection" fails	Community String wrong; UDP 161 blocked; SNMP not active on Didactum → check
MIB Compiler reports error	Missing MIB dependencies → import standard MIBs (SNMPv2-SMI, SNMPv2-TC) first
SNMP View shows no values	View not assigned to node; SNMP not enabled on node; OID not supported
Temperature alarm never triggers	Threshold not × 10 → set Performance Counter Alarm to 280 / 350 (not 28 / 35)
SNMP Trap does not appear in Event Log	Trap Receiver not enabled; Community not in "Accepted Communities"; UDP 162 blocked
No email on alarm	Check SMTP settings; Alert Script not assigned to alarm; send test email
YAML View import fails	YAML syntax error; check indentation with spaces (not tabs!)

View NetCrunch Logs

NetCrunch Console → Tools → Log Viewer
→ Filter: Type = SNMP Error
→ or: Error Level = Warning, Critical
Windows Event Log:
Event Viewer → Applications → AdRem NetCrunch

12. Final Checklist

Didactum Device

SNMP enabled (v2c or v3)
Community String set (not „public"): didactum_netcrunch
Trap receiver IP set to NetCrunch Server
MIB file downloaded
SNMP connection test from NetCrunch MIB Browser successful

NetCrunch Configuration

Community String stored in NetCrunch SNMP Settings
MIB file imported and compiled with MIB Compiler
Didactum node created via discovery or manually
SNMP enabled on node, connection test successful
UDP 161 outbound, UDP 162 inbound opened

SNMP Views & Monitoring Pack

didactum-view.yaml created and imported
SNMP View assigned to node (sensor values visible)
Monitoring Pack "Didactum Monitoring System" created
All Performance Counter Alarms included in the Pack
Temperature thresholds × 10 correct (280 / 350)
Monitoring Pack assigned to Didactum node

Traps & Notification

SNMP Trap Receiver enabled (Port 162)
Didactum Community entered in "Accepted Communities"
Trap Alarm for Enterprise OID .1.3.6.1.4.1.46501 created
SMTP settings configured, test email received
Alert Script "Didactum Email Admin" created
Alert Script assigned to all Didactum alarms
Test alarm triggered and email received

Didactum Monitoring & NetCrunch Integration

1. Prerequisites & System Overview

NetCrunch Server

Didactum Device

Architecture & Data Flow

2. Enable SNMP on the Didactum Device

Step 1 – Open Web Interface

Step 2 – Access SNMP Settings

Step 3 – Enter the following values

SNMPv3 Settings (optional)

3. Import MIB File into NetCrunch MIB Compiler

Step 1 – Download MIB from Didactum Web Interface

Step 2 – Import MIB into NetCrunch

Step 3 – Check MIB in MIB Browser

Step 4 – Query single OID value in MIB Browser

4. Add Didactum Device to NetCrunch (Discovery)

Step 1 – Store SNMP credentials before discovery

Step 2 – Start Network Discovery

Step 3 – Add device manually (alternative)

Step 4 – Configure Node Properties

Step 5 – Test SNMP connection

5. Create Custom SNMP View for Didactum (YAML)

Step 1 – Create Custom SNMP View file

Step 2 – Import Custom View into NetCrunch

Step 3 – Assign View to the device

6. Configure Performance Counter Alarms

Navigation

Performance Counter Alarm: Temperature Sensor

Performance Counter Alarm: Leakage Sensor

Performance Counter Alarm: Humidity

SNMP Variable Value Alarm (for text values and status)

7. Create Monitoring Pack for Didactum

Step 1 – Create Monitoring Pack

Step 2 – Add Alarms to the Pack

Step 3 – Add SNMP View to the Pack

Step 4 – Apply Monitoring Pack to devices

8. Receive & Process SNMP Traps

Step 1 – Check Trap Reception

Step 2 – Configure Trap Community

Step 3 – Create Trap Alarm for Didactum

Step 4 – Trap-specific rules for individual sensors

Step 5 – Check incoming Traps

9. Configure Email Notification

Step 1 – Configure SMTP Server

Step 2 – Create Alert Script (Recipient)

Step 3 – Assign Alert Script to Didactum Alarms

Step 4 – Assign Email Action via Monitoring Pack (for all devices)

10. SNMP OID Reference

OID fields per sensor

Sensor types with OIDs and NetCrunch thresholds

11. Test & Troubleshooting

Test SNMP connection in MIB Browser

Check SNMP View status on the node

Check active alarms

Error messages and solutions

View NetCrunch Logs

12. Final Checklist

Didactum Device

NetCrunch Configuration

SNMP Views & Monitoring Pack

Traps & Notification

Related Links

Powered by

Hint

This website uses cookies