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.


NE40E V800R010C00 Configuration Guide - MPLS 01

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 the Transit Node of the Static CR-LSP

(Optional) Configuring the Transit Node of the Static CR-LSP

This section describes how to configure the transit nodes of a static CR-LSP. Before you set up a static CR-LSP, specify the transit nodes of the CR-LSP. This procedure is optional because the CR-LSP may have no transit node.


If the static CR-LSP has only the ingress and egress, configuring a transit node is not needed. If the static CR-LSP has one or more transit nodes, perform the following steps on each transit node:


  1. Run:


    The system view is displayed.

  2. Run:

    static-cr-lsp transit lsp-name incoming-interface interface-type interface-number in-label in-label { nexthop next-hop-address | outgoing-interface interface-type interface-number } * out-label out-label [ ingress-lsrid ingress-lsrid egress-lsrid egress-lsrid tunnel-id tunnel-id ] [ bandwidth [ ct0 ] bandwidth ]

    The LSR is set as the transit node of the specified static CR-LSP.

    To modify all the parameters except lsp-name, run the static-cr-lsp transit command to set a new value. There is no need to run the undo static-cr-lsp transit command before changing a configured value.

    On the transit and egress nodes, the lsp-name parameter must be unique locally.

    If an Ethernet interface is used as an outbound interface, the nexthop next-hop-address parameter must be configured.

  3. Run:


    The configurations are committed.

Updated: 2018-07-12

Document ID: EDOC1100028530

Views: 101027

Downloads: 336

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