AVAYA-ENTITY-MIB

All MIBs › AVAYA-ENTITY-MIB

Organization: Avaya Inc.

Last Updated: 2006-12-25

Category: Hardware and Environment, Vendor: Avaya

Description: Provides physical and logical entity inventory for Avaya communication equipment using RFC 2737 entity table extensions.

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 AVAYA-ENTITY-MIB?

AVAYA-ENTITY-MIB is an Avaya-specific extension to the standard IETF Entity MIB (RFC 2737), adding physical sensor and USB device details for Avaya communications equipment such as voice gateways and media servers. It extends the standard entity physical table with a sensor table covering high/low warning and shutdown thresholds (with separate clear thresholds) plus an event-support mask, and adds a USB devices table tracking attached USB peripherals and their supported USB version. This is a direct hardware-health monitoring extension: the high/low warning and shutdown threshold objects let an operator detect a temperature, voltage, or other physical sensor reading approaching or exceeding a critical limit before the equipment protectively shuts down, while the USB device table supports inventory/health tracking of attached USB accessories such as storage or licensing dongles. It explicitly depends on and extends the standard Entity MIB (RFC 2737) entPhysicalTable, tying its sensor and USB entries back to standard entity indices. It is deployed on Avaya communication servers, media gateways, and related telephony hardware in enterprise unified-communications environments. Engineers can download the AVAYA-ENTITY-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in AVAYA-ENTITY-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

Avaya communication server/media gateway
Avaya telephony/networking hardware

Monitoring Examples

An administrator would poll avEntPhySensorTable/avEntPhySensorEntry for a given physical entity and compare the current sensor reading against avEntPhySensorHiWarning and avEntPhySensorHiShutdown to catch an overheating component before it trips a protective shutdown, and check whether the reading has crossed back below avEntPhySensorHiWarningClear to confirm recovery. avEntPhyUSBDevicesTable/avEntPhyUSBDevicesEntry with avEntPhyUSBDeviceUSBSupportVersion would be checked to confirm an attached USB device is recognized and supported by the platform, and avEntTraps would notify the NOC automatically when a sensor crosses a warning or shutdown threshold.

What Can Be Monitored

physical sensor readings vs. warning/shutdown thresholds
sensor warning-clear recovery state
attached USB device presence and supported version
sensor event/trap status

Imported Objects

From AVAYAGEN-MIB

lsg	OBJECT-IDENTITY

From ENTITY-MIB

PhysicalIndex
entPhysicalDescr	OBJECT-TYPE
entPhysicalIndex	OBJECT-TYPE
entPhysicalParentRelPos	OBJECT-TYPE

From ENTITY-SENSOR-MIB

EntitySensorValue
entPhySensorValue	OBJECT-TYPE

From RFC1213-MIB

mib-2

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DisplayString
TEXTUAL-CONVENTION
TimeStamp

OIDs

