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

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).
Configuring Leaf Lists

Configuring Leaf Lists

Configuring a leaf list on an ingress specifies all leaf nodes on a P2MP TE tunnel. A leaf list helps you configure and manage these leaf nodes uniformly. The steps in this section must be performed if P2MP TE tunnels are manually established. The steps in this section are optional if the establishment of P2MP TE tunnels is automatically triggered by a service.

Context

For a P2MP TE tunnel, the path that originates from the ingress and is destined for each leaf node can be calculated either by constraint shortest path first (CSPF) or by planning an explicit path for a specific leaf node or each leaf node. After each leaf node is configured on an ingress, the ingress sends signaling packets to each leaf node and then establishes a P2MP TE tunnel. The NE40E uses leaf lists to configure and manage leaf nodes. All leaf nodes and their explicit paths are integrated into a table, which helps you configure and manage the leaf nodes uniformly.

An MPLS network that transmits multicast services selects dynamically leaf nodes on an automatic P2MP TE tunnel and uses constrained shortest path first (CSPF) to calculate a path destined for each leaf node. To control the leaf nodes of an automatic P2MP TE tunnel, configure a leaf list.

Explicit path planning requires you to configure an explicit path for a specific leaf node or each leaf node, and use the explicit path in the leaf list view.

NOTE:

The configuration must prevent a remerge or crossover problem:

  • Remerge event: occurs when two sub-LSPs have different inbound interfaces but the same outbound interface on a transit node. Figure 3-6 shows that a remerge event occurs on the outbound interface shared by two sub-LSPs.
  • Crossover event: occurs when two sub-LSPs have different inbound and outbound interfaces on a transit node. Figure 3-6 shows that a crossover event occurs on the transit node shared by the two sub-LSPs.
Figure 3-6  Remerge and crossover events

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. (Optional) Configure an explicit path to each leaf node.
    1. Run:

      explicit-path path-name

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

    2. Run:

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

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

      You can configure either the include or include parameter:

    3. (Optional) Run:

      add hop ip-address1 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] * | exclude ] { after | before } ip-address2

      A node is added to the explicit path.

    4. (Optional) Run:

      modify hop ip-address1 ip-address2 [ include [ [ strict | loose ] | [ incoming | outgoing ] ] * | exclude ]

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

    5. (Optional) Run:

      delete hop ip-address

      A node is excluded from the explicit path.

    6. Run:

      commit

      The configuration is committed.

    7. Run:

      quit

      Return to the system view.

    For a P2MP TE tunnel, an explicit tunnel can be configured for a specific leaf node or each leaf node.

  3. Run:

    mpls te leaf-list leaf-list-name

    A leaf list is established for a P2MP RSVP-TE tunnel.

  4. Run:

    destination leaf-address

    A leaf node is established in the leaf list.

    The leaf-address parameter specifies the MPLS LSR ID of each leaf node.

  5. (Optional) Run:

    path explicit-path  path-name

    An explicit path is specified for the leaf node.

    The explicit-path path-name parameter specifies the name of the explicit path established in Step 2.

    NOTE:

    Repeat Step 3 and Step 4 on a P2MP TE tunnel to configure all leaf nodes.

  6. Run:

    commit

    The configuration is committed.

Download
Updated: 2018-07-12

Document ID: EDOC1100028530

Views: 101190

Downloads: 336

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