How to reduce the number of LSPs on S series switches

After MPLS LDP is enabled, LSPs are automatically established. If no policy for controlling LSP establishment is configured, a large number of LSPs are established, wasting resources.
To reduce the number of LSPs, you can run the lsp-trigger { all | host | ip-prefix ip-prefix-name | none } command in the MPLS view to set a policy for LSP establishment.
If the all parameter is specified, all static and IGP routes trigger LSP establishment (not recommended). If the host parameter is specified, host IP routes with 32-bit addresses (excluding host IP routes with 32-bit interface addresses) trigger LSP establishment. If the ip-prefix parameter is specified, the IP prefix list triggers LSP establishment. If the none parameter is specified, LSP establishment is not triggered.
The lsp-trigger command configures policies only for ingress and egress LSPs on the public network and ingress and egress LSPs on the private network that are established using IGP routes. To configure a policy for triggering the transit LSP establishment, run the propagate mapping command.
If the lsp-trigger command is run on the ingress node, the ingress node uses all 32-bit routes to establish LDP LSPs. If the lsp-trigger command is run on the egress node, the egress node uses local 32-bit routes to establish LDP LSPs.

Scroll to top