2-5If both a QoS policy referencing CAR and the qos car command are configured on an interface, theQoS policy takes effect.To ensure that a policy can be applied successfully, follow these guidelines when configuring a trafficbehavior:z Do not configure the redirect to CPU, redirect to interface, and redirect to next hop in the sametraffic behavior, because they are conflicting.z Do not configure the filter deny action or an aggregation CAR action with the accounting action inthe same traffic behavior, because they are conflicting.Defining a PolicyA policy defines the mapping between a class and a traffic behavior.In a policy, multiple class-to-traffic-behavior mappings can be configured, and these mappings areexecuted according to the order configured.Follow these steps to define a policy:To do… Use the command… RemarksEnter system view system-view —Create a policy and enter policyview qos policy policy-name RequiredSpecify the traffic behavior for aclass in the policyclassifier tcl-name behaviorbehavior-name RequiredDisplay the specified class andits associated traffic behavior inthe QoS policydisplay qos policyuser-defined [ policy-name[ classifier tcl-name ] ]OptionalAvailable in any viewThe ACL referenced by a QoS policy is used for traffic classification only and therefore the deny andpermit actions in the ACL rules are ignored. How the traffic matching the ACL is handled is decided bythe traffic behavior in the QoS policy.QoS Policy Configuration ExampleNetwork requirementsConfigure a QoS policy test_policy to limit the rate of packets with IP precedence 6 to 100 kbps.
