This guide describes the complete integration of Didactum monitoring devices into the Avaya Visualization Performance and Fault Manager (VPFM). The objective is the centralized monitoring of all connected sensors - temperature, humidity, leakage, voltage, door contacts, and others - via SNMP polling, MIB browser-based performance monitoring, SNMP trap processing, as well as event scripting and alerting.

Note on Product Naming: Avaya VPFM was originally developed by Nortel and subsequently acquired by Avaya. The current version, VPFM Plus (up to version 3.x), runs on Linux and Windows Server and is part of the Avaya Unified Communications Management portfolio. The configuration steps outlined in this guide apply to VPFM versions 2.x and 3.x.

Avaya VPFM is a multi-vendor network management system with comprehensive capabilities for topology discovery, performance monitoring, fault management, and diagnostics. Since VPFM explicitly provides multi-vendor SNMP support and includes an integrated MIB compiler as well as a MIB browser, Didactum devices can be fully integrated – including device-specific OIDs for environmental sensors.

VPFM core functions for Didactum integration

Processing workflow for Didactum sensors in VPFM

1. Discovery: VPFM detects the Didactum device via SNMP walk and ICMP.
2. MIB Import: The Didactum MIB is loaded into the VPFM MIB compiler; OIDs are given readable names.
3. Credential Assignment: The SNMP community string is assigned to the device.
4. Performance Monitoring: Selected sensor OIDs are polled at configured intervals and stored as metrics.
5. Threshold Configuration: Thresholds for temperature, leakage, etc. trigger events.
6. Trap Processing: SNMP traps from the Didactum device are received and processed as fault events.
7. Alerting: Events trigger notifications via email or event scripts.

• Avaya VPFM 2.x or 3.x (VPFM or VPFM Plus) with administrator access
• VPFM server on Linux (CentOS/RHEL) or Windows Server
• Java Runtime (included with VPFM)
• VPFM web interface accessible (default: HTTP port 8080 or HTTPS port 8443)
• SNMP tools (snmpwalk, snmpget) on the VPFM server for testing
• Didactum monitoring device reachable on the network, SNMP enabled
• UDP port 161 open from the VPFM server to the Didactum device
• UDP port 162 open on the VPFM server for SNMP traps
• SNMP community string known (default: public)
• Didactum MIB file available (DIDACTUM-RACKMONI2-MIB.mib)

Check VPFM service

# Linux – check VPFM service:
service kbmd status
# or:
/opt/VPFM/bin/kbmd status
 
# Start VPFM:
service kbmd start
 
# Open web interface:
# <VPFM-SERVER>/vpfm
# or: <VPFM-SERVER>/vpfm

Example network configuration

3.1 Enable SNMP

1. Open the Didactum web interface: 192.168.1.100, log in with the admin account.
2. Navigation: Settings → Network → SNMP (or: Settings → Network → SNMP).
3. 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 IP of the VPFM server (192.168.1.85)
   • SNMP Trap Receiver: IP of the VPFM server, port 162
4. Save settings.

Warning: Change the default community string public in production environments. Use the same string in the VPFM credentials.

3.2 Test connectivity from the VPFM 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 description (basic test):
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). VPFM displays these raw values – take this into account when configuring thresholds and performance trending.

4.1 Log in to the VPFM web interface

1. Open browser: 192.168.1.85/vpfm.
2. Log in with administrator account (default: admin / admin).
3. After login, the VPFM dashboard appears with topology view and event browser.

4.2 Import Didactum MIB file into VPFM

VPFM includes an integrated MIB compiler that processes vendor MIBs and resolves OID names.

1. Navigation: Diagnosis → MIB Browser → Load MIBs (or in the menu: Tools → MIB Compiler).
2. Click on Upload MIB File.
3. Select Didactum MIB file: DIDACTUM-RACKMONI2-MIB.mib.
4. Click Compile – VPFM processes the MIB and shows success or errors.
5. After successful import: OIDs of the Didactum base (1.3.6.1.4.1.3854) appear with readable names in the MIB browser.

Alternatively, copy the MIB file directly into the VPFM MIB directory:

# Linux – copy MIB file into the VPFM directory:
sudo cp DIDACTUM-RACKMONI2-MIB.mib /opt/VPFM/mibs/
 
