bfd-liveness-detection (Layer 2 VPN and VPLS)
Syntax
bfd-liveness-detection {
detection-time {
threshold milliseconds;
}
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
multiplier number;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}
Hierarchy Level
[edit logical-system logical-system-name routing-instances routing-instance-name protocols l2vpn oam], [edit logical-system logical-system-name routing-instances routing-instance-name protocols vpls neighbor neighbor-id oam], [edit logical-system logical-system-name routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor neighbor-id oam], [edit logical-system logical-system-name routing-instances routing-instance-name protocols vpls oam], [edit routing-instances routing-instance-name protocols l2vpn oam], [edit routing-instances routing-instance-name protocols vpls neighbor neighbor-id oam], [edit routing-instances routing-instance-name protocols vpls mesh-group mesh-group-name neighbor neighbor-id oam], [edit routing-instances routing-instance-name protocols vpls oam]
Description
Configure bidirectional failure detection timers.
The BFD failure detection timers are adaptive and can be adjusted
to be more or less aggressive. For example, the timers can adapt to
a higher value if the adjacency fails, or a neighbor can negotiate
a higher value for a timer than the configured value. The timers adapt
to a higher value when a BFD session flap occurs more than three times
in a span of 15 seconds. A back-off algorithm increases the receive
(Rx) interval by two if the local BFD instance is the reason for the
session flap. The transmission (Tx) interval is increased by two if
the remote BFD instance is the reason for the session flap. You can
use the clear bfd adaptation command to return BFD interval
timers to their configured values. The clear bfd adaptation command is hitless, meaning that the command does not affect traffic
flow on the routing device.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 10.0.
Statement introduced in Junos OS Release 13.2 for Layer 2 VPNs and VPLS.