Configuring a Device to Redirect IPv6 VPN Traffic to an SRv6 TE Policy Through Multi-Field Classification

The redirection function can be used to steer IPv6 VPN traffic to an SRv6 TE Policy.

Prerequisites

Before configuring a device to redirect IPv6 VPN traffic to an SRv6 TE Policy through multi-field classification, complete either of the following tasks:

Context

If some IPv6 VPN traffic experiences congestion, QoS multi-field classification can be used to identify and redirect the traffic to an SRv6 TE Policy, resolving the congestion issue. The factors involved in the redirection are an endpoint, color, and SID. If a redirection rule match fails, multi-field classification does not take effect. In this case, the traffic is forwarded over common IPv6. If the SRv6 TE Policy fails, multi-field classification also fails. In this case, the traffic is also forwarded over common IPv6.

Procedure

Run system-view
The system view is displayed.
Run traffic classifier classifier-name [ operator { and | or } ]
A traffic classifier is defined and its view is displayed.
Configure if-match clauses to define matching conditions for IPv6 VPN traffic.
For details, see Defining a Traffic Classifier.
Run quit
Exit the traffic classifier view.
Run traffic behavior behavior-name
A traffic behavior is defined and its view is displayed.
Run redirect srv6-te policy endpoint color [ { sid | vpnsid } sid-ip ]
The device is enabled to redirect IPv6 VPN traffic to an SRv6 TE Policy.

You can specify sid and vpnsid to redirect IPv6 VPN traffic to the IPv6 public network and IPv6 VPN through SRv6 TE Policies, respectively.

sid-ip must be an End.DT6 SID, which is configured using the opcode func-opcode end-dt6 [ vpn-instance vpn-instance-name evpn ] command.
Run quit
Exit the traffic behavior view.
Run traffic policy policy-name
A traffic policy is defined and its view is displayed.
Run classifier classifier-name behavior behavior-name
The traffic behavior is specified for the traffic classifier in the traffic policy.
Run quit
Exit the traffic policy view.
Run ip vpn-instance vpn-instance-name
A VPN instance is created and its view is displayed.
Run ipv6-family
The VPN instance IPv6 address family is enabled, and the view of this address family is displayed.
Run route-distinguisher route-distinguisher
An RD is configured for the VPN instance IPv6 address family.

A VPN instance IPv6 address family takes effect only after being configured with an RD.
Run quit
Exit the VPN instance IPv6 address family view.
Run quit
Exit the VPN instance view.
Run ip binding vpn-instance vpn-instance-name
The VPN instance is bound to the interface.

The value of vpn-instance-name must be the same as the name of the VPN instance created using the ip vpn-instance vpn-instance-name command.
Run interface interface-type interface-number [ .subinterface-number ]
The interface view is displayed.
Run traffic-policy policy-name inbound
The traffic policy is applied to the interface.
Run commit
The configuration is committed.

Verifying the Configuration

After configuring the device to redirect IPv6 VPN traffic to an SRv6 TE Policy through multi-field classification, perform the following operations to verify the configuration:

Run the display traffic classifier { system-defined | user-defined } [ classifier-name ] command to check the traffic classifier configuration.
Run the display traffic behavior user-defined [ behavior-name ] command to check the traffic behavior configuration.
Run the display traffic policy user-defined [ policy-name [ classifier classifier-name ] ] command to check the associations between all traffic classifiers and traffic behaviors or between specified ones in the traffic policy.