The segment-routing lsp-trigger command configures a policy for establishing SR-MPLS BE LSPs on the ingress.
The undo segment-routing lsp-trigger command restores the default configuration.
By default, the ingress establishes SR-MPLS BE LSPs over IP routes with 32-bit masks.
Parameter | Description | Value |
---|---|---|
none |
Indicates that SR-MPLS LSP establishment is not triggered. |
- |
host |
Specifies to trigger SR-MPLS LSPs for host routes with 32-bit addresses. |
- |
ip-prefix ip-prefix-name |
Allows the ingress to use an IP prefix list to establish SR-MPLS BE LSPs. |
The value is a string of 1 to 169 case-sensitive characters, spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string. |
Usage Scenario
After Segment Routing is enabled, a great number of devices establish excessive SR-MPLS BE LSPs, leading to resource wastes. To prevent resource wastes, a policy for establishing SR-MPLS BE LSPs can be configured.
The segment-routing lsp-trigger command configures a policy to allow the ingress to use specified routes to establish SR-MPLS BE LSPs. This prevents unwanted SR-MPLS BE LSPs from being established and reduces resource wastes.Prerequisites
If ip-prefix is to be used, an IP prefix list must have been created using the ip ip-prefix command.
Precautions
The segment-routing lsp-trigger command takes effect on the ingress, not on transit nodes or the egress.