Andy

I am using 122-25.SEE3 Ip services but still seems to be hitting the bug

Configuring mls qos queue-set output 2 threshold 1 3200 3200 100 3200 did reduce the drops but i think i need to be doing it for all the thresholds

Narayan

This is what I currently use as a template when deploying QoS on these switches:

mls qos queue-set output 1 threshold 1 800 800 50 3200

mls qos queue-set output 1 threshold 2 560 640 100 800

mls qos queue-set output 1 threshold 3 800 800 50 3200

mls qos queue-set output 1 threshold 4 320 800 100 800

Obviously there are changes to the default DSCP-to-Queue and CoS-to-Queue mappings as well.

If changing that one line fixed some issues then you need to look at the traffic and understand which queues are being used.

That one line you posted changes queue 1 of queue-set 2 to use more of the common pool buffers, however the other 3 queues won't.

HTH

Andy

Thanks Andy

I will remember the template

The following thing seems to work for me now

mls qos queue-set output 2 threshold 3 800 800 50 3200

mls qos queue-set output 2 threshold 4 900 900 100 3200

We are going to add about 400 more users when i may need to tune these again

Narayan

Andrew, Do you know what exactly does this do in practice?

For example, "mls qos queue-set output 1 threshold 2 560 640 100 800" will not allocate 800% buffers, since Drop threshold 2 and Drop Threshold 3 will max out at 640% of the queue.

And on top of that, 640% will not be reach, unless you are forcibly dissalocating buffers from some other ports into the common pool, using another queue set.