Defining A Qos Policy; Configuring A Parent Policy; Configuring A Child Policy - HP MSR4080 Configuration Manual

Defining a QoS policy

Configuring a parent policy

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

Configuring a child policy

You can nest a QoS policy in a traffic behavior to reclassify the traffic class associated with the behavior.
Then the actions that are defined in the QoS policy are taken on the reclassified traffic. The QoS policy
nested in the traffic behavior is called a child policy. The QoS policy that nests the behavior is called a
parent policy.
To nest QoS policies successfully, follow these guidelines:
If class-based queuing (CBQ) is configured in a child policy, GTS must be configured in the parent
•
policy, and the CIR specified in GTS must be greater than or equal to CBQ bandwidth.
If the CIR in GTS is specified as a percentage for a parent policy, the CBQ bandwidth must be
•
configured as a percentage for the child policy. If the CIR in GTS is specified as a value in kbps for
a parent policy, the CBQ bandwidth can be configured as a percentage or a value in kbps for the
child policy.
• GTS cannot be configured in the child policy.
To nest a child QoS policy in a parent QoS policy:
Step
1. Enter system view.
2. Create a class for the
parent policy and enter
class view.
3. Configure match criteria.
Command
system-view
qos policy policy-name
classifier classifier-name behavior
behavior-name
Command
system-view
traffic classifier classifier-name
[ operator { and | or } ]
if-match [ not ] match-criteria
22
Remarks
N/A
By default, no QoS policy is
configured.
By default, a traffic class is not
associated with a traffic behavior.
Repeat this step to create more
class-behavior associations.
Remarks
N/A
By default, no class is configured.
By default, no match criterion is
configured.
For more information about configuring
match criteria, see ACL and QoS
Command Reference.