lsp-trigger (MPLS view)

Function

The lsp-trigger command configures a policy for establishing LDP LSPs.

The undo lsp-trigger command restores the default policy.

By default, LDP uses IP routes with 32-bit addresses to establish LSPs.

Format

lsp-trigger { all | host | none }

lsp-trigger ip-prefix ip-prefix-name

undo lsp-trigger

Parameters

Parameter	Description	Value
all	Uses all static and IGP routes to establish LSPs.	-
host	Uses IP routes with 32-bit addresses to establish LSPs.	-
none	Does not allow LDP to establish LSPs.	-
ip-prefix ip-prefix-name	Uses routes matching the IP prefix list to establish LSPs.	The name is a string of 1 to 169 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

MPLS view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
mpls-ldp	write

Usage Guidelines

Usage Scenario

An MPLS LDP-enabled device automatically establishes a large number of LSPs, which wastes resources.

The lsp-trigger command can be run to configure a policy for establishing LSPs. LDP can only use specified routes to establish LSPs, reducing LSPs to be established and system resource consumption.

NOTE:

By default, IP routes with 32-bit addresses trigger LDP to set up LSPs. The default setting is recommended. The lsp-trigger all command is not recommended. The all parameter allows LDP to use static routes and IGP routes to establish LSPs, which consumes a lot of label resources and causes LSP convergence slowdown on an MPLS network. Before using the lsp-trigger all command, configure a policy for filtering out routes so that LDP does not use them to establish LSPs. This helps reduce the number of LSPs to be established and efficiently use system resources.
If the lsp-trigger all command is run and some IGP routes are available and are not used to existing MPLS LDP sessions, the system uses the routes to create proxy egress LSPs.

Prerequisites

MPLS has been enabled globally using the mpls command in the system view.

Precautions

The lsp-trigger command can be used to configure policies only for ingress and egress LSPs on the public network and ingress and egress LSPs on the private network that are established using IGP routes. To configure a policy for triggering the transit LSP establishment, run the propagate mapping command.

If the lsp-trigger command is run in both the MPLS view and MPLS-LDP-IPv4, the configuration in the MPLS-LDP-IPv4 view preferentially takes effect.

Example

# Enable LDP to use IP routes with 32-bit addresses to establish LSPs.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] lsp-trigger host