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 auto fast reroute (FRR) backs up local interfaces to provide the fast reroute function for MPLS networks.


On an MPLS network with both active and standby links, if an active link fails, IGP routes re-converge, and the IGP route of the standby link becomes reachable. An LDP LSP over the standby link is then established. During this process, some traffic is lost. To minimize traffic loss, LDP Auto FRR is used.

On the network enabled with LDP Auto FRR, if an interface failure (detected by the interface itself or by an associated BFD session) or a primary LSP failure (detected by an associated BFD session) occurs, LDP FRR is notified of the failure and rapidly forwards traffic to a backup LSP, protecting traffic on the primary LSP. The traffic switchover minimizes the traffic interruption time.



LDP LFA FRR is implemented based on IGP LFA FRR's LDP Auto FRR. LDP LFA FRR uses the liberal label retention mode to obtain a liberal label, applies for a forwarding entry associated with the label, and forwards the forwarding entry to the forwarding plane as a backup forwarding entry to be used by the primary LSP. If an interface detects a failure of its own, bidirectional forwarding detection (BFD) detects an interface failure, or BFD detects a primary LSP failure, LDP LFA FRR rapidly switches traffic to a backup LSP to protect traffic on the primary LSP.

Figure 3-8 Typical usage scenario for LDP Auto FRR (triangle topology)
Figure 3-8 shows a typical usage scenario for LDP Auto FRR. The preferred LSRA-to-LSRB route is LSRA-LSRB and the second optimal route is LSRA-LSRC-LSRB. A primary LSP between LSRA and LSRB is established on LSRA, and a backup LSP of LSRA-LSRC-LSRB is established to protect the primary LSP. After receiving a label from LSRC, LSRA compares the label with the LSRA-to-LSRB route. Because the next hop of the LSRA-to-LSRB route is not LSRC, LSRA preserves the label as a liberal label.

If the backup route corresponding to the source of the liberal label for LDP auto FRR exists, and its destination meets the policy for LDP to create a backup LSP. LSRA can apply a forwarding entry for the liberal label, establish a backup LSP as the backup forwarding entry of the primary LSP, and send the entries mapped to both the primary and backup LSPs to the forwarding plane. In this way, the primary LSP is associated with the backup LSP.

LDP Auto FRR is triggered when the interface detects faults by itself, BFD detects faults in the interface, or BFD detects a primary LSP failure. After LSP FRR is complete, traffic is switched to the backup LSP based on the backup forwarding entry. Then, the route is converged to LSRA-LSRC-LSRB. An LSP is established on the new LSP (the original backup LSP), and the original primary LSP is torn down, and then the traffic is forwarded along the new LSP over the path LSRA-LSRC-LSRB.


LDP LFA FRR cannot calculate backup paths on large networks, especially ring networks, which fails to meet reliability requirements. To address this issue, LDP Remote LFA FRR is used. Remote LFA FRR is implemented based on IGP Remote LFA FRR's (IS-IS Auto FRR) LDP Auto FRR. Figure 3-9 illustrates the typical LDP Auto FRR usage scenario. The primary LDP LSP is established over the path PE1 -> PE2. Remote LFA FRR establishes a Remote LFA FRR LSP over the path PE1 -> P2 -> PE2 to protect the primary LDP LSP.
Figure 3-9 Typical LDP Auto FRR usage scenario - ring topology
The implementation is as follows:
  1. An IGP uses the Remote LFA algorithm to calculate a Remote LFA route with the PQ node (P2) IP address and the iterated outbound interface's next hop and then notifies the route management module of the information. For the PQ node definition, see IS-IS Auto FRR.
  2. LDP obtains the Remote LFA route from the route management module. PE1 automatically establishes a remote LDP peer relationship with the PQ node and a remote LDP session for the relationship. PE1 then establishes an LDP LSP to the PQ node and a Remote LFA FRR LSP over the path PE1 -> P2 -> PE2. For information about how to automatically establish a remote LDP session, see LDP Session.
  3. LDP-enabled PE1 establishes an LDP LSP over the path PE1 -> P1 -> P2 with the iterated outbound interface's next hop. This LSP is called a Remote LFA FRR iterated LSP.
If PE1 detects a fault, PE1 rapidly switches traffic to the Remote LFA FRR LSP.
Updated: 2019-01-14

Document ID: EDOC1100058933

Views: 11211

Downloads: 12

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next