(Optional) Configuring the Transit Node of the Static CR-LSP

This section describes how to configure the transit nodes of a static CR-LSP. Before you set up a static CR-LSP, specify the transit nodes of the CR-LSP. This procedure is optional because the CR-LSP may have no transit node.

Context

If the static CR-LSP has only the ingress and egress, configuring a transit node is not needed. If the static CR-LSP has one or more transit nodes, perform the following steps on each transit node:

Procedure

Run system-view
The system view is displayed.
Run static-cr-lsp transit lsp-name incoming-interface interface-type interface-number in-label in-label { nexthop next-hop-address | outgoing-interface interface-type interface-number } ^* out-label out-label [ ingress-lsrid ingress-lsrid egress-lsrid egress-lsrid tunnel-id tunnel-id ] [ bandwidth [ ct0 ] bandwidth ]
The transit node of the static CR-LSP is configured.

If you need to modify parameters except lsp-name, run the static-cr-lsp transit command without running the undo static-cr-lsp transit command. This means that these parameters can be dynamically updated.

To modify all the parameters except lsp-name, run the static-cr-lsp transit command to set a new value. There is no need to run the undo static-cr-lsp transit command before changing a configured value.

If an Ethernet interface is used as an outbound interface, the nexthop next-hop-address parameter must be configured.
Run commit
The configuration is committed.