OPENNMS-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › OPENNMS-MIB

Organization: The OpenNMS Group, Inc.

Last Updated: 2011-12-21

Category: Network Management

Description: Provides SNMP event and trap objects generated by the OpenNMS open-source network management platform.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is OPENNMS-MIB?

OPENNMS-MIB is a software-platform SNMP module associated with OpenNMS, the open-source enterprise network management application, defining the structure of SNMP trap/event objects that OpenNMS itself can generate or relay. Rather than describing a hardware device, it covers metadata fields carried in OpenNMS-originated events, such as database ID, distributed poller identity, creation time, master station, universal event identifier (uei), event source, node ID, timestamp, host, interface, and service. Its relevance to monitoring is indirect: it does not report CPU, memory, or interface counters itself, but standardizes how OpenNMS communicates its own internal event and alarm status (including legacy traps) to other SNMP-based systems. It is inherently tied to the OpenNMS platform's internal event model rather than to IETF standards, and depends on OpenNMS's own polling and event subsystem for the data it carries. It is used in environments where OpenNMS serves as the primary network monitoring platform and needs to forward its events/alarms as SNMP traps to upstream management systems or other NMS tools. Engineers can download the OPENNMS-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in OPENNMS-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, not tied to a specific manufacturer
  • servers/network devices monitored by an OpenNMS instance

Monitoring Examples

A downstream management system would receive an OpenNMS-generated trap carrying fields like uei, nodeid, interface, service, and time (via the onmsLegacyTraps group) to learn that OpenNMS detected a specific service outage on a specific node and interface. Fields such as distPoller and master-station identify which OpenNMS polling instance generated the event in a distributed monitoring deployment. An administrator correlating dbid and create-time across multiple received traps could reconstruct the sequence of node/service state changes detected by OpenNMS, effectively using this MIB as an event-forwarding contract rather than a device-status source.

What Can Be Monitored

  • event/alarm source node and interface
  • affected service
  • event timestamp
  • distributed poller/master station identity
  • universal event identifier (uei)
Imported Objects

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
enterprises

From SNMPv2-TC

DisplayString
OIDs

RFC description

Defines objects and traps for OpenNMS enterprise-grade network management platform, including events, alarms, and synchronization.

Start monitoring vendor-neutral, standards-based MIB, not tied to a specific manufacturer (OpenNMS event/trap forwarding) 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.

Download OPENNMS-MIB