Network:
Core_RTR-(2)- 172.16.2.x-(1)----C65K---(254)--172.16.1.X--(253)--WAN RTR#1-(5)--192.168.3.0-(6)-{AS 65001}---MPLS#1-{AS 4182}--(AS65001)--Stub Sites
| EIGRP EIGRP/BGP BGP
172.16.253.2/30
| EIGRP
MPLS #2 <-------This cloud is injecting 4 prefixs into EIGRP*****
| EIGRP
172.16..253.10/30
|
| EIGRP/BGP BGP
WAN_RTR#2---192.168.7.8------{AS 65002}-(5)----------------------------------------MPLS#1-{AS 4182}---------------------------(AS65001)--Stub Sites(same as above)
***The goal is to enable dynamic failover for the following networks if the connection from MPLS#2 fails on Core_RTR to transverse via WAN_RTR#2
Network 10.4.32.0/24
Network 10.1.128.0/24
Network 192.168.50.0/24
WAN_RTR1 and WAN_RTR2 are connected to the same ISP and provide connectivity to the stub sites incase of failure. The prefixes from MPLS#2 need to be redundant via either WAN_RTR#1 or WAN_RTR#2
As these networks need to be reachable from the stub sites if the connection from MPLS#2 is lost on the Core_RTR. The question is do I redistribute these prefixes from EIGRP {which they currently are as we are receiving them MPLS#2 as type EX with a AD 170} into BGP or do I originate them via the network command in BGP and pre-pend the paths from each AS?
Any suggestions?
Thanks