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).
Associated Bidirectional CR-LSPs

Associated Bidirectional CR-LSPs

Associated bidirectional CR-LSPs provide bandwidth protection for bidirectional services. Bidirectional switching can be performed for associated bidirectional CR-LSPs if faults occur.

Background

MPLS networks face the following challenges:
  • Traffic congestion: RSVP-TE tunnels are unidirectional. The ingress forwards services to the egress along an RSVP-TE tunnel. The egress forwards services to the ingress over IP routes. As a result, the services may be congested because IP links do not reserve bandwidth for these services.

  • Traffic interruptions: Two MPLS TE tunnels in opposite directions are established between the ingress and egress. If a fault occurs on an MPLS TE tunnel, a traffic switchover can only be performed for the faulty tunnel, but not for the reverse tunnel. As a result, traffic is interrupted.

A forward CR-LSP and a reverse CR-LSP between two nodes are established. Each CR-LSP is bound to the ingress of its reverse CR-LSP. The two CR-LSPs then form an associated bidirectional CR-LSP. The associated bidirectional CR-LSP is mainly used to prevent traffic congestion. If a fault occurs on one end, the other end is notified of the fault so that both ends trigger traffic switchovers, which traffic transmission is uninterrupted.

Implementation

Figure 4-42 illustrates an associated bidirectional CR-LSP that consists of Tunnel1 and Tunnel2. The implementation of the associated bidirectional CR-LSP is as follows:
  • MPLS TE Tunnel1 and Tunnel2 are established using RSVP-TE signaling or manually.

  • The tunnel ID and ingress LSR ID of the reverse CR-LSP are specified on each tunnel interface so that the forward and reverse CR-LSPs are bound to each other. For example, in Figure 4-42, set the reverse tunnel ID to 200 and ingress LSR ID to 4.4.4.4 on Tunnel1 so the reverse tunnel is bound to Tunnel1.

    NOTE:

    The ingress LSR ID of the reverse CR-LSP is the same as the egress LSR ID of the forward CR-LSP.

  • Penultimate hop popping (PHP) is not supported on associated bidirectional CR-LSPs.
    NOTE:

    The forward and reverse CR-LSPs can be established over the same path or over different paths. Establishing the forward and reverse CR-LSPs over the same path is recommended to implement the consistent delay time.

Figure 4-42 Associated bidirectional CR-LSP

Usage Scenario

  • An associated bidirectional static CR-LSP transmits services and returned OAM PDUs on MPLS networks.

  • An associated bidirectional dynamic CRLSP is used on an RSVP-TE network when bit-error-triggered switching is used.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055123

Views: 5912

Downloads: 21

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