HUAWEI-VBST-MIB

        Please provide the descritpion.
    
Source file
HUAWEI-VBST-MIB
Last revised
Identity
hwVbstMIB
Base OID
1.3.6.1.4.1.2011.5.25.323
Imported Objects
ENTITY-MIB entPhysicalName
HUAWEI-MIB hwDatacomm
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
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 'HUAWEI-VBST-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'HUAWEI-VBST-MIB::hwVbstMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'HUAWEI-VBST-MIB' -M '/opt/observium/mibs/huawei:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'HUAWEI-VBST-MIB::hwVbstMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (14)
.1.3.6.1.4.1.2011.5.25.323
.1.3.6.1.4.1.2011.5.25.323.1
Integer32
.1.3.6.1.4.1.2011.5.25.323.1.1
Integer32
.1.3.6.1.4.1.2011.5.25.323.1.2
Integer32
.1.3.6.1.4.1.2011.5.25.323.1.3
.1.3.6.1.4.1.2011.5.25.323.1.4
OctetString
.1.3.6.1.4.1.2011.5.25.323.1.5
OctetString
.1.3.6.1.4.1.2011.5.25.323.1.6
.1.3.6.1.4.1.2011.5.25.323.1.7
OctetString
.1.3.6.1.4.1.2011.5.25.323.1.8
.1.3.6.1.4.1.2011.5.25.323.2
.1.3.6.1.4.1.2011.5.25.323.3
.1.3.6.1.4.1.2011.5.25.323.3.1
.1.3.6.1.4.1.2011.5.25.323.3.2
Dependencies (8) 4 direct · 4 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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. SNMPv2-TCrfc
  3. IANA-ENTITY-MIBrfc
  4. SNMPv2-CONFrfc
  5. SNMP-FRAMEWORK-MIBrfc
  6. UUID-TC-MIBrfc
  7. ENTITY-MIBrfc
  8. HUAWEI-MIBhuawei
  9. HUAWEI-VBST-MIBhuaweiselected
Compliance Statements (1)

OID .1.3.6.1.4.1.2011.5.25.323.3.2.1
The core compliance statement for all implementations.
Required groups
Notifications / Traps (10)
NameOIDDescription
.1.3.6.1.4.1.2011.5.25.323.2.1
Trap message is generated by VBST node when
it detects that number of trunk ports has exceeded the specification limit.
.1.3.6.1.4.1.2011.5.25.323.2.10
In VBST mode, the Eth-Trunk configuration conflicts with the remote observing port configuration.
.1.3.6.1.4.1.2011.5.25.323.2.2
Trap message is generated by VBST node when
it detects that the number of trunk ports has resumed below 95% of the specification limit.
.1.3.6.1.4.1.2011.5.25.323.2.3
Trap message is generated by VBST node when
it detects that the number of PortVlan has exceeded the specification limit.
.1.3.6.1.4.1.2011.5.25.323.2.4
Trap message is generated by VBST node when
it detects that the number of PortVlan has resumed below 95% of the specification limit.
.1.3.6.1.4.1.2011.5.25.323.2.5
Trap message is generated by VBST node when
it detects that the number of VLANs running VBST has exceeded the specification limit.
.1.3.6.1.4.1.2011.5.25.323.2.6
Trap message is generated by VBST node when
it detects that the number of VLANs running VBST has resumed below 95% of the specification limit.
.1.3.6.1.4.1.2011.5.25.323.2.7
Trap message is generated by VBST node when
it detects that the number of VLANs that cannot be calculated in the VBST packets received by interface exceeds the threshold.
.1.3.6.1.4.1.2011.5.25.323.2.8
Trap message is generated by VBST node when
it detects that the number of VLANs on all Eth-Trunks exceeds the limit of VBST.
.1.3.6.1.4.1.2011.5.25.323.2.9
Trap message is generated by VBST node when
it detects the number of VLANs on all Eth-Trunks falls below the limit of VBST.