A comprehensive step-by-step guide on integrating Didactum monitoring devices and sensors into CA Spectrum (now: Broadcom DX NetOps Spectrum) via SNMP - including device discovery, MIB import using MIB Tools, OID mapping to model attributes, device self-certification, SNMP trap configuration (AlertMap/EventDisp), and alerting.

Product Note: 

CA Spectrum has been acquired by Broadcom and is now officially named DX NetOps Spectrum. The functionality remains identical. All steps described herein apply to both CA Spectrum 10.x and DX NetOps Spectrum 23.x/24.x.

• Software: CA Spectrum / DX NetOps Spectrum (Broadcom)
• Components: SpectroSERVER, OneClick Web Console, MIB Tools, Device Certification Manager
• Protocol: SNMP v1 / v2c / v3
• Devices: Didactum Monitoring System 100 / 500T / 500 II
• Sensors: Temperature, Leakage, Humidity, Door Contact, Smoke

CA Spectrum Server

• SpectroSERVER installed and started
• OneClick Web Console accessible (default: <Server>/oneclick)
• UDP port 161 open outbound for SNMP polling
• UDP port 162 open inbound for SNMP trap reception
• Administrator access to the OneClick Console
• Network access to the Didactum device

Didactum Device

• Monitoring System 100T, 300T, 500T or 550T
• SNMP enabled (v2c recommended)
• Device reachable via ICMP (ping) from the SpectroSERVER
• MIB file available in the web interface

Important Spectrum Paths (Windows Server)

%SPECROOT%\\                             <-- Spectrum installation directory
%SPECROOT%\\custom\\Events\\              <-- Custom events (AlertMap, EventDisp, EvFormat)
%SPECROOT%\\custom\\Events\\AlertMap      <-- Global AlertMap file (all GnSNMPDev)
%SPECROOT%\\custom\\Events\\EventDisp     <-- Global EventDisp file
%SPECROOT%\\MIBTools\\                   <-- MIB tools directory
%SPECROOT%\\SG-Support\\CsClib\\          <-- MIB database

Typical SPECROOT path (Windows): C:\\win32app\\spectrum\\
Typical SPECROOT path (Linux): /opt/SPECTRUM/

Spectrum Architecture for Didactum

[OneClick Web Console]         [Administrator Browser]
       |                               |
       v                               v
[SpectroSERVER]  -----SNMP polling UDP 161----->  [Didactum 192.168.1.50]
       ^                                                    |
       |                                                    |
       +-----SNMP traps UDP 162 <--------------------------+

Step 1 – Open Web Interface

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

Step 2 – Open SNMP Settings

System Settings → SNMP

Step 3 – Enter the following values

SNMPv3 Settings (optional)

Spectrum must know the community string before it can address a device via discovery.

Navigation in OneClick

OneClick → Administration → SNMP Communities

Add new community

Click OK and save.

Create SNMPv3 profile (if used)

OneClick → Administration → SNMP v3 Profiles → New

Option A – Create model manually (Create by IP)

OneClick → My Landscape → [Right-click on Landscape] → Create Model
→ Model Type: "Network Device by IP" or "Create By Host Name"

Click OK. Spectrum establishes contact and creates a model. The device initially appears as type GnSNMPDev (Generic SNMP Device), since Spectrum does not directly recognize Didactum. Certification is performed in section 7.

Option B – Automatic discovery scan

OneClick → Discovery → New Discovery

Click Run. The Didactum device appears in the result list after completion. Click Model to add it to the landscape.

Step 3 – Find device in OneClick

OneClick → Locater → IP Address: 192.168.1.50 → Search

The Didactum device appears as a model with the type GnSNMPDev. In the next step, the MIB is imported so that Spectrum can better understand the device.

MIB Tools enable the compiling, importing, and browsing of Management Information Bases in DX NetOps Spectrum as well as customizing the mapping of MIB objects and traps.

Step 1 – Download MIB from the Didactum web interface

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

