Configuring an SR-MPLS TE Policy

SR-MPLS TE Policy is a tunneling technology developed based on SR.

Context

SR-MPLS TE Policies are used to direct traffic to traverse an SR-MPLS TE network. Each SR-MPLS TE Policy can have multiple candidate paths with different preferences. The valid candidate path with the highest preference is selected as the primary path of the SR-MPLS TE Policy, and the valid candidate path with the second highest preference as the hot-standby path.

Procedure

Configure a segment list.
1. Run system-view
  The system view is displayed.
2. Run segment-routing
  SR is enabled globally and the Segment Routing view is displayed.
3. Run segment-list (Segment Routing view) list-name
  A segment list is created for an SR-MPLS TE candidate path and the segment list view is displayed.
4. Run index index sid label label
  A next-hop SID is configured for the segment list.
  
  You can run the command multiple times to configure multiple SIDs. The system generates a segment list with a label stack containing SIDs that are placed by index in ascending order. If a candidate path in the SR-MPLS 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.
5. Run commit
  The configuration is committed.
Configure an SR-MPLS TE Policy.
1. Run system-view
  The system view is displayed.
2. Run segment-routing
  SR is enabled globally and the Segment Routing view is displayed.
3. (Optional) Run sr-te-policy bgp-ls enable
  The SR-MPLS TE Policy is enabled to report information to BGP-LS.
  
  After the sr-te-policy bgp-ls enable command is run, the system sends the path information to BGP-LS with the candidate paths of the SR-MPLS TE Policy as the granularity.
4. Run sr-te policy policy-name [ endpoint ipv4-address color color-value ]
  An SR-MPLS TE Policy is created, the endpoint and color value are configured for the SR-MPLS TE Policy, and the SR-MPLS TE Policy view is displayed.
5. (Optional) Run binding-sid label-value
  A binding SID is configured for the SR-MPLS TE Policy.
  
  The value of label-value needs to be within the scope defined by the local-block begin-value end-value command.
6. (Optional) Run mtu mtu
  An MTU is configured for the SR-MPLS TE Policy.
7. (Optional) Run diffserv-mode { pipe service-class service-color | uniform }
  A DiffServ mode is configured for the SR-MPLS TE Policy to implement end-to-end QoS guarantee.
8. Run candidate-path preference preference
  A candidate path and its preference are configured for the SR-MPLS TE Policy.
  
  Each SR-MPLS TE Policy supports multiple candidate paths. A larger preference value indicates a higher preference. The candidate path with the highest preference takes effect.
9. Run segment-list (candidate path view) list-name [ weight weight-value ]
  A specified segment list of the SR-MPLS TE candidate path is referenced.
  
  The segment list must have been created using the segment-list (Segment Routing view) command.
  
  You can use the weight weight-value parameter to configure a weight for the segment list. If the weight configured for a segment list of a candidate path is less than the average weight, the segment list does not forward traffic. The average weight is calculated using the following formula:
  
  Average weight = Sum of weights of all segment lists of a candidate path/Maximum number of channels supported for load balancing
  
  For example, if the maximum number of channels supported for load balancing is M and a candidate path has a total of N segment lists, the average weight of the N segment lists is calculated as follows: (Weight 1 + Weight 2 + ... + Weight N)/M = X. In this example, X represents the average weight, and segment lists whose weights are less than X do not forward traffic.
10. Run commit
  The configuration is committed.