Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member


I see drops on my PQ even. I don't see the queue utilization reaching 128 Kbps when there are drops. Beside the default queue does not drop anything..

router1#sh policy-map int Hssi 1/0


Service-policy output: test1

Class-map: test2 (match-all)

258200 packets, 44028284 bytes

30 second offered rate 44000 bps, drop rate 1000 bps

Match: access-group name test3


Strict Priority

Output Queue: Conversation 264

Bandwidth 128 (kbps) Burst 6400 (Bytes)

(pkts matched/bytes matched) 21912/4927878

(total drops/bytes drops) 1774/1868112

Class-map: class-default (match-any)

665806 packets, 277465913 bytes

30 second offered rate 463000 bps, drop rate 0 bps

Match: any


Flow Based Fair Queueing

Maximum Number of Hashed Queues 256

(total queued/total drops/no-buffer drops) 0/0/0


Re: QoS

When you configure a LLQ like you did, the value you put after "priority" configures a policer that all traffic entering the queue must conform to.

This policer has a CIR, and a committed burst, in your case the CIR is 128K, and the committed burst is 6.4K. Generally if you dont specify a burst, IOS will automatically pick a small one, like you see above.

To visualize it, imagine a token bucket. The max amount of tokens you can store in the bucket is 6400, which is how many the bucket starts with. This bucket replenishes itself at the rate of your CIR, or 128,000 per second. Every time a packet comes in, the size is subtracted from the bucket, therefore if 6500 bytes worth of traffic comes in at once, 100 bytes will be dropped.

That being said, if the traffic you're sending through the priority queue is bursty in nature, you'll get drops due to the fact that you're overrunning your burst.

To allow for a larger burst, instead of putting 'priority 128' under the class, try 'priority 128 128000'. This would effectively double the size of the committed burst, allowing more traffic to conform.

Keep in mind that the priority queue optimizes itself for a steady stream of small packets, such as voice. If you're trying to guarantee data traffic, you're better off using the 'bandwidth' command.