(Optional) Configuring an LSR ID for a Local LDP Session

Procedure

1. Run system-view

   The system view is displayed.

2. Run interface interface-type interface-number

   The view of the interface on which an LDP session is to be established is displayed.

3. Run mpls ldp local-lsr-id { interface-type interface-number | interface }

   The primary IP address of a specified interface is used as a local LSR ID for the current LDP session.

   You can specify either of the following parameters in this command:

   • interface-type interface-number: uses the primary IP address of a specified interface as a local LSR ID.

   • interface: uses the primary IP address of the current interface as a local LSR ID.

   If multiple links directly connect an LSR pair, the LSR ID configured on the interface of each link must be the same. Otherwise, the LDP session uses the LSR ID of the link that finds the adjacency first while other links with different LSR IDs cannot be bound to the LDP session. As a result, LDP LSP fails to be established on these links.

   If both a local session and a remote LDP session are to be established between an LSR pair, LSR IDs configured for the two sessions must be the same. Otherwise, only the LDP session that finds the adjacency first can be established.

   

   A TCP link must be established between two devices that establish an LDP session. This link is the adjacency. After an adjacency is established, the two devices exchange LDP control messages to establish an LDP session. If an LDP session has only one adjacency, it is called a single-link session. An LDP session with multiple adjacencies is called a multi-link session.

   Running the mpls ldp local-lsr-id command causes a single-link LDP session to reset or causes the current adjacency of a multi-link LDP session to reset.

4. Run commit

   The configuration is committed.