Creating Static LSPs
Configuring LSR ID
Context
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.
Enabling MPLS
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 interface interface-type interface-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.
Verifying the Static LSP Configuration
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-address mask-length ] [ verbose ] command to check the static LSP.
- Run the display mpls label static available [ [ label-from label-index ] label-number label-number ] command to check information about labels available for transmitting static services.