bidirectional static-cr-lsp

Function

The bidirectional static-cr-lsp command creates a static bidirectional co-routed CR-LSP and displays the static bidirectional CR-LSP view.

The undo bidirectional static-cr-lsp command deletes a static bidirectional co-routed CR-LSP.

By default, no static bidirectional co-routed CR-LSP is configured.

Format

bidirectional static-cr-lsp ingress tunnel-name

bidirectional static-cr-lsp transit lsp-name

bidirectional static-cr-lsp egress lsp-name

undo bidirectional static-cr-lsp ingress tunnel-name

undo bidirectional static-cr-lsp transit lsp-name

undo bidirectional static-cr-lsp egress lsp-name

Parameters

Parameter	Description	Value
transit lsp-name	Indicates the LSP name of the transit node of a static bidirectional co-routed CR-LSP.	The value is a string of 1 to 19 case-sensitive characters, spaces not supported.
egress lsp-name	Indicates the LSP name of the egress of a static bidirectional co-routed CR-LSP.	The value is a string of 1 to 19 case-sensitive characters, spaces not supported.
ingress tunnel-name	Indicates the ingress tunnel name of a static bidirectional co-routed CR-LSP.	The value is a string of 1 to 19 case-sensitive characters, spaces not supported.

Parameter

Description

Value

transit lsp-name

Indicates the LSP name of the transit node of a static bidirectional co-routed CR-LSP.

The value is a string of 1 to 19 case-sensitive characters, spaces not supported.

egress lsp-name

Indicates the LSP name of the egress of a static bidirectional co-routed CR-LSP.

The value is a string of 1 to 19 case-sensitive characters, spaces not supported.

ingress tunnel-name

Indicates the ingress tunnel name of a static bidirectional co-routed CR-LSP.

The value is a string of 1 to 19 case-sensitive characters, spaces not supported.

Views

System view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
mpls-te	write

Usage Guidelines

Usage Scenario

A static bidirectional co-routed CR-LSP is manually established and consists of two CR-LSPs passing through the same nodes and links and transmitting traffic in opposite directions. You have to configure MPLS forwarding entries in both directions on each node of a path over which the bidirectional CR-LSP is to be established and bind the two CR-LSPs in opposite directions together on both the ingress and egress.

The bidirectional static-cr-lsp command can be used to create a static bidirectional co-routed LSP and display the static bidirectional LSP view. LSP data, such as the incoming label, outbound interface, and next-hop IP address, can be configured in this view. An ingress is a node where a CR-LSP originates from and its reverse CR-LSP terminates at; an egress is a node where a CR-LSP terminates at and its reverse CR-LSP originates from.

Configuration Impact

If the undo bidirectional static-cr-lsp command is run, all configurations of the static bidirectional co-routed LSP will be deleted.

Precautions

The tunnel name specified in the bidirectional static-cr-lsp ingress tunnel-name command must be the name of an established tunnel.

Example

# Configure a static bidirectional co-routed LSP named Tunnel10 on the egress.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] quit
[*HUAWEI] bidirectional static-cr-lsp egress Tunnel10

# Configure a static bidirectional co-routed LSP named abc on a transit node.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] quit
[*HUAWEI] bidirectional static-cr-lsp transit abc

# Configure a static bidirectional co-routed LSP named Tunnel10 on the ingress.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] quit
[*HUAWEI] bidirectional static-cr-lsp ingress Tunnel10