PACEMAKER-MIB

Description: Monitors Linux-HA Pacemaker cluster manager node membership, resource state, and failover events.

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.

PACEMAKER-MIB is a MIB module for the open-source Linux-HA Pacemaker cluster resource manager, used to provide SNMP-based visibility into cluster node membership, resource state, and failover events on Linux high-availability clusters. Rather than a broad polling table, it is primarily a notification-oriented module, defining trap objects that report node identity, the affected resource, the operation performed, its outcome status, and return codes. This makes it a software-status and fault-monitoring MIB in the truest sense: it directly reports whether a clustered resource, such as a service, filesystem, or virtual IP, started, stopped, or failed on a given node, letting an admin detect a failover or resource failure the moment it happens rather than by polling. It depends on the underlying Pacemaker/Corosync cluster stack's internal event model to generate these notifications, translating cluster-manager-level events into SNMP traps. It is typically deployed on Linux servers running Pacemaker-managed HA clusters, for example for database, filesystem, or application failover, where operators want SNMP trap integration alongside or instead of native cluster tooling. Engineers can download the PACEMAKER-MIB file directly to load it into their MIB browser.

A monitoring station would receive a pacemakerNotification trap containing pacemakerNotificationNode and pacemakerNotificationResource identifying which cluster node and resource the event concerns, along with pacemakerNotificationOperation describing what action (start/stop/monitor) was performed. pacemakerNotificationStatus and pacemakerNotificationReturnCode/pacemakerNotificationTargetReturnCode would be inspected to determine whether the operation succeeded or failed, with a non-zero return code indicating a resource failure that likely triggered a failover to another node. pacemakerNotificationDescription supplies human-readable context useful for a first-pass diagnosis without needing to log into the cluster directly.

MIB objects for the Pacemaker cluster manager implementation, monitoring cluster resource status and operations.