The ingress-lsp trigger route-policy command specifies a routing policy to control the creation of ingress LSPs based on labeled BGP IPv4 routes.
The undo ingress-lsp trigger command restores the default configuration.
By default, ingress LSPs are created based on all received BGP labeled routes.
| 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 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Scenario
On a MAN where the hybrid access mode is used, a large number of labeled BGP 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.
Prerequisites
If the routing policy specified in the ingress-lsp trigger command does not exist, you need to configure the routing policy using the route-policy command first.
Configuration Impact
If the ingress-lsp trigger command is run more than once, the latest configuration overrides the previous one.
Precautions
When a large number of routes flap on a device and the ingress-lsp trigger command is run, a delay occurs when labeled routes recurse to BGP LSPs, but service traffic is not affected.
When a large number of routes flap on a device and the undo ingress-lsp trigger command is run, a delay occurs in the switchback of labeled routes to the original tunnels, but service traffic is not affected.<HUAWEI> system-view [~HUAWEI] route-policy test-policy permit node 10 [*HUAWEI-route-policy] quit [*HUAWEI] bgp 100 [*HUAWEI-bgp] ipv4-family unicast [*HUAWEI-bgp-af-ipv4] ingress-lsp trigger route-policy test-policy