Step 2 – Open MIB Tools in OneClick

OneClick → Select device (didactum-monitor-01)
→ Tools → Utilities → MIB Tools

Alternatively directly:

OneClick → Administration → MIB Tools

Step 3 – Compile and import MIB

1. Click Add MIB in the navigation panel
2. In the dialog, click Browse and select the file didactum.mib
3. Click Compile
4. Messages appear in the "Compiler" section of the dialog – check for Compilation successful
5. Click Add & Close

The MIB now appears in the navigation panel under the vendor path enterprises → 46501 (older devices) or enterprises → 39052 (newer devices).

Step 4 – Verify MIB content

1. Select the imported Didactum MIB in the navigation panel
2. Open the Contents tab – all OIDs of the MIB are displayed
3. Open the Trap Support tab – all trap definitions of the MIB are displayed

Step 5 – Enable trap support

Click "Trap Support", select a trap, and click "Map Traps". In the dialog "MIB Tools: Assign Trap Alarms", set the alarm severity and click OK.

MIB Tools → Navigation: Select Didactum MIB
→ Contents → Trap Support
→ Select trap → Map Traps
→ Set Alarm Severity: Critical → OK

With MIB Tools, MIB OIDs can be mapped to Spectrum model attributes. In the navigation panel, select the device, then open Tools → Utilities → MIB Tools. In the navigation area of the MIB, find the desired OID, open the Map tab, and click "Create attribute".

Step 1 – Open Didactum device in OneClick

OneClick → Locater → IP: 192.168.1.50 → Open device
→ Tools → Utilities → MIB Tools

Step 2 – Navigate MIB in the navigation panel

MIB Tools Navigation Panel:
→ enterprises
  → 46501 (Didactum)
    → 5 (Sensor table)
      → 1
        → 1
          → 7 (sensorValue)
            → 101001 (Sensor ID temperature sensor 01)

Step 3 – Create new attribute for temperature sensor

1. Select OID .1.3.6.1.4.1.46501.5.1.1.7.101001 in the navigation panel
2. Open the Map tab
3. Click Create Attribute (sheet icon with +)
4. Spectrum creates a new attribute and assigns an attribute ID
5. Note the new attribute ID (e.g. 0x00210001)

Step 4 – Create additional OID attributes

Repeat the process for all relevant Didactum OIDs:

Step 5 – Verify attribute on the device

OneClick → Open device didactum-monitor-01
→ Tab "Attributes" or "General" → search for created attributes
→ Current sensor values are displayed here

Since Spectrum does not natively recognize Didactum devices, they initially appear as a generic model GnSNMPDev. With Device Self-Certification, the device is uniquely identified and receives its own model type.

Step 1 – Open Device Certification Manager

OneClick → Select device didactum-monitor-01
→ Tools → Utilities → Device Certification Manager

Step 2 – Identify device

In the Device Certification Manager:

Step 3 – Assign MIBs to the device

In the Device Certification Manager:
→ "Add MIB" button → select DIDACTUM-MIB → Add

Step 4 – Save certification

Click Save. The model is converted from the generic type GnSNMPDev to the new type Didactum Monitoring System. A new icon can optionally be assigned.

Step 5 – Refresh landscape

OneClick → Administration → Event Configuration → Reload Event Configuration

After the reload, all Didactum devices are displayed with the new model type.

Watches continuously monitor attribute values and generate alarms when thresholds are exceeded. They are the equivalent of service checks in other monitoring systems.

Step 1 – Create watch for temperature sensor

OneClick → Open device didactum-monitor-01
→ Tab "Attributes"
→ Find and select attribute "DidactumTemp01"
→ Right-click → Create Watch

Click OK. Create a second watch for critical temperature:

Step 2 – Create watch for leakage sensor

Attribute "DidactumLeak01" → Right-click → Create Watch

Step 3 – Create watch for humidity

Note on temperature raw values in Spectrum watches

The Didactum device transmits temperatures as raw value × 10. 25.5 °C = OID value 255. All thresholds in Spectrum watches must therefore also be specified × 10:

