Didactum Monitoring & ServersCheck Integration

Complete step-by-step guide for integrating Didactum Monitoring Devices and Sensors into ServersCheck Monitoring Software (InfraSensing) via SNMP – including SNMP Check configuration, OID integration, threshold values, email alerting, SMS/Slack notification, reports and troubleshooting.

Product Note: The ServersCheck Monitoring Software (from version 14+, manufacturer: InfraSensing) is a browser-based monitoring solution operated on port 1272 (from version 15 also port 80). In addition to its own ServersCheck sensors, it also supports third-party SNMP sensors via the check type “SNMP Numeric” (for numeric OID values) as well as “3rd Party Sensors (SNMP)” for manufacturer-independent sensor devices. Didactum environmental sensors (temperature, leakage, humidity) are fully integrated via these check types.

Software: ServersCheck Monitoring Software v14+ / v15+ (InfraSensing)
Protocol: SNMP v1 / v2c / v3
Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke

1. Prerequisites & System Overview

ServersCheck Monitoring Server

ServersCheck Monitoring Software v14+ installed on Windows (Windows 7/8/10 or Windows Server 2008/2012/2016)
Web Interface accessible at: <Server-IP> (v14) or <Server-IP> (v15+)
UDP Port 161 outbound for SNMP Polling open
Network access from the ServersCheck server to the Didactum device available
Default login credentials: Username admin, Password admin (please change)

Didactum Device

Monitoring System 100T, 300T, 500T or 550T
SNMP enabled (v2c recommended)
Device reachable via ICMP from the ServersCheck server
MIB file available in the Web Interface (Download under Preferences → SNMP)

Architecture & Data Flow

[ServersCheck Monitoring Server] [Didactum Monitoring System]
  Windows / Monitoring Appliance IP: 192.168.1.50
  Web Interface: <IP>
                    -- SNMP GET UDP 161 (active polling) -->
                    Return value: String or Integer

Access ServersCheck Web Interface

# Local access (no login required):
localhost
# Network access (login required):
192.168.1.10 (v14)
192.168.1.10 (v15+)
Default Login:
  Username: admin
  Password: admin

2. Enable SNMP on the Didactum Device

Step 1 – Open Didactum Web Interface

Open in browser: 192.168.1.50 (adjust to the IP of the Didactum device)

Step 2 – Access SNMP Settings

Preferences → SNMP

Step 3 – Enter the following values

Field in Didactum Web Interface	Value
Enable SNMP	Enabled
SNMP Version	v2c (recommended)
Community String	didactum_sc (do not use "public"!)
SNMP Port	161

Save settings. Test SNMP connection:

# Windows Command Prompt (if net-snmp is installed):
snmpwalk -v2c -c didactum_sc 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1
# All sensor names
snmpwalk -v2c -c didactum_sc 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1.5
# All measured values
snmpwalk -v2c -c didactum_sc 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1.7

Download MIB File

# In the Didactum Web Interface:
Preferences → SNMP → Download MIB file
# Save file as DIDACTUM-ENV-MIB.mib

3. OID Reference for Didactum Sensors

All Didactum OIDs start with .1.3.6.1.4.1.46501. The sensor ID at the end is determined via snmpwalk or the Didactum Web Interface.

OID Fields per Sensor

Field	Meaning	Example OID
.5.x.SENSOR_ID	Sensor Name (String)	.1.3.6.1.4.1.46501.5.1.1.5.101001
.6.x.SENSOR_ID	Status: 0=Normal, 1=Warning, 2=Critical, 3=Error	.1.3.6.1.4.1.46501.5.1.1.6.101001
.7.x.SENSOR_ID	Measured Value (current)	.1.3.6.1.4.1.46501.5.1.1.7.101001

Sensor Types with OIDs and Thresholds for ServersCheck