# Restart VPFM so that the MIB is loaded:
sudo service kbmd restart

4.3 Ensure dependent MIBs

Before importing the Didactum MIB, the following standard MIBs must be present in VPFM (usually preinstalled):

• SNMPv2-SMI
• SNMPv2-TC
• SNMPv2-MIB
• RFC1213-MIB (MIB-2)

If a MIB is missing: check in VPFM navigation: Administration → MIB Repository → Standard MIBs.

4.4 Enable VPFM SNMP trap receiver

1. Navigation: Administration → Server Settings → SNMP Trap Receiver.
2. Check status: Enabled.
3. Port: 162 (UDP).
4. Accepted communities: add public.
5. Save and restart VPFM.

# Open firewall port 162 on the VPFM server:
# Linux (ufw):
sudo ufw allow 162/udp
 
# Linux (iptables):
sudo iptables -A INPUT -p udp --dport 162 -j ACCEPT

5.1 Start automatic discovery

1. VPFM web interface: Navigation: Topology → Discovery → New Discovery Task.
2. Discovery settings:
   • Discovery type: IP range discovery
   • Start IP: 192.168.1.100
   • End IP: 192.168.1.100 (Didactum device only)
   • SNMP version: v2c
   • Community string: public
   • SNMP port: 161
   • ICMP ping: Enabled
3. Click Start Discovery.
4. VPFM performs ICMP ping and SNMP walk.
5. After completion, the Didactum device appears in the topology view.

5.2 Add device manually

1. Navigation: Topology → Add Device.
2. Fill in the following fields:
   • IP address: 192.168.1.100
   • Device name: didactum-rack01
   • Device type: Generic SNMP device (or Environmental monitor if available)
   • Location: Server room A, Rack 03
   • SNMP version: v2c
   • Read community: public
3. Click Add.

5.3 Check device properties after discovery

1. In the topology view: double-click the Didactum device icon.
2. Tab General: check IP address, sysDescr, sysName, sysUpTime.
3. Tab SNMP: confirm community string and SNMP version.
4. Tab Status: device should show Reachable or Up.

5.4 Create device group

1. Navigation: Topology → Groups → Create Group.
2. Name: Didactum-Rack-Monitoring
3. Description: All Didactum Rack Monitoring Units
4. Members: add Didactum device to the group.
5. This group is used for notification rules and performance monitoring assignments.

5.5 Customize device icon in topology

1. Right-click the Didactum device icon → Properties → Icon.
2. Change icon to Server or Environmental sensor (depending on available VPFM icons).
3. Label: Didactum RMU – Server room A

6.1 Create credential set for Didactum

1. Navigation: Administration → Credentials → Add Credential Set.
2. SNMP v2c credentials:
   • Credential set name: Didactum-SNMPv2c
   • SNMP version: v2c
   • Read community: public
   • Write community: private (if SNMP set is needed)
   • SNMP port: 161
   • Timeout: 2000 ms
   • Retries: 3
3. Save.
4. Assign credential to the Didactum device: open device → Credentials → Assign → Didactum-SNMPv2c.

6.2 Credentials for SNMP v3 (enhanced security)

1. New credential set: Didactum-SNMPv3
2. SNMP version: v3
3. Additional fields:
   • Security level: authPriv
   • Security name: SNMP v3 username from the Didactum device
   • Authentication protocol: SHA
   • Authentication passphrase: authentication password
   • Privacy protocol: AES
   • Privacy passphrase: encryption password
4. Save and assign to the device.

6.3 Perform credential test

1. Open device properties → Credentials → Test Credential.
2. VPFM sends a test SNMP request (sysDescr.0) to the Didactum device.
3. Result Success confirms correct configuration.
4. If Timeout or Authentication Failure: check community string and firewall.

7.1 Use MIB browser for Didactum OIDs

1. Navigation: Diagnosis → MIB Browser (or from the device menu: Diagnosis → SNMP MIB Query).
2. Target device: 192.168.1.100, community: public.
3. OID tree: select Enterprises → Didactum (if MIB was imported).
4. Enter OID: 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 (temperature sensor 1).
5. Click Get or Walk – current value is displayed.
6. Value 235 corresponds to 23.5°C (Didactum factor × 10).

