AH-TRAP-MIB

Description: Defines SNMP trap and notification objects for Aerohive Networks wireless devices covering connectivity and performance 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.

AH-TRAP-MIB is an Aerohive Networks (now part of Extreme Networks) proprietary MIB defining the SNMP trap/notification framework used across Aerohive's HiveAP wireless access points and HiveManager-controlled Wi-Fi deployments. It defines a generic, structured trap format carrying an access point identifier and name, a severity level, the affected object's name, a probable cause, current/threshold values, and previous/current state, allowing a single notification schema to cover many different connectivity and performance events. Its monitoring emphasis is heavily on fault and performance-threshold detection for wireless hardware: severity-tagged traps flag when an AP-reported metric crosses a configured threshold, or when an AP transitions between operational states, covering issues like radio interference, client load, or connectivity loss. It works in conjunction with Aerohive's broader AH-* MIB family (e.g., AP inventory/status MIBs) which this trap schema references via the AP identifier and name. It is deployed wherever Aerohive/Extreme HiveAP access points are managed, typically enterprise or branch-office Wi-Fi networks monitored centrally through HiveManager or a third-party NMS via SNMP traps. Engineers can download the AH-TRAP-MIB file directly to load it into their MIB browser.

An NMS receiving an AH-TRAP-MIB notification would read ahAPId/ahAPName to identify which access point raised the alert, ahSeverity and ahProbableCause to triage its urgency and likely root cause, and ahObjectName alongside ahCurValue versus ahThresholdHigh/ahThresholdLow to see exactly which monitored metric (e.g., channel utilization or client count) crossed its configured limit. Comparing ahPreviousState to ahCurrentState in the same trap would show, for example, that an AP flipped from "connected" to "disconnected" from its controller, prompting investigation into a possible network or power issue at that AP.

MIB module for access point trap definitions and notifications on Aerohive HiveAP devices.