AVAYA-ENTITY-MIB
This module defines private extensions for Entity MIB
- Source file
AVAYA-ENTITY-MIB- Last revised
- Identity
avayaEntity- Base OID
1.3.6.1.4.1.6889.2.1.99
Imported Objects
| AVAYAGEN-MIB | lsg |
| ENTITY-MIB | entPhysicalDescr entPhysicalIndex entPhysicalParentRelPos PhysicalIndex |
| ENTITY-SENSOR-MIB | EntitySensorValue entPhySensorValue |
| RFC1213-MIB | mib-2 |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32 |
| SNMPv2-TC | DisplayString TEXTUAL-CONVENTION (no object page) TimeStamp |
Net-SNMP examples using the avaya MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'AVAYA-ENTITY-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AVAYA-ENTITY-MIB::avayaEntity'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'AVAYA-ENTITY-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AVAYA-ENTITY-MIB::avayaEntity'
Objects (40)
Showing 40 of 40 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.6889.2.1.99 |
||
.1.3.6.1.4.1.6889.2.1.99.1 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1.1 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1.2 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1.3 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1.4 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1.5 |
||
.1.3.6.1.4.1.6889.2.1.99.1.1.6 |
||
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.1.1.7 |
|
.1.3.6.1.4.1.6889.2.1.99.2 |
||
.1.3.6.1.4.1.6889.2.1.99.2.0 |
||
.1.3.6.1.4.1.6889.2.1.99.3 |
||
.1.3.6.1.4.1.6889.2.1.99.3.0 |
||
.1.3.6.1.4.1.6889.2.1.99.3.1 |
||
.1.3.6.1.4.1.6889.2.1.99.3.1.1 |
||
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.3.1.1.1 |
|
.1.3.6.1.4.1.6889.2.1.99.3.1.1.2 |
||
.1.3.6.1.4.1.6889.2.1.99.3.1.1.3 |
||
.1.3.6.1.4.1.6889.2.1.99.3.1.1.4 |
||
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.3.1.1.5 |
|
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.3.1.1.6 |
|
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.3.1.1.7 |
|
.1.3.6.1.4.1.6889.2.1.99.3.1.1.8 |
||
.1.3.6.1.4.1.6889.2.1.99.3.2 |
||
.1.3.6.1.4.1.6889.2.1.99.3.2.1 |
||
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.3.2.1.1 |
|
.1.3.6.1.4.1.6889.2.1.99.3.2.1.2 |
||
.1.3.6.1.4.1.6889.2.1.99.3.2.1.3 |
||
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.3.2.1.4 |
|
.1.3.6.1.4.1.6889.2.1.99.4 |
||
.1.3.6.1.4.1.6889.2.1.99.4.1 |
||
|
OctetString
|
.1.3.6.1.4.1.6889.2.1.99.4.2 |
|
.1.3.6.1.4.1.6889.2.1.99.4.3 |
||
.1.3.6.1.4.1.6889.2.1.99.5 |
||
.1.3.6.1.4.1.6889.2.1.99.5.0 |
||
.1.3.6.1.4.1.6889.2.1.99.5.1 |
||
.1.3.6.1.4.1.6889.2.1.99.5.1.1 |
||
|
Enumeration
|
.1.3.6.1.4.1.6889.2.1.99.5.1.1.1 |
|
|
Enumeration
|
.1.3.6.1.4.1.6889.2.1.99.5.1.1.2 |
Dependencies (13) 7 direct · 6 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- AVAYAGEN-MIBavaya
- SNMPv2-TCrfc
- IANA-ENTITY-MIBrfc
- SNMPv2-CONFrfc
- SNMP-FRAMEWORK-MIBrfc
- UUID-TC-MIBrfc
- ENTITY-MIBrfc
- ENTITY-SENSOR-MIBrfc
- IANAifType-MIBrfc
- RFC-1212rfc
- RFC1155-SMIrfc
- RFC1213-MIBrfc
- AVAYA-ENTITY-MIBavayaselected
Type Definitions (1)
| Enumeration |
cleared(1)indeterminate(2)critical(3)major(4)minor(5)warning(6) |
Conformance Groups (2)
|
avEntPhyChFruGroup
|
.1.3.6.1.4.1.6889.2.1.99.5.2
|
|
|
avEntPhyChFruNotificationGroup
|
.1.3.6.1.4.1.6889.2.1.99.5.3
|
Notifications / Traps (30)
| Name | OID | Description |
|---|---|---|
.1.3.6.1.4.1.6889.2.1.99.2.0.1 |
Fan Fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.10 |
3.3V (3300mv) power supply fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.11 |
3.3V (3300mv) power supply fault clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.13 |
2.5V (2500mv) power supply fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.14 |
2.5V (2500mv) power supply fault clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.16 |
1.8V (1800mv) power supply fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.17 |
1.8V (1800mv) power supply fault clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.19 |
1.6V (1600mv) power supply fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.2 |
Fan Fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.20 |
1.6V (1600mv) power supply fault clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.22 |
Ambient High Temprature fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.23 |
Ambient High Temprature clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.24 |
Ambient Low Temprature fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.25 |
Ambient High Temprature clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.4 |
48V power supply fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.5 |
48V power supply fault clear
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.7 |
5V power supply fault
|
|
.1.3.6.1.4.1.6889.2.1.99.2.0.8 |
5V power supply fault clear
|
|
.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. |
|
.1.3.6.1.4.1.6889.2.1.99.3.0.2 |
The notification is based on usb device insecurely removal.
|
|
.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. |
|
.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). |
|
.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. |
|
.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. |
|
.1.3.6.1.4.1.6889.2.1.99.5.0.1 |
FRU unit was removed from chassis
|
|
.1.3.6.1.4.1.6889.2.1.99.5.0.2 |
FRU unit was inserted into chassis
|
|
.1.3.6.1.4.1.6889.2.1.99.5.0.3 |
Power Supply unit failed
|
|
.1.3.6.1.4.1.6889.2.1.99.5.0.4 |
Power Supply unit resumed operation
|
|
.1.3.6.1.4.1.6889.2.1.99.5.0.5 |
Cable Test Failure on Expansion module
|
|
.1.3.6.1.4.1.6889.2.1.99.5.0.6 |
Cable Test Passed OK on Expansion module
|