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.
Context
After an SRv6 TE Policy is configured, traffic needs to be steered into it for forwarding. This process is called traffic steering. Currently, SRv6 TE Policies can be used for various services, such as BGP L3VPN and EVPN services.
Procedure
- Configure a tunnel policy.
Perform any of the following configurations based on the traffic steering mode you select.
-
- Run system-view
The system view is displayed.
- Run tunnel-policy policy-name
A tunnel policy is created, and the tunnel policy view is displayed.
- (Optional) Run description description-information A description is configured for the tunnel policy.
- Run tunnel select-seq ipv6 srv6-te-policy load-balance-number load-balance-numberThe tunnel selection sequence and number of tunnels for load balancing are configured.
After the preceding configurations are complete, routes are allowed to recurse to SRv6 TE Policies. If the color and next hop of a route are the same as the color and endpoint of an SRv6 TE Policy, respectively, the route can successfully recurse to the SRv6 TE Policy. In this case, the traffic forwarded through the route can be steered into the SRv6 TE Policy.
- Run commit
The configuration is committed.
- Run system-view
DSCP-based traffic steering in scenarios where an SRv6 TE flow group is dynamically created through an SRv6 mapping policy
EVPN VPWS and EVPN VPLS services do not support DSCP-based traffic steering.
- Run system-view
The system view is displayed.
- Run segment-routing ipv6
The SRv6 view is displayed.
- Run mapping-policy name-value color color-value
An SRv6 mapping policy is created, and the SRv6 mapping policy view is displayed.
- (Optional) Run description description-value
A description is configured for the SRv6 mapping policy.
- Run match-type dscp
The mapping type of the SRv6 mapping policy is set to DSCP.
Run index index-value dscp { ipv4 | ipv6 } { { dscpBegin [ to dscpEnd ] } &<1-64> } match { srv6-te-policy color color-value | native-ip } or { ipv4 | ipv6 } default match { srv6-te-policy color color-value | native-ip }
A rule is configured either for the mapping between the color values of SRv6 TE Policies in an SRv6 TE flow group and the DSCP values of packets or for the mapping between native IP links in an SRv6 TE flow group and the DSCP values of packets.
In an SRv6 mapping policy, you can configure a separate color-DSCP mapping rule for both the IPv4 address family traffic and IPv6 address family traffic. In the same address family (IPv4 or IPv6), each DSCP value can be mapped to only one color value. Furthermore, such a mapping rule can be configured for an SRv6 TE Policy only if this policy is up.
When IPv4/IPv6 packets with DSCP values enter an SRv6 TE flow group, they are matched against the following rules in sequence to achieve forwarding:
1. The packets are first strictly matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with specified DSCP values in the corresponding address family.
2. If the matching fails, the packets are matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with the default priority in the local address family.
3. If the matching fails, the packets are matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with the smallest DSCP value in the local address family.
4. If the matching fails, the packets are matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with the default priority in the other address family.
5. If the matching fails, the packets are matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with the smallest DSCP value in the other address family.
- Run quit
Return to the SRv6 view.
- Run quit
Return to the system view.
- Run tunnel-policy policy-name
A tunnel policy is created, and the tunnel policy view is displayed.
- (Optional) Run description description-information
A description is configured for the tunnel policy.
Run tunnel select-seq ipv6 srv6-te-flow-group load-balance-number loadBalanceNumber
A tunnel selection policy is configured.
- Run commit
The configuration is committed.
- Run system-view
Service class-based traffic steering in scenarios where an SRv6 TE flow group is dynamically created through an SRv6 mapping policy
- Run system-view
The system view is displayed.
- Run segment-routing ipv6
The SRv6 view is displayed.
- Run mapping-policy name-value color color-value
An SRv6 mapping policy is created, and the SRv6 mapping policy view is displayed.
- (Optional) Run description description-value
A description is configured for the SRv6 mapping policy.
- Run match-type service-class
The mapping type of the SRv6 mapping policy is set to Service Class.
Run index index-value service-class { ipv4 | ipv6 } { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } * match { srv6-te-policy color color-value | native-ip } or default match { srv6-te-policy color color-value | native-ip }
A rule is configured either for the mapping between the color values of SRv6 TE Policies in an SRv6 TE flow group and the service class values of packets or for the mapping between native IP links in an SRv6 TE flow group and the service class values of packets.
In an SRv6 mapping policy, you can specify a rule for the mapping between the color values of SRv6 TE Policies and the service class values of packets or for the mapping between native IP links and the service class values of packets. Each service class value can be associated with only one SRv6 TE Policy or native IP link. Furthermore, such a mapping rule can be configured for an SRv6 TE Policy only if this policy is up.
When packets with service class values enter an SRv6 TE Policy group, they are matched against the following rules in sequence to achieve forwarding:
1. The packets are first strictly matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with the corresponding service class value.
2. If the matching fails, the packets are matched against the SRv6 TE Policy-specific or native IP link-specific rule configured with the default priority.
3. If the rule configured with the default priority does not exist or it fails to go up, the packets are matched against the SRv6 mapping policy rule that is configured with the smallest index and remains up. As such, it is recommended that low-priority service classes (BE < AF1 < AF2 < AF3 < AF4 < EF < CS6 < CS7) be specified in the SRv6 mapping policy rule with a small index. This ensures that unmatched traffic preferentially preempts the low-priority bandwidth instead of the high-priority bandwidth.
- Run quit
Return to the SRv6 view.
- Run quit
Return to the system view.
- Run tunnel-policy policy-name
A tunnel policy is created, and the tunnel policy view is displayed.
- (Optional) Run description description-information
A description is configured for the tunnel policy.
Run tunnel select-seq ipv6 srv6-te-flow-group load-balance-number loadBalanceNumber
A tunnel selection policy is configured.
- Run commit
The configuration is committed.
- Run system-view
-
- Configure service recursion to an SRv6 TE Policy.
Configure BGP L3VPN service recursion to an SRv6 TE Policy.
For details about how to configure BGP L3VPN, see Configuring a Basic BGP/MPLS IP VPN.
Run system-view
The system view is displayed.
- Run ip vpn-instance vpn-instance-name
The VPN instance view is displayed.
- Run ipv4-family
The VPN instance IPv4 address family view is displayed.
- Run tnl-policy policy-name
A tunnel policy is applied to the VPN instance IPv4 address family.
Run commit
The configuration is committed.
Configure BGP L3VPNv6 service recursion to an SRv6 TE Policy.
For details about how to configure BGP L3VPNv6, see Configuring a Basic BGP/MPLS IPv6 VPN.
Run system-view
The system view is displayed.
- Run ip vpn-instance vpn-instance-name
The VPN instance view is displayed.
- Run ipv6-family
The VPN instance IPv6 address family view is displayed.
- Run tnl-policy policy-name
The specified tunnel policy is applied to the VPN instance IPv6 address family.
Run commit
The configuration is committed.
Configure EVPN service recursion to an SRv6 TE Policy.
For details about how to configure EVPN, see Configuring BD-EVPN Functions.
To apply a tunnel policy to an EVPN L3VPN instance, perform the following steps:Run system-view
The system view is displayed.
- Run ip vpn-instance vpn-instance-name
The VPN instance view is displayed.
- Run ipv4-family or ipv6-family
The VPN instance IPv4 or IPv6 address family view is displayed.
- Run tnl-policy policy-name evpn
A tunnel policy is applied to the EVPN L3VPN instance.
Run commit
The configuration is committed.
To apply a tunnel policy to a BD EVPN instance, perform the following steps:Run system-view
The system view is displayed.
Run evpn vpn-instance vpn-instance-name bd-mode
The BD EVPN instance view is displayed.
Run tnl-policy policy-name
A tunnel policy is applied to the BD EVPN instance.
Run commit
The configuration is committed.
To apply a tunnel policy to an EVPN instance that works in EVPN VPWS mode, perform the following steps:Run system-view
The system view is displayed.
Run evpn vpn-instance vpn-instance-name vpws
The view of the EVPN instance that works in EVPN VPWS mode is displayed.
Run tnl-policy policy-name
A tunnel policy is applied to the EVPN instance that works in EVPN VPWS mode.
Run commit
The configuration is committed.
To apply a tunnel policy to a basic EVPN instance, perform the following steps:Run system-view
The system view is displayed.
Run evpn vpn-instance vpn-instance-name
The basic EVPN instance view is displayed.
Run tnl-policy policy-name
A tunnel policy is applied to the basic EVPN instance.
Run commit
The configuration is committed.