Manual:Routing/BFD: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
==Summary== | ==Summary== | ||
BFD is a protocol intended to detect faults in the | Bidirectional Forwarding Detection (BFD) is a 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, | ||
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. | 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. | |||
==Requirements== | ==Requirements== | ||
| Line 20: | Line 10: | ||
==Features supported== | ==Features supported== | ||
* asynchronous mode (draft-ietf-bfd-base-09.txt) | * asynchronous mode ([http://tools.ietf.org/html/draft-ietf-bfd-base-09/draft-ietf-bfd-base-09.txt]) | ||
* BFD timer and detection multiplier configuration per interface; | * BFD timer and detection multiplier configuration per interface; | ||
* enabling BFD for OSPF interfaces | * enabling BFD for OSPF interfaces | ||
* enabling BFD for BGP peers | * enabling BFD for BGP peers | ||
* single hop IPv4 and IPv6 transport (draft-ietf-bfd-v4v6-1hop-10.txt) | * single hop IPv4 and IPv6 transport ([http://tools.ietf.org/html/draft-ietf-bfd-base-09/draft-ietf-bfd-v4v6-1hop-10.txt]) | ||
* multihop IPv4 and IPv6 transport (draft-ietf-bfd-multihop-08.txt) | * multihop IPv4 and IPv6 transport ([http://tools.ietf.org/html/draft-ietf-bfd-base-09/draft-ietf-bfd-multihop-08.txt]) | ||
==Features not yet supported== | |||
* echo function | |||
* on-demand mode | |||
* authentication | |||
==Configuration== | ==Configuration== | ||
| Line 39: | Line 34: | ||
====BFD neighbor status==== | ====BFD neighbor status==== | ||
/routing bfd neighbor | /routing bfd neighbor | ||
==Interoperability == | |||
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, in interface configuration mode type: | |||
no bfd echo | |||
[[Category:Manual]] | [[Category:Manual]] | ||
Revision as of 15:44, 22 December 2009
Summary
Bidirectional Forwarding Detection (BFD) is a 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.
Requirements
RouterOS 4.4 or newer with routing package installed.
Features supported
- asynchronous mode ([1])
- BFD timer and detection multiplier configuration per interface;
- enabling BFD for OSPF interfaces
- enabling BFD for BGP peers
- single hop IPv4 and IPv6 transport ([2])
- multihop IPv4 and IPv6 transport ([3])
Features not yet supported
- echo function
- on-demand mode
- authentication
Configuration
BFD configuration should be added in different places as required
OSPF
/routing ospf interface add interface=all use-bfd=yes
BGP
/routing bgp peer add remote-address=x.x.x.x remote-as=xxxxx use-bfd=yes
BFD timer configuration
/routing bfd interface
BFD neighbor status
/routing bfd neighbor
Interoperability
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, in interface configuration mode type:
no bfd echo