05-20-2021 07:18 AM
Hi Team,
This is with respect to QoS configurations on DMVPN headend router.
Noticed that the child policy is configured but not called under the parent-policy. Will there be any errors or service impact when correct the configurations?
Current Config:
policy-map 10M-qos
class class-default
shape average 10000000
Required Config:
policy-map 10M-qos
class class-default
shaping 10000000
service-policy wanoutput
Child Polciy:
policy-map wanoutput
class real-time
priority percent 33 32500
class routing
bandwidth percent 4
class interactive
bandwidth percent 25
set ip dscp af32
class voice-signal
bandwidth percent 4
class email
bandwidth percent 4
random-detect
Solved! Go to Solution.
05-20-2021 08:11 AM - edited 05-23-2021 07:59 AM
NB: As you didn't note your device or its IOS package, can only address your question very generally.
Usually, changing a QoS policy on an active interface goes unnoticed. I.e. there might be a very brief hit to some in-flight packets, but most applications are not (too) adversely impacted. That said, when possible, always better to make such changes during a scheduled maintenance window, or at the least, during non-busy or non-critical usage times.
BTW, about your policies, I would suggest defining class-default, in your wanoutput policy, with a defined amount of bandwidth. I also suggest not using WRED unless you're a QoS expert. Lastly, I suggest using FQ, at least in class-default, and perhaps in other non-LLQ classes too (if supported). With FQ, in class-default, you may find your need for other defined classes is reduced. Except for your "interactive" class, assigning AF32, you could possible allow all the other non-LLQ classes to just use class-default (again if FQ enabled for that class).
05-20-2021 08:11 AM - edited 05-23-2021 07:59 AM
NB: As you didn't note your device or its IOS package, can only address your question very generally.
Usually, changing a QoS policy on an active interface goes unnoticed. I.e. there might be a very brief hit to some in-flight packets, but most applications are not (too) adversely impacted. That said, when possible, always better to make such changes during a scheduled maintenance window, or at the least, during non-busy or non-critical usage times.
BTW, about your policies, I would suggest defining class-default, in your wanoutput policy, with a defined amount of bandwidth. I also suggest not using WRED unless you're a QoS expert. Lastly, I suggest using FQ, at least in class-default, and perhaps in other non-LLQ classes too (if supported). With FQ, in class-default, you may find your need for other defined classes is reduced. Except for your "interactive" class, assigning AF32, you could possible allow all the other non-LLQ classes to just use class-default (again if FQ enabled for that class).
05-22-2021 06:43 PM
Thanks for the input.
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