were in the process of redesigning our routing between our 2 datacenters and our clients and im looking at eigrp over the top.
has any one used this in production? does it cause issues or is it well supported?
a little background. we proved data center services as well as internet connectivity to about 100 clients around the US. each client is any where from 1-20 locations. a typical client will have either MPLS or Metro E between their branches and our 2 data centers, and then DMVPN back up over a separate internet connection to each DC as well. we also have a pair of DCI links between the 2 DCs that traffic can traverse for the client as a last ditch effort kind of thing if they connectivity directly to the particular DC goes down.
MPLS means we BGP peer with the carrier, and then currently do some redistribution into eigrp for the the rest of the network. this adds some obvious complexity. it also means some differences in configuration between clients who use MPLS and those that use metro E (where we run eigrp) or god forbid T1 lines (rare, but point to point metro E links to a head office with MPLS or other connectivity to branches off head office is not)
we exploring SD wan options later this year, but that probably wont be a thing untill at least 2020 for POC at the earliest. were also exploring just doing all this connectivity via BGP. but im curious in using an overlay of some sort so we dont have to do BGP beyond the carrier edge and came across EIGRP over the top.
tunnels is an option, but that would mean some new hardware as well to support something like DMVPN over the MPLS as well (we would want separate equipment for the hubs from the failover) and brings up some other questions about certain types of outages and its effect.
so, yeah, thoughts on eigrp over the top?
No comments:
Post a Comment