Thanks Saju, that part at the remote site I understand thanks to your help, but what I need to figure next is in my Datacenter what would I need to do to make sure subnet that comes in over the VPN tunnel goes back out the tunnel and not over the WAN.

Hi,

i undetstood that you are looking for the following scenario:

MPLS link is in Cisco Router & VPN Tunnel is in ASA Firewall. So Your requirement is that if MPLS Goes down VPN has to trigger automatically right.

If that is the scenario, Go ahead with the following steps.

it worked for me.

First you have to place a default route in the Router like as follows

ip route InsidelanID subnetmask ASAinterfaceIP

please find the attachement for ASA end Configuration Steps.

Pls Rate me if it help to you

Thanks for the document, so say my remote location is 10.97.x.x and the 10.97.x.x is going over the vpn tunnel to my central data center, how will my core switch know not to send the 10.97.x.x out over the MPLS cloud, but back to the VPN tunnel.

Hi - am running into a similar situation and did a search on forums and noticed your query. Wondering if you were able to resolve this.

my take is to have a similar static route for the remote site at the DC with a higher admin distance. So, at the remote site - you have a default route with say distance 250 pointing to the remote site firewall which terminates the VPN. And at the DC, you have static routes to the remote site subnets with a high distance pointing to the hub end of the firewall that terminates the vpn.

did you have a similar approach

rgds