SUPERMICRO-BFD-MI-MIB

        This proprietary MIB for BFD is to provide a proactive 
mechanism to detect faults using BFD in MPLS and MPLS-TP paths
when Multiple Instances of the router is supported.
    
Source file
SUPERMICRO-BFD-MI-MIB
Last revised
Identity
fsMIBfd
Base OID
1.3.6.1.4.1.10876.101.2.55
Net-SNMP examples using the supermicro 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 'SUPERMICRO-BFD-MI-MIB' -M '/opt/observium/mibs/supermicro:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SUPERMICRO-BFD-MI-MIB::fsMIBfd'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'SUPERMICRO-BFD-MI-MIB' -M '/opt/observium/mibs/supermicro:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SUPERMICRO-BFD-MI-MIB::fsMIBfd'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (50)
.1.3.6.1.4.1.10876.101.2.55
.1.3.6.1.4.1.10876.101.2.55.1
.1.3.6.1.4.1.10876.101.2.55.1.1
.1.3.6.1.4.1.10876.101.2.55.1.1.1
Enumeration
.1.3.6.1.4.1.10876.101.2.55.1.1.1.1
.1.3.6.1.4.1.10876.101.2.55.1.1.1.2
.1.3.6.1.4.1.10876.101.2.55.1.1.1.3
.1.3.6.1.4.1.10876.101.2.55.1.2
.1.3.6.1.4.1.10876.101.2.55.1.2.1
.1.3.6.1.4.1.10876.101.2.55.1.2.1.1
.1.3.6.1.4.1.10876.101.2.55.1.2.1.2
.1.3.6.1.4.1.10876.101.2.55.1.2.1.3
.1.3.6.1.4.1.10876.101.2.55.1.2.1.4
Unsigned32
.1.3.6.1.4.1.10876.101.2.55.1.2.1.5
.1.3.6.1.4.1.10876.101.2.55.1.3
.1.3.6.1.4.1.10876.101.2.55.1.3.1
.1.3.6.1.4.1.10876.101.2.55.1.3.1.1
.1.3.6.1.4.1.10876.101.2.55.1.3.1.2
.1.3.6.1.4.1.10876.101.2.55.1.3.1.3
.1.3.6.1.4.1.10876.101.2.55.1.3.1.4
.1.3.6.1.4.1.10876.101.2.55.2
.1.3.6.1.4.1.10876.101.2.55.2.1
.1.3.6.1.4.1.10876.101.2.55.2.1.1
Enumeration
.1.3.6.1.4.1.10876.101.2.55.2.1.1.1
.1.3.6.1.4.1.10876.101.2.55.2.1.1.10
.1.3.6.1.4.1.10876.101.2.55.2.1.1.11
.1.3.6.1.4.1.10876.101.2.55.2.1.1.12
.1.3.6.1.4.1.10876.101.2.55.2.1.1.13
.1.3.6.1.4.1.10876.101.2.55.2.1.1.14
Enumeration
.1.3.6.1.4.1.10876.101.2.55.2.1.1.2
Unsigned32
.1.3.6.1.4.1.10876.101.2.55.2.1.1.3
Unsigned32
.1.3.6.1.4.1.10876.101.2.55.2.1.1.4
.1.3.6.1.4.1.10876.101.2.55.2.1.1.5
.1.3.6.1.4.1.10876.101.2.55.2.1.1.6
Enumeration
.1.3.6.1.4.1.10876.101.2.55.2.1.1.7
.1.3.6.1.4.1.10876.101.2.55.2.1.1.8
Enumeration
.1.3.6.1.4.1.10876.101.2.55.2.1.1.9
.1.3.6.1.4.1.10876.101.2.55.2.2
.1.3.6.1.4.1.10876.101.2.55.2.2.1
.1.3.6.1.4.1.10876.101.2.55.2.2.1.1
.1.3.6.1.4.1.10876.101.2.55.2.2.1.2
.1.3.6.1.4.1.10876.101.2.55.2.2.1.3
.1.3.6.1.4.1.10876.101.2.55.2.2.1.4
.1.3.6.1.4.1.10876.101.2.55.2.2.1.5
.1.3.6.1.4.1.10876.101.2.55.2.2.1.6
.1.3.6.1.4.1.10876.101.2.55.2.2.1.7
.1.3.6.1.4.1.10876.101.2.55.2.2.1.8
.1.3.6.1.4.1.10876.101.2.55.2.2.1.9
.1.3.6.1.4.1.10876.101.2.55.3
.1.3.6.1.4.1.10876.101.2.55.3.0
Dependencies (9) 4 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
Type Definitions (1)
Enumeration
nonteipv4(1)
nonteipv6(2)
teipv4(3)
teipv6(4)
pw(5)
mep(6)
teipv4protection(7)
Notifications / Traps (3)
NameOIDDescription
.1.3.6.1.4.1.10876.101.2.55.3.0.1
This notification is generated when the BFD session establishment
bootstrap fails due to a failure in the LSP Ping bootstrap
request.
.1.3.6.1.4.1.10876.101.2.55.3.0.2
This notification is generated when the negotiated transmit
interval changes due to a change in the local DesiredMinTxInterval
value or remote RequiredMinRxInterval.
.1.3.6.1.4.1.10876.101.2.55.3.0.3
This notification is generated in case of an error detected in
the BFD sesion. For instance, when fsMIBfdSessTmrNegotiate is set
to false and the value of the received Desired min TX interval is
different from the locally configured reception period, or the
received value of the Detect Multiplier is different from the
locally configured one, a period misconfiguration defect will be
detected and this trap will be raised.

This notification is also generated when any failure occurs
during offloading of the BFD session. This includes failure in
transmission of packets in the Offload module when the same
is indicated to the control plane by the Offload module.