We are currently adding a 50Mbps cable line for a client who at the moment has a T1. Mail will continue to be delivered over the T1, but we want to use the cable line as the default interface for all other traffic. I plan on doing this using SLA's and tracking (we don't need to load-balance, just fail-over from the cable to T1)
I'm curious how this will affect our VPN clients. We have dozens of users who connect via VPN clients using the IP of the old T1 and I need to make sure they can still connect regardless of whether our default route is pointing elsewhere on the ASA. Will it respect the source of the VPN client connection does this require policy-based routing (not supported by ASA's as I understand)
