forward (Static bidirectional co-routed egress view)

Function

The forward command configures a CR-LSP on the egress.

The undo forward command cancels the configuration.

By default, no CR-LSP is configured.

Format

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

undo forward

Parameters

Parameter	Description	Value
lsrid ingress-lsr-id	Specifies the ingress LSR ID. This LSR ID value is used as the FEC value for the reverse CR-LSP.	The value is in dotted decimal notation.
tunnel-id ingress-tunnel-id	Specifies the ingress tunnel ID. The tunnel ID and LSR ID identify an egress CR-LSP in a tunnel originating from the ingress.	The value is an integer ranging from 1 to 65535.
in-label in-label-value	Specifies the incoming label value.	An integer ranging from 16 to 32783.

Parameter

Description

Value

lsrid ingress-lsr-id

Specifies the ingress LSR ID. This LSR ID value is used as the FEC value for the reverse CR-LSP.

The value is in dotted decimal notation.

tunnel-id ingress-tunnel-id

Specifies the ingress tunnel ID. The tunnel ID and LSR ID identify an egress CR-LSP in a tunnel originating from the ingress.

The value is an integer ranging from 1 to 65535.

in-label in-label-value

Specifies the incoming label value.

An integer ranging from 16 to 32783.

Views

Static bidirectional co-routed egress 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.

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 17, ingress LSR ID to 1.1.1.1, and ingress tunnel ID to 1 for a CR-LSP on the egress.

<HUAWEI> system-view
[~HUAWEI] mpls
[*HUAWEI-mpls] mpls te
[*HUAWEI-mpls] quit
[*HUAWEI] bidirectional static-cr-lsp egress Tunnel2
[*HUAWEI-bi-static-egress-Tunnel2] forward in-label 17 lsrid 1.1.1.1 tunnel-id 1