H3C-LPBKDT-MIB

        Loops may cause broadcast storms.  The purpose of loopback detection
is to detect loops on the device and to protect the network.
    
Source file
H3C-LPBKDT-MIB
Last revised
Identity
h3cLpbkdt
Base OID
1.3.6.1.4.1.2011.10.2.95
Imported Objects
HUAWEI-3COM-OID-MIB h3cCommon
IF-MIB ifDescr ifIndex InterfaceIndex
Q-BRIDGE-MIB VlanId
SNMPv2-SMI Integer32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
SNMPv2-TC TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the h3c 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 'H3C-LPBKDT-MIB' -M '/opt/observium/mibs/h3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'H3C-LPBKDT-MIB::h3cLpbkdt'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'H3C-LPBKDT-MIB' -M '/opt/observium/mibs/h3c:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'H3C-LPBKDT-MIB::h3cLpbkdt'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (14)
.1.3.6.1.4.1.2011.10.2.95
.1.3.6.1.4.1.2011.10.2.95.1
.1.3.6.1.4.1.2011.10.2.95.1.0
.1.3.6.1.4.1.2011.10.2.95.2
.1.3.6.1.4.1.2011.10.2.95.2.1
OctetString
.1.3.6.1.4.1.2011.10.2.95.2.2
.1.3.6.1.4.1.2011.10.2.95.2.3
Integer32
.1.3.6.1.4.1.2011.10.2.95.2.4
.1.3.6.1.4.1.2011.10.2.95.2.5
.1.3.6.1.4.1.2011.10.2.95.2.5.1
.1.3.6.1.4.1.2011.10.2.95.2.5.1.1
OctetString
.1.3.6.1.4.1.2011.10.2.95.2.5.1.2
.1.3.6.1.4.1.2011.10.2.95.2.5.1.3
.1.3.6.1.4.1.2011.10.2.95.2.5.1.4
Dependencies (18) 5 direct · 13 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
Type Definitions (1)
Enumeration
none(1)
block(2)
nolearning(3)
shutdown(4)
Notifications / Traps (4)
NameOIDDescription
.1.3.6.1.4.1.2011.10.2.95.1.0.1
Trap message is generated when the interface is looped.
.1.3.6.1.4.1.2011.10.2.95.1.0.2
Trap message is generated when the loops on the interface
are eliminated.
.1.3.6.1.4.1.2011.10.2.95.1.0.3
Trap message is generated when the interface is looped in the VLAN.
.1.3.6.1.4.1.2011.10.2.95.1.0.4
Trap message is generated when the loop on the interface
is eliminated in the VLAN.