The ingress-lsp trigger route-policy command specifies a routing policy to control the creation of ingress LSPs based on private labeled BGP IPv4 routes.
The undo ingress-lsp trigger command restores the default configuration.
By default, ingress LSPs are not created based on received private BGP labeled routes.
| Parameter | Description | Value |
|---|---|---|
| route-policy 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
In the CSC scenario, BGP VPN labeled routes are used to establish end-to-end LSPs. To create ingress LSPs for BGP labeled routes that match a routing policy, run this command.
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.
<HUAWEI> system-view [~HUAWEI] ip vpn-instance vpna [*HUAWEI-vpn-instance-vpna] ipv4-family [*HUAWEI-vpn-instance-vpna-af-ipv4] route-distinguisher 1:1 [*HUAWEI-vpn-instance-vpna-af-ipv4] quit [*HUAWEI-vpn-instance-vpna] quit [*HUAWEI] route-policy test-policy permit node 10 [*HUAWEI-route-policy] quit [*HUAWEI] bgp 100 [*HUAWEI-bgp] ipv4-family vpn-instance vpna [*HUAWEI-bgp-vpna] ingress-lsp trigger route-policy test-policy