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.
1. Run system-view
  The system view is displayed.
2. Run static-cr-lsp ingress { tunnel-interface tunnel interface-number | tunnel-name } destination destination-address { nexthop next-hop-address | outgoing-interface interface-type interface-number } ^* out-label out-label [ bandwidth [ ct0 | ct1 ] bandwidth ]
  The static CR-LSP is configured on the ingress node.
  
  tunnel interface-number specifies the MPLS TE tunnel interface that uses this static CR-LSP. By default, the Bandwidth Constraints value is ct0, and the value of bandwidth is 0. The bandwidth used by the tunnel cannot be higher than the maximum reservable bandwidth of the link.
  
  tunnel-name must be the same as the tunnel name created by using the interface tunnel interface-number command. tunnel-name is a case-sensitive character string in which spaces are not supported.
  
  The next hop or outbound interface is determined by the route from the ingress to the egress. For the difference between the next hop and outbound interface, refer to Creating IPv4 Static Routes in "Static Route Configuration" in the S2720, S5700, and S6700 V200R019C10 Configuration Guide - IP Unicast Routing.
  
  If an Ethernet interface is used as an outbound interface of an LSP, the nexthop next-hop-address parameter must be configured.
  
  The configured bandwidth takes effect only during tunnel establishment and protocol negotiation, and does not limit the bandwidth for traffic forwarding. (S5720-HI does not have this restriction.)
Configure a transit node.
Perform the following operations on the transit node of a static MPLS TE tunnel.
1. Run system-view
  The system view is displayed.
2. Run static-cr-lsp transit lsp-name [ incoming-interface interface-type interface-number ] in-label in-label { nexthop next-hop-address | outgoing-interface interface-type interface-number } ^* out-label out-label [ bandwidth [ ct0 | ct1 ] bandwidth ] [ description description ]
  The static CR-LSP is configured on the transit node.
  
  lsp-name cannot be specified as the same as the name of an existing tunnel on the node. The name of the MPLS TE tunnel interface associated with the static CR-LSP can be used, such as Tunnel1.
  
  If an Ethernet interface is used as an outbound interface of an LSP, the nexthop next-hop-address parameter must be configured.
  
  The configured bandwidth takes effect only during tunnel establishment and protocol negotiation, and does not limit the bandwidth for traffic forwarding. (S5720-HI does not have this restriction.)
Configure the egress node.
Perform the following operations on the egress node of a static MPLS TE tunnel.
1. Run system-view
  The system view is displayed.
2. Run static-cr-lsp egress lsp-name [ incoming-interface interface-type interface-number ] in-label in-label
  The static CR-LSP is configured on the egress node.
  
  lsp-name cannot be specified as the same as the name of an existing tunnel on the node. The name of the MPLS TE tunnel interface associated with the static CR-LSP can be used, such as Tunnel1.