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 |
ciscoExperiment | CISCO-SMI |
InterfaceIndex | IF-MIB |
InetPortNumber, InetAddressType, InetAddress | INET-ADDRESS-MIB |
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP | SNMPv2-CONF |
OBJECT-TYPE, NOTIFICATION-TYPE, Counter64, Counter32, Unsigned32, MODULE-IDENTITY | SNMPv2-SMI |
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TimeStamp | SNMPv2-TC |
Name | Base Type | Values/Constraints |
---|---|---|
noDiagnostic(0), controlDetectionTimeExpired(1), echoFunctionFailed(2), neighborSignaledSessionDown(3), forwardingPlaneReset(4), pathDown(5), concatenatedPathDown(6), administrativelyDown(7), reverseConcatenatedPathDown(8) | ||
range: 0..4294967295 | ||
range: 1..4294967295 |
![]() | .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 | |
![]() | .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 | |
![]() | .1.3.6.1.4.1.9.10.137.1.2.1.13 | |
![]() | .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 | |
![]() | .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 | |
![]() | .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 | |
![]() | .1.3.6.1.4.1.9.10.137.1.2.1.3 | |
![]() | .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 | |
![]() | .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 | |
![]() | .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 |
Name | OID | Description |
---|---|---|
.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. |