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

NE20E-S V800R010C10SPC500 Feature Description - MPLS 01

This is NE20E-S V800R010C10SPC500 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).
mLDP FRR Link Protection

mLDP FRR Link Protection

mLDP fast reroute (FRR) is a protection technique for mLDP LSPs. It consists of node protection and link protection. In this section, link protection is described.

Background

With the growth of user services, the demands for using mLDP LSPs to carry multicast traffic are increasing. Therefore, mLDP LSP protection techniques become increasingly important. In implementation of a mLDP LSP protection technique, an mLDP FRR LSP can be established if routes are reachable and the downstream outbound interface of an mLDP LSP is not co-routed with the outbound interface of the primary mLDP LSP. mLDP FRR link protection is implemented using the primary route to a downstream device, LFA FRR route, RLFA FRR route, or multi-link method, which improves user network reliability.

NOTE:
mLDP P2MP FRR link protection does not support backup links on a TE tunnel.

Related Concepts

  • DS node: downstream node
  • US node: Upstream node

Implementation

An upstream node generates an mLDP FRR path for each outbound interface of an mLDP LSP. If the outbound interface of the primary LSP fails, the forwarding plane rapidly switches traffic to the mLDP FRR path to a directly connected downstream LDP peer, which protects traffic on the primary LSP.

The mLDP FRR path transmits traffic over a P2P LDP LSP that is destined for a directly connected downstream peer. When traffic passes through the mLDP FRR path, the inner label is the outgoing label mapped to the original primary P2MP LDP LSP, and the outer label is the outgoing label of a P2P LDP LSP. After traffic arrives at the downstream directly connected LDP peer, the peer removes the P2P LDP label and swaps the inner P2MP LDP label with another label before forwarding the traffic downstream. An mLDP FRR path is selected based on the following rules:
  • An mLDP FRR path has P2P LDP labels and its destination is the downstream directly connected LDP peer.
  • The outbound interface of a P2P LDP LSP is different from the outbound interface of the primary LDP LSP.
NOTE:
mLDP FRR link protection only protects traffic on the outbound interface of the primary mLDP LSP.

A link fault on the primary mLDP LSP triggers protocol convergence on the control plane. To minimize packet loss during the convergence, configure LDP session protection and mLDP MBB.

On the triangle network shown in Figure 3-28, if a fault occurs on the link between the upstream and downstream nodes, link protection on the mLDP LSP perform the following convergence functions:
  • After the upstream node detects the link fault, the forwarding plane rapidly switches traffic. A P2P LDP label is added to the outbound label of the original primary mLDP LSP in each packet. The packet is forwarded by the P to the downstream node. After the downstream node removes the P2P LDP label, the node swaps the mLDP LSP outgoing label with another label before sending the packet downstream.
  • Without mLDP FRR link protection, the LDP session protection must be enabled for the path between the upstream and downstream nodes to prevent an LDP session disconnection temporarily from link faults. In this situation, the downstream node does not send a request to withdraw a label to the upstream node, and the upstream node does not tear down forwarding entries immediately.
  • Without mLDP FRR link protection, mLDP MBB must have been enabled on a device. Once the control plane detects a fault, the downstream node identifies the change in the next hop of a route to the root node and enters the MBB process. After the DS node-P-US node path is established, the downstream node receives traffic sent only by the new upstream P node to complete the convergence process.
Figure 3-28 Triangle networking

Usage Scenarios

  • Figure 3-28 shows the typical triangle networking.

  • Figure 3-29 shows the typical four-point ring networking. If an RLFA route to the downstream node is used and the outbound interface of the RLFA FRR route differs from the outbound interface of the primary LSP, the upstream node selects the RLFA FRR path as a backup path.

    Figure 3-29 Typical four-point ring networking.
  • Figure 3-30 shows typical multi-link networking.
    • If multiple links load-balance traffic, the upstream node selects a load-balancing link as a protection path, but does not select the outbound interface of the primary mLDP LSP.
    • If multi-link routes form an LFA FRR path, the upstream node selects a protection path in the same way as that in the typical triangle networking.
    • If one of multiple links has an active route and FRR is disabled, the upstream node selects one of multi-link interfaces as a protection path, but does not select the outbound interface of the primary mLDP LSP.
    Figure 3-30 Typical multi-link networking

Benefits

mLDP LSP link protection offers the following benefits:
  • Reduces bandwidth consumption.

  • Reduces deployment costs.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055123

Views: 5882

Downloads: 21

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