OPTIX-PKT-LINK-SEARCH-MIB

        This mib specifies the QOS service configuration information of device
    
Source file
OPTIX-PKT-LINK-SEARCH-MIB
Last revised
Identity
optixPktLinkSearch
Base OID
1.3.6.1.4.1.2011.2.25.4.50.16
Imported Objects
OPTIX-BOARD-MANAGE-MIB optixLogBoardId optixLogSubCardId
OPTIX-OID-MIB optixProvisionPtn
OPTIX-PORT-MANAGE-MIB optixPortId
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) Unsigned32
Net-SNMP examples using the huawei 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 'OPTIX-PKT-LINK-SEARCH-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'OPTIX-PKT-LINK-SEARCH-MIB::optixPktLinkSearch'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'OPTIX-PKT-LINK-SEARCH-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'OPTIX-PKT-LINK-SEARCH-MIB::optixPktLinkSearch'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (17)
.1.3.6.1.4.1.2011.2.25.4.50.16
.1.3.6.1.4.1.2011.2.25.4.50.16.1
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.1
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.10
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.11
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.12
Enumeration
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.13
Enumeration
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.2
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.3
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.4
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.5
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.6
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.7
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.8
.1.3.6.1.4.1.2011.2.25.4.50.16.1.1.1.9
Dependencies (7) 5 direct · 2 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