backward (Static bidirectional co-routed egress view)

Function

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

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

By default, no reverse CR-LSP is configured.

Format

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

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

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

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

undo backward

Parameters

Parameter Description Value
nexthop next-hop-address

Specifies the next-hop IP address of a reverse CR-LSP on the egress.

The value is in dotted decimal notation.
outgoing-interface

Specifies the type and number of an outbound interface of a reverse CR-LSP on the egress.

-
interface-type

Specifies the type of an outbound interface of a reverse CR-LSP on the egress.

-
interface-number

Specifies the number of an outbound interface of a reverse CR-LSP on the egress.

-
out-label out-label-value

Specifies an outgoing label value on the egress.

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 for CT0.

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 smaller than the value of bandwidth.

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 to each other 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 reverse 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.2.3.2, outgoing interface to GE 0/1/0, the outgoing label value to 17, and CT0 bandwidth to 1000 kbit/s for a reverse 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] backward nexthop 10.2.3.2 outgoing-interface GigabitEthernet 0/1/0 out-label 17 bandwidth ct0 1000 pir 2000
Parent Topic: MPLS TE Configuration Commands
Copyright © Huawei Technologies Co., Ltd.
Copyright © Huawei Technologies Co., Ltd.
< Previous topic Next topic >