Hi all,
Does anyone have any production experience with aggressively tuned
EIGRP timers in a DMVPN environment?
We have a requirement to detect loss of end-to-end connectivity over
DMVPN (multipoint GRE protected by IPSec) tunnels and re-route traffic
very quickly. This is due to a centralised VoIP implementation. We
need to detect loss of connectivity and converge inside 12 seconds.
Example using 3 second hellos and 9 second hold-time:
interface Tunnel0
ip hello-interval eigrp 100 3
ip hold-time eigrp 100 9
The DMVPN design guide doesn't delve into this very much, and uses a
35 second hold-time timer in all examples. GRE keepalives aren't
supported with DMVPN.
We have a dual cloud, single hub (per cloud) DMVPN design, and each
hub maintains ~35 EIGRP adjacencies. We have a mix of WAN access types
and speeds, from 4Mbps EoSHDSL to 200Mbps EoSDH. We provide end-to-end
QoS for control plane protocols so forwarding of EIGRP packets from CE
to CE should be handled appropriately through the provider MPLS core.
I have lab tested the above configs (as well as 2 sec/6 sec) and it
all works nicely, but I wasn't able to scale it up to accurately
represent the production network.
If you have 'been there, done that' and have some war stories, or,
better yet, success stories, please let me know.
Thanks,
Dale
Blogs and organic groups at http://www.ccie.net
Received on Fri Sep 18 2009 - 12:45:46 ART
This archive was generated by hypermail 2.2.0 : Sun Oct 04 2009 - 07:42:03 ART