Configuring Multiple Ldp Lsr Id - Alcatel-Lucent 7950 SR User Configuration Manual

Label Distribution Protocol
The user configures the FEC prefix export policy using the following command:
config>router>ldp>peer-parameters>peer>import-prefixes policy-name
By default, all FEC prefixes are imported from this peer.

Configuring Multiple LDP LSR ID

The multiple LDP LSR-ID feature provides the ability to configure and initiate multiple Targeted
LDP (T-LDP) sessions on the same system using different LDP LSR-IDs. In the current
implementation, all T-LDP sessions must have the LSR-ID match the system interface address.
This feature continues to allow the use of the system interface by default, but also any other
network interface, including a loopback, address on a per T-LDP session basis. Note that LDP
control plane will not allow more than a single T-LDP session with different local LSR ID values
to the same LSR-ID in a remote node.
An SDP of type LDP can use a provisioned targeted session with the local LSR-ID set to any
network IP for the T-LDP session to the peer matching the SDP far-end address. If, however, no
targeted session has been explicitly pre-provisioned to the far-end node under LDP, then the SDP
will auto-establish one but will use the system interface address as the local LSR-ID.
An SDP of type RSVP must use an RSVP LSP with the destination address matching the remote
node LDP LSR-ID. An SDP of type GRE can only use a T-LDP session with a local LSR-ID set to
the system interface.
The multiple LDP LSR-ID feature also provides the ability to use the address of the local LDP
interface, or any other network IP interface configured on the system, as the LSR-ID to establish
link LDP Hello adjacency and LDP session with directly connected LDP peers. The network
interface can be a loopback or not.
Link LDP sessions to all peers discovered over a given LDP interface share the same local LSR-
ID. However, LDP sessions on different LDP interfaces can use different network interface
addresses as their local LSR-ID.
By default, the link and targeted LDP sessions to a peer use the system interface address as the
LSR-ID unless explicitly configured using this feature. Note, however, that the system interface
must always be configured on the router or the LDP protocol will not come up on the node. There
is no requirement to include it in any routing protocol.
Note that when an interface other than system is used as the LSR-ID, the transport connection
(TCP) for the link or targeted LDP session will also use the address of that interface as the
transport address.
7950 SR OS MPLS Configuration Guide Page 335