Usage Scenario
You can set different qos-local-id values for routes based on the IPv6 BGP route attributes. If traffic classification must be implemented based on qos-local-id values of IPv6 routes, run the if-match ipv6 qos-local-id command to configure a matching rule based on the IPv6 QoS policy ID.
Prerequisites
The association between BGP routes and QoS local routes has been defined in the route-policy, and QPPB has been enabled on the interface.
Configuration Impact
The configured traffic behavior is applied to packets that match the traffic classifier.
Precautions
When the ipv6 qos-local-id matching mode is enabled in a traffic policy:
- It cannot be enabled if the policy contains a C-B pair, and the following message is displayed:
Error: Please remove this classifier from the policy first.
- After it is configured, the policy does not support priority-based (dscp, tos, precedence) rules, and the following message is displayed:
Error: The ipv6 dscp,tos and precedence rules are not supported on the policy with match-type ipv6 qos-local-id enable.
- When the ipv6 qos-local-id matching mode is not configured for the policy, the ipv6 qos-local-id rule cannot be applied, and the following message is displayed:
Error: The ipv6 qos-local-id rule is not supported on the policy without match-type ipv6 qos-local-id enable.
- After it is configured, if the policy is applied to unsupported scenarios, the following messages are displayed (including in the global or bd view, on not supported interfaces, VSIs, VPNs, and behaviors):
a, For unsupported interfaces:Error:The policy cannot be configured on the interface with match-type ipv6 qos-local-id enable.
b, In the global view: Error: Global ACL and UCL cannot be applied with match-type ipv6 qos-local-id enable.
c, In the behavior view: Error: The policy with match-type ipv6 qos-local-id enable does not support the traffic-policy behavior.
d, In the bd view: Error: The policy cannot be configured on Bridge-Domain with the match-type ipv6 qos-local-id enable.
e, In the VSI view: Error: The policy cannot be configured on vsi with match-type ipv6 qos-local-id enable.
f, In the VPN view: Error: The policy cannot be configured on vpn-instance with match-type ipv6 qos-local-id enable.
- When both QPPB and the traffic classifier are configured and matched, if their actions are both CAR, the configured lower bandwidth takes effect.
- If another same action (actions other than deny or redirect) is configured, the action specified for QPPB takes effect for incoming traffic, and the action specified in the traffic policy takes effect for outgoing traffic.
- If different actions (actions other than deny or redirect) are configured for QPPB and the traffic policy, both actions take effect.
- If a redirection or deny action is configured in an inbound interface ACL, the QPPB action does not take effect. If the action deny is configured for outbound QPPB, the interface ACL does not take effect.
- The ipv6 qos-local-id rule cannot be configured in a common policy profile. It can be configured only in a policy profile for which the ipv6 qos-local-id matching mode has been enabled.
- If the traffic matches both the ACL for a traffic policy and QPPB ACL and the forwarding action in the traffic behavior is redirect/deny/permit, the redirect and deny actions in the QPPB action table do not take effect.
- If outgoing traffic on an interface matches both a traffic policy and a QPPB policy and the traffic policy is implemented based on the qos-local-id, only the QPPB policy takes effect.