19
Defining a traffic class
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a traffic class and
enter traffic class view.
traffic classifier
classifier-name
[
operator
{
and
|
or
} ]
By default, no traffic classes exist.
3.
Configure a match criterion.
if-match match-criteria
By default, no match criterion is
configured.
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 traffic class.
To define a traffic behavior:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a traffic behavior and
enter traffic behavior view.
traffic behavior behavior-name
By default, no traffic behaviors
exist.
3.
Configure an action in the
traffic behavior.
See the subsequent chapters,
depending on the purpose of the
traffic behavior: traffic policing,
traffic filtering, priority marking,
traffic accounting, and so on.
By default, no action is configured
for a 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 Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Create a QoS policy and
enter QoS policy view.
qos policy
policy-name
By default, no QoS policies exist.
3.
Associate a traffic class with
a traffic behavior to create a
class-behavior association
in the QoS policy.
classifier
classifier-name
behavior behavior-name
[
insert-before
before-classifier-name
]
By default, a traffic class is not
associated with a traffic behavior.
Repeat this step to create more
class-behavior associations.
Summary of Contents for FlexFabric 5940 Series
Page 23: ...17 Figure 3 QoS processing flow ...
Page 84: ...78 Figure 26 MPLS label structure ...
Page 91: ...85 Switch burst mode enable ...
