FOUNDRY-BFD-STD-MIB

        Bidirectional Forwarding Management Information Base.
    
Source file
FOUNDRY-BFD-STD-MIB
Last revised
Identity
bfdMIB
Base OID
1.3.6.1.4.1.1991.3.3.1
Imported Objects
FOUNDRY-SN-ROOT-MIB bfd
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 brocade 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 'FOUNDRY-BFD-STD-MIB' -M '/opt/observium/mibs/brocade:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FOUNDRY-BFD-STD-MIB::bfdMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'FOUNDRY-BFD-STD-MIB' -M '/opt/observium/mibs/brocade:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'FOUNDRY-BFD-STD-MIB::bfdMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (48)
.1.3.6.1.4.1.1991.3.3.1
.1.3.6.1.4.1.1991.3.3.1.0
.1.3.6.1.4.1.1991.3.3.1.1
.1.3.6.1.4.1.1991.3.3.1.1.1
Enumeration
.1.3.6.1.4.1.1991.3.3.1.1.1.1
.1.3.6.1.4.1.1991.3.3.1.1.1.3
.1.3.6.1.4.1.1991.3.3.1.1.1.4
.1.3.6.1.4.1.1991.3.3.1.1.2
.1.3.6.1.4.1.1991.3.3.1.1.2.1
.1.3.6.1.4.1.1991.3.3.1.1.2.1.1
.1.3.6.1.4.1.1991.3.3.1.1.2.1.10
.1.3.6.1.4.1.1991.3.3.1.1.2.1.11
.1.3.6.1.4.1.1991.3.3.1.1.2.1.12
.1.3.6.1.4.1.1991.3.3.1.1.2.1.13
.1.3.6.1.4.1.1991.3.3.1.1.2.1.14
.1.3.6.1.4.1.1991.3.3.1.1.2.1.15
.1.3.6.1.4.1.1991.3.3.1.1.2.1.16
.1.3.6.1.4.1.1991.3.3.1.1.2.1.17
.1.3.6.1.4.1.1991.3.3.1.1.2.1.18
.1.3.6.1.4.1.1991.3.3.1.1.2.1.19
.1.3.6.1.4.1.1991.3.3.1.1.2.1.2
.1.3.6.1.4.1.1991.3.3.1.1.2.1.20
.1.3.6.1.4.1.1991.3.3.1.1.2.1.21
Enumeration
.1.3.6.1.4.1.1991.3.3.1.1.2.1.22
Unsigned32
.1.3.6.1.4.1.1991.3.3.1.1.2.1.3
Unsigned32
.1.3.6.1.4.1.1991.3.3.1.1.2.1.4
.1.3.6.1.4.1.1991.3.3.1.1.2.1.5
Enumeration
.1.3.6.1.4.1.1991.3.3.1.1.2.1.6
.1.3.6.1.4.1.1991.3.3.1.1.2.1.7
.1.3.6.1.4.1.1991.3.3.1.1.2.1.8
Enumeration
.1.3.6.1.4.1.1991.3.3.1.1.2.1.9
.1.3.6.1.4.1.1991.3.3.1.1.3
.1.3.6.1.4.1.1991.3.3.1.1.3.1
.1.3.6.1.4.1.1991.3.3.1.1.3.1.1
.1.3.6.1.4.1.1991.3.3.1.1.3.1.2
.1.3.6.1.4.1.1991.3.3.1.1.3.1.3
.1.3.6.1.4.1.1991.3.3.1.1.3.1.4
.1.3.6.1.4.1.1991.3.3.1.1.3.1.5
.1.3.6.1.4.1.1991.3.3.1.1.3.1.6
.1.3.6.1.4.1.1991.3.3.1.1.3.1.7
.1.3.6.1.4.1.1991.3.3.1.1.3.1.8
.1.3.6.1.4.1.1991.3.3.1.1.3.1.9
.1.3.6.1.4.1.1991.3.3.1.1.4
.1.3.6.1.4.1.1991.3.3.1.1.4.1
.1.3.6.1.4.1.1991.3.3.1.1.4.1.1
.1.3.6.1.4.1.1991.3.3.1.3
.1.3.6.1.4.1.1991.3.3.1.3.1
.1.3.6.1.4.1.1991.3.3.1.3.2
Dependencies (5) 5 direct 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. FOUNDRY-SN-ROOT-MIBbrocade
  3. SNMPv2-TCrfc
  4. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. FOUNDRY-BFD-STD-MIBbrocadeselected
Type Definitions (3)
Enumeration
noDiagnostic(1)
controlDetectionTimeExpired(2)
echoFunctionFailed(3)
neighborSignaledSessionDown(4)
forwardingPlaneReset(5)
pathDown(6)
concatenatedPathDown(7)
administrativelyDown(8)
reverseConcatenatedPathDown(9)
Unsigned32 range: 1..4294967295
Unsigned32 range: 1..4294967295
Compliance Statements (1)

OID .1.3.6.1.4.1.1991.3.3.1.3.2.1
Compliance statement for agents that provide full
support for BFD-MIB. Such devices can
then be monitored and also be configured using
this MIB module.
Required groups
mandatory bfdSessionGroup
mandatory bfdSessionPerfGroup
mandatory bfdSessionPerfHCGroup
mandatory bfdNotificationGroup
optional bfdSessionPerfHCGroup This group is mandatory for those bfdPerfTable
entries for which any of the objects
bfdSessPerfPktInHC or bfdSessPerfPktOutHC
wraps around too quickly
based on the criteria specified in RFC 2863 for
high-capacity counters.
optional bfdNotificationGroup This group is only mandatory for those
implementations which can efficiently implement
the notifications contained in this group.
Object refinements
ObjectAccessSyntaxDescription
bfdSessAddrType
unknown(0), ipv4(1), ipv6(2)
Only unknown(0), ipv4(1) and ipv6(2) support
is required.
bfdSessAddr 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.1991.3.3.1.0.1
This notification is generated when the
bfdSessState object for one or more contiguous
entries in bfdSessTable are about to enter the up(2)
state from some other state. The included values of
bfdSessDiag MUST both be set equal to this
new state (i.e: up(1)). The two instances of
bfdSessDiag 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(1) 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 bfdSessEntry, then
the instance identifier (and values) of the two
bfdSessDiag objects MUST be the identical.
.1.3.6.1.4.1.1991.3.3.1.0.2
This notification is generated when the
bfdSessState object for one or more contiguous
entries in bfdSessTable are about to enter the down(4)
or adminDown(5) states from some other state. The included
values of bfdSessDiag MUST both be set equal to this
new state (i.e: down(4) or adminDown(5)). The two instances
of bfdSessDiag 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(4) or adminDown(5) 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 bfdSessEntry, then
the instance identifier (and values) of the two
bfdSessDiag objects MUST be the identical.