I am having a very similar issue to the one documented above here. In my case, the Primary MPLS (BGP) fails and backup link (EIGRP) takes over. Once the Primary MPLS link comes up, the traffic remains routing over backup due to the redistributed EIGRP route staying in the routing table for the Primary router. One thing that I don't quite understand is WHY this happens.
If EIGRP route is recieved first for a prefix then its entered to the routing table. If BGP establishes and eBGP learns the same prefix, the EIGRP route remains in the routing table becuase it has a higher weight of 32768 vs the default eBGP weight of 0 i,e Best Path Selection Process is used to calculate the best path and AD is NOT even considered.
However, if eBGP route enters the routing table first, and then EIGRP route is recieved, the BGP route remains in the routing table because the AD of eBGP is better than EIGRP (AD 20 vs 90).
How come Best Path Selection is not used in that case? Why does AD get used in this case and not like in the first scenario?
Then the same prefix comes via EIGRP and the router compares the ADs of both prefixes (the best ones per routing protocol) to decide which should go to the RIB.
So the eBGP route remains in the RIB and the EIGRP prefix is not redistributed to BGP (note: Only routes which are in RIB can be redistributed to other routing protocols!).
In Scenario 1:
The EIGRP route comes to the RIB as the first one.
Then it gets redistributed to BGP. Then the same prefix comes via eBGP. It's compared by the BGP Best Path selection Algorithm with the same prefix already present in the BGP database (redistributed from EIGRP originally) to choose the best route within BGP protocol. As the redistributed prefix has got better weight attribute, it remains the best within BGP. So no new best BGP route and no reason to compare the ADs!
If you want the eBGP prefix to win again in Scenario 1, you need to configure a route-map used for EIGRP to BGP redistribution which would change the weight attribute to 0 for the redistribiuted prefixes. Then other BGP attributes would get compared and the eBGP prefix might win (if you want to be sure, increase its local preference, e.g.).
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...