Configuring Hierarchical Modular QoS on Cisco ASR 9000 Series Routers
Restrictions for Hierarchical Policies
In Cisco IOS XR Release 4.0.0, the following restrictions apply:
ASR 9000 Ethernet Line Cards
In a three-level hierarchy, the configuration is rejected if the top-level class has queueing actions but the
middle-level class or bottom-level class do not have queueing actions.
For example, the following configuration was valid in previous releases but is not valid in
Cisco IOS XR Release 4.0.0 because the top-level class has a queueing action (shaping) but the
middle-level and bottom-level classes do not have queueing actions:
OL-23108-02
policy-map grand-parent
class class-default
shape average 10 mbps
service-policy parent
policy-map parent
class p1
service-policy child
police rate 10 mbps
class p2
service-policy child
police rate 10 mbps
class p3
police rate 10 mbps
service-policy child
class class-default
policy-map child
class c1
police rate 2 mbps
class c2
police rate 5 mbps
class class-default
police rate 10 mbps
To correct the configuration and retain queueing in the top-level class, you can add a queueing action
to the middle-level or bottom-level classes. For example, the bandwidth remaining action is added
to the middle-level classes in this example. You could also correct this configuration by removing
queueing from the top-level class.
policy-map grand-parent
class class-default
shape average 10 mbps
service-policy parent
policy-map parent
class p1
service-policy child
police rate 10 mbps
bandwidth remaining ratio 1
class p2
service-policy child
police rate 10 mbps
bandwidth remaining ratio 1
class p3
police rate 10 mbps
service-policy child
bandwidth remaining ratio 1
class class-default
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide
Information About Hierarchical QoS
QC-125