Defining A Class; Defining A Traffic Behavior - HP FlexNetwork MSR Series Configuration Manuals

Predefined classes
The system predefines some classes and defines general rules for the classes. You can use the
following predefined classes when defining a policy:
•
default-class—Matches the default traffic.
•
ef, af1, af2, af3, af4—Matches IP DSCP value ef, af1, af2, af3, af4, respectively.
•
ip-prec0, ip-prec1, ...ip-prec7—Matches IP precedence value 0, 1, ...7, respectively.
•
mpls-exp0, mpls-exp1, ...mpls-exp7—Matches MPLS EXP value 0, 1, ...7, respectively.
Predefined traffic behaviors
The system predefines some traffic behaviors and defines QoS features for the behaviors.
•
ef—Assigns a class of packets to the EF queue and assigns 20% of the available interface or
PVC bandwidth to the class of packets.
•
af—Assigns a class of packets to the AF queue and assigns 20% of the available interface or
PVC bandwidth to the class of packets.
•
be—Defines no features.
•
be-flow-based—Assigns a class of packets to a WFQ queue and specifies the drop policy as
WRED. By default, 256 WFQ queues exist, and WRED is an IP precedence-based drop policy.
Predefined QoS policy
The system predefines a QoS policy, specifies a predefined class for the policy and associates a
predefined behavior with the class. The policy is named default, with the default CBQ action.
The policy default is defined as follows:
•
Associates the predefined class ef with the predefined traffic behavior ef.
•
Associates predefined classes af1 through af4 with the predefined traffic behavior af.
•
Associates the predefined class default-class with the predefined traffic behavior be.

Defining a class

Step
1. Enter system view.
2. Create a traffic class
and enter traffic class
view.
3. Configure a match
criterion.

Defining a traffic behavior

To define a traffic behavior, create the traffic behavior first and then configure QoS attributes in traffic
behavior view.
Configure AF and the minimum guaranteed bandwidth
When you configure AF and the minimum guaranteed bandwidth, follow these restrictions and
guidelines:
•
You can apply this traffic behavior only to the outgoing traffic of an interface.
Command
system-view
traffic classifier
classifier-name [ operator
{ and | or } ]
if-match [ not
match-criteria
72
Remarks
N/A
By default, no traffic classes exist.
By default, no match criterion is configured.
]
For more information about configuring match
criteria, see ACL
Reference.
and QoS Command