Configuring a static LSP
Overview
A static label switched path (LSP) is established by manually specifying the incoming label and
outgoing label on each node (ingress, transit, or egress node) of the forwarding path.
Static LSPs consume fewer resources, but they cannot automatically adapt to network topology
changes. Therefore, static LSPs are suitable for small and stable networks with simple topologies.
Follow these guidelines to establish a static LSP:
•
The ingress node performs the following operations:
a. Determines an FEC for a packet according to the destination address.
b. Adds the label for that FEC into the packet.
c. Forwards the packet to the next hop or out of the outgoing interface.
Therefore, on the ingress node, you must specify the outgoing label for the destination address
(the FEC) and the next hop or the outgoing interface.
•
A transit node swaps the label carried in a received packet with a label, and forwards the packet
to the next hop or out of the outgoing interface. Therefore, on each transit node, you must
specify the incoming label, the outgoing label, and the next hop or the outgoing interface.
•
If PHP is not configured, an egress node pops the incoming label of a packet, and performs
label forwarding according to the inner label or IP forwarding. Therefore, on the egress node,
you only need to specify the incoming label.
•
The outgoing label specified on an LSR must be the same as the incoming label specified on
the directly connected downstream LSR.
Configuration prerequisites
Before you configure a static LSP, perform the following tasks:
1.
Identify the ingress node, transit nodes, and egress node of the LSP.
2.
Enable MPLS on all interfaces that participate in MPLS forwarding. For more information, see
"Configuring basic
3.
Make sure the ingress node has a route to the destination address of the LSP. This is not
required on transit and egress nodes.
Configuration procedure
To configure a static LSP:
Step
1.
Enter system view.
2.
Configure the ingress
node of the static LSP.
3.
Configure the transit
node of the static LSP.
MPLS."
Command
system-view
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
static-lsp transit lsp-name in-label
in-label { nexthop next-hop-addr |
13
Remarks
N/A
If you specify a next hop for the
static LSP, make sure the ingress
node has an active route to the
specified next hop address.
If you specify a next hop for the
static LSP, make sure the transit
Need help?
Do you have a question about the HPE FlexNetwork MSR Router Series and is the answer not in the manual?
Questions and answers