ACL-based Simplified Traffic Policy Overview

The device to which an ACL-based simplified traffic policy is applied matches packet characteristics with ACLs and provides the same QoS for packets matching ACL rules, implementing differentiated services.

To control traffic entering a network, configure an ACL to match information such as the source IP address, fragment flag, destination IP address, source port number, and source MAC address and then configure an ACL-based simplified traffic policy so that the device can filter, polices, re-marks, counts, mirrors, or redirects packets matching ACL rules.

Compared with a traffic policy based on traffic classifiers, an ACL-based simplified traffic policy is easy to configure because you do not need to configure a traffic classifier, traffic behavior, or traffic policy independently. However, an ACL-based simplified traffic policy defines less matching rules than a traffic policy based on traffic classifiers.

The packets destined for the local switch are sent to the CPU. After functions related to some protocols such as BGP, OSPF, and LACP are enabled, packets of these protocols are also sent to the CPU. If packets sent to the CPU match both CPCAR and the ACL rule defined in the simplified traffic policy, but the actions to be taken conflict with each other, the ACL rule defined in the simplified traffic policy takes effect.