Matching precedence order

When a packet is matched by multiple TCAM Lookups with the same action, a precedence order is followed.

For example, if a packet matches an IPv6 ACL with a count action and a MAC ACL with a count action, the IPv6 count action takes precedence and the MAC ACL will not count the packet. However, if a packet matches both an ACL and a policy with count actions, both will be counted. Regardless of precedence, if a packet is to be dropped by a configured feature, it will be dropped. Ingress packets do not take precedence over egress packets nor do egress packets take precedence over ingress packets.

The precedence order from highest to lowest is as follows:

Meter Actions:
Port Access Client Policy
Ingress Routed Port Policy
Port Policy
Routed Ingress VLAN Policy
VLAN Policy
Ingress Global Policy

QoS Actions:
Port Access Client Policy Remark
Routed Ingress Port Policy Remark
Ingress/Egress Port Policy Remark
Routed Ingress VLAN Policy Remark
Ingress/Egress VLAN Policy Remark
Global Policy Remark
QoS DSCP Map Entry
QoS COS Map Entry
QoS Port Config
MAC Port ACL Logging
IP Port ACL Logging
MAC VLAN ACL Logging
IP VLAN ACL Logging

Redirect actions:
Software Route
Policy L2 Tunnel
PBR Nexthop
Normal Route Table Hit
PBR Default Nexthop
Default Route Table Hit
Port Access Client Policy Captive-portal