Sensor Type	Sensor ID	OID Measured Value	Scaling	Warning	Critical
Temperature Sensor Port 1	101001	.1.3.6.1.4.1.46501.5.1.1.7.101001	Raw value ÷ 10 = °C (215 = 21.5 °C)	280 (28 °C)	350 (35 °C)
Temperature Sensor Port 2	101002	.1.3.6.1.4.1.46501.5.1.1.7.101002	Raw value ÷ 10 = °C	280	350
Humidity Sensor Port 1	102001	.1.3.6.1.4.1.46501.5.1.1.7.102001	Direct value = %rH	80	90
Combo Sensor Temperature (CAN)	103001	.1.3.6.1.4.1.46501.5.1.1.7.103001	Raw value ÷ 10 = °C	280	350
Combo Sensor Humidity (CAN)	103002	.1.3.6.1.4.1.46501.5.1.1.7.103002	Direct value = %rH	80	90
Door Contact	104001	.1.3.6.1.4.1.46501.5.1.1.7.104001	0 = closed, 1 = open	> 0	–
Smoke Detector	106001	.1.3.6.1.4.1.46501.5.1.1.7.106001	0 = OK, 1 = Alarm	–	> 0
Leakage Sensor (Spot)	107001	.1.3.6.1.4.1.46501.5.1.1.7.107001	0 = dry, 1 = water	–	> 0
Leakage Sensor (Cable)	107002	.1.3.6.1.4.1.46501.5.1.1.7.107002	0 = dry, 1 = water	–	> 0
System Status (device overall)	–	.1.3.6.1.4.1.46501.1.1.0	0 = OK, 1 = Warning, 2 = Critical	> 0	> 1

Important Note – Temperature Thresholds:

ServersCheck compares the raw SNMP value directly. Since Didactum transmits temperatures as raw value × 10 (215 = 21.5 °C), all threshold values must also be entered × 10. 28 °C warning = threshold 280.

Find Sensor ID:

In the Didactum Web Interface under System Tree → Sensor → Details or via snmpwalk.

4. Add Device in ServersCheck

Before creating SNMP checks, the Didactum device must be added as a Device in ServersCheck.

Navigation

ServersCheck Web Interface → <Server-IP>
→ Menu → Settings → Devices
→ Click "Add Device"

Field	Value
Device Name	Didactum Server Room
IP Address / Hostname	192.168.1.50
Location	Server Room (optional)
Device Type	Other / Generic

Click Save. The device will then appear in the device list and can be linked with SNMP checks.

5. Create SNMP Numeric Check (Main Method)

The check type SNMP Numeric is the most direct method to monitor a single numeric OID value from any SNMP device, set thresholds and trigger alarms.

Navigation

ServersCheck Web Interface
→ Menu → Add Check → "SNMP Numeric"
(or: Menu → Settings → Adding Checks for SNMP Numeric)

Check 1: Temperature Sensor Port 1

Field	Value
Check Name	Temperature Sensor 01 Server Room
Device	Didactum Server Room (192.168.1.50)
SNMP Version	v2c
Community String	didactum_sc
OID	.1.3.6.1.4.1.46501.5.1.1.7.101001
Warning Value (High)	280 (raw value = 28.0 °C)
Critical Value (High)	350 (raw value = 35.0 °C)
Unit	0.1 °C (raw value without scaling)
Check Interval	300 seconds (5 minutes)
Alert Email	admin@yourdomain.com
Group	Server Room Environment

Click Save.

Check 2: Leakage Sensor

Field	Value
Check Name	Leakage Sensor Underfloor
Device	Didactum Server Room (192.168.1.50)
SNMP Version	v2c
Community String	didactum_sc
OID	.1.3.6.1.4.1.46501.5.1.1.7.107001
Warning Value (High)	empty
Critical Value (High)	0 (from value 1 = water detected = immediately critical)
Check Interval	120 seconds (2 minutes – shorter interval for leakage)
Alert Email	admin@yourdomain.com, emergency@yourdomain.com

All SNMP Numeric Checks at a Glance

