When implementing QoS on a switch (e.g. 3550, etc), it uses WRR for output scheduling. Let's say, we run QoS on a 3550 gigabit interface. In WRR, the interface gets 4096 buffers to queue frames/packets (can be verified by #show mls qos interface <int> statistics). However, if I look at the interface (#show interfaces <int>), I see the output queue size set at 40 (the default).
I wonder if this number has any relevance or if this is just the queue size used when QoS is not turned on. What effect can I expect if I increase the output queue size on the interface ((config-if)hold-queue <n> out). Any comments?
I hope the "hold-queue x" command applicable only when any type of manual queueing configuration is not done. So, in your case, with WRR configuration, 4096 buffers got allocated for that one. From one Cisco document, eventhough it's not talking about WRR, I thought of relevance...
"If priority output queueing is being used, the length of the four output queues is set using the priority-list global configuration command. The hold-queue command cannot be used to set an output hold queue length in this situation."
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...