No relevant resource is found in the selected language.
Enterprise
Worldwide
Search
Support Documentation
CloudEngine 12800 V200R019C10 Configuration Guide - MPLS

This document describes the configurations of MPLS, including MPLS Basic, MPLS LDP, MPLS QoS, MPLS TE, and SR-MPLS TE.

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 an SR-MPLS BE Tunnel

Configuring an SR-MPLS BE Tunnel

Usage Scenario

SR-MPLS BE can be implemented after basic SR-MPLS BE functions are configured. After basic SR-MPLS BE functions are configured, you can configure optimization methods, for example, the policy for triggering SR-LSP setup and policy for preferentially selecting the SE-BE tunnel.

Creating an SR-MPLS BE tunnel involves the following operations:
  • Devices report topology information to a controller (if the controller is used to create a tunnel) and are assigned labels.
  • The devices compute paths.

Pre-configuration Tasks

Before configuring a manual SR-MPLS BE tunnel, complete the following tasks:

  • Configure IS-IS to implement network layer connectivity for LSRs.

  • Set an LSR ID for each LSR.

  • Enable MPLS globally on all LSRs.

Configuration Procedure

Configuring Basic SR-MPLS BE Functions

This section describes how to configure basic SR-MPLS BE functions.

Context

Basic SR-MPLS BE function configurations involve enabling the global segment routing capability, configuring the segment routing global block (SRGB), and setting a prefix segment ID (SID).

Procedure

  1. Globally enable the segment routing capability.
    1. Run system-view

      The system view is displayed.

    2. Run segment-routing

      The segment routing view is displayed.

    3. Run commit

      The configuration is committed.

  2. Configure an SRGB.
    1. Run system-view

      The system view is displayed.

    2. Run isis [ process-id ]

      The IS-IS view is displayed.

    3. Run network-entity net

      The network entity title (NET) is configured.

    4. Run cost-style { wide | compatible | wide-compatible }

      The IS-IS wide metric function is enabled.

    5. Run segment-routing mpls

      The segment routing function for an IS-IS process is enabled.

    6. Run segment-routing global-block begin-value end-value

      An SRGB is configured in an existing IS-IS instance.

    7. Run commit

      The configuration is committed.

  3. Set an SID.
    1. Run system-view

      The system view is displayed.

    2. Run interface loopback loopback-number

      A loopback interface is created, and the loopback interface view is displayed.

    3. Run isis enable [ process-id ]

      The IS-IS interface is enabled.

    4. Run ip address ip-address { mask | mask-length }

      The IP address is configured for the loopback interface.

    5. Run isis prefix-sid { absolute sid-value | index index-value } [ node-disable ]

      The prefix SID is set on the loopback interface.

    6. Run commit

      The configuration is committed.

(Optional) Configuring a Policy for Triggering SR-LSP Establishment

A policy can be configured to allow the ingress node to establish SR-LSPs based on eligible routes.

Context

After segment routing is enabled, a great number of devices establish excessive E2E LSPs, leading to resource wastes. To prevent resource wastes, a policy for establishing LSPs can be configured. The policy allows the ingress node to use only allowed routes to establish SR-LSPs.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run isis

    The IS-IS view is displayed.

  3. Run segment-routing lsp-trigger { none | host | ip-prefix ip-prefix-name }

    A policy for establishing SR-LSPs is configured on the ingress node.

    • host: The ingress node is allowed to use host IP routes with 32-bit masks to establish SR-LSPs.

    • ip-prefix: The ingress node is allowed to use FECs filtered by an IP address prefix list to establish SR-LSPs.

    • none: The ingress node is disabled from establishing SR-LSPs.

  4. Run commit

    The configuration is committed.

(Optional) Configuring a Policy for Preferentially Selecting an SR-MPLS BE Tunnel

By configuring a policy for preferentially selecting an SR-MPLS BE tunnel, you can improve the priority of the SR tunnel and preferentially select the SR tunnel.

Context

In a tunnel iteration scenario, an LDP tunnel is preferentially selected to forward traffic by default. To enable a device to preferentially select an SR-MPLS BE tunnel, improve the SR-MPLS BE tunnel priority so that the SR-MPLS BE tunnel takes preference over the LDP tunnel.

Procedure

  1. Run system-view

    The system view is displayed.

  2. Run segment-routing

    The segment routing view is displayed.

  3. Run tunnel-prefer segment-routing

    SR-MPLS TE tunnels are configured to take precedence over LDP tunnels.

  4. Run commit

    The configuration is committed.

Verifying the SR-MPLS BE Tunnel Configuration

After successfully configure SR-MPLS BE, you can view SR-MPLS BE configurations.

Prerequisites

The SR-MPLS BE functions have been configured.

Procedure

After completing the configurations, you can run the following commands to check the configurations.

  • Run the display isis lsdb [ { level-1 | level-2 } | verbose | { local | lsp-id | is-name symbolic-name } ] * [ process-id | vpn-instance vpn-instance-name ] command to check IS-IS LSDB information.

  • Run the display segment-routing prefix mpls forwarding command to check the label forwarding table for segment routing.
Translation
简体中文
Download
Updated: 2021-04-01

Document ID: EDOC1100138150

Views: 86629

Downloads: 115

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next

Copyright © 2023 Huawei Technologies Co., Ltd. All rights reserved.

You are going to visit :