All MIBs › IB-TRAPONE-MIB
Organization: Infoblox.
Last Updated: 2005-04-17
Category: Vendor: Infoblox
Description: Infoblox MIB providing additional SNMP trap definitions for operational alerts on Infoblox appliance platforms.
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-TRAPONE-MIB?
IB-TRAPONE-MIB is an Infoblox proprietary MIB supplying shared trap/notification variable bindings used across Infoblox DDI (DNS/DHCP/IPAM) grid appliance products. It exposes trap metadata such as node identity, severity, affected subsystem, probable cause, threshold values, and state transitions, rather than continuously-polled counters. Its core purpose is fault and alarm monitoring: it carries threshold-breach data (current vs. high/low thresholds) and previous/current state pairs for a named subsystem, letting an NMS flag hardware or software resource problems (e.g., disk, CPU, or service-level alarms) as they occur. It functions as a companion module to Infoblox's other core IB-* platform and status MIBs, supplying the common trap varbind structure many of their notifications reuse. It's deployed in enterprise DNS/DHCP/IPAM infrastructure where SNMP trap receivers/NMS platforms correlate Infoblox appliance alerts centrally. Engineers can download the IB-TRAPONE-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in IB-TRAPONE-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 DDI grid appliances (DNS/DHCP/IPAM) - shared trap varbind module used across the product line
Monitoring Examples
When a trap carries ibTrapSeverity of critical alongside ibCurThresholdValue exceeding ibThresholdHigh for a named ibSubsystemName, an operator knows a specific appliance subsystem crossed a resource threshold. ibProbableCause and ibTrapDesc supply a human-readable explanation for the NMS console, while ibPreviousState and ibCurrentState show exactly what state transition triggered the alert (e.g., normal to degraded), letting an admin correlate the alarm with a specific subsystem failure rather than guessing from the trap OID alone.
What Can Be Monitored
- trap/alarm severity level
- affected subsystem name
- threshold breach value vs. high/low limits
- state transition (previous vs current)
- probable cause description
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 |
OIDs
RFC description
Infoblox vendor-private MIB for TRAPONE trap definitions and event notification management.
Start monitoring Infoblox DDI grid appliances 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.