20Step Command Remarks2. Create a traffic class andenter traffic class view.traffic classifier classifier-name[ operator { and | or } ] By default, no traffic class exists.3. Configure match criteria. if-match [ not ] match-criteriaBy default, no match criterion isconfigured.For more information, see theif-match command in ACL andQoS Command Reference.Defining a traffic behaviorA traffic behavior is a set of QoS actions (such as traffic policing and priority marking) to take on atraffic class.To define a traffic behavior:Step Command Remarks1. Enter system view. system-view N/A2. Create a traffic behavior andenter traffic behavior view. traffic behavior behavior-name By default, no traffic behaviorexists.3. Configure actions in thetraffic behavior.See the subsequent chapters,depending on the purpose of thetraffic behavior: traffic policing,traffic filtering, and prioritymarking.By default, no action is configuredfor a traffic behavior.Defining a QoS policyTo perform actions defined in a behavior for a class of packets, associate the behavior with the classin a QoS policy.To associate a traffic class with a traffic behavior in a QoS policy:Step Command Remarks1. Enter system view. system-view N/A2. Create a QoS policy andenter QoS policy view. qos policy policy-name By default, no QoS policy exists.3. Associate a traffic class witha traffic behavior to create aclass-behavior associationin the QoS policy.classifier classifier-namebehavior behavior-name[ insert-beforebefore-classifier-name ]By default, a traffic class is notassociated with a traffic behavior.Repeat this step to create moreclass-behavior associations.Applying the QoS policyYou can apply a QoS policy to the following destinations:• Interface—The QoS policy takes effect on the traffic sent or received on the interface.• User profile—The QoS policy takes effect on the traffic sent or received by the online users ofthe user profile.