7.2 Set up performance trending for temperature sensors

VPFM supports instance-based performance monitoring, where individual OID values are stored as time-series data.

1. Right-click the Didactum device → Performance → Add Performance Instance.
2. Settings for temperature sensor 1:
   • Instance name: Temperatur-Sensor-1
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
   • Instance type: Gauge
   • Polling interval: 300 seconds (5 minutes)
   • Description: Temperature rack front (raw value × 10)
3. Click Add.
4. Repeat steps 1–3 for additional sensors (sensor 2, leakage, humidity, etc.).

7.3 All performance instances for Didactum

7.4 View performance trending graphs

1. Right-click the Didactum device → Performance → View Trends.
2. Select instance: Temperatur-S1.
3. Choose time range: Last 24 Hours, Last 7 Days, Last 30 Days.
4. Graph shows raw value trend; adjust legend: Display Unit: × 0.1 °C (document manually in label).
5. Multiple instances in one graph: Overlay → Add Instance → Temperatur-S2.

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.).

8.1 Temperature sensors

8.2 Leakage sensors

8.3 Humidity and other sensors

9.1 Create threshold rules for performance instances

1. Right-click the Didactum device → Performance → Thresholds → Add Threshold.
2. Threshold for temperature sensor 1 – warning:
   • Instance: Temperatur-S1
   • Condition: Rising threshold
   • Value: 300 (= 30.0 °C × 10)
   • Severity: Warning
   • Event message: Temperature sensor 1 above 30 °C on {deviceName} (raw value: {value})
   • Rearm value: 280 (= 28.0 °C – alarm clears)
3. Threshold for temperature sensor 1 – critical:
   • Value: 350 (= 35.0 °C × 10)
   • Severity: Critical
   • Rearm value: 320
4. Save.

9.2 Threshold for leakage (immediate alarm)

1. New threshold for instance Leckage-Status-S1:
   • Condition: Rising threshold
   • Value: 1
   • Severity: Critical
   • Event message: LEAKAGE DETECTED on {deviceName} – sensor 1! Immediate action required!
   • Rearm value: 0
2. Set polling interval of the instance to 60 seconds (time-critical).

9.3 Open and check event browser

1. Navigation: Fault → Event Browser.
2. Filter: Device = didactum-rack01.
3. Filter events by severity: Critical, Warning, Normal.
4. Show event details: click an event → timestamp, OID value, device name.
5. Acknowledge event: right-click → Acknowledge.

9.4 Event scripting for notifications

VPFM supports event-handling scripts that are executed on specific events:

1. Navigation: Fault → Event Handling → Add Rule.
2. Settings:
   • Rule name: Didactum-leakage-email
   • Match condition: Event message contains LEAKAGE DETECTED
   • Severity: Critical
   • Action: Run script
   • Script: /opt/VPFM/scripts/didactum_alert.sh

# Example alert script:
sudo nano /opt/VPFM/scripts/didactum_alert.sh

#!/bin/bash
# VPFM event handler script for Didactum alarms
DEVICE="$1"
SEVERITY="$2"
MESSAGE="$3"
TIMESTAMP=$(date '+%Y-%m-%d %H:%M:%S')
ALERT_EMAIL="admin@example.com"
 
echo -e "Subject: [VPFM/${SEVERITY}] Didactum alarm: ${MESSAGE}\\n\\nDevice: ${DEVICE}\\nSeverity: ${SEVERITY}\\nMessage: ${MESSAGE}\\nTime: ${TIMESTAMP}" \\
    | sendmail "${ALERT_EMAIL}"

sudo chmod +x /opt/VPFM/scripts/didactum_alert.sh

9.4 Configure email notification in VPFM

1. Navigation: Administration → Notifications → Email Settings.
2. Enter SMTP server, port, sender address, and authentication.
3. Send test email.
4. Notification rule: Administration → Notifications → New Notification Rule:
   • Trigger: severity Critical or Warning
   • Device group: Didactum-Rack-Monitoring
   • Recipient: admin@example.com

9.6 Recommended thresholds

VPFM includes a native SNMP trap receiver that receives traps directly from the Didactum device and logs them as fault events in the event browser – without additional software.

10.1 Check VPFM trap receiver status

