forward (Static bidirectional co-routed ingress view)

Function

The forward command configures the forward LSP of a static bidirectional co-routed LSP on the ingress.

The undo forward command cancels the configuration.

By default, no forward LSP is configured.

Format

forward nexthop next-hop-address outgoing-interface { interface-name | interface-type interface-number } out-label out-label-value [ [ bandwidth ct0 bandwidth ] | [ pir pir ] ] ^*

forward outgoing-interface { interface-name | interface-type interface-number } nexthop next-hop-address out-label out-label-value [ [ bandwidth ct0 bandwidth ] | [ pir pir ] ] ^*

forward nexthop next-hop-address out-label out-label-value [ [ bandwidth ct0 bandwidth ] | [ pir pir ] ] ^*

forward outgoing-interface { interface-name | { interface-type interface-number } } out-label out-label-value [ [ bandwidth ct0 bandwidth ] | [ pir pir ] ] ^*

undo forward

Parameters

Parameter	Description	Value
nexthop next-hop-address	Specifies the next-hop IP address for a static bidirectional co-routed LSP.	The value is in dotted decimal notation.
outgoing-interface	Specifies the type and number of an outbound interface. This parameter is set only for a point-to-point (P2P) link.	-
interface-type	Specifies the type of an outbound interface. This parameter is set only for a point-to-point (P2P) link.	-
interface-number	Specifies the number of an outbound interface. This parameter is set only for a point-to-point (P2P) link.	-
out-label out-label-value	Specifies an outgoing label value.	The value is an integer ranging from 16 to 1048575.
bandwidth	Indicates the bandwidth of a static bidirectional co-routed LSP.	-
ct0 bandwidth	Specifies the bandwidth to be reserved.	The value is an integer ranging from 0 to 4000000000, in kbit/s.
pir pir	Specifies the peak information rate (PIR) of the reservable bandwidth. If ct0 bandwidth is not set to 0, the PIR parameter must be set.	The value is an integer ranging from 0 to 4000000000, in kbit/s. The value cannot be less than the value of bandwidth.

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 together on both the ingress and egress.

To configure a static bidirectional co-routed LSP, perform the following operations 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.

If a pair of an outbound interface name and an outgoing label or a pair of a next-hop IP address and an outgoing label is assigned to an existing static LSP, a different parameter pair must be specified for the forward LSP of a static bidirectional LSP to be established. If the same parameter pair is configured, an outsegment entry conflict occurs, which results in a service diversion failure.

Example

# Set the next-hop IP address to 10.1.2.2, outgoing interface to GE0/1/0, outgoing label value to 16, and CT0 bandwidth to 100 kbit/s for a 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] forward nexthop 10.1.2.2 outgoing-interface GigabitEthernet 0/1/0 out-label 16 bandwidth ct0 100 pir 2000