The only other thing you need to be aware of is that X and Y will both receive the remote site routes via MPLS and redistribute into EIGRP.
This means both sites will also advertise these remote site networks down the dedicated link.
It shouldn't be an issue in terms of path selection because the metric should be worse ie. the best path will always be via their own MPLS router but it is something to watch out for.
However what is an issue is that you need to make sure that you don't then redistribute these back into BGP on the MPLS routers ie.
site X receives remote networks from BGP and redistributes into EIGRP. But it also receives the same networks from site Y via EIGRP.
Now it won't put them in the routing table on the MPLS router because the BGP routes will be there and they have a better AD.
But if site X then loses it's MPLS connection those routes do get put into the routing table and redistributed into BGP.
When the MPLS connection comes backup the BGP routes received from the PE will not replace them because -
BGP route received from PE has a weight of 0
BGP route from redistributed EIGRP routes has a weight of 32768
and so your MPLS router keeps the existing route which means all traffic for remote sites from X goes via Y.
And exactly the same process would happen at Y if it's MPLS connection goes down.
So when you redistribute into EIGRP at X and Y do not redistribute any of the EIGRP external routes for the remote branches.
You could actually stop them being advertised via the dedicated link but you probably don't want that as if either X or Y's MPLS connections fails that link could be used to get to the other site provided you are advertising out each other networks as suggested in previous post.
Hope that makes sense, if not then please come back.
Jon
