15
To do…
Use the command…
Remarks
Specify the type of the label to be
distributed by the egress to the
penultimate hop
label advertise
{
explicit-null
|
implicit-null
|
non-null
}
Optional
By default, an egress distributes to
the penultimate hop an implicit null
label.
NOTE:
•
The switch supports PHP when it works as a penultimate hop. It can accept the explicit or implicit null
label.
•
When working as the egress, the switch does not support distributing a normal label to the penultimate
hop (that is, it does not support the
non-null
type). HP recommends using a device that supports PHP as
the penultimate hop.
•
For LDP sessions existing before the
label advertise
command is configured, you must reset the LDP
sessions by using the
reset mpls ldp
command for the PHP configuration to take effect.
•
After sessions are established, if you use the
label advertise
command to change the type of label that
the egress should distribute to the penultimate hop, you need to restart the switch for the configuration
to take effect.
Configuring the policy for triggering LSP establishment
You can configure an LSP triggering policy on an LSR, so that only routes matching the policy can trigger
establishment of LSPs, reducing the number of LSPs to be established on the LSR and avoiding instability
of the LSR caused by excessive LSPs.
An LSR supports two types of LSP triggering policies:
•
Allowing all routing entries to trigger establishment of LSPs.
•
Filtering routing entries by an IP prefix list, so that static and IGP routes denied by the IP prefix list
will not trigger LSP establishment. To use this policy, you must create the IP prefix list. For information
about IP prefix list configuration, see
Layer 3—IP Routing Configuration Guide
.
To configure the policy for triggering LSP establishment:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter MPLS view
mpls
—
Configure the LSP establishment
triggering policy
lsp-trigger
[
vpn-instance
vpn-instance-name
] {
all
|
ip-prefix
prefix-name
}
Optional
By default, only host routes with
32-bit masks can trigger
establishment of LSPs.
NOTE:
•
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 combination 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.
