ADTRAN-GENAUTOCONFIG-MIB

        This MIB defines the objects for the Auto-Config MIB.
    
Source file
ADTRAN-GENAUTOCONFIG-MIB
Last revised
Identity
adGenAutoConfigMIB
Base OID
1.3.6.1.4.1.664.6.10000.70.59.1
Net-SNMP examples using the adtran 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 'ADTRAN-GENAUTOCONFIG-MIB' -M '/opt/observium/mibs/adtran:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ADTRAN-GENAUTOCONFIG-MIB::adGenAutoConfigMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ADTRAN-GENAUTOCONFIG-MIB' -M '/opt/observium/mibs/adtran:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ADTRAN-GENAUTOCONFIG-MIB::adGenAutoConfigMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (23)
.1.3.6.1.4.1.664.5.70.59.0
.1.3.6.1.4.1.664.5.70.59.1
.1.3.6.1.4.1.664.5.70.59.1.1
Unsigned32
.1.3.6.1.4.1.664.5.70.59.1.10
Unsigned32
.1.3.6.1.4.1.664.5.70.59.1.11
Enumeration
.1.3.6.1.4.1.664.5.70.59.1.12
Unsigned32
.1.3.6.1.4.1.664.5.70.59.1.13
.1.3.6.1.4.1.664.5.70.59.1.14
.1.3.6.1.4.1.664.5.70.59.1.15
.1.3.6.1.4.1.664.5.70.59.1.16
Enumeration
.1.3.6.1.4.1.664.5.70.59.1.17
Enumeration
.1.3.6.1.4.1.664.5.70.59.1.18
.1.3.6.1.4.1.664.5.70.59.1.2
.1.3.6.1.4.1.664.5.70.59.1.3
.1.3.6.1.4.1.664.5.70.59.1.4
.1.3.6.1.4.1.664.5.70.59.1.5
.1.3.6.1.4.1.664.5.70.59.1.6
.1.3.6.1.4.1.664.5.70.59.1.7
.1.3.6.1.4.1.664.5.70.59.1.8
.1.3.6.1.4.1.664.5.70.59.1.9
.1.3.6.1.4.1.664.5.70.59.2
Enumeration
.1.3.6.1.4.1.664.5.70.59.2.1
.1.3.6.1.4.1.664.6.10000.70.59.1
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
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.664.5.70.59.0.1
This notification indicates a failure in the Auto-Config sequence
that may require user intervention to resolve. Possible reasons the
network element may activate this alarm may include:
1) A received file is rejected because it is corrupt
2) A received file is rejected because it does not apply to the
network element or does not meet minimum requirements
3) A critical file does not exist on the file server
.1.3.6.1.4.1.664.5.70.59.0.2
This notification indicates the network element has exhausted all of
its application-layer retries when attempting to retrieve a file from
the server during the Auto-Config sequence.