Restrictions For Multiple Qos Policy Support - Cisco ASR 9000 Series Configuration Manual

Restrictions for Multiple QoS Policy Support

QueueID: 0 (Port Default)
----------------------------------------------------------------------
Restrictions for Multiple QoS Policy Support
Policy Classification Restrictions
• Classification policy must always be executed before the queuing policy. Also, queuing actions are not
• Classification policy supports unconditional set traffic-class actions. The valid values for set traffic-class
• In a conditional policer action, set traffic-class action is not supported.
• At least one set traffic-class action must be present for a policy to be considered a classification policy
• Only two additional packet fields can be unconditionally set along with set traffic-class.
• Class-maps in a classification policy cannot be used to match on traffic-class.
• Only one set traffic-class action is permitted in a hierarchy (either parent or child).
• Flow aware and shared policers are not supported.
• In a three-level policy, set traffic-class action is permitted only at the lowest two-levels.
• In a policer action, conditional set traffic-class is not supported.
Queuing Policy Restrictions
• Queuing policy can only classify on traffic-class field.
• At least one class-map with match traffic-class must be present for a policy to be considered a queuing
• Class-map with match not traffic-class is not supported.
• Non-queuing actions like policer and set are not supported.
• Since policer is not supported in queuing policy, when priority level 1 queue is used, the service rate
Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide, Release
6.1.x
160
supported within a classification policy.
are 0 – 63.
in the multi policy context.
◦ Valid values for match traffic-class are 0-63.
◦ Class-maps can match up to 8 discreet traffic-class values or traffic-class ranges.
policy in the multiple qos policy support feature.
computed for lower priority queues is very low (with priority 1 utilizing all the bandwidth, the bandwidth
remaining for lower priority queues is very low). Due to the same reason, minimum bandwidth is also
not be supported with priority level 1. However, bandwidth remaining ratio may be used instead of
minimum bandwidth. Since the default queue-limit and time based queue-limit configurations use
service-rate to calculate queue-limit in bytes, it is recommended to explicitly configure queue-limit in
bytes when using priority 1 queue.
Configuring Modular QoS Service Packet Classification