Configuring A Child Policy; Applying The Qos Policy - HP FlexNetwork MSR Series Configuration Manuals

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 system performs the actions defined in the QoS policy on the reclassified traffic.
The QoS policy nested in the traffic behavior is called the child policy. The QoS policy that nests the
behavior is called the parent policy.
To nest QoS policies successfully, follow these guidelines:
•
If class-based queuing (CBQ) is configured in a child policy, make sure the following
requirements are met:
GTS is configured in the parent policy.

The CIR specified in GTS is greater than or equal to CBQ bandwidth.

•
If the CIR in GTS is specified as a percentage for a parent policy, configure the CBQ bandwidth
as a percentage for the child policy.
•
If the CIR in GTS is specified in kbps for a parent policy, configure the CBQ bandwidth as a
percentage or 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 traffic class for the
parent policy and enter
traffic class view.
3. Configure
criterion.
4. Return to system view.
5. Create a traffic behavior for
the parent policy and enter
traffic behavior view.
6. Nest the child QoS policy.
7. Return to system view.
8. Create the parent policy
and enter parent policy
view.
9. Associate the class with the
behavior
policy.

Applying the QoS policy

You can apply a QoS policy to the following destinations:
•
Interface or PVC—The QoS policy takes effect on the traffic sent or received on the interface
or PVC.
Command
system-view
traffic classifier classifier-name
[ operator { and | or } ]
a match
if-match [ not ] match-criteria
quit
traffic behavior behavior-name
traffic-policy policy-name
quit
qos policy policy-name
classifier
in the parent
behavior behavior-name
Remarks
N/A
By default, no traffic classes exist.
By default, no match criterion is
configured.
For
configuring match criteria, see ACL
and QoS Command Reference.
N/A
By default, no traffic behaviors exist.
By default, policy nesting is not
configured.
N/A
By default, no parent policy exists.
classifier-name By default, a class is not associated
with a behavior.
29
more information about