backward (Static bidirectional co-routed ingress view)

Function

The backward command configures a reverse CR-LSP on the ingress.

The undo backward command tears down a reverse CR-LSP.

By default, no reverse CR-LSP is configured.

Format

backward in-label in-label-value [ lsrid ingress-lsr-id tunnel-id ingress-tunnel-id ]

undo backward

Parameters

Parameter	Description	Value
in-label in-label-value	Specifies the incoming label value on the ingress.	An integer ranging from 16 to 32783.
lsrid ingress-lsr-id	Specifies the label switching router (LSR) ID of an egress.	The value is in dotted decimal notation.
tunnel-id ingress-tunnel-id	Specifies the tunnel ID of an Ingress.	The value is an integer ranging from 1 to 65535.

Parameter

Description

Value

in-label in-label-value

Specifies the incoming label value on the ingress.

An integer ranging from 16 to 32783.

lsrid ingress-lsr-id

Specifies the label switching router (LSR) ID of an egress.

The value is in dotted decimal notation.

tunnel-id ingress-tunnel-id

Specifies the tunnel ID of an Ingress.

The value is an integer ranging from 1 to 65535.

Views

Static bidirectional co-routed ingress 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 to each other on both the ingress and egress.

To configure a static bidirectional co-routed LSP, perform the following configurations to configure MPLS forwarding entries for traffic in opposite directions:

On the ingress
Run the forward (bidirectional static-cr-lsp ingress) command in the static bidirectional ingress LSP view to configure a CR-LSP.
Run the backward (bidirectional static-cr-lsp ingress) command in the static bidirectional ingress LSP view to configure a reverse CR-LSP.
On a transit node
Run the forward (bidirectional static-cr-lsp transit) command in the static bidirectional transit LSP view to configure a CR-LSP.
Run the backward (bidirectional static-cr-lsp transit) command in the static bidirectional transit LSP view to configure a reverse CR-LSP.
On the egress
Run the forward (bidirectional static-cr-lsp egress) command in the static bidirectional egress LSP view to configure a CR-LSP.
Run the backward (bidirectional static-cr-lsp egress) command in the static bidirectional egress LSP view to configure a reverse CR-LSP.

Precautions

If the static bidirectional co-routed LSP has the same outgoing label value, outbound interface, or next-hop IP address as a common static CR-LSP has, and the configuration fails.

Example

# Set the incoming label value to 16, egress LSR ID to 3.3.3.3, and ingress tunnel ID to 1 for a reverse CR-LSP on the ingress.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] quit
[*HUAWEI] bidirectional static-cr-lsp ingress Tunnel1
[*HUAWEI-bi-static-ingress-Tunnel1] backward in-label 16 lsrid 3.3.3.3 tunnel-id 1