Configuring a candidate path to use manually configured SID lists
About this task
Before you specify a SID list for a candidate path, you need to create the SID list and add nodes to the SID list.
After you add nodes to a SID list, the system will sort the nodes in ascending order of node index.
The node with the smallest index represents the next hop of the source node on the forwarding path.
To reduce the SRH cost, you can use four 32-bit G-SIDs to represent one normal 128-bit SRv6 SID.
In a SID list, you can add a 128-bit SRv6 SID with a COC flavor, indicating that the next node of the current node is a 32-bit G-SID. For more information about G-SIDs, see "Configuring SRv6."
Restrictions and guidelines
When you add G-SIDs to a SID list, make sure the following conditions are met:
•
The SRv6 SID for the previous node of the G-SID must be End(COC32) SID or End.X(COC32)
SID.
•
The SRv6 SID for the last node does not contain the COC flavor. That is, you cannot use the
index index-number coc32 ipv6 command to specify the SRv6 SID for the penultimate node.
Procedure
1. Enter system view. system-view
2. Enter SRv6 view. segment-routing ipv6
3. Enter SRv6 TE view. traffic-engineering
4. Create a SID list and enter SID list view. segment-list segment-list-name
5. Add a node to the SID list.
Add a normal 128-bit SRv6 SID. index index-number ipv6 ipv6-address
Add a 128-bit SRv6 SID with the COC flavor, and specify the common prefix length for the next G_SID.
index index-number coc32 ipv6 ipv6-address common-prefix-length
6. Return to SRv6 TE view. quit
7. Enter SRv6 TE policy view. policy policy-name
8. Create and enter SRv6 TE policy candidate path view. candidate-paths
9. Set the preference for a candidate path and enter SRv6 TE policy path preference view. preference preference-value
By default, no candidate path preferences are set.
Each preference represents a candidate path.
10. Specify an explicit path for the candidate path.
170