Check Name	OID	Warning High	Critical High	Interval
Temperature Sensor 01	.1.3.6.1.4.1.46501.5.1.1.7.101001	280	350	300 sec.
Temperature Sensor 02	.1.3.6.1.4.1.46501.5.1.1.7.101002	280	350	300 sec.
Humidity Sensor 01	.1.3.6.1.4.1.46501.5.1.1.7.102001	80	90	300 sec.
Leakage Sensor Spot	.1.3.6.1.4.1.46501.5.1.1.7.107001	empty	0	120 sec.
Leakage Sensor Cable	.1.3.6.1.4.1.46501.5.1.1.7.107002	empty	0	120 sec.
Door Contact 01	.1.3.6.1.4.1.46501.5.1.1.7.104001	0	empty	60 sec.
Smoke Detector 01	.1.3.6.1.4.1.46501.5.1.1.7.106001	empty	0	60 sec.
Sensor Status 01	.1.3.6.1.4.1.46501.5.1.1.6.101001	0	1	300 sec.
Device System Status	.1.3.6.1.4.1.46501.1.1.0	0	1	300 sec.

6. Create 3rd Party SNMP Sensor Check (Alternative Method)

The check type “Adding Checks for 3rd Party Sensors (SNMP)” enables the integration of external sensor devices with multi-level threshold logic. This type is particularly suitable for devices with their own status OID.

Navigation

ServersCheck Web Interface
→ Menu → Add Check → "3rd Party Sensors (SNMP)"

Field	Value (Example: Didactum device overall)
Check Name	Didactum System Status
Device	Didactum Server Room (192.168.1.50)
SNMP Version	v2c
Community String	didactum_sc
Value OID	.1.3.6.1.4.1.46501.1.1.0
Status OID (optional)	.1.3.6.1.4.1.46501.5.1.1.6.101001
Normal Status Value	0
Warning Status Value	1
Critical Status Value	2
Alert Email	admin@yourdomain.com

Click Save.

7. Configure Email Alerting

ServersCheck supports several email delivery methods. The configuration applies to all checks simultaneously and can be overridden with individual recipients per check.

Navigation

ServersCheck Web Interface → Menu → Settings → Email Alerts
(or directly from the Dashboard screen: click "Email Alerts" link)

Variant A: SMTP Mail Server (recommended for enterprise environments)

Field	Value
Server Type	SMTP Mail Server
From Email Address	serverscheck@yourdomain.com
SMTP Server	mail.yourdomain.com
Server Port	587 (STARTTLS) or 465 (SSL)
Username	serverscheck@yourdomain.com
Password	Your SMTP Password
Uses TLS	Yes
Send Email Alert by default to	admin@yourdomain.com

Click Save, then send Test Email and check inbox.

Option: Apply alerts to all sensors
After email configuration, the option “Apply to all sensors” appears. Activate this to automatically apply the email settings to all existing and new checks.

Variant B: Built-in Mail Server (without own SMTP)

Field	Value
Server Type	Built-In Mail Server
From Email Address	serverscheck@yourdomain.com
Send Email Alert by default to	admin@yourdomain.com

Separate multiple email recipients with commas (no spaces): admin@yourdomain.com,noc@yourdomain.com

Variant C: Gmail

Field	Value
Server Type	Gmail
Gmail Username	youraccount@gmail.com
Gmail Password	App Password (not the regular Gmail password!)
Send Email Alert by default to	admin@yourdomain.com

Gmail Note: An App Password is required. This is generated in Google Account → Security → App Passwords. 2-Factor Authentication must be enabled for the Google account.

8. Configure SMS and Slack Alerting (optional)

In addition to email, ServersCheck also supports SMS and Slack as notification channels – ideal for critical events such as leakage or temperature alarms.

SMS Alerting

ServersCheck Web Interface → Menu → Settings → SMS Alerts

Field	Value
SMS Method	ServersCheck Premium Alerts (100 or 500 Credits)
Account	Account at my.infrasensing.com required
SMS Recipient	+491701234567 (mobile number)
Activation	Activate under "SMS Alert" in the respective check

Slack Alerting

ServersCheck Web Interface → Menu → Settings → Slack Alerts

Field	Value
Slack Webhook URL	hooks.slack.com/services/YOUR-WEBHOOK-URL
Slack Channel	#server-room-alerts
Activation	Activate under "Slack Alert" in the respective check

Create Slack Webhook URL: Slack Workspace → Apps → Incoming Webhooks → "Add to Slack" → Select channel → Copy Webhook URL.

9. Generate Reports

