Configuring Rate Limits on Enhanced Queuing DPCs
You can rate-limit the strict-high and high queues on the Enhanced Queuing DPC. Without rate limits, traffic in higher priority queues can block the transmission of lower priority packets. Unless limited, higher priority traffic is always sent before lower priority traffic, causing the lower priority queues to “starve” and cause timeouts and unnecessarily resent packets.
On the Enhanced Queuing DPC, you can rate-limit queues before the packets are queued for output. All packets exceeding the configured rate limit are dropped, so care is required when establishing this limit. This model is also supported on IQ2 PICs. For more information about configuring CoS on IQ2 PICs, see CoS on Enhanced IQ2 PICs Overview.
 | Note: Rate limiting is implemented differently on Enhanced Queuing DPCs and non-queuing Packet Forwarding Engines. On Enhanced Queuing DPCs, rate-limiting is implemented using a single rate two color policer. On non-queuing Packet Forwarding Engines, rate-limiting is achieved by shaping the queue to the transmit rate and keeping the queue delay buffers small to prevent too many packets from being queued once the shaping rate is reached. |
To rate-limit queues, include the transmit-rate statement with the rate-limit option at the [edit class-of-service schedulers scheduler-name] hierarchy level:
This example limits the transmit rate of a strict-high expedited-forwarding queue to 1 Mbps. The scheduler and scheduler map are defined, and then applied to the traffic at the [edit interfaces] and [edit class-of-service] hierarchy levels:
You can issue the following operational mode commands to verify your configuration (the first shows the rate limit in effect):
- show class-of-service scheduler-map scheduler-map-name
- show class-of-service interface interface-name
