OSPFv3 (respectively). The BFD protocol uses control packets and shorter detection
time limits to more rapidly detect failures in a network. Also, because they are
adjustable, you can modify the BFD timers for more or less aggressive failure
detection.
When you issue the
ip ospf bfd-liveness-detection
or
ipv6 ospf
bfd-liveness-detection
command on an OSPF peer, the peer establishes BFD liveness
detection with all BFD-enabled OSPF peers. When the local peer receives an update
from a remote OSPF peer—if BFD is enabled and if the session is not already
present—the local peer attempts to create a BFD session to the remote peer.
Each adjacent pair of peers negotiates an acceptable transmit interval for BFD packets.
The negotiated value can be different on each peer. Each peer then calculates a BFD
liveness detection interval. When a peer does not receive a BFD packet within the
detection interval, it declares the BFD session to be down and purges all routes
learned from the remote peer.
NOTE:
Before the router can use the
ip ospf bfd-liveness-detection
or
ipv6 ospf
bfd-liveness-detection
command, you must specify a BFD license key. To view an
already configured license, use the
show license bfd
command.
For general information about configuring and monitoring the BFD protocol, see
JUNOSe IP Services Configuration Guide
.
ip ospf bfd-liveness-detection
ipv6 ospf bfd-liveness-detection
■
Use to enable BFD (bidirectional forwarding detection) and define BFD values
to more quickly detect OSPFv2 or OSPFv3 data path failures.
■
The peers in an OSPF adjacency use the configured values to negotiate the actual
transmit intervals for BFD packets.
■
You can use the
minimum-transmit-interval
keyword to specify the interval
at which the local peer proposes to transmit BFD control packets to the
remote peer. The default value is 300 milliseconds.
■
You can use the
minimum-receive-interval
keyword to specify the minimum
interval at which the local peer must receive BFD control packets from the
remote peer. The default value is 300 milliseconds.
■
You can use the
minimum-interval
keyword to specify the same value for
both of those intervals. Configuring a minimum interval has the same effect
as configuring the minimum receive interval and the minimum transmit
interval to the same value. The default value is 300 milliseconds.
■
You can use the
multiplier
keyword to specify the detection multiplier value.
The calculated BFD liveness detection interval can be different on each peer.
The multiplier value is roughly equivalent to the number of packets that can be
missed before the BFD session is declared to be down. The default value is 3.
■
For details on liveness detection negotiation, see
JUNOSe IP Services Configuration
Guide
.
Configuring the BFD Protocol for OSPF
■
277
Chapter 5: Configuring OSPF
Summary of Contents for IGP - CONFIGURATION GUIDE V11.1.X
Page 6: ...vi...
Page 8: ...viii JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 18: ...xviii List of Figures JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 20: ...xx List of Tables JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 26: ...2 Internet Protocol JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 228: ...204 Internet Protocol Routing JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 264: ...240 Monitoring RIP JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 438: ...414 Monitoring IS IS JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 439: ...Part 3 Index Index on page 417 Index 415...
Page 440: ...416 Index JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...
Page 454: ...430 Index JUNOSe 11 0 x IP IPv6 and IGP Configuration Guide...