3-4Suppose the logical relationship between classification rules is and. Note the following when using theif-match command to define matching rules.z If multiple matching rules with the acl or acl ipv6 keyword specified are defined in a class, theactual logical relationship between these rules is or when the policy is applied.z If multiple matching rules with the customer-vlan-id or service-vlan-id keyword specified aredefined in a class, the actual logical relationship between these rules is or.The matching criteria listed below must be unique in a traffic class with the operator being AND.Therefore, even though you can define multiple if-match clauses for these matching criteria or inputmultiple values for a list argument (such as the 8021p-list argument) listed below in a traffic class,avoid doing that. Otherwise, the QoS policy referencing the class cannot be applied to interfacessuccessfully.z customer-dot1p 8021p-listz destination-mac mac-addressz dscp dscp-listz ip-precedence ip-precedence-listz service-dot1p 8021p-listz source-mac mac-addressTo create multiple if-match clauses or specify multiple values for a list argument for any of thematching criteria listed above, ensure that the operator of the class is OR.Defining a Traffic BehaviorTo define a traffic behavior, you must first create it and then configure QoS actions such as prioritymarking and redirect in traffic behavior view.Follow these steps to define a traffic behavior:To do… Use the command… RemarksEnter system view system-view —Create a traffic behavior and entertraffic behavior view traffic behavior behavior-name RequiredConfigure other actions in thetraffic behaviorSee the subsequent sections depending on the purpose of the trafficbehavior: traffic policing, traffic filtering, traffic redirecting, prioritymarking, traffic accounting and so on.