R3303-HP HSR6800 Routers ACL and QoS Configuration Guide

145
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 pre-defines 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.
To define a traffic behavior:
Ste
p
Command Remarks
1. Enter system view.
system-view N/A
2. Create a traffic behavior and
enter traffic behavior view.
traffic behavior behavior-name N/A
3. Configure actions in the traffic
behavior.
See the following parts in QoS configuration: traffic policing, traffic
filtering, traffic redirecting, priority marking, traffic accounting, and so
on.
Defining a policy
Configuring parent QoS 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.
The system provides a pre-defined 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:
Ste
p
Command
1. Enter system view.
system-view
2. Create a policy and enter policy view.
qos policy policy-name
3. Associate a class with a behavior in the policy.
classifier classifier-name behavior behavior-name
NOTE:
On some devices, if the ACL contains deny rules, the if-match clause is i
g
nored and the matchin
g
process
continues.