Defining A Traffic Behavior; Defining A Qos Policy; Applying The Qos Policy - H3C WX5500H series User Configuration Manual

Step
Create a traffic class and
2.
enter traffic class view.
Configure match criteria.
3.

Defining a traffic behavior

A traffic behavior is a set of QoS actions (such as traffic policing and priority marking) to take on a
traffic class.
To define a traffic behavior:
Step
Enter system view.
1.
Create a traffic behavior and
2.
enter traffic behavior view.
Configure actions in the
3.
traffic behavior.

Defining a QoS policy

To perform actions defined in a behavior for a class of packets, associate the behavior with the class
in a QoS policy.
To associate a traffic class with a traffic behavior in a QoS policy:
Step
Enter system view.
1.
Create a QoS policy and
2.
enter QoS policy view.
Associate a traffic class with
3.
a traffic behavior to create a
class-behavior association
in the QoS policy.

Applying the QoS policy

You 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 of
the user profile.
Command
traffic classifier classifier-name
[ operator { and | or } ]
if-match [ not ] match-criteria
Command
system-view
traffic behavior behavior-name
See the subsequent chapters,
depending on the purpose of the
traffic behavior: traffic policing,
traffic filtering, and priority
marking.
Command
system-view
qos policy policy-name
classifier classifier-name
behavior behavior-name
[ insert-before
before-classifier-name ]
20
Remarks
By default, no traffic class exists.
By default, no match criterion is
configured.
For more information, see the
if-match command in ACL and
QoS Command Reference.
Remarks
N/A
By default, no traffic behavior
exists.
By default, no action is configured
for a traffic behavior.
Remarks
N/A
By default, no QoS policy exists.
By default, a traffic class is not
associated with a traffic behavior.
Repeat this step to create more
class-behavior associations.