1. Navigation: Administration → Server Settings → SNMP.
2. SNMP trap receiver: confirm status Enabled and port 162.
3. Add community filter if needed: public.

10.2 Configure trap-to-event mapping

1. Navigation: Fault → SNMP Trap Definitions → Add Definition.
2. Definition for leakage trap:
   • Trap OID: .1.3.6.1.4.1.3854.1.7.2
   • Event name: Didactum-leakage-alarm
   • Severity: Critical
   • Message template: LEAKAGE detected on {sourceAddress} – sensor {trapVarBinding1}
3. Definition for temperature alarm:
   • Trap OID: .1.3.6.1.4.1.3854.1.7.1
   • Event name: Didactum-temperature-alarm
   • Severity: Major
4. Create additional trap definitions analogously.

Tip: 

After the MIB import (section 4.2), VPFM automatically recognizes Didactum trap OIDs with readable names. The trap definitions can then be created from the MIB browser.

10.3 Perform trap test

# Send test trap from Didactum device to VPFM:
snmptrap -v2c -c public 192.168.1.85 '' \\
  .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
 
# Event appears in VPFM event browser:
# Fault → Event Browser → Filter: Source = 192.168.1.100

10.4 Important Didactum trap OIDs

11.1 Customize topology view for Didactum

1. Navigation: Topology → Network View.
2. Open subnet with the Didactum device.
3. Device icon: automatically shows color coding by current severity status (green/yellow/orange/red).
4. Click the icon → detail view with all device properties.
5. Background image: upload server room floor plan as background: Topology → Edit Background → Upload Image.

11.2 Set up performance dashboard

1. Navigation: Performance → Dashboard → Add Widget.
2. Widget: Line chart → add instances Temperatur-S1 and Temperatur-S2.
3. Widget: Gauge → instance Temperatur-S1, min: 0, max: 500 (raw value), show thresholds at 300 and 350.
4. Widget: Status summary → device group Didactum-Rack-Monitoring.
5. Widget: Event table → last 10 events of the device group.
6. Save dashboard and set as home page.

11.3 Generate reports

1. Navigation: Reports → Performance Report.
2. Settings:
   • Device: didactum-rack01
   • Instances: Temperatur-S1, Luftfeuchtigkeit-S1, Leckage-Status-S1
   • Time range: Last month
   • Report type: min / max / average
3. Export format: PDF or HTML.
4. Automatic delivery: Schedule report → Monthly → email to admin@example.com.

11.4 SNMP MIB query as diagnostic tool

1. Navigation: Diagnosis → SNMP MIB Query (or from the device menu).
2. Direct OID query for quick diagnosis:
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1 → returns current temperature raw value
   • OID: .1.3.6.1.4.1.3854.1.2.2.1.18.1.4.1 → returns leakage status
3. Walk through the entire Didactum OID base: .1.3.6.1.4.1.3854

# Check VPFM service:
service kbmd status
 
# Start / restart VPFM:
service kbmd start
service kbmd restart
 
# Check VPFM log:
sudo tail -f /opt/VPFM/logs/vpfm.log
sudo tail -f /opt/VPFM/logs/kbmd.log
 
# Test SNMP reachability:
snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854
 
# Query single OID:
snmpget -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.1
 
# Walk all temperature sensors:
snmpwalk -v2c -c public 192.168.1.100 1.3.6.1.4.1.3854.1.2.2.1.16.1.3
 
# Query MIB file with name resolution:
snmpget -v2c -c public -m +DIDACTUM-RACKMONI2-MIB \\
  192.168.1.100 tempValue.1
 
# Send test trap to VPFM:
snmptrap -v2c -c public 192.168.1.85 '' \\
  .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 (ufw):
sudo ufw status verbose
 
# Open ports 161 and 162:
sudo ufw allow 161/udp
sudo ufw allow 162/udp
 
# Open ports 8080 and 8443 (VPFM web):
sudo ufw allow 8080/tcp
sudo ufw allow 8443/tcp
 
# Check SELinux status (disable if necessary for VPFM):
sestatus
# Temporarily disable:
sudo setenforce 0

Always consult the current Didactum device documentation for firmware-specific OIDs and supported sensor types. VPFM version-specific details can be looked up in the Avaya documentation (NN48014-500 and NN48014-100).