CISCO-IETF-BFD-MIB

        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
    

Imported Objects

ciscoExperimentCISCO-SMI
InterfaceIndexIF-MIB
InetPortNumber, InetAddressType, InetAddressINET-ADDRESS-MIB
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUPSNMPv2-CONF
OBJECT-TYPE, NOTIFICATION-TYPE, Counter64, Counter32, Unsigned32, MODULE-IDENTITYSNMPv2-SMI
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TimeStampSNMPv2-TC

Type Definitions (3)

Name Base Type Values/Constraints
CiscoBfdDiagnoDiagnostic(0), controlDetectionTimeExpired(1), echoFunctionFailed(2), neighborSignaledSessionDown(3), forwardingPlaneReset(4), pathDown(5), concatenatedPathDown(6), administrativelyDown(7), reverseConcatenatedPathDown(8)
CiscoBfdIntervalrange: 0..4294967295
CiscoBfdSessIndexTCrange: 1..4294967295

Objects

ciscoIetfBfdMIB .1.3.6.1.4.1.9.10.137
ciscoBfdNotifications .1.3.6.1.4.1.9.10.137.0
ciscoBfdObjects .1.3.6.1.4.1.9.10.137.1
ciscoBfdScalarObjects .1.3.6.1.4.1.9.10.137.1.1
ciscoBfdAdminStatus .1.3.6.1.4.1.9.10.137.1.1.1
ciscoBfdVersionNumber .1.3.6.1.4.1.9.10.137.1.1.3
ciscoBfdSessNotificationsEnable
.1.3.6.1.4.1.9.10.137.1.1.4
ciscoBfdSessTable .1.3.6.1.4.1.9.10.137.1.2
ciscoBfdSessEntry .1.3.6.1.4.1.9.10.137.1.2.1
ciscoBfdSessIndex .1.3.6.1.4.1.9.10.137.1.2.1.1
ciscoBfdSessDemandModeDesiredFlag
.1.3.6.1.4.1.9.10.137.1.2.1.10
ciscoBfdSessEchoFuncModeDesiredFlag
.1.3.6.1.4.1.9.10.137.1.2.1.11
ciscoBfdSessControlPlanIndepFlag
.1.3.6.1.4.1.9.10.137.1.2.1.12
ciscoBfdSessAddrType
.1.3.6.1.4.1.9.10.137.1.2.1.13
ciscoBfdSessAddr
.1.3.6.1.4.1.9.10.137.1.2.1.14
ciscoBfdSessDesiredMinTxInterval .1.3.6.1.4.1.9.10.137.1.2.1.15
ciscoBfdSessReqMinRxInterval .1.3.6.1.4.1.9.10.137.1.2.1.16
ciscoBfdSessReqMinEchoRxInterval .1.3.6.1.4.1.9.10.137.1.2.1.17
ciscoBfdSessDetectMult .1.3.6.1.4.1.9.10.137.1.2.1.18
ciscoBfdSessStorType
.1.3.6.1.4.1.9.10.137.1.2.1.19
ciscoBfdSessApplicationId .1.3.6.1.4.1.9.10.137.1.2.1.2
ciscoBfdSessRowStatus
.1.3.6.1.4.1.9.10.137.1.2.1.20
ciscoBfdSessAuthPresFlag
.1.3.6.1.4.1.9.10.137.1.2.1.21
ciscoBfdSessAuthenticationType .1.3.6.1.4.1.9.10.137.1.2.1.22
ciscoBfdSessVersionNumber .1.3.6.1.4.1.9.10.137.1.2.1.23
ciscoBfdSessType .1.3.6.1.4.1.9.10.137.1.2.1.24
ciscoBfdSessInterface
.1.3.6.1.4.1.9.10.137.1.2.1.25
ciscoBfdSessDiscriminator .1.3.6.1.4.1.9.10.137.1.2.1.3
ciscoBfdSessRemoteDiscr .1.3.6.1.4.1.9.10.137.1.2.1.4
ciscoBfdSessUdpPort
.1.3.6.1.4.1.9.10.137.1.2.1.5
ciscoBfdSessState .1.3.6.1.4.1.9.10.137.1.2.1.6
ciscoBfdSessRemoteHeardFlag
.1.3.6.1.4.1.9.10.137.1.2.1.7
ciscoBfdSessDiag .1.3.6.1.4.1.9.10.137.1.2.1.8
ciscoBfdSessOperMode .1.3.6.1.4.1.9.10.137.1.2.1.9
ciscoBfdSessPerfTable .1.3.6.1.4.1.9.10.137.1.3
ciscoBfdSessPerfEntry .1.3.6.1.4.1.9.10.137.1.3.1
ciscoBfdSessPerfPktIn
.1.3.6.1.4.1.9.10.137.1.3.1.1
ciscoBfdSessPerfPktOut
.1.3.6.1.4.1.9.10.137.1.3.1.2
ciscoBfdSessUpTime
.1.3.6.1.4.1.9.10.137.1.3.1.3
ciscoBfdSessPerfLastSessDownTime
.1.3.6.1.4.1.9.10.137.1.3.1.4
ciscoBfdSessPerfLastCommLostDiag .1.3.6.1.4.1.9.10.137.1.3.1.5
ciscoBfdSessPerfSessUpCount
.1.3.6.1.4.1.9.10.137.1.3.1.6
ciscoBfdSessPerfDiscTime
.1.3.6.1.4.1.9.10.137.1.3.1.7
ciscoBfdSessPerfPktInHC
.1.3.6.1.4.1.9.10.137.1.3.1.8
ciscoBfdSessPerfPktOutHC
.1.3.6.1.4.1.9.10.137.1.3.1.9
ciscoBfdSessMapTable .1.3.6.1.4.1.9.10.137.1.4
ciscoBfdSessMapEntry .1.3.6.1.4.1.9.10.137.1.4.1
ciscoBfdSessMapBfdIndex .1.3.6.1.4.1.9.10.137.1.4.1.1
ciscoBfdSessDiscMapTable .1.3.6.1.4.1.9.10.137.1.5
ciscoBfdSessDiscMapEntry .1.3.6.1.4.1.9.10.137.1.5.1
ciscoBfdSessDiscMapIndex .1.3.6.1.4.1.9.10.137.1.5.1.1
ciscoBfdSessIpMapTable .1.3.6.1.4.1.9.10.137.1.6
ciscoBfdSessIpMapEntry .1.3.6.1.4.1.9.10.137.1.6.1
ciscoBfdSessIpMapIndex .1.3.6.1.4.1.9.10.137.1.6.1.1
ciscoBfdConformance .1.3.6.1.4.1.9.10.137.3
ciscoBfdGroups .1.3.6.1.4.1.9.10.137.3.1
ciscoBfdCompliances .1.3.6.1.4.1.9.10.137.3.2

Notifications/Traps

NameOIDDescription
ciscoBfdSessUp


.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.
ciscoBfdSessDown


.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.