RE: Nested Policy in QOS

Good afternoon,

The value of the child/parent policy is to take 1 "interface bandwidth control" action at the first level (parent) for ALL traffic, and then take 1 or more 2 traffic based actions at the second level (child).

In your example below we do LLQ for EF (voice) and CBWFQ for AF11 traffic. At the top level all traffic is traffic-shaped as shown.

As stated by many excellent CCIE authors (S. Morris, M. Heusinger) this is an excellent way to enforce qos on an interface without a native queue (hardware queue, etc)

-Joe

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Routing Freak
Sent: Tuesday, December 07, 2010 1:25 PM
To: Cisco certification
Subject: Nested Policy in QOS

Can anyone explain me what is the meaning of nested policy
class-map match-any AF
 match dscp af11
class-map match-all VOICE
 match dscp ef
policy-map CHILD
 class VOICE
    priority percent 20
 class AF
    bandwidth percent 15
 class class-default
    fair-queue
policy-map PARENT
 class class-default
    shape average 64000
    shape adaptive 32000
  service-policy CHILD

Blogs and organic groups at http://www.ccie.net
Received on Tue Dec 07 2010 - 14:20:25 ART