All MIBs › IB-TRAP-MIB
Organization: Infoblox.
Last Updated: 2010-10-10
Category: Vendor: Infoblox
Description: Infoblox MIB defining SNMP trap notifications for system events and service failures on Infoblox DDI appliances.
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 IB-TRAP-MIB?
IB-TRAP-MIB is an Infoblox vendor-specific MIB that defines the SNMP trap/notification vocabulary used across Infoblox DDI (DNS/DHCP/IPAM) grid appliances, rather than a polling-oriented data MIB. Its five NOTIFICATION-TYPEs cover the major event classes: ibEquipmentFailureTrap for hardware faults, ibProcessingFailureTrap for software/daemon failures, ibThresholdCrossingEvent for counters crossing configured high/low thresholds, ibStateChangeEvent for generic state transitions, and ibProcStartStopTrap for normal process start/stop events. Each trap carries a probable-cause code from the extensive IbProbableCause enumeration -- spanning disk, fan, and power-supply failures; database, Apache, SSHD, NTPD, DHCPD, and BIND (named) software failures; NAC authentication server-group up/down; and RAID states (optimal/degraded/rebuilding/battery failed) -- alongside an IbState enumeration used by ibStateChangeEvent to report before/after states such as high-availability active/passive, grid connected/disconnected, replication online/offline/snapshotting, and NTP sync status. Because it only defines notifications and their accompanying varbind types, this MIB has no scalar/table data to poll directly; its value comes from configuring a trap receiver to parse and alert on these events as they arrive. It depends on IB-SMI-MIB for the ibTrapOne registration point and shared IbString/IbNode types. It is deployed on Infoblox NIOS-based DDI appliances (grid members, NAC appliances), and operations teams building fault-monitoring dashboards around the IB-TRAP-MIB MIB typically map ibProbableCause values to their NMS's severity/alert categories rather than polling OIDs directly.
IPNetwork Monitor allows you to monitor SNMP objects defined in IB-TRAP-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
- Infoblox NIOS-based DDI (DNS/DHCP/IPAM) grid appliances
Monitoring Examples
A trap receiver ingests an ibEquipmentFailureTrap carrying an ibProbableCause of ibPowerSupplyFailure for a given ibNodeName; combined with ibTrapSeverity of critical, this would page an on-call engineer to check the physical power supply on that specific Infoblox grid member before the appliance loses redundancy.
What Can Be Monitored
- equipment/hardware failure traps (disk, fan, power supply)
- software/daemon failure traps (DB, Apache, SSHD, NTPD, named, DHCPD)
- threshold-crossing events
- HA/grid/replication/NTP state-change events
- RAID state and NAC authentication server-group status
Imported Objects
From IB-SMI-MIB
| IbNode | |
| IbString | |
| ibTrapOne | OBJECT-IDENTITY |
From SNMPv2-SMI
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| Unsigned32 |
From SNMPv2-TC
| DisplayString | |
| TEXTUAL-CONVENTION |
OIDs
RFC description
Defines SNMP trap definitions for Infoblox One appliances including system state and service notifications.
Start monitoring Infoblox NIOS-based DDI (DNS/DHCP/IPAM) grid appliance (trap definitions) 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.