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.


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 an Explicit Path

(Optional) Configuring an Explicit Path

An explicit path is configured on the ingress of an MPLS TE tunnel. It defines the nodes through which the MPLS TE tunnel must pass or the nodes that are excluded from the MPLS TE tunnel.


An explicit path consists of a series of nodes. These nodes are arranged in sequence and form a vector path. An interface IP address on every node is used to identify the node on an explicit path. The loopback IP address of the egress node is usually used as the destination address of an explicit path.

Two adjacent nodes are connected in either of the following modes on an explicit path:

  • Strict: A hop is directly connected to its next hop.

  • Loose: Other nodes may exist between a hop and its next hop.

The strict and loose modes are used either separately or simultaneously.

TE tunnels are classified as intra-area tunnels and inter-area tunnels. In this situation, areas indicate OSPF and IS-IS areas, but not an autonomous system (AS) running the Border Gateway Protocol (BGP). OSPF areas are divided based on different area IDs while IS-IS areas are divided based on different levels.

  • Intra-area tunnel: is a TE tunnel in a single OSPF or IS-IS area. An intra-area tunnel can be established over a strict or loose explicit path.

  • Inter-area tunnel: is a TE tunnel traversing multiple OSPF or IS-IS areas. An explicit path must be used to establish an inter-area TE tunnel and an ABR or an Autonomous System Boundary Router (ASBR) must be included in the explicit path.

The explicit path in use can be updated.


  1. Run system-view

    The system view is displayed.

  2. Run explicit-path path-name

    An explicit path is created and the explicit path view is displayed.

  3. Run next hop ip-address [ include [ [ strict | loose ] | [ incoming | outgoing ] ] * | exclude ]

    The next-hop address is specified for the explicit path.

    The include parameter indicates that the tunnel does pass through a specified node; the exclude parameter indicates that the tunnel does not pass through a specified node.

  4. (Optional) Run add hop ip-address1 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] * | exclude ] { after | before } ip-address2

    A node is added to the explicit path.

  5. (Optional) Run modify hop ip-address1 ip-address2 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] * | exclude ]

    The address of a node on an explicit path is changed.

  6. (Optional) Run delete hop ip-address

    A node is removed from an explicit path.

  7. (Optional) Run list hop [ ip-address ]

    Information about nodes on an explicit path is displayed.

  8. Run commit

    The configurations are committed.

Updated: 2019-01-03

Document ID: EDOC1100055103

Views: 20120

Downloads: 35

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