Hello,
I have a question about BGP routing as we begin to introduce BGP in prep for Meraki SDWAN. Currently, all routing is using EIGRP right now. Everything I am trying to test is in a lab and I can't get it to work how I would like it to.
I have 2 data centers. Between the data centers is a direct link running BGP between 2 core switches. The switches are peered using BGP AS 65501.
The primary data center, call it CORP, has a BGP peer with a distribution switch using BGP AS 65502 (I have tried eBGP as well, no luck). The distribution switch has multiple WAN links and there are various paths to the secondary data center. The distribution switch is also peered with a router using EIGRP over a WAN link. The distribution switch is also connected to access switches.
The secondary data center is also peered with another EIGRP router over a WAN link as well. So I have multiple paths to either data center, including the direct link between the core switches.
Everything works generally well as I am redist EIGRP into BGP and BGP into EIGRP.
Here is where I have troubles. When the link between the distribution switch and corp core switch is up, things are good. The user subnets off of the dist switch route over the BGP peer to the core switch. I see this in the routing table.
*> 10.126.95.0/24 192.168.204.1 0 0 65501 i
If I shutdown that link between CORP and DIST, again as expected the routing takes place over the WAN via secondary data center back to the CORP switch and this shows up in my bgp route table
*> 10.126.95.0/24 192.168.203.2 25626368 32768 ?
However, if I bring the link back up between the CORP and DIST switch, it never fails back to BGP. It will forever prefer EIGRP until EIGRP does down and I see the 2 routes.
* 10.126.95.0/24 192.168.204.1 0 0 65501 i
*> 192.168.203.2 25626368 32768 ?
I have tried setting various metrics and weights, but nothing ever fails back to BGP in this scenario. Anything I can do to dynamically fail back to iBGP (or BGP in general) vs EIGRP?
