Configuring an SRv6 TE Policy (Dynamic Delivery by a Controller)

SRv6 TE Policy is a tunneling technology developed based on SRv6.

Pre-configuration Tasks

Before configuring an SRv6 TE Policy, configure an IGP to implement network layer connectivity.

Context

An SRv6 TE Policy can either be manually configured on a forwarder through CLI or NETCONF, or be delivered to a forwarder after being dynamically generated through a protocol, such as BGP, on a controller. The dynamic mode facilitates network deployment.

The process for a controller to dynamically generate and deliver an SRv6 TE Policy to a forwarder is as follows:

The controller collects information, such as network topology and SID information, through BGP-LS. Network topology information includes link cost, latency, packet loss rate and more.
The controller and headend forwarder establish an IPv6 SR Policy address family-specific BGP peer relationship.
The controller computes an SRv6 TE Policy based on link cost, latency, packet loss rate and other factors, and then delivers the SRv6 TE Policy to the headend through a BGP peer relationship. The headend forwarder then generates SRv6 TE Policy entries.

Enabling SRv6: Other SRv6 TE Policy configurations can be performed only after SRv6 is enabled.

Configuring SRv6 SIDs: The headend can orchestrate network paths only if SIDs are allocated to adjacencies and nodes on the network.

Configuring TE Attributes: TE attributes configured for links are advertised to IS-IS. IS-IS advertises these attributes to BGP-LS, which then advertises them to a controller. This enables the controller to adjust links based on the TE attributes during SRv6 TE Policy calculation.

Configuring IS-IS Topology Advertisement to BGP-LS: After IS-IS topology information is advertised to BGP-LS, BGP-LS reports the topology information to a controller for path planning.

Configuring BGP Peer Relationships Between the Controller and Forwarder: This section describes how to configure BGP peer relationships between a controller and a forwarder, so that the controller can deliver SRv6 TE Policies to the forwarder. This improves SRv6 TE Policy deployment efficiency.

Configuring SRv6 TE Policy Status Advertisement to BGP-LS: Configure a forwarder to advertise SRv6 TE Policy status to BGP-LS. BGP-LS can then advertise the status to peers.

Configuring a BGP Extended Community: This section describes how to add a BGP extended community, that is, the color extended community, to routes through a route-policy, enabling the routes to perform SRv6 recursion based on the color value.

Configuring Traffic Steering: This section describes how to configure traffic steering to recurse a route to an SRv6 TE Policy so that traffic can be forwarded through a path in the SRv6 TE Policy.

Verifying the SRv6 TE Policy Configuration: After configuring SRv6 TE Policies, verify the configuration.