20
2.
Create a class and
enter class
mapping view.
traffic classifier
classifier-name
[
operator
{
and
|
or
} ]
By default, the operator of a class is AND.
The operator of a class can be AND or OR.
•
AND
—A packet is assigned to a class only
when the packet matches all the criteria in the
class.
•
OR
—A packet is assigned to a class if it
matches any of the criteria in the class.
3.
Configure match
criteria.
if-match
[
not
]
match-criteria
For more information, see the
if-match
command in
ACL and QoS Command Reference
.
Defining a traffic behavior
A traffic behavior is a set of QoS actions (such as traffic filtering, shaping, policing, and priority
marking) to take on a class of traffic.
The system predefines some traffic behaviors and defines general QoS actions for them. A
user-defined behavior cannot be named the same as a system-defined behavior. You can use these
behaviors when defining a policy. The system-defined behaviors are as follows:
•
ef
—Expedited forwarding.
•
af
—Assured forwarding.
•
be
—Best-effort.
•
be-flow-based
—Uses the weighted random early detection (WRED) drop policy.
For more information about these system-defined behaviors, see "Configuring congestion
management."
To define a traffic behavior:
Step
Command
1.
Enter system view.
system-view
2.
Create a traffic behavior and
enter traffic behavior view
traffic behavior
behavior-name
3.
Configure actions in the
traffic behavior.
See the subsequent chapters, depending on the purpose of the traffic
behavior: traffic policing, traffic filtering, traffic redirecting, priority
marking, traffic accounting, and so on.
Defining a policy
You associate a behavior with a class in a QoS policy to perform the actions defined in the behavior
for the class of packets.
You can configure multiple class-behavior associations in a QoS policy, which are matched in the
order they are configured.
The system provides a predefined QoS policy named
default
. It includes the associations between
predefined classes and predefined traffic behaviors:
•
Class
ef
with behavior
ef
.
•
Classes
af1
through
af4
with behavior
af
.
•
Class
default-class
with behavior
be
.
You cannot name a user-defined QoS policy the same as the system-defined QoS policy.
To associate a class with a behavior in a policy:
