Label Distribution Protocol
480
MPLS Guide
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com
3HE 18686 AAAB TQZZA
bfd-enable
Syntax bfd-enable [ipv4] [ipv6]
[no] bfd-enable
Context config>router>ldp>if-params>if
config>router>ldp>targeted-session>peer
Description This command enables or disables bidirectional forwarding detection (BFD) tracking of the
LDP session for the interface or the T-LDP session for the peer.
When BFD is enabled on an LDP interface, the system tracks the next hop of the IPv4 and
IPv6 prefixes in addition to tracking the LDP peer address of the Hello adjacency over that
link. This is required because LDP can resolve both IPv4 and IPv6 prefix FECs over a single
IPv4 or IPv6 LDP session and as such, the next hop of a prefix does not necessarily match
the LDP peer source address of the Hello adjacency.
The no form of the command disables BFD tracking.
Default n/a
local-lsr-id
Syntax local-lsr-id interface-name
no local-lsr-id
Context config>router>ldp>targeted-session>peer
Description This command enables the use of the address of a specific interface as the LSR ID in order
to establish a targeted LDP (T-LDP) adjacency and session with one or more non-directly
connected LDP peers. The interface can be a regular interface or a loopback interface,
including the system interface.
By default, a T-LDP session uses the system interface address as the LSR ID, unless the
LSR ID is explicitly configured. This means that T-LDP and interface LDP share a common
LDP TCP session and therefore a common LDP label space. The system interface must be
always be configured on the router or the LDP protocol will not come up on the node.
At initial configuration, the LDP session to the peers remains down while the interface is
down. If the user changes the LSR ID while the LDP session is up, LDP immediately tears
down the session and attempts to re-establish it using the new LSR ID. If the interface used
for the local LSR ID goes down, the LDP session to all peers using this LSR ID will also go
down.
The user-configured LSR ID is used for extended peer discovery to establish the T-LDP hello
adjacency. It is also used as the transport address for the LDP TCP session when it is
bootstrapped by the T-LDP hello adjacency. The user-configured LSR ID is not used in basic
peer discovery to establish a link-level LDP hello adjacency.
To Next Page
Loading...
Need help?
General
