Origin codes: i - IGP, e - EGP, ? - incomplete Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, Gateway of last resort is 10.0.1.2 to network 0.0.0.0

O - ODR, P - periodic downloaded static route Ia - IS-IS inter area, * - candidate default, U - per-user static route I - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2 *Sep 9 18:59:52.567: %BGP-5-ADJCHANGE: neighbor 65.113.57.153 UpĬodes: C - connected, S - static, R - RIP, M - mobile, B - BGPĭ - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area Not sure where I'm in the wrong here, unless theres a specific default metric I'd need to assign to the redistribution points to make BGP preferred? Already tried changing the weight path (higher is better) but to no avail. If you were to sh ip route after BGP is back, OSPF does not budge. If you were to sh ip route when BGP fails, OSPF will take over all routes. The only thing that works is disconnecting the OSPF device manually or shutting it, clearing OSPF routes out and letting BGP come back to save the day. When BGP link is alive, never rolls over to OSPF. When BGP link dies, rolls over to OSPF no problem. Scenario: OSPF as a backup WAN link, BGP as the main WAN link into MPLS.

Eigrp to bgp redistribution timers