BFD can be configured under the LAG context to create and establish the micro-BFD session per link after the LAG and associated links have been configured. An IP interface must be associated with the LAG or a VLAN within the LAG, if dot1q encapsulation is used, before the micro-BFD sessions can be established.
Complete the following steps to enable and configure BFD over the individual LAG links:
When configuring the local and remote IP address for the BFD over LAG link sessions, the local-ip parameter should always match an IP address associated with the IP interface to which this LAG is bound. In addition, the remote-ip parameter should match an IP address on the remote system and should also be in the same subnet as the local-ip address. If the LAG bundle is re-associated with a different IP interface, the local-ip and remote-ip parameters should be modified to match the new IP subnet. The local-ip and remote-ip values do not have to match a configured interface in the case of tagged LAG/ports.
The optional parameters that can be configured for the BFD over LAG links include:
Transmit Interval
Receive Interval
Multiplier
Max-Wait-for-Up-Time, this parameter controls how long a link remains active if BFD is enabled after the LAG and associated links are active and in a forwarding state.
Max-Time-Admin-Down, this parameter controls how long the system waits before bringing the associated link out of service if an admin down message is received from the far-end.
The following is an example configuration:
*A:Dut-C>config>lag# info
----------------------------------------------
bfd
family ipv4
local-ip-address 10.120.1.2
receive-interval 1000
remote-ip-address 10.120.1.1
transmit-interval 1000
no shutdown
exit
exit
no shutdown