AVAYAGEN-MIB

        Avaya top-level OID tree.
This MIB module deals defines the Avaya enterprise-specific tree.
Development organizations within Avaya who wish to register MIBs 
under the Avaya enterprise OID, should:
a. Contact the maintainer of this module, and get an organization OID and
   group OID.
b. Import the definition of their Organization OID from this MIB.
    
Source file
AVAYAGEN-MIB
Last revised
Identity
avaya
Base OID
1.3.6.1.4.1.6889
Imported Objects
SNMPv2-SMI enterprises MODULE-IDENTITY (no object page)
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 'AVAYAGEN-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'AVAYAGEN-MIB::avaya'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'AVAYAGEN-MIB' -M '/opt/observium/mibs/avaya:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'AVAYAGEN-MIB::avaya'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (8)
.1.3.6.1.4.1.6889
.1.3.6.1.4.1.6889.1
.1.3.6.1.4.1.6889.1.6
.1.3.6.1.4.1.6889.2
lsg
.1.3.6.1.4.1.6889.2.1
.1.3.6.1.4.1.6889.2.1.10
.1.3.6.1.4.1.6889.2.1.11
.1.3.6.1.4.1.6889.2.6
Dependencies (1) 1 direct 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
  1. SNMPv2-SMIrfc
  2. AVAYAGEN-MIBavayaselected