static-cr-lsp ingress
Function
The static-cr-lsp ingress command configures a static CR-LSP on the ingress LSR.
The undo static-cr-lsp ingress command deletes a static CR-LSP from the ingress LSR.
By default, no static CR-LSP on the ingress LSR is configured.
Format
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 ]
undo static-cr-lsp ingress { tunnel-interface tunnel interface-number | tunnel-name }
Parameters
| Parameter | Description | Value |
|---|---|---|
| tunnel-interface tunnel interface-number | Specifies the tunnel interface of a static CR-LSP. interface-number indicates the tunnel interface number. | - |
| tunnel-name | Specifies the name of a CR-LSP. | The name is a string of 1 to 19 case-sensitive characters, spaces and abbreviation not supported. If you use the interface Tunnel 1 command to create a tunnel interface for a static CR-LSP, the tunnel name in the static-cr-lsp ingress command must be formatted as "Tunnel1", otherwise, the tunnel cannot be created. There is no such a limit for the transit node and egress node. |
| destination destination-address | Specifies the destination IP address of a static CR-LSP. | The value is in dotted decimal notation. |
| nexthop next-hop-address | Specifies the next-hop IP address of a static CR-LSP. | The value is in dotted decimal notation. |
| outgoing-interface interface-type interface-number | Specifies the type and number of an outgoing interface. This parameter is only applicable to a P2P link. | - |
| out-label out-label | Specifies the value of an outgoing label. | The value is an integer ranges from 16 to 1048575. |
| bandwidth [ ct0 | ct1 ] bandwidth |
Specifies the bandwidth values of CR-LSPs of CT0 to CT1. |
The value is an integer ranges from 0 to 4000000000, in kbit/s. The default value is 0. |
Usage Guidelines
Usage Scenario
Run this command on the ingress node to configure a static CR-LSP.
Before setting up an MPLS TE tunnel through a static CR-LSP, configure a static route or an IGP to ensure connectivity between LSRs, and enable basic MPLS and MPLS TE functions. After setting up a static CR-LSP, you can run the display mpls static-cr-lsp command to ensure that the static CR-LSP is established successfully.
Precautions
To modify parameters including destination destination-address, nexthop next-hop-address, outgoing-interface interface-type interface-number, and out-label out-label, run the static-cr-lsp ingress command to set a new value. There is no need to run the undo static-cr-lsp ingress command before changing a configured value.
If you specify a next hop when configuring a static CR-LSP, specify a next hop when configuring a static IP route. If you do not specify a next hop, the static LSP cannot be set up. For example:
[HUAWEI] ip route-static 10.1.3.0 24 10.1.1.2 [HUAWEI] static-cr-lsp ingress Tunnel1 destination 10.1.3.1 nexthop 10.1.1.2 out-label 237
If a dynamic routing protocol applies to the link between LSRs, the next-hop IP address along the LSP must be the same as the IP address of the next hop in the routing table.
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.)