11
•
On the ingress LSR, the specified next hop or outgoing interface must be consistent with the
next hop or outgoing interface of the optimal route in the routing table. If you configure a static
IP route for the LSP, be sure to specify the same next hop or outgoing interface for the static
route and the static LSP. For information about configuring a static IP route, see
Layer 3—IP
Routing Configuration Guide
.
•
For an ingress or transit LSR, do not specify the public address of an interface on the LSR as
the next hop address.
Configuration procedure
To configure a static LSP:
Step Command
7.
Enter system view.
system-view
8.
Configure a static LSP taking the current LSR
as the ingress.
static-lsp
ingress
lsp-name
destination
dest-addr
{
mask
|
mask-length
} {
nexthop
next-hop-addr
|
outgoing-interface
interface-type
interface-number
}
out-label
out-label
9.
Configure a static LSP taking the current LSR
as a transit LSR.
static-lsp
transit
lsp-name
incoming-interface
interface-type interface-number
in-label
in-label
{
nexthop
next-hop-addr
|
outgoing-interface
interface-type interface-number
}
out-label
out-label
10.
Configure a static LSP taking the current LSR
as the egress.
static-lsp egress
lsp-name
incoming-interface
interface-type interface-number
in-label
in-label
Establishing dynamic LSPs through LDP
Perform the tasks in this section so the device can use LDP to set up dynamic LSPs.
Configuring MPLS LDP capability
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enable LDP capability globally and
enter MPLS LDP view.
mpls ldp
Not enabled by default.
3.
Configure the LDP LSR ID.
lsr-id
lsr-id
Optional.
By default, the LDP LSR ID is the
same as the MPLS LSR ID.
You need to perform this task only
in a multi-VPN context to make
sure that different LDP instances
have different LDP LSR IDs if
their address spaces overlap.
Otherwise, TCP connections
cannot be established.
4.
Return to system view.
quit
N/A
5.
Enter interface view.
interface
interface-type
interface-number
N/A