93
Parameters
None
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
lsp-trigger
Description
Use the
lsp-trigger
command to configure the LSP establishment triggering policy.
Use the
undo lsp-trigger
command to restore the default.
By default, only host routes with 32-bit masks can trigger establishment of LDP LSPs.
•
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. With loopback
addresses using 32-bit masks, only exactly matching host routing entries can trigger LDP to establish
LSPs.
•
If you specify the
vpn-instance
vpn-instance-name
combination, the command configures an LSP
establishment triggering policy for the specified VPN instance. Otherwise, the command configures
an LSP establishment triggering policy for the public network routes.
•
For information about IP prefix list, see the
Layer 3—IP Routing Configuration Guide
.
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
}
View
MPLS view
Default level
2: System level
Parameters
vpn-instance
vpn-instance-name
: Specifies a VPN instance by its name, which is 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, which is a string of 1 to 19 characters.