OID symbolic	OID numeric	Type	Access	Description
avayaEntity	1.3.6.1.4.1.6889.2.1.99			This module defines private extensions for Entity MIB
avEntPhySensorTable	1.3.6.1.4.1.6889.2.1.99.1		not-accessible	This table extends entPhySensorTable with thresholds on the sensors.
avEntPhySensorEntry	1.3.6.1.4.1.6889.2.1.99.1.1		not-accessible	Thresholds for sensors described in entPhySensorTable. The Threshold values correspond to entPhySensorValue. Entries are created in this table by the agent. An entry for each physical sensor SHOULD be created at the same time as the associated entPhysicalEntry. An entry SHOULD be destroyed if the associated entPhysicalEntry is destroyed. No entry means that no thresholds are defined for the corresponding sensor
ENT avEntPhySensorHiShutdown	1.3.6.1.4.1.6889.2.1.99.1.1.1	EntitySensorValue	read-only	The system shuts down when the sensor reading reaches this value
ENT avEntPhySensorHiWarning	1.3.6.1.4.1.6889.2.1.99.1.1.2	EntitySensorValue	read-only	The system generates a warning event when the sensor reading rises and crosses this value
ENT avEntPhySensorHiWarningClear	1.3.6.1.4.1.6889.2.1.99.1.1.3	EntitySensorValue	read-only	The system generates a warning-clear event when the sensor reading falls and crosses below this value
ENT avEntPhySensorLoWarningClear	1.3.6.1.4.1.6889.2.1.99.1.1.4	EntitySensorValue	read-only	The system generates a warning-clear event when the sensor reading rises and crosses this value
ENT avEntPhySensorLoWarning	1.3.6.1.4.1.6889.2.1.99.1.1.5	EntitySensorValue	read-only	The system generates a warning event when the sensor reading falls and crosses this value
ENT avEntPhySensorLoShutdown	1.3.6.1.4.1.6889.2.1.99.1.1.6	EntitySensorValue	read-only	The system shuts down if the sensor reaches this value
OCT avEntPhySensorEventSupportMask	1.3.6.1.4.1.6889.2.1.99.1.1.7	OCTET STRING	read-only	A trap and an event is generated upon threshold crossing if the correspond bit is set. Note that there may be other trap filtering mechanisms. 0/0: hiShutdown(0) 0/1: hiWarning(1) 0/2: hiWarningClear(2) 0/3: loWarningClear(3) 0/4: loWarning(4) 0/5: loShowdown(5)
avEntTraps	1.3.6.1.4.1.6889.2.1.99.2
avEntTrapsV3separator	1.3.6.1.4.1.6889.2.1.99.2.0
NTF avEntFanFlt	1.3.6.1.4.1.6889.2.1.99.2.0.1			Fan Fault
NTF avEntFanOk	1.3.6.1.4.1.6889.2.1.99.2.0.2			Fan Fault
NTF avEnt48vPwrFlt	1.3.6.1.4.1.6889.2.1.99.2.0.4			48V power supply fault
NTF avEnt48vPwrFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.5			48V power supply fault clear
NTF avEnt5vPwrFlt	1.3.6.1.4.1.6889.2.1.99.2.0.7			5V power supply fault
NTF avEnt5vPwrFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.8			5V power supply fault clear
NTF avEnt3300mvPwrFlt	1.3.6.1.4.1.6889.2.1.99.2.0.10			3.3V (3300mv) power supply fault
NTF avEnt3300mvPwrFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.11			3.3V (3300mv) power supply fault clear
NTF avEnt2500mvPwrFlt	1.3.6.1.4.1.6889.2.1.99.2.0.13			2.5V (2500mv) power supply fault
NTF avEnt2500mvPwrFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.14			2.5V (2500mv) power supply fault clear
NTF avEnt1800mvPwrFlt	1.3.6.1.4.1.6889.2.1.99.2.0.16			1.8V (1800mv) power supply fault
NTF avEnt1800mvPwrFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.17			1.8V (1800mv) power supply fault clear
NTF avEnt1600mvPwrFlt	1.3.6.1.4.1.6889.2.1.99.2.0.19			1.6V (1600mv) power supply fault
NTF avEnt1600mvPwrFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.20			1.6V (1600mv) power supply fault clear
NTF avEntAmbientHiTempFlt	1.3.6.1.4.1.6889.2.1.99.2.0.22			Ambient High Temprature fault
NTF avEntAmbientHiTempFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.23			Ambient High Temprature clear
NTF avEntAmbientLoTempFlt	1.3.6.1.4.1.6889.2.1.99.2.0.24			Ambient Low Temprature fault
NTF avEntAmbientLoTempFltOk	1.3.6.1.4.1.6889.2.1.99.2.0.25			Ambient High Temprature clear
avEntPhyUSBDevices	1.3.6.1.4.1.6889.2.1.99.3
avEntPhyUSBDevicesTraps	1.3.6.1.4.1.6889.2.1.99.3.0
NTF avEntPhyUSBDeviceRemovalOnBackupRestoreOperation	1.3.6.1.4.1.6889.2.1.99.3.0.1			The notification is based on usb mass storage device removal during backup/restore operation to it. If other usb devices are removed during this operation then no harm/syslog.
NTF avEntPhyUSBDeviceInsecureRemoval	1.3.6.1.4.1.6889.2.1.99.3.0.2			The notification is based on usb device insecurely removal.
NTF avEntPhyUSBDevicePowerFailure	1.3.6.1.4.1.6889.2.1.99.3.0.3			The notification is based on usb device lack of power. For cases as: a. Connecting device which requires more power then gateway can supply. b. Connecting USB device to non power hub which has not enough power. C. Disconnecting power from the USB HUB and there is not enough power to drive the usb devices. D. Disconnecting power from a usb device which requires external power. E. Disconnecting power from USB device and the gateway/USB Hub can not supply power to it.
NTF avEntPhyUSBDeviceNotSupported	1.3.6.1.4.1.6889.2.1.99.3.0.4			The notification is based on attaching non supported usb device to the gateway. The Gateways supports usb mass storage devices based on flash drives that their sub class is SCSI and their protocol is Bulk Only Transport. The Gateways supports usb modems that complies to sub class SFF-8020i, MMC-2 (ATAPI) and protocol Control/Bulk/Interrupt protocol (with no command completion Interrupt).
NTF avEntPhyUSBDeviceExceedMaxNumber	1.3.6.1.4.1.6889.2.1.99.3.0.5			The notification is based on reaching the max number of usb devices connected to the gateway. G250/G350 allows only USB Modem with only one usb mass storage device at the same time.
NTF avEntPhyUSBFileSystemNotSupported	1.3.6.1.4.1.6889.2.1.99.3.0.6			The notification is based on reaching connecting USB mass storage device with file system that is not supported.
avEntPhyUSBDevicesTable	1.3.6.1.4.1.6889.2.1.99.3.1		not-accessible	This table extends entPhysicalTable with USB devices parameters.
avEntPhyUSBDevicesEntry	1.3.6.1.4.1.6889.2.1.99.3.1.1		not-accessible	This table includes extension to entPhysicalTable with usb devices parameters.
STR avEntPhyUSBDeviceUSBSupportVersion	1.3.6.1.4.1.6889.2.1.99.3.1.1.1	DisplayString	read-only	The USB standard version. Possible values are: 1.1 and 2.0.
I32 avEntPhyUSBDeviceClassCode	1.3.6.1.4.1.6889.2.1.99.3.1.1.2	Integer32	read-only	The usb device class code. Value Hex Value Descriptor 1 1 Audio 2 2 CDC-Control 3 3 HID 5 5 Physical 6 6 Image (subclass & protocol must be 1) 7 7 Printer 8 8 Mass-Storage 9 9 HUB 10 A CDC-Data 11 B Chip/Smart Card 13 D Content-Security 14 E Video 220 DC Diagnostic Device (see below for details) 224 E0 Wireless Controller (see below for details) 254 FE Application-Specific (see below for details) 255 FF Vendor-Specific The G250/G350 supports usb mass storage devices of class code of 0x8 and usb modem with class 0x2.
I32 avEntPhyUSBDeviceSubClassCode	1.3.6.1.4.1.6889.2.1.99.3.1.1.3	Integer32	read-only	The usb device subclass code. USB standard describe the following class codes: 0x01 - RBC (Reduced Block Commands) 0x02 - SFF-8020i, MMC-2 (ATAPI) 0x03 - QIC-157 0x04 - UFI 0x05 - SFF-8070i 0x06 - SCSI The G250/G350 supports 0x06 - SCSI for USB mass storage devices and 0x2 - SFF-8020i, MMC-2 (ATAPI) for USB modem.
I32 avEntPhyUSBDeviceProtocol	1.3.6.1.4.1.6889.2.1.99.3.1.1.4	Integer32	read-only	The usb device protocol code. 0x0 - Control/Bulk/Interrupt protocol (with command completion Interrupt). 0x1 - Control/Bulk/Interrupt protocol (with no command completion Interrupt). 0x50 - Bulk Only Transport. The G250/G350 supports 0x50 protocol for usb mass storage devices and 0x1 for USB modem.
OCT avEntPhyUSBDeviceVendorId	1.3.6.1.4.1.6889.2.1.99.3.1.1.5	OCTET STRING	read-only	The USB device vendor HEX-formatted string as it is provided to the USB host by the USB device
STR avEntPhyUSBDeviceSpeed	1.3.6.1.4.1.6889.2.1.99.3.1.1.6	DisplayString	read-only	The USB device speed. Possible values: 'Low', 'Full' and 'High'. G250/G350 supports 'Full' and 'High'
STR avEntPhyUSBDevicePower	1.3.6.1.4.1.6889.2.1.99.3.1.1.7	DisplayString	read-only	The USB device power. Possible values: 'Unknown', 'Self Powered' and 'Bus Powered'.
I32 avEntPhyUSBDeviceCurrent	1.3.6.1.4.1.6889.2.1.99.3.1.1.8	Integer32	read-only	The USB current consumption in mA.
avEntPhyUSBMassStorageDevicesTable	1.3.6.1.4.1.6889.2.1.99.3.2		not-accessible	This table extends entPhysicalTable with USB mass storage devices parameters.
avEntPhyUSBMassStorageDevicesEntry	1.3.6.1.4.1.6889.2.1.99.3.2.1		not-accessible	This table includes extension to entPhysicalTable with usb mass storage devices parameters.
STR avEntPhyUSBMassStorageDeviceFileSystemName	1.3.6.1.4.1.6889.2.1.99.3.2.1.1	DisplayString	read-only	The usb mass storage device File system name. An exmaple for one usb mass storage device on the gateway is mapped to /usbdevice0/.
I32 avEntPhyUSBMassStorageDeviceCapacity	1.3.6.1.4.1.6889.2.1.99.3.2.1.2	Integer32	read-only	Capacity of USB Mass storage device in KBytes.
I32 avEntPhyUSBMassStorageDeviceFreeMemory	1.3.6.1.4.1.6889.2.1.99.3.2.1.3	Integer32	read-only	Free memory of USB Mass storage device in KB. For R/O USB mass storage devices (as CDROM) this value returns 0. Note that this MIB item shall be updated according backup operations that may consume memory space.
STR avEntPhyUSBMassStorageDeviceFs	1.3.6.1.4.1.6889.2.1.99.3.2.1.4	DisplayString	read-only	The file system supported by the USB device. Possible values: 'FAT16' and 'FAT32'.
avEntPhyNotificationDefinitions	1.3.6.1.4.1.6889.2.1.99.4
AVE avEntPhySeverity	1.3.6.1.4.1.6889.2.1.99.4.1	AvEntPhyItuPerceivedSeverity	accessible-for-notify	The severity of the notification.
STR avEntPhyProductId	1.3.6.1.4.1.6889.2.1.99.4.2	DisplayString	accessible-for-notify	The Product Id of Avaya Device - 10 characters.
PHY avEntPhysicalIndex	1.3.6.1.4.1.6889.2.1.99.4.3	PhysicalIndex	accessible-for-notify	The index for this entry.
avEntPhyChFru	1.3.6.1.4.1.6889.2.1.99.5
avEntPhyChFruNotifications	1.3.6.1.4.1.6889.2.1.99.5.0
NTF avEntPhyChFruRemoval	1.3.6.1.4.1.6889.2.1.99.5.0.1			FRU unit was removed from chassis
NTF avEntPhyChFruInsertion	1.3.6.1.4.1.6889.2.1.99.5.0.2			FRU unit was inserted into chassis
NTF avEntPhyChFruPsuFlt	1.3.6.1.4.1.6889.2.1.99.5.0.3			Power Supply unit failed
NTF avEntPhyChFruPsuFltOk	1.3.6.1.4.1.6889.2.1.99.5.0.4			Power Supply unit resumed operation
NTF avEntPhyChFruExpansionTestFailure	1.3.6.1.4.1.6889.2.1.99.5.0.5			Cable Test Failure on Expansion module
NTF avEntPhyChFruExpansionTestClear	1.3.6.1.4.1.6889.2.1.99.5.0.6			Cable Test Passed OK on Expansion module
avEntPhyChFruTable	1.3.6.1.4.1.6889.2.1.99.5.1		not-accessible	Table depicting the status of chassis FRU units such as Power-Supplies and Fan-Tray
avEntPhyChFruEntry	1.3.6.1.4.1.6889.2.1.99.5.1.1		not-accessible	Table entry depicting the status of chassis FRU units such as Power-Supplies and Fan-Tray
INT avEntPhyChFruOperStat	1.3.6.1.4.1.6889.2.1.99.5.1.1.1	INTEGER	read-only	Operational status of the chassis FRU unit.
INT avEntPhyChFruFault	1.3.6.1.4.1.6889.2.1.99.5.1.1.2	INTEGER	read-only	Description of fault, in case an FRU has failed
avEntPhyChFruGroup	1.3.6.1.4.1.6889.2.1.99.5.2			avEntPhyChFruGroup
avEntPhyChFruNotificationGroup	1.3.6.1.4.1.6889.2.1.99.5.3			avEntPhyChFruNotificationGroup

RFC description

Extends entity and sensor monitoring for Avaya telecommunications equipment.

Start monitoring Avaya communication servers/media gateways 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.

Download AVAYA-ENTITY-MIB

What Is AVAYA-ENTITY-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description