The lsp-trigger bgp-label-route command enables LDP to allocate labels to labeled BGP routes on the public network.
The undo lsp-trigger bgp-label-route command restores the default setting.
By default, LDP does not allocate labels to labeled BGP routes on the public network.
lsp-trigger bgp-label-route [ ip-prefix ip-prefix-name ] [ not-only-host ]
undo lsp-trigger bgp-label-route
| Parameter | Description | Value |
|---|---|---|
ip-prefix ip-prefix-name |
Specifies the name of the IP prefix list that triggers the labeled BGP routes on the public network to set up LDP LSPs. |
The value is an existing IP prefix list name. |
not-only-host |
Uses labeled public network BGP routes with 0-bit to 32-bit masks based on the IP prefix list to establish LDP LSPs. |
- |
Usage Scenario
Both the lsp-trigger bgp-label-route command and the lsp-trigger command can be used to configure policies to trigger the establishment of LDP LSPs. The former command is used for labeled public network BGP routes with 0-bit to 32-bit masks, and the latter command is used for static routes and IGP routes.
If not-only-host is not configured, LDP distributes labels only for labeled public network BGP routes with 32-bit masks. If not-only-host is configured, LDP distributes labels for labeled public network BGP routes with 0-bit to 32-bit masks.
Precautions
Modifying the LSP-triggering policy during the LDP GR period is invalid.
Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all public-network labeled BGP routes trigger LDP LSP establishment.