Configuration procedure

Static CRLSPs are special static LSPs. They use the same label space as static LSPs. On a device, a static CRLSP and a static LSP cannot use the same incoming label.

A static CRLSP can forward MPLS TE traffic only after you create an MPLS TE tunnel interface on the ingress node and specify the static CRLSP for the tunnel interface. For more information about MPLS TE, see "Configuring MPLS TE."

Before you configure a static CRLSP, perform the following tasks:

Identify the ingress node, transit nodes, and egress node of the CRLSP.
Enable MPLS on all interfaces that participate in MPLS forwarding. For more information, see "Configuring basic MPLS."
Enable MPLS TE for each node and interface that the CRLSP traverses. For more information, see "Configuring MPLS TE."

To configure a static CRLSP:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a static CRLSP.	Configure the ingress node:static-cr-lsp ingress lsp-name { nexthop ip-address \| outgoing-interface interface-type interface-number } out-label out-label-value [ bandwidth [ ct0 \| ct1 \| ct2 \| ct3 ] bandwidth-value ] Configure a transit node:static-cr-lsp transit lsp-name in-label in-label-value { nexthop ip-address \| outgoing-interface interface-type interface-number } out-label out-label-value [ bandwidth [ ct0 \| ct1 \| ct2 \| ct3 ] bandwidth-value ] Configure the egress node:static-cr-lsp egress lsp-name in-label in-label-value	Use one command according to the position of a device on the network. By default, no static CRLSPs exist. Do not configure the next hop address as a local public IP address when configuring the static CRLSP on the ingress node or a transit node. You do not need to execute the static-cr-lsp egress command on the egress node if the outgoing label configured on the penultimate hop of the static CRLSP is 0 or 3.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Create a static CRLSP.

Configure the ingress node:static-cr-lsp ingress lsp-name { nexthop ip-address | outgoing-interface interface-type interface-number } out-label out-label-value [ bandwidth [ ct0 | ct1 | ct2 | ct3 ] bandwidth-value ]
Configure a transit node:static-cr-lsp transit lsp-name in-label in-label-value { nexthop ip-address | outgoing-interface interface-type interface-number } out-label out-label-value [ bandwidth [ ct0 | ct1 | ct2 | ct3 ] bandwidth-value ]
Configure the egress node:static-cr-lsp egress lsp-name in-label in-label-value

Use one command according to the position of a device on the network.

By default, no static CRLSPs exist.

Do not configure the next hop address as a local public IP address when configuring the static CRLSP on the ingress node or a transit node.

You do not need to execute the static-cr-lsp egress command on the egress node if the outgoing label configured on the penultimate hop of the static CRLSP is 0 or 3.

prev	up	next
Overview	home	Displaying static CRLSPs