No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Feature Description - MPLS 01

NE05E and NE08E V300R003C10SPC500

This is NE05E and NE08E V300R003C10SPC500 Feature Description - MPLS
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
LDP Session Protection

LDP Session Protection

LDP session protection is an enhancement to the basic peer discovery mechanism. If the basic peer discovery mechanism fails, LDP session protection uses an extended peer discovery mechanism to maintain a session between LDP peers. After the basic peer discovery mechanism recovers, LDP can use it to rapidly converge routes and reestablish an LSP.


If a direct link for a local LDP session fails, the LDP adjacency is torn down, and the session and labels are deleted. After the direct link recovers, the local LDP session is reestablished and distributes labels so that an LSP can be reestablished over the session. Before the LSP is reestablished, however, LDP LSP traffic is dropped.

To speed up LDP LSP convergence and minimize packet loss, the NE implements LDP session protection.

LDP session protection helps maintain an LDP session, eliminating the need to reestablish an LDP session or re-distribute labels.


In Figure 3-7, LDP session protection is configured on the nodes at both ends of a link. The two nodes exchange Link Hello messages to establish a local LDP session and exchange Targeted Hello messages to establish a remote LDP session, forming a backup relationship between the remote LDP session and local LDP session.
Figure 3-7 LDP session protection

In Figure 3-7, if the direct link between LSRA and LSRB fails, the adjacency established using Link Hello messages is torn down. Because the indirectly connected link is working properly, the remote adjacency established using Targeted Hello messages remains. Therefore, the LDP session is maintained by the remote adjacency, and the mapping between FECs and labels for the session also remains. After the direct link recovers, the local LDP session can rapidly restore LSP information. There is no need to reestablish the LDP session or re-distribute labels, which minimizes the time required for LDP session convergence.

Session Hold Time

In addition to LDP session protection, a session hold time can be configured. After a local adjacency established using Link Hello messages is torn down, a remote adjacency established using Targeted Hello messages continues to maintain an LDP session within the configured session hold time. If the local adjacency does not recover after the session hold time elapses, the remote adjacency is torn down, and the LDP session maintained using the remote adjacency is also torn down. If the session hold time is not specified, the remote adjacency permanently maintains the LDP session.

Updated: 2019-01-14

Document ID: EDOC1100058933

Views: 9142

Downloads: 12

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next