EIGRP issue - how to force EXTERNAL EIGRP routes to be preferred over INTERNAL EIGRP routes

Hello,

I have a situation where routes being learned from EIGRP that is redistributed from BGP are being preferred over routes learned from EIGRP connected to backup VPN routers using GRE over IPSec tunnels.

What we have is an MPLS topology using EIGRP for route distribution internally (redistributed from BGP from the MPLS provider).

For BACKUP if / when these MPLS connections go down, we have VPN routers using GRE over IPSec with Tunnel interfaces.

Because the GRE over IPSec is considered INTERNAL EIGRP, and the BGP redistributed into EIGRP is considered EXTERNAL EIGRP (because it's redistributed via another routing protocol), the BACKUP routers are always being preferred over the MPLS routers.

The metric from EXTERNAL EIGRP from the MPLS providers routers is 170.

The metric from INTERNAL EIGRP from the GRE over IPSec tunnels is 90.

How can we force the EIGRP from the EXTERNAL EIGRP system (MPLS Providers routers) to be preferred over the GRE over IPSec EIGRP ??

We have full control over the backup routers (Internal EIGRP), and we can set admin distance, delay, bandwidth, etc....if the change needs to happen on the MPLS providers side, we would need to make a change request.

It would be easiest to make the change on the INTERNAL EIGRP. If we could get the METRIC to be higher than 170, that would fix it. I'd rather not set static routes with a manual metric higher than 170, but that of course will be our last resort.

Thank you!