89[Sysname] mpls ldp vpn-instance vpn1[Sysname-mpls-ldp-vpn-instance-vpn1] loop-detectRelated commands• hops-count• path-vectorslsp-triggerUse lsp-trigger to configure the LSP establishment triggering policy.Use undo lsp-trigger to restore the default.Syntaxlsp-trigger [ vpn-instance vpn-instance-name ] { all | ip-prefix prefix-name }undo lsp-trigger [ vpn-instance vpn-instance-name ] { all | ip-prefix prefix-name }DefaultOnly host routes with 32-bit masks can trigger establishment of LDP LSPs.ViewsMPLS viewDefault command level2: System levelParametersvpn-instance vpn-instance-name: Specifies an MPLS L3VPN by its instance name, a case-sensitive stringof 1 to 31 characters.all: Specifies that all routing entries can trigger establishment of LDP LSPs.ip-prefix prefix-name: Specifies an IP prefix list to filter routing entries, so that static routes and IGP routesthat denied by the IP prefix list cannot trigger LSP establishment. The prefix-name argument indicates thename of the IP prefix list, a string of 1 to 19 characters.Usage guidelinesAn IP prefix list affects only static routes and IGP routes.For an LSP to be established, an exactly matching routing entry must exist on the LSR. For example, on anLSR, to establish an LSP to a loopback address with a 32-bit mask, there must be an exactly matching hostrouting entry on the LSR.If the vpn-instance vpn-instance-name option is specified, the command configures an LSP establishmenttriggering policy for the specified VPN. Otherwise, the command configures an LSP establishmenttriggering policy for the public network routes.For information about IP prefix list, see Layer 3—IP Routing Configuration Guide.Examples# Specify that all routing entries can trigger establishment of LDP LSPs. system-view[Sysname] mpls[Sysname-mpls] lsp-trigger all
