Bidirectional Forwarding Detection (BFD) is a low-overhead and short-duration protocol intended to detect faults in the bidirectional path between two forwarding engines, including physical interfaces, sub-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.
BFD is basically a hello protocol for checking bidirectional neighbor reachability. It provides sub-second link failure detection support. BFD is not routing protocol specific, unlike protocol hello timers or such.
BFD Control packets is transmitted in UDP packets with destination port 3784. Source port is in the range 49152 through 65535. And BFD Echo packets are encapsulated in UDP packet with destination port 3785.
Standards and Technologies:
- RFC 5880 Bidirectional Forwarding Detection (BFD)
- RFC 5881 BFD for IPv4 and IPv6 (Single Hop)
- RFC 5882 Generic Application of BFD (Single Hop)
RouterOS 4.4 or newer with routing package installed.
- asynchronous mode 
- BFD timer and detection multiplier configuration per interface;
- enabling BFD for OSPF interfaces
- enabling BFD for BGP peers
- single hop IPv4 and IPv6 transport 
- multihop IPv4 and IPv6 transport 
Features not yet supported
- echo function
- on-demand mode
BFD configuration should be added in different places as required
BFD timer configuration
/routing bfd interface
|interface (string; Default: )||Interface name to which BFD timers will be applied|
|interval (decimal [0.01 .. 10]sec; Default: 0.2sec)||Desired rate at which BFD Control packets should be transmitted to the remote system.|
|min-rx (decimal [0.01..10]sec; Default: 0.2sec)||Min interval desired between received BFD packets|
|multiplier (integer [1..100]; Default: 5)||The negotiated Control packet transmission interval, multiplied by this variable, will be the Detection Time for the session.|
BFD neighbor status
/routing bfd neighbor
|actual-tx-interval (decimal)||Actual rate at which BFD Control packets are transmitted|
|address (IP | IPv6)||IP/IPv6 address of the neighbor|
|desired-tx-interval (decimal)||The minimum interval between transmitted BFD Control packets that this system would like to use.|
|interface (string)||interface name on which BFD neighbor is reachable|
|multihop (yes | no)||Whether neighbor is multiple hops away|
|multiplier (integer)||Desired Detection Time multiplier for BFD Control packets on the local system|
|packets-rx (integer)||Number of received packets|
|protocols (ospf | bgp)||For which protocols BFD is used, currently only OSPF and BGP are possible.|
|remote-min-rx (decimal)||The last value of Required Min RX Interval received from the remote system in a BFD Control packet|
|required-min-rx (decimal)||The minimum interval between received BFD Control packets that this system requires.|
|state (up | down)||Shows the current BFD session state|
|state-changes (integer)||Number of state changes occurred between the neighbors|
|up (yes | no)||Whether link to the neighbor is up|
|uptime (time)||Link uptime|
Example of BFD neighbor. Neighbor is used by OSPF and is directly connected.
[admin@R3-493G] /routing bfd neighbor> print detail Flags: U - up 0 U state=up address=10.5.101.1 interface=ether1 protocols=ospf multihop=no state-changes=1 uptime=12s desired-tx-interval=0.2sec actual-tx-interval=0.2sec required-min-rx=0.2sec remote-min-rx=0.2sec multiplier=5 hold-time=1sec packets-rx=76 packets-tx=77
There is only one parameter per OSPF interface to enable BFD
/routing ospf interface add interface=all use-bfd=yes
Similar to OSPF, only one option per BGP peer to enable BFD
/routing bgp peer add remote-address=x.x.x.x remote-as=xxxxx use-bfd=yes
For interoperability with Cisco make sure to disable echo mode (it is enabled on Cisco by default), since it's not supported on MT.
To do that, on Cisco in interface configuration mode type:
no bfd echo