Configuring SRv6 BE Network Slicing

SRv6 BE network slicing enables a physical network to meet the differentiated requirements of various services.

Prerequisites

Before configuring SRv6 BE network slicing, complete the following task:

Configure an IGP to implement network layer connectivity.

Context

Network slicing divides a physical network into multiple virtual networks that contain specific network functions and consist of customized network topologies and network resources. This meets the service function requirements of different network slice tenants and provides SLA assurance.

Before planning network slices, you need to create network slice instances and allocate slice IDs. A physical network is divided into multiple network slices by dividing interface forwarding resources.

On the network shown in Figure 1, network slice instances are created on P1 and P3, network slice interfaces are planned and bound to the network slice instances, and forwarding resources such as bandwidth are reserved.

Figure 1 Interface-based network slice planning

In SRv6 BE network slicing scenarios, slice IDs are essential for connecting the control and forwarding planes, as shown in Figure 5.

Figure 2 Connecting the control and forwarding planes through slice IDs

Activating a Network Slice License: In network slicing scenarios, before binding a network slice to an interface, you need to allocate and activate a purchased network slice license to the specified board. After the corresponding function takes effect, you can increase network slice resources for the board.

Configuring Network Slice Instances: Configuring network slice instances is the first step for implementing network slicing. Interfaces can be added to network slices only after network slice instances are configured.

Configuring Network Slice Interfaces: You can configure network slice interfaces and specify the network slice instances to which they belong.

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 SRv6 BE Services: After SRv6 BE services are configured, they can be forwarded based on network slices.

Configuring Route Forwarding Based on Network Slices: You can associate services with forwarding resources based on a slice ID by associating a route color and the slice ID.

Verifying the Configuration: After configuring SRv6 BE network slicing, you can verify the configuration.