default match (SRv6 mapping policy service-class view)

Usage Scenario

Each SRv6 TE Policy in an SRv6 TE Flow Group has its own color attribute.

This command is used together with the index service-class match command.

Using the index service-class { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } * match srv6-te-policy color command, you can configure the mapping between a color and a service class.

Using the index service-class { be | af1 | af2 | af3 | af4 | ef | cs6 | cs7 } * match native-ip command, you can configure the mapping between native IPv6 links and service classes.

In an SRv6 mapping policy, the Service Class->Color->SRv6 TE Policy mapping is formed through the association of colors. After the service class value is associated with an SRv6 TE Policy, IP packets can be diverted to the SRv6 TE Policy based on the service class value. If the mapping between the service class and native IP link is configured, traffic is forwarded through IPv6 after the service class is associated with the native IP link.

The default match srv6-te-policy color command enables a device to redirect packets that do not match the service class configured using the index service-class match command to a specified SRv6 TE Policy.

The default match native-ip command configures the device to forward packets that do not match the service class configured using the index service-class match command through IPv6 by default.

Precautions

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.
4. The SRv6 mapping policy mapping rule with a smaller index value (BE < AF1 < AF2 < AF3 < AF4 < EF < CS6 < CS7) is preferred for traffic steering. 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.