04-14-2015 05:37 PM - edited 03-05-2019 01:14 AM
Hi All,
if I have a queuing scheme similar to below and when there is no congestion or realtime traffic would queuing be FIFO and when congestion occurred due to transactional traffic would the transactional be limited to using 16% of the 4M and remaining bandwidth allocated to the other classes or transactional takes majority of bandwidth and other classes limited to their defined percentage
policy-map OUT-01
class realtime
priority 2000
police 2000000 conform-action transmit exceed-action drop
class priority
bandwidth remaining percent 40
random-detect dscp-based
class missioncritical
bandwidth remaining percent 39
random-detect dscp-based
class transactional
bandwidth remaining percent 16
random-detect dscp-based
class general
bandwidth remaining percent 1
random-detect dscp-based
class class-default
bandwidth remaining percent 4
random-detect dscp-based
policy-map OUT-SHAPE
class class-default
shape average 4000000 17000 0
04-15-2015 05:50 AM
Disclaimer
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.
Liability Disclaimer
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.
Posting
Generally, "ordinary" CBWFQ bandwidth settings set a guaranteed minimum, they do not limit. For example, your 16% transaction could use 100%.
Also on most CBWFQ platforms (ASRs being an exception?), "bandwidth" classes containing for bandwidth will split it in the ratios of their bandwidth statement assignments. For example if your transactional, general and default classes were contending for bandwidth, they would split it 16:4:1.
BTW, your 16% is defined as "remaining", so it doesn't guarantee 16% of the 4 Mbps because you've also defined a LLQ class with 2 Mbps. I.e. you've "guaranteed" 16% of the remaining 2 Mbps.
PS:
Also BTW, unless you're a QoS expert I would recommend you NOT use random-detect.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide