Is there a mathematical method of configuring bandwidth weights and queue limits or is it more art than science? For example, using the 3550 series switches, when you perform auto-qos, it chooses the following parameters:
wrr-queue bandwidth 10 20 70 1
wrr-queue queue-limit 50 25 15 10
I need to know the reason for how this values were chosen, in order to understand how changing these values affect the overall queueing process. Is there some kind of best practice (recommended) values for setting them? I notice a pattern that bandwidth weights with the exception of the priority queue (qid 4) are larger; whereas the queue-limit values are lower for higher priority traffic, i.e. they get the smallest slice of the egress buffers.
Also the burst-byte value parameter in policing under policy map. How do you obtain an appropriate value for this? How does that relate to the access-rate?
In the auto-qos it gives the same 8000 byte value to the burst byte, see below:
To allocate bandwidth between standard transmit queue 1 (low priority) and standard transmit queue 2 (high priority), use the wrr-queue bandwidth command is used. Use the no form of this command to return to the default settings.
Thanks for you time. However, the question was more to do with techniques or best practice or mathematical process, to come up with the appropriate values for wrr weights and allocating the buffer using the queue-limit. I have read a lot of documentation, but they never really dig deeper.
Also reference you gave is for the 6500 and not the 35550, they are different.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...