CISCO-IETF-BFD-MIB

Monitored by Observium
        This document contains the Management information base for
Bidirectional Forwarding Detection(BFD) Protocol as defined
in draft-ietf-bfd-base-06.txt.
        
BFD is a protocol intended to detect faults in the
bidirectional path between two forwarding engines, including
interfaces, data link(s), and to the extent possible the forwarding
engines themselves, with potentially very low latency.  It operates
independently of media, data protocols, and routing protocols.
        
This MIB module is based on the Internet Draft
draft-ietf-bfd-mib-03.txt and draft-ietf-bfd-mib-04.txt
    
Observium actively monitors this MIB
Observium uses this MIB in discovery or polling workflows on applicable devices.
Polling
Explore Observium network monitoring
Source file
CISCO-IETF-BFD-MIB
Last revised
Identity
ciscoIetfBfdMIB
Base OID
1.3.6.1.4.1.9.10.137
Imported Objects
CISCO-SMI ciscoExperiment
IF-MIB InterfaceIndex
INET-ADDRESS-MIB InetAddress InetAddressType InetPortNumber
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 Counter64 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC RowStatus StorageType TEXTUAL-CONVENTION (no object page) TimeStamp TruthValue
Net-SNMP examples using the cisco 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 'CISCO-IETF-BFD-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-IETF-BFD-MIB::ciscoIetfBfdMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-IETF-BFD-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-IETF-BFD-MIB::ciscoIetfBfdMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (57)
24 directly used by Observium
.1.3.6.1.4.1.9.10.137
.1.3.6.1.4.1.9.10.137.0
.1.3.6.1.4.1.9.10.137.1
.1.3.6.1.4.1.9.10.137.1.1
ciscoBfdAdminStatus OBS ✓ r/w
Enumeration
.1.3.6.1.4.1.9.10.137.1.1.1
.1.3.6.1.4.1.9.10.137.1.1.3
.1.3.6.1.4.1.9.10.137.1.1.4
.1.3.6.1.4.1.9.10.137.1.2
.1.3.6.1.4.1.9.10.137.1.2.1
.1.3.6.1.4.1.9.10.137.1.2.1.1
.1.3.6.1.4.1.9.10.137.1.2.1.10
.1.3.6.1.4.1.9.10.137.1.2.1.11
.1.3.6.1.4.1.9.10.137.1.2.1.12
ciscoBfdSessAddrType OBS ✓ r/w
.1.3.6.1.4.1.9.10.137.1.2.1.13
ciscoBfdSessAddr OBS ✓ r/w
.1.3.6.1.4.1.9.10.137.1.2.1.14
.1.3.6.1.4.1.9.10.137.1.2.1.15
.1.3.6.1.4.1.9.10.137.1.2.1.16
.1.3.6.1.4.1.9.10.137.1.2.1.17
.1.3.6.1.4.1.9.10.137.1.2.1.18
.1.3.6.1.4.1.9.10.137.1.2.1.19
.1.3.6.1.4.1.9.10.137.1.2.1.2
.1.3.6.1.4.1.9.10.137.1.2.1.20
.1.3.6.1.4.1.9.10.137.1.2.1.21
Enumeration
.1.3.6.1.4.1.9.10.137.1.2.1.22
.1.3.6.1.4.1.9.10.137.1.2.1.23
Enumeration
.1.3.6.1.4.1.9.10.137.1.2.1.24
.1.3.6.1.4.1.9.10.137.1.2.1.25
Unsigned32
.1.3.6.1.4.1.9.10.137.1.2.1.3
Unsigned32
.1.3.6.1.4.1.9.10.137.1.2.1.4
.1.3.6.1.4.1.9.10.137.1.2.1.5
Enumeration
.1.3.6.1.4.1.9.10.137.1.2.1.6
.1.3.6.1.4.1.9.10.137.1.2.1.7
.1.3.6.1.4.1.9.10.137.1.2.1.8
Enumeration
.1.3.6.1.4.1.9.10.137.1.2.1.9
.1.3.6.1.4.1.9.10.137.1.3
.1.3.6.1.4.1.9.10.137.1.3.1
.1.3.6.1.4.1.9.10.137.1.3.1.1
.1.3.6.1.4.1.9.10.137.1.3.1.2
.1.3.6.1.4.1.9.10.137.1.3.1.3
.1.3.6.1.4.1.9.10.137.1.3.1.4
.1.3.6.1.4.1.9.10.137.1.3.1.5
.1.3.6.1.4.1.9.10.137.1.3.1.6
.1.3.6.1.4.1.9.10.137.1.3.1.7
.1.3.6.1.4.1.9.10.137.1.3.1.8
.1.3.6.1.4.1.9.10.137.1.3.1.9
.1.3.6.1.4.1.9.10.137.1.4
.1.3.6.1.4.1.9.10.137.1.4.1
.1.3.6.1.4.1.9.10.137.1.4.1.1
.1.3.6.1.4.1.9.10.137.1.5
.1.3.6.1.4.1.9.10.137.1.5.1
.1.3.6.1.4.1.9.10.137.1.5.1.1
.1.3.6.1.4.1.9.10.137.1.6
.1.3.6.1.4.1.9.10.137.1.6.1
.1.3.6.1.4.1.9.10.137.1.6.1.1
.1.3.6.1.4.1.9.10.137.3
.1.3.6.1.4.1.9.10.137.3.1
.1.3.6.1.4.1.9.10.137.3.2
Dependencies (8) 6 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
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. IANAifType-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMPv2-MIBrfc
  7. IF-MIBrfc
  8. INET-ADDRESS-MIBrfc
  9. CISCO-IETF-BFD-MIBciscoselected
