ADTRAN-TA5K-REDUNDANCY-MIB

Monitored by Observium
        Total Access 5000 Redundancy MIB
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Status
Explore Observium network monitoring
Source file
ADTRAN-TA5K-REDUNDANCY-MIB
Last revised
Identity
adTa5kRedundancyModuleIdentity
Base OID
1.3.6.1.4.1.664.6.10000.67.1.1.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-TA5K-REDUNDANCY-MIB' -M '/opt/observium/mibs/adtran:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ADTRAN-TA5K-REDUNDANCY-MIB::adTa5kRedundancyModuleIdentity'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ADTRAN-TA5K-REDUNDANCY-MIB' -M '/opt/observium/mibs/adtran:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ADTRAN-TA5K-REDUNDANCY-MIB::adTa5kRedundancyModuleIdentity'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (37)
2 directly used by Observium
.1.3.6.1.4.1.664.5.67.1.1.1
.1.3.6.1.4.1.664.5.67.1.1.1.1
.1.3.6.1.4.1.664.5.67.1.1.1.1.1
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.1
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.2
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.3
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.4
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.5
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.6
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.7
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.8
.1.3.6.1.4.1.664.5.67.1.1.1.1.1.9
.1.3.6.1.4.1.664.5.67.1.1.1.3
.1.3.6.1.4.1.664.5.67.1.1.1.3.1
.1.3.6.1.4.1.664.5.67.1.1.1.3.1.1
.1.3.6.1.4.1.664.5.67.1.1.1.3.1.2
.1.3.6.1.4.1.664.5.67.1.1.2
.1.3.6.1.4.1.664.5.67.1.1.2.1
.1.3.6.1.4.1.664.5.67.1.1.2.1.1
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.2.1.1.1
Enumeration
.1.3.6.1.4.1.664.5.67.1.1.2.1.1.2
.1.3.6.1.4.1.664.5.67.1.1.2.1.1.3
.1.3.6.1.4.1.664.5.67.1.1.2.1.1.4
.1.3.6.1.4.1.664.5.67.1.1.3
.1.3.6.1.4.1.664.5.67.1.1.3.0
.1.3.6.1.4.1.664.5.67.1.1.4
.1.3.6.1.4.1.664.5.67.1.1.4.1
.1.3.6.1.4.1.664.5.67.1.1.4.1.1
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.1
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.2
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.3
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.4
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.5
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.6
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.7
.1.3.6.1.4.1.664.5.67.1.1.4.1.1.8
.1.3.6.1.4.1.664.6.10000.67.1.1.1
Dependencies (13) 8 direct · 5 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 (13)
NameOIDDescription
.1.3.6.1.4.1.664.5.67.1.1.3.0.1
Indicates that the standby card in redundant pair has become the active module.
.1.3.6.1.4.1.664.5.67.1.1.3.0.10
Indicates that the user has initiated a manual protection switch.
.1.3.6.1.4.1.664.5.67.1.1.3.0.12
This alarm indicates that the 'working' module has now become active.
This alarm is only generated when revertive mode is enabled. The 'working' module is always the left-most module (odd slot).
The 'protect' module is always the right-most module (even slot).
.1.3.6.1.4.1.664.5.67.1.1.3.0.13
This alarm indicates that the 'working' module has failed and the 'protect' module is now active.
This alarm is only generated when revertive mode is enabled. The 'working' module is always the left-most module (odd slot).
The 'protect' module is always the right-most module (even slot).
.1.3.6.1.4.1.664.5.67.1.1.3.0.14
Indicates that the equipment initiated an automatic protection switch.
.1.3.6.1.4.1.664.5.67.1.1.3.0.2
Redundancy protection is available for this slot.
.1.3.6.1.4.1.664.5.67.1.1.3.0.3
Redundancy protection is not available for this slot.
.1.3.6.1.4.1.664.5.67.1.1.3.0.4
Indicates that the Active module code version mismatch with its peer has cleared.
.1.3.6.1.4.1.664.5.67.1.1.3.0.5
Indicates that the Active module code version does not match with its peer.
.1.3.6.1.4.1.664.5.67.1.1.3.0.6
Indicates that the xM's peer database mirroring is in sync.
.1.3.6.1.4.1.664.5.67.1.1.3.0.7
Indicates that the peer database mirroring sync is in progress on the xM.
.1.3.6.1.4.1.664.5.67.1.1.3.0.8
Indicates that the peer remote database sync is in progress on the SM.
.1.3.6.1.4.1.664.5.67.1.1.3.0.9
Indicates that the xM's remote database is in sync.