Configuring a Static MPLS TE Tunnel
Pre-configuration Tasks
Configuring a static MPLS TE tunnel can implement setup of static CR-LSPs. The configuration is simple. Labels are allocated manually and control packets do not need to exchanged, so static LSPs consume less resources.
Before configuring a static MPLS TE tunnel, complete the following tasks:
Configure an LSR ID on each LSR.
Enable basic MPLS functions on each LSR globally and on each interface.
After a static CR-LSP is bound to a tunnel interface, the static CR-LSP takes effect without an IP route configured.
Enabling MPLS TE
Procedure
- Run system-view
The system view is displayed.
- Run mpls
The MPLS view is displayed.
- Run mpls te
MPLS TE is enabled on the node globally.
- Run quit
Return to the system view.
- Run interface interface-type interface-number
The view of the interface is displayed.
- Run mpls
The MPLS is enabled on the interface.
- Run mpls te
The MPLS TE is enabled on the interface.
Configuring an MPLS TE Tunnel Interface
Context
Before setting up an MPLS TE Tunnel, you must create a tunnel interface and configure other tunnel attributes on the tunnel interface. An MPLS TE tunnel interface is responsible for establishing an MPLS TE tunnel and managing packet forwarding on the tunnel.
Because the type of the packet forwarded by the MPLS TE tunnel is MPLS, the commands, such as the ip verify source-address and urpf commands, related to IP packet forwarding configured on this interface are invalid.
Perform the following configurations on the ingress node of an MPLS TE tunnel.
Procedure
- Run system-view
The system view is displayed.
- Run interface tunnel interface-number
A tunnel interface is created and the tunnel interface view is displayed.
- To configure the IP address of the tunnel interface, run either of the following commands:
ip address ip-address { mask | mask-length } [ sub ]
The IP address of the tunnel interface is configured.
The secondary IP address of the tunnel interface can be configured only after the primary IP address is configured.
ip address unnumbered interface interface-type interface-number
The tunnel interface is configured to borrow an IP address from other interfaces.
An MPLS TE tunnel can be established even if the tunnel interface is assigned no IP address. The tunnel interface must obtain an IP address before forwarding traffic. The MPLS TE tunnel is unidirectional and does not need to configure a separate IP address for the tunnel interface. Generally, a loopback interface is created on the ingress node and a 32-bit address that is the same as the LSR ID is assigned to the loopback interface. Then the tunnel interface borrows the IP address of the loopback interface.
- Run tunnel-protocol mpls te
MPLS TE is configured as a tunnel protocol.
- Run destination dest-ip-address
The destination address of the tunnel is configured, which is usually the LSR ID of the egress node.
Different types of tunnels need different destination addresses. When the tunnel protocol is changed to MPLS TE from other protocols, the configured destination address is deleted automatically and you need to configure an address again.
- Run mpls te tunnel-id tunnel-id
The tunnel ID is configured.
- Run mpls te signal-protocol cr-static
The signal protocol of the tunnel is configured to be static CR-LSP.
- (Optional) Run mpls te signalled tunnel-name tunnel-name
The tunnel name is specified.
By default, the tunnel interface name such as Tunnel0/0/1 is used as the name of the TE tunnel.
- Run mpls te commit
The current tunnel configuration is committed.
If MPLS TE parameters on a tunnel interface are modified, run the mpls te commit command to activate them.
(Optional) Configuring Link Bandwidth
Context
When a non-Huawei device as the ingress node of an MPLS TE tunnel initiates a request for setting up a CR-LSP with bandwidth constraints, configure link bandwidth on the connected Huawei device for negotiation so that the CR-LSP can be set up and network resources are used efficiently.
Perform the following configurations on each node of the MPLS TE tunnel.
Procedure
- Run system-view
The system view is displayed.
- Run interface interface-type interface-number
The MPLS-TE-enabled interface view is displayed.
- Run mpls te bandwidth max-reservable-bandwidth bw-value
The maximum available bandwidth of the link is configured.
By default, the maximum reservable bandwidth of a link is 0 bit/s. The bandwidth allocated to a static CR-LSP built over a link is certainly higher than 0 bit/s. If the maximum reservable bandwidth of the link is not configured, the static CR-LSP cannot be set up due to insufficient bandwidth.
- Run mpls te bandwidth { bc0 bc0-bw-value | bc1 bc1-bw-value } *
The BC bandwidth of the link is configured.
- The maximum reservable bandwidth of a link cannot be greater than the actual bandwidth of the link. A maximum of 80% of the actual bandwidth of the link is recommended for the maximum reservable bandwidth of the link.
- Neither the BC0 bandwidth nor the BC1 bandwidth can be greater than the maximum reservable bandwidth of the link.
Configuring the Static CR-LSP
Context
When configuring a static MPLS TE tunnel, configure static CR-LSPs on the ingress, transit, and egress nodes. When there is no intermediate node, there is no need to configure a static CR-LSP on the intermediate node.
After static CR-LSPs are configured, you can execute commands again to modify CR-LSP parameters.
Procedure
- Configure the ingress node.
Perform the following operations on the ingress node of a static MPLS TE tunnel.
- Configure a transit node.
Perform the following operations on the transit node of a static MPLS TE tunnel.
- Configure the egress node.
Perform the following operations on the egress node of a static MPLS TE tunnel.
Verifying the Static MPLS TE Tunnel Configuration
Procedure
- Run the display mpls static-cr-lsp [ lsp-name ] [ { include | exclude } ip-address mask-length ] [ verbose ] command to check information about the static CR-LSP.
- Run the display mpls te tunnel [ destination ip-address ] [ lsp-id ingress-lsr-id session-id local-lsp-id ] [ lsr-role { all | egress | ingress | remote | transit } ] [ name tunnel-name ] [ { incoming-interface | interface | outgoing-interface } interface-type interface-number ] [ te-class0 | te-class1 | te-class2 | te-class3 | te-class4 | te-class5 | te-class6 | te-class7 ] [ verbose ] command to check tunnel information.
- Run the display mpls te tunnel statistics or display mpls lsp statistics command to check the tunnel statistics.
- Run the display mpls te tunnel-interface [ tunnel interface-number ] command to check information about the tunnel interface on the ingress node.