ADTRAN-GEN-MONITOR-SESSION-MIB

        This MIB defines the objects for the Monitor Session. 
Monitor Session is used for Port Mirroring. This is used for monitoring network traffic. 
Switch sends all network packets on source port to destination port where packets can be analyzed.  
Creation of Monitor Session, Source interfaces and Destination interface provisioning to the monitor
session can be done using these objects.
    
Source file
ADTRAN-GEN-MONITOR-SESSION-MIB
Last revised
Identity
adGenMonitorSessionMIB
Base OID
1.3.6.1.4.1.664.6.10000.70.61.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-GEN-MONITOR-SESSION-MIB' -M '/opt/observium/mibs/adtran:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'ADTRAN-GEN-MONITOR-SESSION-MIB::adGenMonitorSessionMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'ADTRAN-GEN-MONITOR-SESSION-MIB' -M '/opt/observium/mibs/adtran:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'ADTRAN-GEN-MONITOR-SESSION-MIB::adGenMonitorSessionMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (19)
.1.3.6.1.4.1.664.5.70.61.1
.1.3.6.1.4.1.664.5.70.61.1.1
.1.3.6.1.4.1.664.5.70.61.1.1.1
Integer32
.1.3.6.1.4.1.664.5.70.61.1.1.1.1
Enumeration
.1.3.6.1.4.1.664.5.70.61.1.1.1.2
.1.3.6.1.4.1.664.5.70.61.1.1.1.3
.1.3.6.1.4.1.664.5.70.61.1.1.1.4
.1.3.6.1.4.1.664.5.70.61.1.2
.1.3.6.1.4.1.664.5.70.61.1.2.1
.1.3.6.1.4.1.664.5.70.61.1.2.1.1
Enumeration
.1.3.6.1.4.1.664.5.70.61.1.2.1.2
.1.3.6.1.4.1.664.5.70.61.1.2.1.3
.1.3.6.1.4.1.664.5.70.61.1.2.1.4
.1.3.6.1.4.1.664.5.70.61.1.3
.1.3.6.1.4.1.664.5.70.61.1.3.1
.1.3.6.1.4.1.664.5.70.61.1.3.1.1
.1.3.6.1.4.1.664.5.70.61.1.3.1.2
.1.3.6.1.4.1.664.5.70.61.1.3.1.3
.1.3.6.1.4.1.664.6.10000.70.61.1
Dependencies (13) 5 direct · 8 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