1642
C
85: Q
S P
HAPTER
O
Introduction to QoS
Policies
QoS Policy
Configuration
Configuration
Prerequisites
Defining a Class
C
OLICY
ONFIGURATION
Introduction to each QoS policies
Name
CAR (Traffic policing)
GTS (Traffic shaping)
Traffic filtering
Traffic redirection
Priority remark
Queue
Congestion avoidance
For the configuration of queue and congestion avoidance, refer to
Class-based Queuing" on page
The class name and rule are defined in a policy.
■
The traffic name and actions included in a traffic behavior are defined,
■
The policy name is defined.
■
The interface on which policy is applied is defined
■
Before you can define a class, you must first create its class name. Then you can
configure matching rules in this class view.
Configuration procedure
Follow these steps to define a class
To do...
Enter system view
Define a class and enter
the class view
Define the rule matching
all packets
Display class information
Class
Users use the if-match match-criteria
command to define a class as needed.
Users use the if-match match-criteria
command to define a class as needed.
Users use the if-match match-criteria
command to define a class as needed.
Users use the if-match match-criteria
command to define a class as needed.
Users use the if-match match-criteria
command to define a class as needed.
Users use the if-match match-criteria
command to define a class as needed.
Users use the if-match match-criteria
command to define a class as needed.
1661.
Use the command...
system-view
traffic classifier tcl-name
[ operator { and | or } ]
if-match [ not ]
match-criteria
display traffic classifier
{ system-defined |
user-defined } [ tcl-name ]
Command
car
gts
filter
redirect
remark
queue
wred
"Configuring
Remarks
-
Required
The class defaults to and. That is, the
relation between respective
matching rules in the class view is
logic AND.
Required
Optional
The display command can be
executed in any view.
Need help?
Do you have a question about the MSR 50 Series and is the answer not in the manual?
Questions and answers