bfd-liveness-detection (Routing Options Static Route)
Syntax
bfd-liveness-detection {
description Site- xxx;
authentication {
algorithm algorithm-name;
key-chain key-chain-name;
loose-check;
}
detection-time {
threshold milliseconds;
}
echo
minimum-interval milliseconds
echo-lite
minimum-interval milliseconds
holddown-interval milliseconds;
local-address ip-address;
minimum-interval milliseconds;
minimum-receive-interval milliseconds;
minimum-receive-ttl number;
multiplier number;
neighbor address;
no-adaptation;
transmit-interval {
minimum-interval milliseconds;
threshold milliseconds;
}
version (1 | automatic);
}
Hierarchy Level
[edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static route destination-prefix], [edit logical-systems logical-system-name routing-instances routing-instance-name routing-options static route destination-prefix qualified-next-hop (interface-name | address)], [edit logical-systems logical-system-name routing-options rib routing-table-name static route destination-prefix], [edit logical-systems logical-system-name routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit logical-systems logical-system-name routing-options static route destination-prefix], [edit logical-systems logical-system-name routing-options static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix], [edit routing-instances routing-instance-name routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-instances routing-instance-name routing-options static route destination-prefix], [edit routing-instances routing-instance-name routing-options static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-options rib routing-table-name static route destination-prefix], [edit routing-options rib routing-table-name static route destination-prefix qualified-next-hop (interface-name | address)], [edit routing-options static route destination-prefix], [edit routing-options static route destination-prefix qualified-next-hop (interface-name | address)]
Description
Configure bidirectional failure detection timers and authentication criteria for static routes.
Options
authentication algorithm algorithm-name —Configure the algorithm used to authenticate the specified BFD session: simple-password, keyed-md5, keyed-sha-1, meticulous-keyed-md5, or meticulous-keyed-sha-1.
authentication key-chain key-chain-name—Associate a security key with the specified BFD session
using the name of the security keychain. The name you specify must
match one of the keychains configured in the authentication-key-chains
key-chain statement at the [edit security] hierarchy
level.
authentication loose-check—(Optional) Configure loose authentication checking on the BFD session. Use only for transitional periods when authentication may not be configured at both ends of the BFD session.
detection-time threshold milliseconds—Configure a threshold for the adaptation of the BFD session detection time. When the detection time adapts to a value equal to or greater than the threshold, a single trap and a single system log message are sent.
echo—(Optional) Enable BFD echo mode. This
feature sends BFD echo packets back and forth from a neighboring device to ensure
that a forwarding path is available. BFD echo mode only works if
the neighboring device supports BFD.
echo-lite—(Optional) Enable BFD echo-lite
mode. This feature performs the same funciton as BFD echo mode but
it works even if the neighboring device does not support BFD.
holddown-interval milliseconds—Configure an interval specifying how long a BFD session must remain up before a state change notification is sent. If the BFD session goes down and then comes back up during the hold-down interval, the timer is restarted.
Range: 0 through 255,000
Default: 0
local-address ip-address—Enable a multihop BFD session and configure the source address for the BFD session.
minimum-interval milliseconds—Configure
the minimum interval after which the local routing device transmits
a hello packet and then expects to receive a reply from the neighbor
with which it has established a BFD session. Optionally, instead of
using this statement, you can configure the minimum transmit and receive
intervals separately using the transmit-interval minimum-interval and minimum-receive-interval statements.
Range: 1 through 255,000
minimum-receive-interval milliseconds—Configure the minimum interval after which the routing
device expects to receive a reply from a neighbor with which it has
established a BFD session. Optionally, instead of using this statement,
you can configure the minimum receive interval using the minimum-interval statement at the [edit routing-options static route destination-prefix bfd-liveness-detection] hierarchy
level.
Range: 1 through 255,000
minimum-receive-ttl number—Configure the time to live (TTL) for the multihop BFD session.
Range: 1 through 255
Default: 255
multiplier number—Configure number of hello packets not received by the neighbor that causes the originating interface to be declared down.
Range: 1 through 255
Default: 3
neighbor address—Configure a next-hop address for the BFD session for a next hop specified as an interface name.
no-adaptation—Specify for BFD sessions not to adapt to changing network conditions. We recommend that you not disable BFD adaptation unless it is preferable not to have BFD adaptation enabled in your network.
transmit-interval threshold milliseconds—Configure the threshold for the adaptation of the BFD session transmit interval. When the transmit interval adapts to a value greater than the threshold, a single trap and a single system message are sent. The interval threshold must be greater than the minimum transmit interval.
Range: 0 through 4,294,967,295
transmit-interval minimum-interval milliseconds—Configure the minimum interval at which the routing device
transmits hello packets to a neighbor with which it has established
a BFD session. Optionally, instead of using this statement, you can
configure the minimum transmit interval using the minimum-interval statement at the [edit routing-options static route destination-prefix bfd-liveness-detection] hierarchy
level.
Range: 1 through 255,000
version—Configure the BFD version to detect: 1 (BFD version 1) or automatic (autodetect the BFD version).
Default: automatic
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced before Junos OS Release 7.4.
detection-time threshold and transmit-interval threshold options introduced in Junos OS Release 8.2.
local-address statement introduced in Junos OS Release 8.2.
minimum-receive-ttl statement introduced in Junos
OS Release 8.2.
Support for logical routers introduced in Junos OS Release 8.3.
holddown-interval statement introduced in Junos OS
Release 8.5.
no-adaptation statement introduced in Junos OS Release 9.0.
Support for IPv6 static routes introduced in Junos OS Release 9.1.
authentication algorithm, authentication key-chain, and authentication loose-check statements introduced
in Junos OS Release 9.6.
echo and echo-lite statements introduced in Junos
OS Release 22.4R1.