ingress-lsp trigger

Function

The ingress-lsp trigger command specifies a routing policy to control the creation of ingress LSPs based on BGP labeled routes.

The undo ingress-lsp trigger command restores the default setting.

By default, ingress LSPs are created based on all received BGP labeled routes.

S5731-S, S5731S-S, S6730-S, and S6730S-S do not support this parameter.

Format

ingress-lsp trigger route-policy route-policy-name

undo ingress-lsp trigger

Parameters

Parameter	Description	Value
route-policy route-policy-name	Specifies the name of a routing policy to be used to create ingress LSPs based on BGP labeled routes.	The name is a string of 1 to 40 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

Views

BGP view, BGP-IPv4 unicast address family view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

In a MAN where the hybrid access mode is used, a large number of BGP labeled routes are used to establish end-to-end LSPs. On certain intermediate nodes where VPN services do not need to be supported, excessive ingress LSPs are created, causing the waste of network resources. In this case, you can run the ingress-lsp trigger command to create ingress LSPs based on a routing policy to save network resources.

Precautions

If the ingress-lsp trigger command is run more than once, the latest configuration overrides the previous ones.

Creating a route-policy before it is referenced is recommended. By default, nonexistent route-policies cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent route-policy is referenced using the current command, ingress LSPs are established for all labeled routes.

Example

# Specify a routing policy named test-policy to control the creation of ingress LSPs based on labeled IPv4 routes.

<HUAWEI> system-view
[HUAWEI] bgp 100
[HUAWEI-bgp] ipv4-family unicast
[HUAWEI-bgp-af-ipv4] ingress-lsp trigger route-policy test-policy