mpls te hotstandby-lsp-constraint

Function

The mpls te hotstandby-lsp-constraint command allows you to use a CR-LSP attribute template to set up a hot-standby CR-LSP.

The undo mpls te hotstandby-lsp-constraint command deletes the used CR-LSP attribute template.

No CR-LSP attribute template is used to set up a hot-standby CR-LSP by default.

Format

mpls te hotstandby-lsp-constraint number { dynamic | lsp-attribute lsp-attribute-name }

undo mpls te hotstandby-lsp-constraint number

Parameters

Parameter	Description	Value
number	Specifies the number of a CR-LSP attribute template. It indicates the sequence of using each CR-LSP attribute template to set up a hot-standby CR-LSPs The CR-LSP attribute templates are used in ascending order.	An integer ranging from 1 to 3.
dynamic	Indicates that when a hot-standby CR-LSP is being set up, it is assigned the same bandwidth and priority as the primary CR-LSP, but specified with a different path from the primary LSP.	-
lsp-attribute lsp-attribute-name	Specifies the name of a CR-LSP attribute template.	The value is an existing CR-LSP attribute template name.

Views

Tunnel interface view

Default Level

2: Configuration level

Usage Guidelines

A maximum number of three CR-LSP attribute templates can be configured to set up hot-standby CR-LSPs. The hot-standby CR-LSPs must be consistent with the primary CR-LSP in the following attributes:

Setup priority
Holding priority
Bandwidth type

In each of the three CR-LSP attribute template types corresponding to the primary CR-LSP, the hot-standby CR-LSP, and the ordinary backup CR-LSP respectively, only one attribute template can be specified with the dynamic parameter.

The parameter number is used to number each CR-LSP attribute template, which indicates the sequence of using each CR-LSP attribute template to set up a hot-standby CR-LSP. To set up a hot-standby CR-LSP, the system attempts to apply each CR-LSP attribute template by the template number in ascending order until a hot-standby CR-LSP is successfully up.

Before configuring the mpls te hotstandby-lsp-constraint command, you must run the mpls te primary-lsp-constraint command to use a CR-LSP attribute template to set up a primary CR-LSP.
When the mpls te hotstandby-lsp-constraint command is configured to help set up a hot-standby CR-LSP, the record-route function is automatically enabled.

Example

# Use the attribute template named t2 to set up a hot-standby CR-LSP.

<HUAWEI> system-view
[HUAWEI] interface tunnel 1
[HUAWEI-Tunnel1] mpls te primary-lsp-constraint lsp-attribute t1
[HUAWEI-Tunnel1] mpls te hotstandby-lsp-constraint 1 lsp-attribute t2
[HUAWEI-Tunnel1] mpls te commit