Configure Bfd Over Bundles Cisco/Ietf Mode Support On A Per Bundle Basis - Cisco ASR 9000 Series Routing Configuration Manual

Configuring BFD on Bundle Member Links
Command or Action
Step 5
bfd minimum-interval milliseconds
Example:
RP/0/RSP0/CPU0:router(config)# bfd
minimum-interval 15
Step 6
bfd multiplier multiplier
Example:
RP/0/RSP0/CPU0:router(config)# bfd multiplier
2
Step 7 bfd address-family ipv4 destination ip-address
Example:
RP/0/RSP0/CPU0:router(config)# bfd
address-family ipv4 destination 10.20.20.1
Step 8 bfd address-family ipv4 timers start seconds
Example:
RP/0/RSP0/CPU0:router(config)# bfd
address-family ipv4 timers start 60
Step 9 bfd address-family ipv4 timers nbr-unconfig
seconds
Example:
RP/0/RSP0/CPU0:router(config)# bfd
address-family ipv4 timers nbr-unconfig 3600
Step 10
commit

Configure BFD over Bundles CISCO/IETF Mode Support on a Per Bundle Basis

To configure BFD over Bundles CISCO/IETF mode support on a per bundle basis use these steps:
Before You Begin
The BFD mode change (Cisco to IETF and vice-versa) goes through when a bundle is newly created or only
when the BFD state for the bundle is 'down' or 'BoB nonoperational.'
This procedure is applicable from release 5.3.1 onwards.
Note
Cisco ASR 9000 Series Aggregation Services Router Routing Configuration Guide, Release 5.3.x
268
Purpose
Sets the BFD minimum interval. Range is 15-30000
milliseconds.
Sets the BFD multiplier.
Specifies the primary IPv4 address assigned to the bundle
interface on a connected remote system, where ip-address
is the 32-bit IP address in dotted-decimal format (A.B.C.D).
Specifies the number of seconds after startup of a BFD
member link session to wait for the expected notification from
the BFD peer to be received, so that the session can be
declared up. If the state change notification is not received
after that period of time, the BFD session is declared down.
The range is 60 to 3600.
Specifies the number of seconds to wait after receipt of
notification that BFD configuration has been removed by a
BFD neighbor, so that any configuration inconsistency
between the BFD peers can be fixed. If the BFD configuration
issue is not resolved before the specified timer is reached, the
BFD session is declared down. The range is 30 to 3600.
Implementing BFD