ServersCheck offers built-in report generation by sensor name or sensor type. These can be used as historical trend reports for temperature and leakage sensors.

Report by Sensor Names

ServersCheck Web Interface → Menu → Reports → By Sensor Names
  → Select sensor: "Temperature Sensor 01 Server Room"
  → Time period: last 7 days / 30 days / custom
  → Generate report and export as CSV or PDF

Report by Sensor Types

ServersCheck Web Interface → Menu → Reports → By Sensor Types
  → Select type: SNMP Numeric
  → All Didactum SNMP checks are listed
  → Choose time period and export format

View Alert History

ServersCheck Web Interface → Menu → Alerts
  → All triggered alerts with timestamp, sensor, value and status
  → Filtering by device "Didactum Server Room" possible

10. MIB Template for External SNMP Tools

If SNMP OIDs need to be verified with an external browser (e.g. iReasoning MIB Browser) or another NMS, save the following MIB template as DIDACTUM-ENV-MIB.mib:

-- ============================================================
-- DIDACTUM-ENV-MIB | Enterprise OID: 1.3.6.1.4.1.46501
-- ============================================================
DIDACTUM-ENV-MIB DEFINITIONS ::= BEGIN
IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Integer32, enterprises
        FROM SNMPv2-SMI
    DisplayString
        FROM SNMPv2-TC;
didactum MODULE-IDENTITY
    LAST-UPDATED "202401010000Z"
    ORGANIZATION "Didactum Security GmbH"
    CONTACT-INFO "support@didactum-security.com"
    DESCRIPTION "MIB for Didactum Environmental Monitoring Systems"
    ::= { enterprises 46501 }
didactumSensors OBJECT IDENTIFIER ::= { didactum 5 }
didactumSensorTable OBJECT IDENTIFIER ::= { didactumSensors 1 }
didactumSensorEntry OBJECT IDENTIFIER ::= { didactumSensorTable 1 }
sensorName OBJECT-TYPE
    SYNTAX DisplayString
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "Designation of the sensor"
    ::= { didactumSensorEntry 5 }
sensorStatus OBJECT-TYPE
    SYNTAX Integer32 (0..3)
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "Status: 0=Normal 1=Warning 2=Critical 3=Error"
    ::= { didactumSensorEntry 6 }
sensorValue OBJECT-TYPE
    SYNTAX Integer32
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "Measured value: Temp raw value div 10 = degrees C; Leakage 0 or 1"
    ::= { didactumSensorEntry 7 }
-- Common OIDs:
-- Temperature Sensor Port 1: .1.3.6.1.4.1.46501.5.1.1.7.101001
-- Temperature Sensor Port 2: .1.3.6.1.4.1.46501.5.1.1.7.101002
-- Humidity Port 1: .1.3.6.1.4.1.46501.5.1.1.7.102001
-- Leakage Spot: .1.3.6.1.4.1.46501.5.1.1.7.107001
-- Leakage Cable: .1.3.6.1.4.1.46501.5.1.1.7.107002
-- Door Contact: .1.3.6.1.4.1.46501.5.1.1.7.104001
-- Smoke Detector: .1.3.6.1.4.1.46501.5.1.1.7.106001
-- System Status: .1.3.6.1.4.1.46501.1.1.0
END

11. Test & Troubleshooting

Test SNMP Connection

# Windows Command Prompt (net-snmp required):
snmpwalk -v2c -c didactum_sc 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1
# Check single temperature value (raw value / 10 = degrees Celsius)
snmpget -v2c -c didactum_sc 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1.7.101001
# Example output: INTEGER: 215 → 21.5 degrees Celsius
# Check leakage status (0 = dry, 1 = water detected)
snmpget -v2c -c didactum_sc 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1.7.107001

Check Check Status in Dashboard

ServersCheck Web Interface → Dashboard (main page)
  OK Status (green): Sensor within thresholds
  Warning Status (yellow): Warning threshold exceeded
  Down Status (red): Critical threshold exceeded or connection error
→ Menu → Alerts → Alert history of all events

Error Messages and Solutions

