PET-MIB

Description: Provides SNMP objects for receiving and decoding IPMI Platform Event Traps (PET) from server baseboard management controllers.

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.

PET-MIB is a small standards-oriented MIB used to receive and represent IPMI Platform Event Traps (PET), a standardized alerting mechanism defined by the Intelligent Platform Management Interface specification for server hardware. Rather than exposing polled operational data, its purpose is almost entirely notification-oriented: it defines the trap object (pETTrap) and associated structure so SNMP managers can receive and decode hardware fault events forwarded from a server's baseboard management controller (BMC). Because it relays IPMI PET events, this MIB is fundamentally about hardware status monitoring — the underlying IPMI events it carries typically cover sensor conditions like temperature, voltage, fan failure, power supply loss, chassis intrusion, and other critical hardware faults. It depends conceptually on the IPMI specification and the wired-for-management alerting standard from which PET traps originate, though it does not itself pull in other SNMP MIB modules for object definitions. It is typically deployed wherever a server's BMC/service processor is configured to send SNMP traps for out-of-band hardware alerting, common in rack and blade servers. Engineers implementing or auditing this functionality typically reference the PET-MIB RFC/standard documentation for the authoritative specification.

A monitoring system configured to receive pETTrap notifications would be alerted the moment a server's BMC detects a hardware fault such as a fan failure or over-temperature condition, without needing to poll the server continuously. Because PET-MIB is essentially a trap-reception shim rather than a table of live sensor data, there are no walkable runtime tables here — the actual sensor detail lives in the IPMI event payload the trap carries, not in additional MIB objects. Detecting a pETTrap firing from a specific host would typically trigger an admin to check that server's IPMI sensor log or BMC web interface for the specific fault.

Intel Alert on LAN presence and heartbeat trap management for out-of-band system monitoring.