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

Configuration Guide - MPLS

S7700 and S9700 V200R010C00

This document describes MPLS configurations supported by the switch, including the principle and configuration procedures of static LSPs, MPLS LDP, MPLS TE, MPLS QoS, MPLS OAM, Seamless MPLS, and MPLS common features, and provides configuration examples.
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 Policy for Triggering LDP LSP Establishment

(Optional) Configuring a Policy for Triggering LDP LSP Establishment

Context

After MPLS LDP is enabled, LSPs are automatically established. If no policy is configured, an increasing number of LSPs are established, wasting resources.

  • Configure the lsp-trigger command on the ingress and egress nodes to trigger LSP setup based on routes. This setting controls the number of LSPs and saves network resources.

  • Configure the propagate mapping command on the transit node to allow LDP to use routes matching specified conditions to establish transit LSPs. For the routes that do not match specified conditions, the local device does not send Label Mapping messages to the upstream device, which reduces the number of LSPs and saves network resources.

By default, the lsp-trigger command is used. If policies cannot be configured on the ingress and egress nodes, configure the propagate mapping command.

NOTE:

A policy for triggering LSP establishment cannot be modified during the LDP graceful restart (GR) process.

Procedure

  • Perform the following steps on the ingress and egress nodes:
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      mpls

      The MPLS view is displayed.

    3. Run the following commands as required.

      • Run:

        lsp-trigger { all | host | ip-prefix ip-prefix-name | none }

        A policy for triggering LSP establishment based on static and IGP routes is configured.

        By default, the policy is host. This policy allows LDP to use 32-bit host-address routes ( except 32-bit host-address of interfaces ) to establish LSPs.

        NOTE:

        LSPs can be established using exactly matching routes on LSRs. For example, an exactly matching host route to an IP address with a 32-bit mask of a loopback interface can be used to trigger LSP establishment.

      • Run:

        lsp-trigger bgp-label-route [ ip-prefix ip-prefix-name ]

        A policy for triggering LSP establishment based on labeled public network BGP routes is configured.

        By default, LDP does not allocate labels to labeled BGP routes on the public network.

    4. Run:

      proxy-egress disable

      The device is disabled from establishing proxy egress LSPs.

      By default, a device is enabled to establish proxy egress LSPs.

      If a policy allows a device to use all static and IGP routes to establish LSPs or use an IP address prefix list to establish LSPs, the policy also triggers proxy egress LSP establishment. However, the proxy egress LSPs may be unavailable, which wastes system resources. To prevent this problem, run the proxy-egress disable command to disable a device from establishing such proxy egress LSPs.

  • Perform the following steps on the transit nodes:
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      mpls ldp

      The MPLS LDP view is displayed.

    3. Run:

      propagate mapping for ip-prefix ip-prefix-name

      A policy for triggering transit LSP establishment is configured.

      By default, LDP uses all routes without filtering them to establish transit LSPs.

Translation
Download
Updated: 2019-04-18

Document ID: EDOC1000141902

Views: 69217

Downloads: 189

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