Sorry if this is not the right place for QoS questions...
I am wondering if there is actual effect on traffic for this command, or is it simply to warn you how much bandwidth you can reserve.
Let's say that I have a slow link of 1.5mbps. The max-r config is set to default 75%. I have two classes under the policy-map
bandwidth percent 75
service-policy output qos
Then I have two streams going out of the interface. One falls in class1 category. Another one in class-default. Let say that both streams send traffic as much as they could without any flow control mechnism (e.g. ping x.x.x.x size 1500 timeout 0 repeat 10000000).
My question is, will this actually gurantee 25% for the class-default traffic for the 2nd stream? In your opinion how the traffic will be divided?
the max-reserved-bandwidth is deprecated in HQF, which is the default in IOS 12.4(20T). In HQF a policy can reserve up to 100% of the bandwidth or 99% if class-default is not explicitly defined. According to cisco documentation, PAK priority traffic is protected by HQF, so no need to keep badwidth for them.
In HQF fair-queue schedules all flow equally, previously in CBWFQ was weighted by default with higher precedence getting more bandwidth. Also, in HQF you may specifiy the percentage of the excess BW, for the distribution in the classes. The default is 1, which means that the remaining bandwidth is distributed evenly between the classes.
So, in your case if you are using HQF you should get 1.125 Mbps for class1 and 375 Kbps for the class-default.
Re: max-reserved-bandwidth - actual effect on traffic
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
In pre-HQF CBWFQ, max-reserved-bandwidth just determine the maximum aggregate of bandwidth you can define for all the non-default classes.
In CBWFQ, bandwidth really set the proportional (de)scheduling weight.
In pre-HQF, if you don't explicity assign bandwidth to class-default, I'm unsure its traffic will receive 1/3 the weight of your class1.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...