Type Definitions (3)
Enumeration
noDiagnostic(0)
controlDetectionTimeExpired(1)
echoFunctionFailed(2)
neighborSignaledSessionDown(3)
forwardingPlaneReset(4)
pathDown(5)
concatenatedPathDown(6)
administrativelyDown(7)
reverseConcatenatedPathDown(8)
Unsigned32 range: 0..4294967295
Unsigned32 range: 1..4294967295
Conformance Groups (7)
Collection of objects needed for BFD sessions.
.1.3.6.1.4.1.9.10.137.3.1.1
Collection of objects needed to monitor the
performance of BFD sessions.
.1.3.6.1.4.1.9.10.137.3.1.2
Collection of objects needed to monitor the
performance of BFD sessions for which the
values of ciscoBfdSessPerfPktIn, ciscoBfdSessPerfPktOut
wrap around too quickly.
.1.3.6.1.4.1.9.10.137.3.1.3
Set of notifications implemented in this
module.
.1.3.6.1.4.1.9.10.137.3.1.4
Collection of objects needed for BFD sessions for both
draft-ietf-bfd-mib-03.txt and draft-ietf-bfd-mib-04.txt.
.1.3.6.1.4.1.9.10.137.3.1.5
Collection of objects needed for BFD sessions to support
draft-ietf-bfd-mib-03.txt.
.1.3.6.1.4.1.9.10.137.3.1.6
Collection of objects needed for BFD sessions to support
draft-ietf-bfd-mib-04.txt.
.1.3.6.1.4.1.9.10.137.3.1.7
Compliance Statements (2)

OID .1.3.6.1.4.1.9.10.137.3.2.1
Compliance statement for agents that provide full
support for CISCO-IETF-BFD-MIB of draft-ietf-bfd-mib-03.txt.
Such devices can then be monitored and also be configured
using this MIB module. This compliance statement is
superceded by ciscoBfdModuleFullComplianceRev2.
Required groups
Object refinements
ObjectAccessSyntaxDescription
ciscoBfdSessAddrType
unknown(0), ipv4(1), ipv6(2)
Only unknown(0), ipv4(1) and ipv6(2) support
is required.
ciscoBfdSessAddr
An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes.

OID .1.3.6.1.4.1.9.10.137.3.2.2
Compliance statement for agents that provide full
support for CISCO-IETF-BFD-MIB of draft-ietf-bfd-mib-04.txt.
Such devices can then be monitored and also be configured
using this MIB module.
Required groups
mandatory ciscoBfdSession0304Group
mandatory ciscoBfdSessionPerfGroup
mandatory ciscoBfdSessionPerfHCGroup
mandatory ciscoBfdNotificationGroup
optional ciscoBfdSession03Group This group is mandatory only when draft-ietf-bfd-mib-03.txt
is implemented on the system.
optional ciscoBfdSession04Group This group is mandatory only when draft-ietf-bfd-mib-04.txt
is implemented on the system.
Object refinements
ObjectAccessSyntaxDescription
ciscoBfdSessAddrType
unknown(0), ipv4(1), ipv6(2)
Only unknown(0), ipv4(1) and ipv6(2) support
is required.
ciscoBfdSessAddr
An implementation is only required to support
unknown(0), ipv4(1) and ipv6(2) sizes.
Notifications / Traps (2)
NameOIDDescription
.1.3.6.1.4.1.9.10.137.0.1
This notification is generated when the
ciscoBfdSessState object for one or more contiguous
entries in ciscoBfdSessTable are about to enter the up(4)
state from some other state. The included values of
ciscoBfdSessDiag MUST both be set equal to this
new state (i.e: up(4)). The two instances of
ciscoBfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the
instance identifiers of these two objects. For the
cases where a contiguous range of sessions
have transitioned into the up(4) state at roughly
the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single ciscoBfdSessEntry, then
the instance identifier (and values) of the two
ciscoBfdSessDiag objects MUST be the identical.
.1.3.6.1.4.1.9.10.137.0.2
This notification is generated when the
ciscoBfdSessState object for one or more contiguous
entries in ciscoBfdSessTable are about to enter the down(2)
or adminDown(1) states from some other state. The included
values of ciscoBfdSessDiag MUST both be set equal to this
new state (i.e: down(2) or adminDown(1)). The two instances
of ciscoBfdSessDiag in this notification indicate the range
of indexes that are affected. Note that all the indexes
of the two ends of the range can be derived from the
instance identifiers of these two objects. For
cases where a contiguous range of sessions
have transitioned into the down(2) or adminDown(1) states
at roughly the same time, the device SHOULD issue a single
notification for each range of contiguous indexes in
an effort to minimize the emission of a large number
of notifications. If a notification has to be
issued for just a single ciscoBfdSessEntry, then
the instance identifier (and values) of the two
ciscoBfdSessDiag objects MUST be the identical.