Problem	Cause & Solution
Check remains permanently in "Down" status	SNMP connection failed → Check community string; UDP 161 open?; Ping to Didactum device possible?
Temperature value 10× too high (e.g. 215 instead of 21.5)	Scaling not taken into account → Enter thresholds × 10 (28 °C = 280); Note in Unit field
Leakage does not trigger alarm	Critical Value wrong → Set Critical High to 0 (at value 1 = alarm triggered)
No email on alarm	Check email settings; Send test email; AV software blocks s-alerts.exe? → Add exception for s-alerts.exe in Windows Firewall/AV
Email classified as spam	Use your own SMTP server instead of Built-In Mail Server; Check SPF/DKIM record
ServersCheck Web Interface not reachable	Windows Firewall → Add sserver.exe as exception; Open port 1272 (v14) or port 80 (v15)
SNMP OID returns string instead of integer	Some Didactum firmware versions return measured values as string → Check if value is interpreted correctly in ServersCheck; test with snmpget -Oqv
Check interval too long for leakage	Default interval too long → Set leakage checks to 60–120 seconds

Activate Debug Mode (for persistent problems)

Start → Programs → ServersCheck → Run in Debug Mode
# Alternative:
Start → Programs → ServersCheck → Upgrade ServersCheck
→ Step: "Run in Debug Mode" select
# Debug log files are located in the ServersCheck installation folder:
C:\Program Files (x86)\ServersCheck\logs\

12. Final Checklist

Didactum Device

SNMP enabled (v2c)
Community String set (not "public"): didactum_sc
Device reachable via ping from ServersCheck server
MIB file downloaded
snmpwalk from ServersCheck server successful

ServersCheck – Basic Configuration

Web Interface reachable (http://<IP>:1272 or <IP>)
Default password changed (admin/admin → own password)
Device Didactum Server Room created under Settings → Devices
Windows Firewall: sserver.exe and s-alerts.exe added as exceptions

SNMP Numeric Checks

Check for Temperature Sensor 01 created (Critical High = 350 / Warning High = 280)
Check for Temperature Sensor 02 created
Check for Leakage Sensor Spot created (Critical High = 0, Interval 120 sec.)
Check for Leakage Sensor Cable created
Check for Humidity, Door Contact and Smoke Detector created
All checks visible in dashboard with "OK" status (green)

Alerting & Notification

Email settings configured (SMTP or Built-In Mail Server)
Test email received successfully
"Apply to all sensors" activated or email set per check individually
SMS alerting configured for leakage and smoke checks (optional)
Slack webhook configured for critical alerts (optional)
Alert history under Menu → Alerts shows correct entries
Reports under Menu → Reports generatable for temperature trend

Didactum Monitoring & ServersCheck Integration

1. Prerequisites & System Overview

ServersCheck Monitoring Server

Didactum Device

Architecture & Data Flow

Access ServersCheck Web Interface

2. Enable SNMP on the Didactum Device

Step 1 – Open Didactum Web Interface

Step 2 – Access SNMP Settings

Step 3 – Enter the following values

Download MIB File

3. OID Reference for Didactum Sensors

OID Fields per Sensor

Sensor Types with OIDs and Thresholds for ServersCheck

4. Add Device in ServersCheck

Navigation

5. Create SNMP Numeric Check (Main Method)

Navigation

Check 1: Temperature Sensor Port 1

Check 2: Leakage Sensor

All SNMP Numeric Checks at a Glance

6. Create 3rd Party SNMP Sensor Check (Alternative Method)

Navigation

7. Configure Email Alerting

Navigation

Variant A: SMTP Mail Server (recommended for enterprise environments)

Variant B: Built-in Mail Server (without own SMTP)

Variant C: Gmail

8. Configure SMS and Slack Alerting (optional)

SMS Alerting

Slack Alerting

9. Generate Reports

Report by Sensor Names

Report by Sensor Types

View Alert History

10. MIB Template for External SNMP Tools

11. Test & Troubleshooting

Test SNMP Connection

Check Check Status in Dashboard

Error Messages and Solutions

Activate Debug Mode (for persistent problems)

12. Final Checklist

Didactum Device

ServersCheck – Basic Configuration

SNMP Numeric Checks

Alerting & Notification

Related Links

Powered by

Hint

This website uses cookies