(Optional) Locking a Backup CR-LSP Attribute Template
Context
A maximum of three hot-standby or ordinary backup attribute templates can be used for establishing a hot-standby or an ordinary CR-LSP. TE attribute templates are prioritized. The system attempts to use each template in ascending order by priority to establish a backup CR-LSP.
If an existing backup CR-LSP is set up using a lower-priority attribute template, the system automatically attempts to set up a new backup CR-LSP using a higher-priority attribute template, which is unneeded sometimes. If a CR-LSP has been established using the locked CR-LSP attribute template, the CR-LSP will not be unnecessarily reestablished using another template with a higher priority. Locking a CR-LSP attribute template allows the existing CR-LSP to keep transmitting traffic without triggering unneeded traffic switchovers, efficiently using system resources.
Perform the following configurations on the ingress node of an MPLS TE tunnel.
Procedure
- Run system-view
The system view is displayed.
- Run interface tunnel tunnel-number
The tunnel interface view is displayed.
- Run mpls te primary-lsp-constraint { dynamic | lsp-attribute lsp-attribute-name }
An attribute template is specified for setting up a primary CR-LSP.
- Run either of the following commands as needed to establish
a backup CR-LSP:
- To establish an ordinary backup CR-LSP, run mpls te ordinary-lsp-constraint number { dynamic | lsp-attribute lsp-attribute-name }
- To establish a hot-standby CR-LSP, run mpls te hotstandby-lsp-constraint number { dynamic | lsp-attribute lsp-attribute-name }
- Run either of the following commands as needed to lock
a backup CR-LSP attribute template:
- To lock an attribute template for an ordinary backup CR-LSP, run mpls te backup ordinary-lsp-constraint lock
- To lock an attribute template for a hot-standby CR-LSP, run mpls te backup hotstandby-lsp-constraint lock
A used attribute template can be unlocked after the undo mpls te backup ordinary-lsp-constraint lock or undo mpls te backup hotstandby-lsp-constraint lock command is run. After unlocking templates, the system uses each available template in ascending order by priority. If a template has a higher priority than that of the currently used template, the system establishes a CR-LSP using the higher-priority template.
- Run mpls te commit
The configuration is committed.