so I have this output, the "local" route is appearing in my routing table via eigrp. 10.33.254.20 is not a bgp neigh, and 10.40.33.4 is this routers loopback. The primary route should be via bgp. Those routes are being redistirbuted int eigrp with a tag of 1000, then eigrp is being redistibuted back into bgp except for the tagged routes. 10.33.254.20 is actually our backup dmvpm router which is where the eigrp route is coming from, I just can't figure out why the bgp route isnt being put into the routing table instead of the eigrp route. Note it is working correctly on about 50 sites and just about 10 are doing this. Also if you look at an eigrp neigh, this route doesnt have the 1000 tag. Perhaps, I am redistributing the route and learning the routes via dmvpn, and the dmvpn router has a better cost than the redistributed route, but bgp route should still be installed due to admin distance right?
router2#sho ip bgp 10.35.10.0
BGP routing table entry for 10.35.10.0/24, version 170673
Paths: (2 available, best #2, table Default-IP-Routing-Table)
Advertised to update-groups:
1 2
65000 10
147.225.157.153 from 147.225.157.153 (159.24.198.5)
Origin IGP, localpref 100, valid, external
Local
10.33.254.20 from 0.0.0.0 (10.40.33.4)
Origin incomplete, metric 25858816, localpref 100, weight 32768, valid, sourced, best
router2#sho ip route 10.35.10.0
Routing entry for 10.35.10.0/24
Known via "eigrp 136", distance 90, metric 25858816, type internal
Redistributing via eigrp 136, bgp 1
Advertised by bgp 1 route-map eigrp_to_bgp
Last update from 10.33.254.20 on FastEthernet0/0, 6d00h ago
Routing Descriptor Blocks:
* 10.33.254.20, from 10.33.254.20, 6d00h ago, via FastEthernet0/0
Route metric is 25858816, traffic share count is 1
Total delay is 10110 microseconds, minimum bandwidth is 100 Kbit
Reliability 255/255, minimum MTU 1400 bytes
Loading 198/255, Hops 2
