EIGRP External network via MPLS link

[pciaccio]

I have an issue I would like to resolve, so I thought I would throw it out to the forum... I used to have a Point-to-Point dedicated T-1 between my facilities. The subnet was the same and as EIGRP learned it was a neighbor and all routes were advertised as local routes in the routing table. I recently removed this T-1 and upgraded to a MPLS service (T-1 hand off) and both ends are now separate subnets. However now my routes are being seen as External on the routing table and now I see that the remote end does not show up as a neighbor in EIGRP. I do not want this to happen. It is causing havoc to my backup links when they come active and restore back to normal. Routes prefere my backup to the primary link because when the backup comes up it is a point-to-point link and is learned as a local neighbor. When the primary is restored the routes do not want to bounce back to the MPLS because again it is external and the remote end is not a neighbor. Is there a way to make the MPLS path show up as local route and have the remote end show up as its neighbor via the MPLS??? Thanks in advance for any assistance..

[pciaccio]

For those of you who would like to know,

I was able to get this working well in my environment through the MPLS. I used the DISTANCE EIGRP 170 170(IntAS)(extAS) command on the router that has my backup T-1 on it only on one side of the circuit. This way it advertises an AS of 170 for Internal and External routes. I still see EX on the routes over the MPLS but now I have made it where the MPLS routes are AS 90 and backup T-1 AS 170. I removed this command and noticed EIGRP neighboring changes for the wrong route and when implemented routes diverge correctly....Thanks everyone for their assistance and comments...

[arathyram]

Hi - would you be able to copy/send your config (without the sensitive info). Was the admin distance modification done at the point to point router on the remote end ? We are in a similar fix, but my understanding is that changing the admin distance is not 'supported' by cisco/tac - though the command is there. In our case, we have a similar issue with the mpls (D-EX) needing to be primary and the framerelay (EIGRP int) has to be backup.