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 Configuration Guide - MPLS 01

This is NE20E-S V800R010C10SPC500 Configuration Guide - 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).
(Optional) Setting Leaf Switching and Deletion Delays

(Optional) Setting Leaf Switching and Deletion Delays

To prevent two copies of traffic on a P2MP TE tunnel's egress, a leaf CR-LSP switchover hold-off time and a deletion hold-off time can be set for MBB.

Context

Before the primary sub-LSP is deleted, both the primary sub-LSP and Modified sub-LSP carry traffic. If the egress cannot receive traffic only from one sub-LSP, two copies of traffic exist. To prevent two copies of traffic, perform the following steps to reset the leaf CR-LSP switchover hold-off time and deletion hold-off time.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run mpls

    MPLS is enabled globally and the MPLS view is displayed.

  3. Run mpls te

    MPLS TE is enabled globally.

    A leaf CR-LSP switchover hold-off time and deletion hold-off time can be set only after MPLS TE is enabled globally.

  4. Run mpls te p2mp-te leaf switch-delay delete-delay

    A leaf CR-LSP switchover hold-off time and deletion hold-off time are set.

    After the mpls te p2mp-te leaf switch-delay delete-delay command is run, traffic may be interrupted if an ingress is idle but the egress is busy. In this situation, either of the following may occur:
    • The Modified sub-LSP has been ready on the ingress and the primary sub-LSP has been deleted, but the Modified sub-LSP is not ready on the egress. If this occurs, when the ingress switches traffic to the Modified sub-LSP, traffic is temporarily interrupted.

    • The primary sub-LSP has been deleted, but the Modified sub-LSP failure message cannot be immediately sent to the ingress. If this occurs, traffic is temporarily interrupted.

  5. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055103

Views: 19794

Downloads: 35

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