R3102-R3103-HP 6600/HSR6600 Routers MPLS Command Reference Guide

48
Examples
# Enable loop detection for the public network LDP instance.
<Sysname> system-view
[Sysname] mpls ldp
[Sysname-mpls-ldp] loop-detect
# Enable loop detection for LDP instance vpn1.
<Sysname> system-view
[Sysname] mpls ldp vpn-instance vpn1
[Sysname-mpls-ldp-vpn-instance-vpn1] loop-detect
Related commands
• hops-count
• path-vectors
lsp-trigger
Use lsp-trigger to configure the LSP establishment triggering policy.
Use undo lsp-trigger to restore the default.
Syntax
lsp-trigger [ vpn-instance vpn-instance-name ] { all | ip-prefix prefix-name }
undo lsp-trigger [ vpn-instance vpn-instance-name ] { all | ip-prefix prefix-name }
Default
Only host routes with 32-bit masks can trigger establishment of LDP LSPs.
Views
MPLS view
Default command level
2: System level
Parameters
vpn-instance vpn-instance-name: Specifies an MPLS L3VPN by its instance name, a case-sensitive string
of 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 routes
that denied by the IP prefix list cannot trigger LSP establishment. prefix-name indicates the name of the IP
prefix list, a string of 1 to 19 characters.
Usage guidelines
An 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 an
LSR, to establish an LSP to a loopback address with a 32-bit mask, there must be an exactly matching host
routing entry on the LSR.
If the vpn-instance vpn-instance-name option is specified, the command configures an LSP establishment
triggering policy for the specified VPN. Otherwise, the command configures an LSP establishment
triggering policy for the public network routes.