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

Reminder

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

upgrade

Configuration Guide - MPLS

S7700 and S9700 V200R010C00

This document describes MPLS configurations supported by the switch, including the principle and configuration procedures of static LSPs, MPLS LDP, MPLS TE, MPLS QoS, MPLS OAM, Seamless MPLS, and MPLS common features, and provides configuration examples.
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).
Coexistent Local and Remote LDP Session

Coexistent Local and Remote LDP Session

When a local node establishes both local and remote LDP adjacencies with the same LDP peer, local and remote LDP sessions coexist.

Figure 3-5 shows a coexistent local and remote LDP session between two nodes.

Figure 3-5  Coexistent local and remote LDP session

In Figure 3-5, when the local LDP adjacency is deleted due to a failure in the link to which the adjacency is connected, the peer type may change without affecting its presence or status. (The peer type is determined by the adjacency type, which can be local, remote, and coexistent local and remote.) If the link becomes faulty or is recovering from a fault, the peer type and corresponding session type may change. The session however stays Up and is not deleted or set to Down.

A typical application of coexistent local and remote LDP session is Layer 2 virtual private network (L2VPN). In Figure 3-5, L2VPN services are transmitted between PE_1 and PE_2. When the direct link between PE_1 and PE_2 is disconnected and then recovers, changes in the peer and session types are as follows:

  1. MPLS LDP is enabled on the directly connected PE_1 and PE_2, and a local LDP session is set up between them. PE_1 and PE_2 are then configured as the remote peer of each other, and a remote LDP session is set up between them. PE_1 and PE_2 maintain both local and remote adjacencies. In this case, a coexistent local and remote LDP session is set up between PE_1 and PE_2 to transmit L2VPN messages.
  2. When the physical link between PE_1 and PE_2 goes Down, local LDP adjacency goes Down. The route between PE_1 and PE_2 is reachable through the P, which indicates that the remote LDP adjacency is still Up. The session type changes to remote so that it can remain Up. The L2VPN is uninformed of the session type change and does not delete the session. This avoids the neighbor disconnection and recovery process and therefore reduces service interruption time.
  3. When the physical link between PE_1 and PE_2 recovers, local LDP adjacency goes Up. The session type is restored to coexistent local and remote and remains Up. Again, L2VPN is uninformed of the session type change and does not delete the session. This reduces service interruption time.
Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141902

Views: 69767

Downloads: 189

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