(Optional) Configuring a Transit Node of a Static Bidirectional Co-routed LSP

The transit node of a static bidirectional co-routed LSP needs to be manually specified. This configuration is optional because a static bidirectional co-routed LSP may have no transit node.

Context

Skip this procedure if a static bidirectional co-routed LSP has only an ingress and an egress. If a static bidirectional co-routed LSP has a transit node, perform the following steps on this transit node:

Procedure

Run system-view
The system view is displayed.
Run bidirectional static-cr-lsp transit lsp-name
A static bidirectional co-routed LSP is created, and the static bidirectional LSP view is displayed.

lsp-name specified on a transit node or an egress cannot be the same as the existing tunnel name on the transit node or the egress.
Run forward in-label in-label-value { nexthop next-hop-address | outgoing-interface interface-type interface-number } ^* out-label out-label-value [ ingress-lsrid ingress-lsrid egress-lsrid egress-lsrid tunnel-id tunnel-id ] [ bandwidth ct0 bandwidth | pir pir ] ^*
A forward CR-LSP is configured on the transit node.
Run backward in-label in-label-value { nexthop next-hop-address | outgoing-interface interface-type interface-number } ^* out-label out-label-value [ bandwidth ct0 bandwidth | pir pir ] ^*
A reverse CR-LSP is configured on the transit node.
(Optional) Run description text
A description is configured for the static bidirectional co-routed CR-LSP.
Run commit
The configuration is committed.