MIB Reference Guide

Dell Networking W-Series ArubaOS 6.x MIB | Reference Guide MIBs Overview | 17
embedded in the controller firmware, unlike some devices such as servers that require the agent to be
installed separately.
 MIBs are used for communication between the Managers and the Agents. The OIDs of the MIBs enable
the Managers and Agents to communicate specific data requests and data returns.
 To ensure functionality with SNMP, MIB objects must be defined with the proper keywords, as shown in
Table 6.
ArubaOS Enterprise MIBs support SNMPv1, SNMPv2, and SNMPv3.
Traps
An event is a change on a network device, such as a change in value that crosses threshold. Some events are
categorized as alarms, other events only provide information. When an event occurs on a network device,
SNMP notifications are sent out as traps or information requests.
 Traps are unconfirmed notifications—the receiver does not acknowledge to the sender that the
information was received.
 Inform requests are confirmed notifications—the receiver acknowledges to the sender that the
information was received.
Following are descriptions of trap types.
 Discrete Alarm Inputs
These traps, also known as digital inputs or contact closures, are used for monitoring equipment
failures, intrusion alarms, beacons, and flood and fire detectors.
 Analog Alarm Inputs
Analog alarms measure characteristics that can affect equipment performance—variable levels of
voltage or current, temperature, humidity, and pressure.
 Ping Alarms
Table 6 MIB Keywords
Keyword Description
Sequence The sequence of objects of the MIB. This keyword is used mostly with entry MIB
objects to list the MIB objects that exchange information.
Syntax Textual conventions, such as Integer32.
Max-Access Defines the object accessibility:
read-only: can be retrieved but not modified
read-write: can be retrieved and modified
not-accessible: cannot be retrieved; it is for internal (device) use only
accessible-for-notify: can be retrieved when a trap message (notification) is
sent
Status Defines the status of the object:
current: up to date
deprecated. obsolete, and to be phased out in the future
Description A text string that describes the object.
NO
History may be included in some MIB tables—it lists in which ArubaOS release the MIB was updated or otherwise
changed.