To receive SNMP traps from the Didactum device, three configuration files must be created in Spectrum: AlertMap (trap → event mapping), EventDisp (event processing), and EvFormat (display format).

Option A – Automatically map traps via MIB Tools (recommended)

If the MIB contains trap definitions, the import in section 5 (step 5) can automatically generate the AlertMap entries. After MIB import and trap mapping, the configuration is saved under:

%SPECROOT%\\custom\\Events\\AlertMap
%SPECROOT%\\custom\\Events\\EventDisp

Option B – Manual AlertMap for Didactum

Step 1 – Create folder for Didactum

%SPECROOT%\\custom\\Events\\Didactum\\

Create two files inside without file extension: AlertMap and EventDisp.

Step 2 – Create AlertMap file

%SPECROOT%\\custom\\Events\\Didactum\\AlertMap

Enter the following content:

# ================================================================
# Didactum Monitoring System – AlertMap
# Maps SNMP traps to Spectrum events
# ================================================================

# Enterprise OID of the Didactum traps
# Older devices: .1.3.6.1.4.1.46501
# Newer devices: .1.3.6.1.4.1.39052

# Leakage trap: water detected (OID .107001)
{ .1.3.6.1.4.1.46501.5.1.1.7.107001 }
{
    { 0x00000001 }   EventID = 0x00f10001;
    VARBIND_FORMAT
    {
        (101, 1) \\   # Trap OID
        (102, 2) \\   # Sensor ID
        (103, 3) \\   # Sensor name
        (104, 4) \\   # Sensor value (0=dry, 1=water)
    }
}

# Temperature alarm trap (OID .101001 status)
{ .1.3.6.1.4.1.46501.5.1.1.6.101001 }
{
    { 0x00000001 }   EventID = 0x00f10002;
    VARBIND_FORMAT
    {
        (101, 1) \\
        (102, 2) \\
        (103, 3) \\
        (104, 4) \\
    }
}

# Smoke detector alarm trap (OID .106001)
{ .1.3.6.1.4.1.46501.5.1.1.7.106001 }
{
    { 0x00000001 }   EventID = 0x00f10003;
    VARBIND_FORMAT
    {
        (101, 1) \\
        (102, 2) \\
        (103, 3) \\
        (104, 4) \\
    }
}

# Door alarm trap (OID .104001)
{ .1.3.6.1.4.1.46501.5.1.1.7.104001 }
{
    { 0x00000001 }   EventID = 0x00f10004;
    VARBIND_FORMAT
    {
        (101, 1) \\
        (102, 2) \\
        (103, 3) \\
        (104, 4) \\
    }
}

Step 3 – Create EventDisp file

%SPECROOT%\\custom\\Events\\Didactum\\EventDisp

# ================================================================
# Didactum Monitoring System – EventDisp
# Defines how Spectrum events are processed
# A 3 = Alarm, Severity Critical
# A 2 = Alarm, Severity Major
# A 1 = Alarm, Severity Minor
# ================================================================
# Leakage event → Critical alarm
EVENT 0x00f10001 A 3 ,0xfff0006e
# Temperature status event → Critical alarm
EVENT 0x00f10002 A 3 ,0xfff0006e
# Smoke detector event → Critical alarm
EVENT 0x00f10003 A 3 ,0xfff0006e
# Door contact event → Major alarm
EVENT 0x00f10004 A 2 ,0xfff0006e

Step 4 – Create EvFormat files (display text)

%SPECROOT%\\custom\\Events\\EvFormat\\

Create a separate file for each event (name = EventID + "_en_US", no file extension):

File: 00f10001_en_US
Content:
DIDACTUM LEAKAGE ALARM: Water detected at sensor {101} – Sensor name: {103} – Value: {104}

File: 00f10002_en_US
Content:
DIDACTUM TEMPERATURE ALARM: Sensor {103} reports status {104} (1=alarm, 2=no signal)

