OPMANTEK-MIB

Description: Opmantek Ltd MIB defining the enterprise OID root and event notification objects for the Opmantek opEvents network and IT operations 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.

OPMANTEK-MIB is the root SNMP module for Opmantek Ltd's network and IT operations management platform, notably opEvents, defining the enterprise OID subtree and the common event-notification objects used across Opmantek's monitoring products. It belongs to the event/fault-management category of MIBs, exposing structured event data such as event name, source node/host/element, event state, and free-text details rather than raw hardware counters. As such, it is used less for direct hardware sensor readings and more for relaying processed operational status, for example whether a monitored node or service is in an alarm ('stateful') condition, when the event occurred, and what element of the infrastructure is affected, effectively acting as a unified fault-notification channel for whatever underlying issue opEvents has detected on the monitored device. It functions as a root/common module that other Opmantek product MIBs likely build upon for their own specific event and object definitions. It is typically deployed within NMS (network management system) environments where Opmantek's opEvents platform aggregates alerts from many network devices, with OPMANTEK-MIB SNMP monitoring forwarding them onward to a higher-level monitoring or ticketing system.

An NMS integrator would trap on events carrying omkEventName, omkNode, and omkHost to identify what happened and on which monitored device, using omkElement to pinpoint the specific interface or component involved and omkState/omkStateful to determine whether the condition is active/ongoing or has cleared. The omkDetails field would supply human-readable context, such as 'interface down' or 'CPU threshold exceeded,' while omkTime and omkDate timestamp the occurrence for correlation with other monitoring data. A stream of omkStateful='true' events for the same omkNode would indicate a persistent, unresolved fault on that device requiring escalation.

Opmantek root MIB assignment defining SNMP MIB structure for network events, alarms, and notifications.