Hey,
One example that could help understand it is as follows:
@You have a 2 Mbps link with an ISP
@You need to prioritize VOIP traffic
Thus you can done it in a certain way:
You configure a parent policy which says that you want to shape your total
output (matching class-default) to 2 Mbps. Within those 2 Mbps for instance
you would like to limit & prioritize Voice traffic, thus you match it in
another policy and configure LLQ.
Finally the outer policy (parent policy) calls the child policy. Something
of this form. Another reason it can be used is that under subinterfaces you
will not be able to apply LLQ, thus you make it in the form of OUTER & INNER
Policies and then you attach the outer policy to the subinterface which in
turn will call the inner one..
policy-map INNER_POLICY
class VOIP
priority <upper limit>
exit
policy-map OUTER_POLICY (Shape to the agreed rate with the ISP)
class class-default
shape average
service-policy INNER_POLICY
exit
HTH,
On Sun, Sep 19, 2010 at 2:57 PM, CCIE KID <eliteccie_at_gmail.com> wrote:
> Hey What is actually meant by child and parent policy in qos MQC
> configurations
> I am little bit confused with it
> Can anyone explain me about that?
>
>
>
> --
> With Warmest Regards,
>
> CCIE KID
> IN PURSUIT OF CCIE
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- KJ Blogs and organic groups at http://www.ccie.netReceived on Sun Sep 19 2010 - 15:39:18 ART
This archive was generated by hypermail 2.2.0 : Fri Oct 01 2010 - 05:58:05 ART