Configuring an SRv6 TE Policy

An SRv6 TE Policy can either be configured manually or delivered by a controller. This section describes how to configure an SRv6 TE Policy manually.

Context

SRv6 TE Policies are used to direct traffic to traverse an SRv6 TE network. Each SRv6 TE Policy can have multiple candidate paths with different preferences. A valid candidate path with the highest preference is selected as the primary path, and a valid candidate path with the second highest preference as the backup path.

Procedure

Configure a segment list.
1. Run system-view
  The system view is displayed.
2. Run segment-routing ipv6
  SRv6 is enabled, and the SRv6 view is displayed.
3. Run segment-list list-name
  A segment list is created for the SRv6 TE Policy candidate path, and the segment list view is displayed.
4. Run index index sid ipv6 ipv6address [ compress block block-value ] [ verification ]
  The next-hop SID in the segment list is specified.
  
  You can run the command multiple times to specify multiple SIDs. The system generates a SID stack by index index in ascending order. If a candidate path in the SRv6 TE Policy is preferentially selected, traffic is forwarded using the segment list of the candidate path. A maximum of 10 SIDs can be configured for each segment list.
  In SRv6 SRH compression scenarios, pay attention to the following points:
  1. When configuring a segment list, you need to configure the compress block block-value parameter, with the value of block-value being the same as that of block-length specified in the locator locator-name [ ipv6-prefix ipv6-address prefix-length compress block block-length [ compress-static compress-length | static static-length | args args-length | flex-algo flexAlgoId ] ^* ] command.
  2. The last SID in a segment list cannot be of the COC type.
  3. After the verification parameter is configured, the system verifies the IGP route reachability of the SID in the corresponding SRv6 TE Policy. Do not configure this parameter for inter-AS or binding SIDs. Otherwise, IGP routes are unreachable, and SID reachability verification fails.
5. Run commit
  The configuration is committed.
Configure an SRv6 TE Policy.
1. Run system-view
  The system view is displayed.
2. Run segment-routing ipv6
  SRv6 is enabled, and the SRv6 view is displayed.
3. (Optional) Run ttl-mode { uniform | pipe }
  A TTL processing mode is configured for SRv6 TE Policies to which public IP routes recurse.
4. (Optional) Run srv6-te-policy switch-delay switchDelay delete-delay deleteDelay
  Switching and deletion delays are configured for all SRv6 TE Policies.
5. Run srv6-te-policy locator locator-name
  A locator is configured for you to specify a binding SID for the SRv6 TE Policy to be created.
6. Run srv6-te policy name-value endpoint endpoint-ip color color-value
  An SRv6 TE Policy is created, and the SRv6 TE Policy view is displayed.
7. (Optional) Run encapsulation-mode { insert | encaps | insert-encaps }
  An SRv6 TE Policy encapsulation mode is configured.
  
  When forwarded data enters an SRv6 TE Policy, new SID stack encapsulation is required. If no service SID is available, the SRv6 TE Policy needs to use the encaps encapsulation mode. Otherwise, the endpoint cannot remove the SRv6 encapsulation. The headend encapsulates IPv6 header and SRH information into data when the data enters the SRv6 TE Policy, and the endpoint implements the USD flavor to remove the encapsulated IPv6 header and SRH information.
8. (Optional) Run binding-sid binding-sid
  A binding SID is specified for the SRv6 TE Policy.
  
  The value of binding-sid must be within the static range defined using the locator locator-name [ ipv6-prefix ipv6-address prefix-length [ static static-length | args args-length ] ^* ] command.
9. Run candidate-path preference preference
  A candidate path with a specified preference is configured for the SRv6 TE Policy.
  
  Each SRv6 TE Policy supports multiple candidate paths. A larger preference value indicates a higher candidate path preference. If multiple candidate paths are configured, the one with the highest preference takes effect.
10. Run segment-list list-name [ weight weight-value | path-mtu mtu-value ] ^*
  A segment list is referenced by the candidate path of the SRv6 TE Policy.
  
  The segment list must have been created using the segment-list (Segment-Routing IPv6 view) command.
11. Run commit
  The configuration is committed.