All MIBs › DPI20-MIB
Organization: IBM Research - T.J. Watson Research Center
Last Updated: 1996-09-30
Category: Network Interfaces, SNMP Framework
Description: Defines objects for the SNMP Distributed Protocol Interface version 2.0, allowing sub-agent processes to register MIB variables with the main SNMP agent.
IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring DPI20-MIB with a free 30-day trial of IPNetwork Monitor.
What Is DPI20-MIB?
DPI20-MIB is IBM's implementation of the IETF Distributed Protocol Interface version 2.0 (RFC 1592), a mechanism that lets external sub-agent processes register and serve additional MIB variables through a master SNMP agent rather than compiling them directly into it. The MIB itself is intentionally tiny: dpiPortForTCP and dpiPortForUDP report the TCP/UDP port numbers the agent listens on for DPI connections (zero meaning that transport isn't supported), and dpiPathNameForUnixStream reports the AF_UNIX socket path for local DPI connections on Unix-like systems. Because DPI is purely an agent-extension protocol rather than a device-management feature, this MIB models agent capability/configuration rather than any hardware or network state; monitoring it tells you whether a given SNMP agent supports sub-agent registration and over which transport. It is deployed wherever an SNMP agent implements the older DPI 1.x/2.0 extension architecture, a pattern largely superseded by AgentX (RFC 2741) in modern agents, and engineers troubleshooting legacy sub-agent setups still consult the DPI20-MIB reference.
IPNetwork Monitor allows you to monitor SNMP objects defined in DPI20-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- vendor-neutral, standards-based MIB (RFC 1592), implemented here by IBM SNMP agents supporting the DPI 2.0 sub-agent extension architecture
Monitoring Examples
An operator reads dpiPortForTCP and dpiPortForUDP on a target agent to confirm which transport a DPI sub-agent should connect over; both values reading zero when a sub-agent is expected to be registered would indicate the agent isn't listening for DPI connections at all, explaining why the sub-agent's objects never appear.
What Can Be Monitored
- DPI TCP listening port
- DPI UDP listening port
- AF_UNIX stream socket path for local DPI connections
- DPI 2.0 vs. DPI 1.0/1.1 backward-compatibility group support
Imported Objects
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| enterprises |
From SNMPv2-TC
| DisplayString |
OIDs
RFC description
IBM DPI20 MIB exposing TCP/UDP port numbers for Distributed Program Interface agent connections.
Start monitoring IBM SNMP agent implementing DPI 2.0 sub-agent extension (RFC 1592) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.