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) Configuring a Transit Node of a Static Bidirectional Co-routed LSP

(Optional) Configuring a Transit Node of a Static Bidirectional Co-routed LSP

The transit node of a static bidirectional co-routed LSP needs to be manually specified. This configuration is optional because a static bidirectional co-routed LSP may have no transit node.

Context

Skip this procedure if a static bidirectional co-routed LSP has only an ingress and an egress. If a static bidirectional co-routed LSP has a transit node, perform the following steps on this transit node:

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run bidirectionalstatic-cr-lsp transit lsp-name

    A static bidirectional co-routed LSP is created, and the static bidirectional LSP view is displayed.

    lsp-name specified on a transit node or an egress cannot be the same as the existing tunnel name on the transit node or the egress.

  3. Run forward in-label in-label-value { nexthop next-hop-address | outgoing-interface interface-type interface-number } * out-label out-label-value [ ingress-lsrid ingress-lsrid egress-lsrid egress-lsrid tunnel-id tunnel-id ] [ bandwidth ct0 bandwidth ]

    A CR-LSP is configured on the transit node.

  4. Run backward in-label in-label-value { nexthop next-hop-address | outgoing-interface interface-type interface-number } * out-label out-label-value [ bandwidth ct0 bandwidth ]

    A reverse CR-LSP is configured on the transit node.

  5. (Optional) Run description text

    A description is configured for the static bidirectional co-routed CR-LSP.

  6. Run commit

    The configuration is committed.

Translation
Download
Updated: 2019-01-03

Document ID: EDOC1100055103

Views: 19373

Downloads: 35

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