Defining A Traffic Behavior - 3Com S7906E Configuration Manual

Suppose the logical relationship between classification rules is and. Note the following when using the
if-match command to define matching rules.
If multiple matching rules with the acl or acl ipv6 keyword specified are defined in a class, the
actual logical relationship between these rules is or when the policy is applied.
If multiple matching rules with the customer-vlan-id or service-vlan-id keyword specified are
defined 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 input
multiple 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 interfaces
successfully.
customer-dot1p 8021p-list
destination-mac mac-address
dscp dscp-list
ip-precedence ip-precedence-list
service-dot1p 8021p-list
source-mac mac-address
system-index index-value-list
To create multiple if-match clauses or specify multiple values for a list argument for any of the matching
criteria listed above, ensure that the operator of the class is OR.

Defining a Traffic Behavior

To define a traffic behavior, you must first create it and then configure QoS actions such as priority
marking and redirect in traffic behavior view.
Follow these steps to define a traffic behavior:
To do...
Enter system view
Create a traffic behavior and
enter traffic behavior view
Configure other actions in the
traffic behavior
Use the command...
system-view
traffic behavior
behavior-name
Refer to the subsequent sections depending on the purpose of the
traffic behavior: traffic policing, traffic filtering, traffic redirecting,
priority marking, traffic accounting and so on.
2-4
Remarks
—
Required