Cisco ASR 920 series - Policing Traffic in Child Classes and Parent Classes

conform-color hipri-conform
service-policy child-policy
Figure 2: Simple Two-Level Color-Aware Policer
To avoid drops at the parent level for "conformed" child traffic, the parent policer must have a rate and
burst that are equal to or greater than the sum of the child conform rates and burst sizes. There is no check
for inappropriate (parent-to-child) rates and burst sizes in code. You must be aware of this limitation and
configure appropriately. In the following example, explicit marking actions are supported in conjunction
with color-aware policing and operate similarly color-aware policer marking actions. If these marking
actions ("set qos-group," for example) are present in the child policies, the resulting bit values are evaluated
by the parent color-aware policer (same as for child policer marking actions): 50k >= 10k (user1-acl-child)
+ 20k (user2-acl-child)
Note
Policing Traffic in Child Classes and Parent Classes
Prior to the release of the Hierarchical Color-Aware Policing feature, policing and marking were typically
used as input QoS options. For example, a voice customer was limited to 112 kb/s for voice control and 200
kb/s for voice traffic. The class-default class has no policer. The only limit is the physical bandwidth of the
QoS: Policing and Shaping Configuration Guide (Cisco ASR 920 Series)
54
Hierarchical Color-Aware Policing
Policing Traffic in Child Classes and Parent Classes