02-09-2016 01:41 PM - edited 03-05-2019 03:18 AM
I am working on implementing QoS on our WAN router and want to run this by the community to see if I am doing what I think I am doing. Here are the facts.
Here's my proposed config:
class-map match-any REALTIME
match dscp ef
class-map match-any INTERACTIVE
match dscp af41
class-map match-any BUSINESS_CRITICAL
match dscp af31
class-map match-any NORMAL
match dscp af21
class-map match-any LOW_PRIORITY
match dscp af11
!
policy-map EGRESS
class NORMAL
bandwidth percent 50
class INTERACTIVE
bandwidth percent 10
class BUSINESS_CRITICAL
bandwidth percent 20
class LOW_PRIORITY
bandwidth percent 10
!
policy-map qos-voice
class REALTIME
priority 62200
class class-default
fair-queue
random-detect dscp-based
service-policy EGRESS
!
Any suggestions? Any possible issues?
02-09-2016 05:17 PM
Why not just create the one policy?
policy-map EGRESS
class REALTIME
priority 62200
class NORMAL
bandwidth percent 50
class INTERACTIVE
bandwidth percent 10
class BUSINESS_CRITICAL
bandwidth percent 20
class LOW_PRIORITY
bandwidth percent 10
02-09-2016 06:26 PM
My company has a strict policy against efficient use of CLI : )
Thanks, Phil. That was a good catch!
02-09-2016 06:33 PM
Oh, you work for a Microsoft shop. :-)
02-10-2016 03:10 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 wha2tsoever (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
Philip already noted you don't need a child policy.
With a combined single policy, your normal class could use the default class.
I recommend you avoid using RED, as it's actually much more complicated to "get right" than the manual or most QoS texts explain.
If you platform supports it, you might want to enable FQ on all your non-LLQ classes.
BTW, when using FQ, often you don't need to break out different non-LLQ classes, except when you have a critical need to guarantee bandwidth or you're trying to prioritize traffic. For example you might give your Interactive class 50%, not that you expect it will use that bandwidth, but to insure it gets more attention from the scheduler for packet forwarding. (NB: with higher speed links, like your OC-12, scheduling priority isn't as important.)
Your platform might also support a percentage for LLQ.
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