Hello there!

I've run into a routing problem I can't seem to find a solution for and I was hoping someone who was far more versed in EIGRP and OSPF might be able to assist me.

I have a lab I have set up and this routing scheme will be used in a real world situation, so essentially I can test any suggestions or recommendations safely.

It's worth saying, in this original set up only EIGRP was run. Because of an MPLS provider change, we've had to add OSPF into the configuration.


I have 5 remote routers which all run EIGRP and OSPF. I redistribute EIGRP static in each remote router.
The primary internet connection is used to connect to a data center (we'll Call it DC for short) via a GRE Tunnel (this primary connection for each remote site is going away because the new MPLS backbone is being made the primary).
Each router has a secondary internet/dsl backup connection. This connection is split into 2 GRE Tunnels, 1 tunnel is for Local internet browsing and the second tunnel connects to the DC.
These routers all have an MPLS connection to a Core router. The Core also runs EIGRP and OSPF and redistribute's EIGRP static.

The way it was: The primary connection was used to go to the DC. If that failed then the DSL tunnel was used to connect to the DC and if that failed then the MPLS backbone was used to connect to the DC.

The way they want it now: All DC traffic needs to be routed down the MPLS backbone to get to the Core (which has a 100megabit connection to the DC) which then routes it to the DC. If the MPLS fails then the secondary DSL tunnel will be used to connect to the DC.

The problem is: We can route everything over the MPLS backbone without a problem, except when the secondary DSL Tunnel is up, then it wants to use that internal tunnel route instead of the OSPF external routes across the MPLS backbone.

I've tried various things (which trying to explain will likely muddle up this post) but I can't get the routing to work so that the tunnel is only used if the main mpls connection is down.

Does anyone have any suggestions?

I can provide more information as needed. I'm not our main routing guy, he's out and unavailable and the original configuration changed in mid-mpls switch so our original lab/model became outdated with the customers newly desired change.

I'd appreciate any help anyone can give me since I'm a bit out of my depth.

Draw a diagram

_________________
www.mellowd.co.uk/ccie/

Attached is a jpg of the network in it's current configuration.

All 5 of the remote routers each represent a remote office and all 5 are set up the same way, so I represented them simply with 1 router.

Tunnel 0 is each router's secondary connection to the Data Center (these tunnels are currently ADMIN DOWN)
Tunnel 1 is each router's secondary connection to the internet
MPLS is the MPLS backbone / internal network connectivity.

Currently all internal traffic/data center traffic is routing across the MPLS connections.
All internet traffic is routing across tunnel 1.

The problem is if I turn up Tunnel 0 on the remote routers then routing stops going across the MPLS and starts to go across Tunnel 0.

OSPF sees the MPLS connections as External routes (and that is the protocol required by the MPLS provider to connect all these routers together).
Each remote router sees it's own Tunnel 0 as a directly connected / EIGRP internal routes.

So what I need to accomplish is to have the Tunnel 0's on the remote routers to act as secondary connections which are only utilized if the MPLS connection goes down.

if i understand correctly ... i would configure a route to those networks at the DC, with a higher admin distance via the tunnel 0 on remote offices.

You mean change the EIGRP advertised distance on the DC with higher for internal than external routes?