You can configure a slice ID for an SRv6 TE Policy to associate services and forwarding resources.
Before configuring a slice ID for an SRv6 TE Policy, complete the following task:
A slice ID connects the control and forwarding planes. If services are forwarded over an SRv6 TE Policy's candidate path for which a slice ID has been configured, the ingress inserts SRH information into a packet and performs the following encapsulations in sequence: encapsulates the SID list of the SRv6 TE Policy, encapsulates the HBH header that carries the slice ID information, and encapsulates the IPv6 basic header. The ingress then forwards the packet, which is associated with the specified network slice interface based on the slice ID information.
If the active SID on the egress of an SRv6 TE Policy is a service SID advertised by the egress, the egress executes the service SID's instructions to decapsulate the packet and remove the SRH, HBH, and IPv6 basic headers.
An SRv6 TE Policy can be statically configured or delivered by a controller. In cases of the latter, the controller delivers a BGP Update message to a forwarder through a BGP IPv6 SR Policy peer relationship, and the BGP Update message carries the slice ID of the SRv6 TE Policy's candidate path.
This section describes how to configure a slice ID for a statically configured SRv6 TE Policy.
The system view is displayed.
SRv6 is enabled and the SRv6 view is displayed.
The SRv6 TE Policy view is displayed.
A candidate path and its preference are configured for the SRv6 TE Policy.
The larger the preference value, the higher the preference of the candidate path.
In the same SRv6 TE Policy, the valid candidate path with the highest preference is used as the primary path, while that with the second highest preference is used as the backup path.
A slice ID is configured for the candidate path of the SRv6 TE Policy.
Different slice IDs can be configured for different candidate paths of an SRv6 TE Policy.
The configuration is committed.