Didactum Monitoring & IBM Tivoli Network Manager (ITNM) Integration
Complete step-by-step guide for integrating Didactum monitoring devices and sensors into IBM Tivoli Network Manager IP Edition (ITNM) via SNMP – including discovery configuration, MIB import, AOC definition, poll policies, poll definitions, SNMP trap integration via Netcool/OMNIbus and alerting.
Product note: IBM Tivoli Network Manager (ITNM) IP Edition has been renamed by IBM to IBM Netcool Network Management or IBM Tivoli Netcool/OMNIbus with ITNM extension. Current versions run under IBM Netcool Operations Insight (NOI). All configuration steps described here apply to ITNM 3.9.x and 4.x as well as current NOI versions, since the core components (ncp_disco, ncp_poller, Tivoli Integrated Portal) remain unchanged.
- Software: IBM Tivoli Network Manager IP Edition 3.9 / 4.x (Netcool Network Management)
- Components: ncp_disco (Discovery), ncp_poller (Polling), TIP (Tivoli Integrated Portal), Netcool/OMNIbus (Event Management)
- Protocol: SNMP v1 / v2c / v3
- Devices: Didactum Monitoring System 100T / 300T / 500T / 550T
- Sensors: Temperature, Leak, Humidity, Door Contact, Smoke
1. Requirements & System Overview
ITNM Server
- IBM Tivoli Network Manager IP Edition installed and licensed
- Tivoli Integrated Portal (TIP) reachable: <Server>/ibm/console
- Netcool/OMNIbus ObjectServer started
- ITNM domain configured (default: NCOMS)
- 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 by ICMP from the ITNM server
- MIB file available in the web interface
Important ITNM Directories and Variables
$NCHOME = /opt/IBM/tivoli/netcool (Linux default) $ITNMHOME = $NCHOME/precision
$ITNMHOME/etc/precision/ <-- configuration files $ITNMHOME/etc/precision/mibs/ <-- MIB database $ITNMHOME/etc/precision/CommunityMap/ <-- SNMP community configuration $ITNMHOME/etc/precision/PollEngine/ <-- poll policies and definitions $ITNMHOME/etc/precision/Disco/ <-- discovery configuration $NCHOME/omnibus/probes/ <-- OMNIbus probe configuration
ITNM Architecture for Didactum
[TIP Web Console] | v [ITNM Domain: NCOMS] ncp_disco ──SNMP Discovery UDP/161──> [Didactum 192.168.1.50] ncp_poller ──SNMP Polling UDP/161──> [Didactum 192.168.1.50] | | v SNMP Traps UDP/162 [Netcool/OMNIbus ObjectServer] <────────────────┘ nco_p_ncpmonitor (Poller probe) nco_p_mib2syslog (Trap probe) | v [Active Event List (AEL)] [Event Viewer / Dashboards]
2. Enable SNMP on the Didactum Device
Step 1 – Open the web interface
In the browser: 192.168.1.50 (adjust Didactum device IP)
Step 2 – Open 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_itnm (do not use "public") |
| SNMP Port | 161 |
| Trap Receiver IP | 192.168.1.10 (ITNM server IP) |
| Trap Port | 162 |
| Trap Version | v2c |
SNMPv3 settings (optional)
| Field | Value |
|---|---|
| Security Name | itnm_user |
| Auth Protocol | SHA |
| Auth Password | min. 8 characters |
| Priv Protocol | AES |
| Priv Password | min. 8 characters |
| Security Level | authPriv |
3. Import MIB File (SNMP MIB Browser / MIB Database)
Step 1 – Download MIB from Didactum web interface
System Settings → SNMP → "Download MIB file" → didactum.mib
Step 2 – Import the MIB into the ITNM MIB database
MIBs are imported into ITNM via the Tivoli Integrated Portal:
TIP → Availability → Network Topology → Utilities → SNMP MIB Browser → Tab "MIB Management" → Click "Import MIB" → Upload file didactum.mib → Click "Compile" → Check for "Compilation successful"
Alternatively via command line:
# Copy MIB into ITNM MIB directory cp didactum.mib $ITNMHOME/etc/precision/mibs/ Recompile MIB database cd $ITNMHOME ./scripts/perl/scripts/ncp_mib_compiler.pl -domain NCOMS -mibfile didactum.mib... # check compilation ls $ITNMHOME/etc/precision/mibs/ | grep -i didactum
Step 3 – Test the MIB in the SNMP MIB Browser
TIP → Availability → Network Topology → Utilities → SNMP MIB Browser → IP Address: 192.168.1.50 → Community: didactum_itnm → OID: .1.3.6.1.4.1.46501.5.1.1 → Click "Walk" → Sensor values appear in the result table
Step 4 – Query a single OID
SNMP MIB Browser: OID: .1.3.6.1.4.1.46501.5.1.1.7.101001 Operation: Get → Result: e.g. 235 (= 23.5 °C; raw value ÷ 10)
4. Discovery Configuration (ncp_disco)
ITNM uses the discovery process ncp_disco to automatically detect network devices. For Didactum devices the community string must be configured and a discovery scope defined.
Step 1 – Add SNMP community for Didactum
TIP → Availability → Network Discovery → Configure Discovery → Tab "Agent Access" → Click "Add"
| Field | Value |
|---|---|
| IP Range / Single IP | 192.168.1.50 |
| SNMP Version | SNMPv2c |
| Community String | didactum_itnm |
| SNMP Port | 161 |
| Timeout (sec) | 5 |
| Retries | 3 |
Alternatively directly in the configuration file:
sudo nano $ITNMHOME/etc/precision/CommunityMap/CommunityMap.NCOMS.cfg
# ================================================================
Didactum Community Map entry
Format: { IP-address or range } community_string snmp_version
================================================================
{ 192.168.1.50 } didactum_itnm 2c;
Alternatively whole subnet:
{ 192.168.1.0/24 } didactum_itnm 2c;
Step 2 – Define discovery scope
TIP → Availability → Network Discovery → Configure Discovery → Tab "Scope" → Click "Add IP Range" Start IP: 192.168.1.50 End IP: 192.168.1.50 (or Subnet: 192.168.1.0/24) → Save
Step 3 – Start discovery
TIP → Availability → Network Discovery → Configure Discovery → Click the green "Start Discovery" arrow → Monitor discovery progress in the status bar
After completion the Didactum device appears in the Network Topology Map. Since ITNM does not natively know Didactum, it will initially appear as a generic SNMP device. Exact classification is done via the AOC in section 5.
Step 4 – Check discovery result
TIP → Availability → Network Views → Network Hop View → Search for device 192.168.1.50 → View SNMP data (right-click → "Launch SNMP Browser")
5. Create AOC Definition for Didactum
AOC (Amos Object Class) is the ITNM device classification. With a dedicated AOC definition ITNM recognizes Didactum devices automatically and assigns the correct icon and appropriate poll policies.
Step 1 – Create AOC file
sudo nano $ITNMHOME/etc/precision/DiscoAgents.NCOMS.cfg
Add the following AOC definition at the end of the file:
# ================================================================
Didactum Monitoring System – AOC Definition
Device detection via sysObjectID
================================================================
Older Didactum devices (Enterprise OID .46501)
{
RecordType = "DeviceRecord";
EntityClass = "Didactum";
EntityType = "DidactumMonitoringSystem";
DisplayName = "Didactum Monitoring System";
Icon = "generic_device.gif";
Enabled = TRUE;
Rule {
snmpOID = ".1.3.6.1.4.1.46501";
}
}... # Newer Didactum devices (Enterprise OID .39052)
{
RecordType = "DeviceRecord";
EntityClass = "Didactum";
EntityType = "DidactumMonitoringSystemV2";
DisplayName = "Didactum Monitoring System (New)";
Icon = "generic_device.gif";
Enabled = TRUE;
Rule {
snmpOID = ".1.3.6.1.4.1.39052";
}
}
Step 2 – Configure AOC via TIP (alternative)
TIP → Availability → Network Discovery → Configure Discovery → Tab "Device Classification" → Click "Add Classification Rule" Name: DidactumMonitoring OID Prefix: .1.3.6.1.4.1.46501 Device Class: Didactum Device Type: MonitoringSystem → Save
Step 3 – Run discovery again
After adding the AOC definition run discovery again so the Didactum device is correctly classified:
TIP → Availability → Network Discovery → Configure Discovery → "Run Partial Discovery" for 192.168.1.50
6. Create Poll Policy (ncp_poller)
Poll policies define WHICH devices are monitored. Poll definitions specify WHAT is queried on those devices. Together they form the SNMP monitoring framework in ITNM.
Step 1 – Create Poll Policy via TIP
TIP → Availability → Network Polling → Polling Policies → Click "Create Polling Policy"
| Field | Value |
|---|---|
| Policy Name | Didactum-Sensor-Polling |
| Description | SNMP polling for all Didactum monitoring devices |
| Domain | NCOMS (or your domain name) |
| Active | Enabled |
| Poll Interval | 300 seconds (5 minutes) |
Step 2 – Define device scope for the poll policy
In the Poll Policy → Tab "Device Scope" → Click "Add" Filter Type: Entity Class Value: Didactum (or) Filter Type: IP Range Start IP: 192.168.1.50 End IP: 192.168.1.55 → Save
Step 3 – Poll policy as a file (alternative)
sudo nano $ITNMHOME/etc/precision/PollEngine/PollPolicy.NCOMS.cfg
# ================================================================
Didactum Poll Policy
================================================================
INSERT INTO polls.pollPolicy
(Name, Active, PollInterval, Definition)
VALUES
("DidactumSensorPolling", 1, 300, "DidactumTempPoll"),
("DidactumSensorPolling", 1, 300, "DidactumLeakPoll"),
("DidactumSensorPolling", 1, 120, "DidactumLeakStatusPoll"),
("DidactumSensorPolling", 1, 300, "DidactumHumPoll"),
("DidactumSensorPolling", 1, 60, "DidactumDoorPoll"),
("DidactumSensorPolling", 1, 60, "DidactumSmokePoll");
7. Poll Definitions for Didactum Sensors
Poll definitions specify OID, threshold, event description and event type for each monitored sensor value.
Step 1 – Create poll definitions via TIP
TIP → Availability → Network Polling → Poll Definitions → Click "Create Poll Definition"
Poll Definition: Temperature Sensor
| Field | Value |
|---|---|
| Definition Name | DidactumTempPoll |
| Description | Didactum temperature sensor 01 – raw value x0.1 = °C |
| Poll Type | SNMP |
| OID | .1.3.6.1.4.1.46501.5.1.1.7.101001 |
| Expression Type | Threshold |
| Warning Threshold (High) | 280 (= 28.0 °C; raw value × 10) |
| Critical Threshold (High) | 350 (= 35.0 °C; raw value × 10) |
| Event Severity (Warning) | Warning |
| Event Severity (Critical) | Critical |
| Event Description | Didactum temperature exceeds threshold: $snmpValue (raw; ÷10=°C) |
Important – temperature thresholds: Didactum provides temperature values as raw value × 10. 28.0 °C = OID value 280. Therefore all thresholds in poll definitions must be specified as raw value × 10.
Poll Definition: Leak Sensor
| Field | Value |
|---|---|
| Definition Name | DidactumLeakPoll |
| OID | .1.3.6.1.4.1.46501.5.1.1.7.107001 |
| Expression Type | Threshold |
| Critical Threshold (High) | 0.5 (value ≥ 1 = water detected) |
| Event Severity (Critical) | Critical |
| Event Description | DIDACTUM LEAKAGE: Water detected! Sensor value: $snmpValue (1=water) |
Poll Definition: Leak Status (OID .6.x)
| Field | Value |
|---|---|
| Definition Name | DidactumLeakStatusPoll |
| OID | .1.3.6.1.4.1.46501.5.1.1.6.107001 |
| Critical Threshold (High) | 0.5 |
| Event Description | Didactum sensor status: $snmpValue (0=OK, 1=Alarm, 2=No signal) |
Poll Definition: Humidity
| Field | Value |
|---|---|
| Definition Name | DidactumHumPoll |
| OID | .1.3.6.1.4.1.46501.5.1.1.7.102001 |
| Warning Threshold (High) | 80 (= 80%) |
| Critical Threshold (High) | 90 (= 90%) |
| Event Description | Didactum humidity: $snmpValue % (Warning from 80%, Critical from 90%) |
Poll Definition: Door Contact
| Field | Value |
|---|---|
| Definition Name | DidactumDoorPoll |
| OID | .1.3.6.1.4.1.46501.5.1.1.7.104001 |
| Warning Threshold (High) | 0.5 (value ≥ 1 = open) |
| Event Severity | Warning |
| Event Description | Didactum door contact: $snmpValue (0=closed, 1=open) |
Poll Definition: Smoke Detector
| Field | Value |
|---|---|
| Definition Name | DidactumSmokePoll |
| OID | .1.3.6.1.4.1.46501.5.1.1.7.106001 |
| Critical Threshold (High) | 0.5 |
| Event Severity | Critical |
| Event Description | DIDACTUM SMOKE DETECTOR ALARM: Smoke detected! Value: $snmpValue |
All definitions as a file (alternative)
sudo nano $ITNMHOME/etc/precision/PollEngine/PollDef.NCOMS.cfg
# ================================================================
Didactum Poll Definitions
File: $ITNMHOME/etc/precision/PollEngine/PollDef.NCOMS.cfg
================================================================
INSERT INTO polls.pollDef
(Name, Description, OID, ExprType, WarnHigh, CritHigh, EventDesc)
VALUES
("DidactumTempPoll",
"Temperature sensor 01 (raw ×0.1 = °C)",
".1.3.6.1.4.1.46501.5.1.1.7.101001",
"snmpThreshold",
280, 350,
"Didactum temperature: $snmpValue (raw; /10=°C)"),
("DidactumLeakPoll",
"Leak sensor 01 (0=dry, 1=water)",
".1.3.6.1.4.1.46501.5.1.1.7.107001",
"snmpThreshold",
NULL, 1,
"LEAKAGE ALARM: Water detected! Value=$snmpValue"),
("DidactumHumPoll",
"Humidity 01 (value in %)",
".1.3.6.1.4.1.46501.5.1.1.7.102001",
"snmpThreshold",
80, 90,
"Didactum humidity: $snmpValue %"),
("DidactumDoorPoll",
"Door contact 01 (0=closed, 1=open)",
".1.3.6.1.4.1.46501.5.1.1.7.104001",
"snmpThreshold",
1, NULL,
"Didactum door contact: $snmpValue"),
("DidactumSmokePoll",
"Smoke detector 01 (0=OK, 1=Alarm)",
".1.3.6.1.4.1.46501.5.1.1.7.106001",
"snmpThreshold",
NULL, 1,
"SMOKE DETECTOR ALARM: $snmpValue");
8. Configure MIB Grapher for Visualization
The MIB Grapher in ITNM visualizes SNMP data as time-series graphs directly from the Tivoli Integrated Portal.
Step 1 – Open MIB Grapher
TIP → Availability → Network Topology → [select device] → Right-click → "Launch MIB Grapher"
Step 2 – Configure temperature sensor graph
MIB Grapher → "New Graph" click Graph Name: Didactum Temperature OID: .1.3.6.1.4.1.46501.5.1.1.7.101001 Poll Interval: 300 seconds Divisor: 10 ← IMPORTANT: raw ÷ 10 = degrees Celsius Unit: °C Display Name: Temperature Sensor 01 → "Add" click → "Draw" click
Step 3 – Configure leak graph
MIB Grapher → "New Graph" OID: .1.3.6.1.4.1.46501.5.1.1.7.107001 Divisor: 1 Unit: (empty) Name: Leak Sensor 01
Step 4 – Humidity graph
MIB Grapher → "New Graph" OID: .1.3.6.1.4.1.46501.5.1.1.7.102001 Divisor: 1 Unit: % Name: Humidity Sensor 01
9. Receive SNMP Traps via Netcool/OMNIbus
SNMP traps from the Didactum device are received in ITNM via the Netcool/OMNIbus SNMP probe and converted into events.
Step 1 – Configure OMNIbus SNMP probe
sudo nano $NCHOME/omnibus/probes/nco_p_mib2syslog.props
# SNMP Trap receive configuration TrapPort : 162 ReadCommunity : "didactum_itnm"
Step 2 – Create probe rules file for Didactum traps
sudo nano $NCHOME/omnibus/probes/rules/didactum_traps.rules
# ================================================================
Didactum SNMP Trap Rules for Netcool/OMNIbus
================================================================
Detect leakage trap
if(match($enterprise, ".1.3.6.1.4.1.46501"))
{
# Enterprise trap from Didactum
$Node = $agent_addr;
$NodeAlias = "Didactum Monitoring System";
$Manager = "ITNM";
# Distinguish trap type by OID
if(match($oid, "..107001."))
{
$Summary = "DIDACTUM LEAKAGE ALARM: Water detected!";
$Severity = 5; # Critical
$AlertKey = "DidactumLeak";
$AlertGroup = "Didactum-Sensors";
}
else if(match($oid, "..101001."))
{
$Summary = "DIDACTUM TEMPERATURE ALARM: Sensor reports alarm";
$Severity = 5;
$AlertKey = "DidactumTemp";
$AlertGroup = "Didactum-Sensors";
}
else if(match($oid, "..106001."))
{
$Summary = "DIDACTUM SMOKE DETECTOR ALARM: Smoke detected!";
$Severity = 5;
$AlertKey = "DidactumSmoke";
$AlertGroup = "Didactum-Sensors";
}
else if(match($oid, "..104001."))
{
$Summary = "DIDACTUM DOOR ALARM: Door opened";
$Severity = 3; # Warning
$AlertKey = "DidactumDoor";
$AlertGroup = "Didactum-Sensors";
}
else
{
$Summary = concat("Didactum SNMP Trap: OID=", $oid);
$Severity = 2; # Minor
$AlertKey = "DidactumGeneric";
$AlertGroup = "Didactum-Sensors";
}
update(@Alerts.status);
}
Step 3 – Start probe with Didactum rules
# Restart probe $NCHOME/omnibus/bin/nco_p_mib2syslog -rules $NCHOME/omnibus/probes/rules/didactum_traps.rules -server NCO_PA &... # Or as service (if configured): /etc/init.d/nco_p_mib2syslog restart
Step 4 – Check incoming traps in the AEL
TIP → Availability → Event Management → Active Event List (AEL) → Filter: AlertGroup = "Didactum-Sensors" → Incoming Didactum traps appear here after receipt
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 (current) | .1.3.6.1.4.1.46501.5.1.1.7.101001 |
Sensor types with OIDs and ITNM poll definition thresholds
| Sensor Type | Sensor ID | OID Measurement | OID Status | Poll Def. 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 | WarnHigh: 280 / CritHigh: 350 (× 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 | WarnHigh: 280 / CritHigh: 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 | CritHigh: 1 (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 | WarnHigh: 80 / CritHigh: 90 (direct in %) |
| Potential-free 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 | WarnHigh: 1 (1 = closed) |
| 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 | WarnHigh: 1 (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 | CritHigh: 1 (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 ITNM:
Didactum provides temperatures as raw value × 10. 28 °C = OID value 280. Therefore all ITNM poll definition thresholds must be entered × 10. The MIB Grapher supports a divisor parameter; enter divisor 10 for correct °C display.
MIB prefix per model:
Older devices use .1.3.6.1.4.1.46501, newer models may use .1.3.6.1.4.1.39052. Refer to the exact OIDs in your device's MIB file.
11. Alerting & Event Forwarding
Step 1 – Open Active Event List (AEL)
TIP → Availability → Event Management → Active Event List → Filter: AlertGroup = "Didactum-Sensors" → Didactum alerts from poll violation or trap reception
Step 2 – Email notification via OMNIbus automation
TIP → Event Management → Automations → Create Automation
| Field | Value |
|---|---|
| Automation Name | Didactum-Email-Alert |
| Trigger Condition | AlertGroup = 'Didactum-Sensors' AND Severity >= 4 |
| Action Type | Run Command |
| Command | /opt/IBM/tivoli/netcool/bin/send_alert.sh "$Node" "$Summary" "$Severity" |
Step 3 – Create alert script
sudo nano /opt/IBM/tivoli/netcool/bin/send_alert.sh
#!/bin/bash NODE="$1" SUMMARY="$2" SEVERITY="$3" RECIPIENT="admin@yourdomain.de" echo "Time: $(date) Node: $NODE Message: $SUMMARY Severity: $SEVERITY" | mail -s "[ITNM Didactum ALARM] $NODE: $SUMMARY" "$RECIPIENT"
sudo chmod +x /opt/IBM/tivoli/netcool/bin/send_alert.sh
Step 4 – Ensure email sending
# Check Postfix on the ITNM server sudo systemctl status postfix Send test mail echo "Test ITNM" | mail -s "Test" admin@yourdomain.de
12. Test & Troubleshooting
Test SNMP connection
# From the ITNM server: snmpget -v 2c -c didactum_itnm 192.168.1.50 sysDescr.0 snmpwalk -v 2c -c didactum_itnm 192.168.1.50 .1.3.6.1.4.1.46501.5.1.1 SNMP MIB Browser in TIP: TIP → Availability → Utilities → SNMP MIB Browser → IP: 192.168.1.50 / Community: didactum_itnm → Walk on .1.3.6.1.4.1.46501.5.1.1
ncp_poller SNMP walk script
# ITNM diagnostic script $ITNMHOME/scripts/perl/scripts/snmp_walk.pl -host 192.168.1.50 -community didactum_itnm -oid .1.3.6.1.4.1.46501.5.1.1
Check poll policy status
TIP → Availability → Network Polling → Polling Policies → Select "Didactum-Sensor-Polling" → Status: Active → Click "View Poll Results" → see current sensor values
Errors and solutions
| Problem | Cause & Solution |
|---|---|
| Device does not appear after discovery | Community string wrong; device not pingable; discovery scope too narrow → check CommunityMap.cfg |
| Device classified as "Unknown Device" | AOC definition missing or sysObjectID incorrect → rerun discovery with correct OID prefix |
| Poll definition returns NODATA | OID not supported by device; wrong sensor ID → run snmp_walk.pl and check OID |
| MIB compilation fails | MIB dependencies missing → import SNMPv2-SMI, SNMPv2-TC first |
| Temperature value 10× too large in MIB Grapher | Divisor setting missing → MIB Grapher: set Divisor = 10 |
| Threshold alarm never triggers | Threshold not entered × 10 → edit Poll Definition, enter WarnHigh/CritHigh × 10 |
| SNMP trap not appearing in AEL | OMNIbus probe not started; UDP 162 blocked; trap rules file not loaded |
| ncp_poller does not start | PollDef.cfg syntax error → check log at $ITNMHOME/log/ncp_poller.NCOMS.log |
View ITNM logs
# ncp_disco log (Discovery) tail -f $ITNMHOME/log/ncp_disco.NCOMS.log ncp_poller log (Polling) tail -f $ITNMHOME/log/ncp_poller.NCOMS.log MIB compilation log tail -f $ITNMHOME/log/ncp_mib_compiler.log... # OMNIbus probe log tail -f $NCHOME/omnibus/log/nco_p_mib2syslog.log
13. Final Checklist
Didactum Device
- SNMP enabled (v2c or v3)
- Community string set (not "public"): didactum_itnm
- Device reachable by ping from ITNM server
- Trap receiver IP set to ITNM server
- MIB file downloaded
- snmpwalk from ITNM server successful
ITNM Configuration
- Community string in CommunityMap.cfg or TIP configured
- MIB file imported and compiled with MIB Browser
- Discovery scope defined for Didactum IP
- Discovery successful: device appears in topology map
- AOC definition created for Didactum (EntityClass: Didactum)
- Discovery re-run: device correctly classified
Poll Policies & Definitions
- Poll Policy "Didactum-Sensor-Polling" created and active
- Device scope of the policy set to Didactum class or IP
- Poll definitions for temperature (WarnHigh 280, CritHigh 350) created
- Poll definition for leakage (CritHigh 1) created
- Poll definitions for humidity, door contact, smoke detector created
- Poll results: sensor values visible in TIP
- MIB Grapher: temperature graph configured with Divisor 10
SNMP Traps & Alerting
- OMNIbus SNMP probe configured (UDP 162)
- Trap rules file created with Didactum enterprise OID
- OMNIbus automation for email notification created
- Email alert script created and executable
- Incoming traps visible in AEL
- Test alarm triggered and email received