File: 00f10003_en_US
Content:
DIDACTUM SMOKE DETECTOR ALARM: Smoke detected at sensor {103}

File: 00f10004_en_US
Content:
DIDACTUM DOOR ALARM: Door opened – Sensor {103}

Step 5 – Reload event configuration

OneClick → Administration → Event Configuration → Reload Event Configuration

After that, incoming Didactum traps appear as correctly mapped alarms in OneClick.

All Didactum OIDs begin 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

Sensor types with OIDs and Spectrum watch thresholds

Determine sensor ID: 

In the Didactum web interface under System tree → select sensor → details. This ID is appended to the end of the OID.

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. The exact OIDs can be found in the MIB file of your device.

Step 1 – Check alarm in OneClick

OneClick → Alarms → Alarm Manager
→ Filter: Source = didactum-monitor-01
→ Alarms are displayed here after watch violations or trap reception

Step 2 – Configure email notification

OneClick → Administration → Alarm Notification Manager → New

Step 3 – Configure SMTP settings

OneClick → Administration → System Settings → Email Settings
  SMTP Server:    mail.yourdomain.com
  SMTP Port:      587
  From Address:   [spectrum@yourdomain.com](mailto:spectrum@yourdomain.com)
  Auth:           Yes (STARTTLS)
  Username:       [spectrum@yourdomain.com](mailto:spectrum@yourdomain.com)
  Password:       Your mail password

Step 4 – Test notification

Alarm Notification Manager → Test → Test email is sent

Test SNMP connection (command line)

# Connection test
snmpget -v 2c -c didactum_spectrum 192.168.1.50 sysDescr.0

# Query temperature value (raw value ÷ 10 = degrees Celsius)
snmpget -v 2c -c didactum_spectrum 192.168.1.50 \\
    .1.3.6.1.4.1.46501.5.1.1.7.101001

# List all sensors
snmpwalk -v 2c -c didactum_spectrum 192.168.1.50 \\
    .1.3.6.1.4.1.46501.5.1.1

SNMP test via MIB Tools in OneClick

OneClick → Select device → Tools → Utilities → MIB Tools
→ Enter OID: .1.3.6.1.4.1.46501.5.1.1.7.101001
→ Host: 192.168.1.50
→ Execute "Get" or "Walk"
→ Result in the right panel

Error messages and solutions

View Spectrum logs

# SpectroSERVER log (Windows)
%SPECROOT%\\logs\\SpectroSERVER.log

# OneClick log
%SPECROOT%\\logs\\OneClick.log

# SNMP trap log
%SPECROOT%\\logs\\SpectroSERVER-TRAP.log

# Reload event configuration after changes to AlertMap/EventDisp:
OneClick → Administration → Event Configuration → Reload Event Configuration

Didactum Device

• SNMP enabled (v2c or v3)
• Community string set (not "public"): didactum_spectrum
• Device reachable via ping from the SpectroSERVER
• Trap receiver IP set to SpectroSERVER
• MIB file downloaded

CA Spectrum – Basic configuration

• SNMP community didactum_spectrum configured in Spectrum
• UDP 161 outbound, UDP 162 inbound open
• Didactum device created as a model via discovery or manually
• MIB file successfully compiled and imported using MIB Tools
• Trap support enabled in MIB Tools and severity set

OID mapping & certification

• OID attributes created for all sensor types in MIB Tools
• Attribute IDs noted and visible on the device in OneClick
• Device self-certification: GnSNMPDev → Didactum Monitoring System
• Event configuration reloaded

Watches & alarms

• Watch for temperature (warn: 280, crit: 350) created
• Watch for leakage (>= 1 = critical) created
• Watch for humidity created
• AlertMap for Didactum traps created
• EventDisp and EvFormat files created
• Event configuration reloaded after AlertMap changes

Notification & test

• SMTP settings configured in Spectrum
• Alarm Notification Manager rule created
• Test alarm triggered and email received
• Incoming traps visible in the OneClick Alarm Manager