I have a client with a meshed MPLS network for their private traffic using BGP with locations in various states. Each location has its own internet access through a local T1 or cable modem, etc. One location is downsizing and they wish to cut the internet circuit, running it instead over the MPLS circuit to the corporate location, which is causing me a brainfreeze. The MPLS router (Cisco 2811xm) at the remote is not the default gateway, there is a smaller Cisco router (2620) that handles this function, and I've modified the route that pointed to their watchguard to go to the mpls router now. Depending on where I'm trying to go (say tracert to google.com, cisco.com, etc.), I get different interface results, but each with this similiarity: tracert ping-pongs between the local mpls router interface and one of the remotes or the corporate until it times out at 30 hops. As this is BGP, a simple "ip route 0.0.0.0 0.0.0.0 corpoffiint" type statement isn't going to work.
I'm trying to wrap my mind around this, any help would be appreciated. :)