All,
Hi, any assistance on this would be great, we're all out of ideas at the moment.
I have 2 x central L3 switches (3560's - Primary & Secondary) running BGP to a private MPLS cloud. I redistribute BGP (WAN) into EIGRP (LAN), there is no iBGP.
The above switches are connected to the internal LAN and to each other via one of their Gig Interfaces.
A number of remote branches connect to the same MPLS cloud and back to the central site.
At the central site routes to these remote locations are learned via eBGP with a metric of 20. However, routes to 3-4 branches are learned in EIGRP by the Primary via the Secondary (AD 170). If I bounce the Gig link between them everything is OK for a while, then a few days later, the EIGRP route pops up again.
There is no inbound route filtering on the 3560's as we wanted to see all routes.
The routes concerned do show in the BGP table with the next hop as the eBGP peer. For some reason this route is ignored and the EIGRP path is followed.
Any ideas ?
Regards
Darren