01-17-2013 03:42 AM - edited 02-21-2020 06:37 PM
Dear All,
we have the unusual situation that on of our DMVPN Spoke Sites has a higher bandwidth rate (33 Mbit/s) than our
DMVPN Hub Site.
Therefore, we need to apply traffic shaping to 10 Mbit/s on the tunnel interface on the spoke.
The following link only describes how to apply shaping on the hub end but not on the spoke end site:
How should we proceed with this on the spoke router ?
Will creating a service policy and then applying it to the tunnel interface do the job ? Will shaping be done then after the traffic encryption or before ?
And would we then need to increase the replay window-size buffer of 1024 to something higher ?
Would the following example work ? We would apply the Policy outbound to the Tunnel interface:
class-map match-any CLASS_ANY
match any
policy-map POLICY_SHAPE10MEG
class CLASS_ANY
shape average 10000000
interface Tunnel 0
service-policy output POLICY_SHAPE10MEG
Thanks for your help,
Thorsten
Solved! Go to Solution.
09-17-2014 01:33 PM
I don't understand. I agree that the hub to spoke policy map is working but I don't seen the spoke to hub policy map working..
04-23-2020 08:12 AM
This is an old post and possibly you found your solution. In any case for everyone else:
The per-tunnel qos applied on DMVPN hub interface just does that: Applies egress policies from the hub towards the spokes.
It does nothing for the opposite direction.
You must apply a seperate policy in the spoke side for egress traffic towards the hub.
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