targeted-session
config>router>ldp
This command configures targeted LDP sessions. Targeted sessions are LDP sessions between non-directly connected peers. Hello messages are sent directly to the peer platform instead of to all the routers on this subnet multicast address.
The discovery messages for an indirect LDP session are addressed to the specified peer and not to the multicast address.
n/a
[no] disable-targeted-session
config>router>ldp>targeted-session
This command disables support for targeted sessions. Targeted sessions are LDP sessions between non-directly connected peers. The discovery messages for an indirect LDP session are addressed to the specified peer and not to the multicast address.
The no form of the command enables the setup of any targeted sessions.
no disable-targeted-session
[no] peer ip-address
config>router>ldp>targeted-session
This command configures parameters for an LDP peer.
n/a
specifies the IPv4 or IPv6 address of the LDP peer in dotted-decimal notation
bfd-enable [ipv4][ipv6]
[no] bfd-enable
config>router>ldp>if-params>if
config>router>ldp>targeted-session>peer
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 therefore, 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.
n/a
local-lsr-id interface-name
no local-lsr-id
config>router>ldp>targeted-session>peer
This command enables the use of the address of a specific interface as the LSR ID 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 does 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 also goes 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.
The no form of the command resets the local-lsr-id to the default value, which means that the system interface address is used as the LSR ID.
no local-lsr-id
specifies the name, up to 32 characters in length, of the network IP interface. An interface name cannot be in the form of an IP address. If the string contains special characters (such as #, $, spaces), the entire string must be enclosed within double quotes.
[no] tunneling
config>router>ldp>targeted-session>peer
This command enables LDP over tunnels.
The no form of the command disables tunneling.
no tunneling
[no] lsp lsp-name
config>router>ldp>targeted-session>peer>tunneling
This command configures an LSP destined for this peer to be used for tunneling an LDP FEC over RSVP-TE. A maximum of four RSVP-TE LSPs can be used for tunneling LDP FECs to the T-LDP peer.
It is not necessary to specify any RSVP-TE LSP in this context unless there is a need to restrict the tunneling to selected LSPs. All RSVP-TE LSPs with a to address matching that of the T-LDP peer are eligible by default. The user can also exclude specific LSP names by using the ldp-over-rsvp exclude command in the config>router>mpls>lsp lsp-name context.
The no form of this command removes the LSP association.
specifies the name of the LSP