No relevant resource is found in the selected language.
Your browser version is too early. Some functions of the website may be unavailable. To obtain better user experience, upgrade the browser to the latest version.
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Creating Static LSPs
Creating Static LSPs
Pre-configuration Tasks
Before creating
static LSPs, configure a static unicast route or an IGP to connect
LSRs at the network layer.
Configuration Process
Create static LSPs
according to the following sequence.
An LSR ID identifies an LSR on a network. An LSR does not have the default LSR ID, and you must configure an LSR ID for it. To enhance network reliability, you are advised to use the IP address of a loopback interface on the LSR as the LSR ID.
Perform the following steps on each node in an MPLS domain.
Procedure
Run system-view
The system view is displayed.
Run mpls lsr-idlsr-id
The LSR ID of the local node is configured.
By default, no LSR ID is set.
Follow-up Procedure
Before changing the configured LSP ID, run the undo mpls command in the system view.
Running the undo mpls command to delete all MPLS configurations will interrupt MPLS services, so plan the LSR ID of each LSP uniformly to prevent LSR ID change.
Enabling MPLS
Context
Perform the following steps on each LSR in an MPLS domain:
Procedure
Run system-view
The
system view is displayed.
Run mpls
MPLS is enabled
globally and the MPLS view is displayed.
By default, no node
is enabled with MPLS.
Run quit
Return to
the system view.
Run interfaceinterface-typeinterface-number
The interface to
participate in MPLS forwarding is specified.
Run mpls
MPLS is enabled
on the interface.
By default, no interface is enabled with MPLS.
Establishing a Static LSP
Context
Static LSPs and static Constraint-based Routed LSPs (CR-LSPs)
share the same label space (16-1023). Note that the value of the outgoing
label of the previous node is equal to the value of the incoming label
of the next node.
Perform the following operations on the ingress,
transit, and egress nodes of the static LSP. Figure 2-2 shows planned
labels.
Figure 2-2 Networking of establishing a static LSP
The
local node is configured as the ingress node of a specified LSP.
You are advised to set up a static LSP by specifying a next
hop. Ensure that the local routing table contains the route entries,
including the destination IP address and the next hop IP addresses
of the LSP to be set up.
If an Ethernet interface is used as
an outbound interface of an LSP, the nexthopnext-hop-address parameter must be configured.
As shown in Figure 2-2, the LSP name
is LSP1, destination address is 3.3.3.9/32, next hop address is 172.1.1.2,
outbound interface is GigabitEthernet0/0/1, and outgoing label is 100.
Configure the transit node.
Run system-view
The system view is displayed.
Run static-lsp transitlsp-nameincoming-interfaceinterface-typeinterface-numberin-labelin-label { nexthopnext-hop-address | outgoing-interfaceinterface-typeinterface-number } *out-labelout-label
The
local node is configured as the transit node of a specified LSP.
You are advised to set up a static LSP by specifying a next
hop address. In addition, ensure that the local routing table contains
the route entries, including the destination IP address and the next
hop IP address of the LSP to be set up.
If an Ethernet interface
is used as an outbound interface of an LSP, the nexthopnext-hop-address parameter must be configured.
As shown in Figure 2-2, the LSP name
is LSP1, the inbound interface is GigabitEthernet0/0/1, incoming label is 100, next hop address
is 172.2.1.2, outbound interface is GigabitEthernet0/0/2, and outgoing label is 200.
Configure the egress node.
Run system-view
The system view is displayed.
Run static-lsp egresslsp-nameincoming-interfaceinterface-typeinterface-numberin-labelin-label[ lsridingress-lsr-idtunnel-idtunnel-id ]
The local node is configured as the egress
node of a specified LSP.
As shown in Figure 2-2, the LSP name
is LSP1, the inbound interface is GigabitEthernet0/0/1, and incoming label is 200.
Verifying the Static LSP Configuration
Prerequisites
The configurations of the static LSP function are complete.
Procedure
Run the display default-parameter mpls management command to check default configurations of the MPLS management module.
Run the display mpls static-lsp [ lsp-name ] [ { include | exclude } ip-addressmask-length ] [ verbose ] command to check the static LSP.
Run the display mpls label static available [ [ label-fromlabel-index ] label-numberlabel-number ] command to check information about labels available for transmitting static services.
