(Optional) Referencing the CR-LSP Attribute Template to Set Up a CR-LSP

Context

You can create a CR-LSP by using the following methods:

Creating a CR-LSP without using a CR-LSP attribute template
Creating a CR-LSP by using a CR-LSP attribute template

It is recommended that a CR-LSP attribute template be used to set up a CR-LSP because this method has the following advantages:
- A CR-LSP attribute template can greatly simplify the configurations of CR-LSPs.
- A maximum of three CR-LSP attribute templates can be created for a hot-standby CR-LSP or an ordinary backup CR-LSP. You can set up a hot-standby CR-LSP or an ordinary backup CR-LSP with different path options. (Among the three attribute templates, the template with the smallest sequence number is preferred. If the setup fails, the template with a greater sequence number is used.)
- If configurations of a CR-LSP attribute template are modified, configurations of the CR-LSPs established by using the CR-LSP attribute template are automatically updated, which makes the configurations of CR-LSPs more flexible.

The preceding two methods can be used together. If the TE attribute configured in the tunnel interface view and the TE attribute configured through a CR-LSP attribute template coexist, the former takes precedence over the latter.

Perform the following configurations on the ingress node of an MPLS TE tunnel.

Configuring a CR-LSP Attribute Template

Steps 3 to 10 are optional. You can perform one or more of them as required.
Setting Up a CR-LSP by Using a CR-LSP Attribute Template

You can use a CR-LSP attribute template to set up the primary CR-LSP, hot-standby CR-LSP, and ordinary backup CR-LSP.

Procedure

Configure a CR-LSP attribute template.
1. Run system-view
  The system view is displayed.
2. Run lsp-attribute lsp-attribute-name
  A CR-LSP attribute template is created and the LSP attribute view is displayed.
  
  A CR-LSP attribute template can be deleted only when it is not used by any tunnel interface.
3. (Optional) Run bandwidth { ct0 ct0-bandwidth | ct1 ct1-bandwidth }
  The bandwidth is set for the CR-LSP attribute template.
  
  Perform this step to provide bandwidth protection for services transmitted on a TE tunnel established using this template.
4. (Optional) Run explicit-path path-name
  An explicit path is configured for the CR-LSP attribute template.
  
  Perform this step to control the path over which a TE tunnel is established.
5. (Optional) Run affinity property affinity-value [ mask mask-value ]
  The affinity attribute is set for the CR-LSP attribute template.
  
  By default, both the affinity value and the affinity mask are 0x0.
  
  This step helps you control the path over which a TE tunnel is established.
6. (Optional) Run priority setup_priority_value [ hold_priority_value ]
  The setup priority and hold priority are set for the CR-LSP attribute template.
  
  By default, both the setup priority and the hold priority are 7.
  
  If resources are insufficient, setting the setup and holding priority values helps a device release resources used by LSPs with lower priorities and use the released resources to establish LSPs with higher priorities.
7. (Optional) Run hop-limit hop-limit
  The hop limit is set for the CR-LSP attribute template.
  
  By default, the hop limit is 32.
8. (Optional) Run fast-reroute [ bandwidth ]
  FRR is enabled for the CR-LSP attribute template.
  
  By default, FRR is disabled.
  
  FRR is recommended for networks requiring high reliability.
  Before enabling or disabling FRR for the CR-LSP attribute template, note the following:
  - After FRR is enabled, the system automatically records routes for the CR-LSP.
  - After FRR is disabled, attributes of the bypass tunnel are automatically deleted.
  - The undo mpls te record-route command can take effect only when FRR is disabled.
9. (Optional) Run record-route [ label ]
  The system is configured to record routes for the CR-LSP attribute template.
  
  By default, the system does not record routes for the CR-LSP attribute template.
  
  Perform this step to view label information and the number of hops on a path over which a TE tunnel is established.
10. (Optional) Run bypass-attributes { bandwidth bandwidth | priority setup_priority_value [ hold_priority_value ] }^*
  The bypass tunnel attributes are configured for the CR-LSP attribute template.
  
  By default, the bypass tunnel attributes are not configured.
11. Run commit
  Configurations of the CR-LSP attribute template are committed.
  When the CR-LSP attribute template is used to set up a CR-LSP:
  - The CR-LSP is removed and a new CR-LSP is created if the Break-Before-Make attribute (the priority attribute) of the CR-LSP attribute template is modified.
  - The CR-LSP is removed after an eligible CR-LSP is created and traffic switches to the new CR-LSP if the Make-Before-Break attribute of the CR-LSP attribute template is modified.
Set up a CR-LSP by using a CR-LSP attribute template.
1. Run system-view
  The system view is displayed.
2. Run interface tunnel interface-number
  The tunnel interface view is displayed.
3. Run mpls te primary-lsp-constraint { dynamic | lsp-attribute lsp-attribute-name }
  The primary CR-LSP is set up through the specified CR-LSP attribute template.
  
  If dynamic is used, it indicates that when a CR-LSP attribute template is used to set up a primary CR-LSP, all attributes in the template use the default values.
4. (Optional) Run mpls te hotstandby-lsp-constraint number { dynamic | lsp-attribute lsp-attribute-name }
  The hot-standby CR-LSP is set up by using the specified CR-LSP attribute template.
  
  A maximum of three CR-LSP attribute templates can be used to set up a hot-standby CR-LSP. The hot-standby CR-LSP must be consistent with the primary CR-LSP in the attributes of the setup priority, hold priority, and bandwidth type. To set up a hot-standby CR-LSP, you should keep on attempting to use CR-LSP attribute templates one by one in ascending order of the number of the attribute templates until the hot-standby CR-LSP is set up.
  
  If dynamic is used, it indicates that the hot-standby CR-LSP is assigned the same bandwidth and priority as the primary CR-LSP, but specified with a different path from the primary CR-LSP.
5. (Optional) Run mpls te backup hotstandby-lsp-constraint wtr interval
  The Wait to Restore (WTR) time is set for the traffic to switch back from the hot-standby CR-LSP to the primary CR-LSP.
  
  By default, the WTR time for the traffic to switch back from the hot-standby CR-LSP to the primary CR-LSP is 10 seconds.
  
  The hot-standby CR-LSP specified in the mpls te backup hotstandby-lsp-constraint wtr command must be an existing one established by running the mpls te hotstandby-lsp-constraint command.
6. (Optional) Run mpls te ordinary-lsp-constraint number { dynamic | lsp-attribute lsp-attribute-name }
  The ordinary backup CR-LSP is set up by using the specified CR-LSP attribute template.
  
  A maximum of three CR-LSP attribute templates can be used to set up an ordinary backup CR-LSP. The ordinary backup CR-LSP must be consistent with the primary CR-LSP in the attributes of the setup priority, hold priority, and bandwidth type. To set up an ordinary backup CR-LSP, you should keep on attempting to use CR-LSP attribute templates one by one in ascending order of the number of the attribute template until the ordinary backup CR-LSP is set up.
  
  If dynamic is used, it indicates that the ordinary backup CR-LSP is assigned the same bandwidth and priority as the primary CR-LSP.
7. (Optional) Run mpls te backup ordinary-lsp-constraint lock
  The attribute template of the ordinary backup CR-LSP is locked.
  
  By default, the attribute template of the ordinary backup CR-LSP is not locked.
  
  Before running this command, you must run the mpls te ordinary-lsp-constraint command to reference the CR-LSP attribute template to set up an ordinary backup CR-LSP.
8. Run mpls te commit
  The configurations of the CR-LSP are committed.