05-17-2012 08:11 AM
Hi all,
I've got a Remote Access VPN up and running in a PIX Firewall. The VPN session are establish trough the outside (connect to an ISP) interface.
Now I want to backup this connection with another ISP. Obviously I need to configure another interface (with public IP address), set the “crypto map” and the “crypto isakmp” to be enable in this new interface, but the problem is the route (the default gateway must change when the outside interface is not available).
What are the options to backup the remote access VPN? Is it possible to do that configuration?
Thx in advance
/mserrao
Solved! Go to Solution.
05-17-2012 08:22 AM
To setup interface tracking on your ASA...
sla monitor 1
type echo protocol ipIcmpEcho 4.2.2.1 interface OUTSIDE1
frequency 30
!
sla monitor 2
type echo protocol ipIcmpEcho 4.2.2.2 interface OUTSIDE2
frequency 30
!
track 1 rtr 1 reachability
track 2 rtr 2 reachability
!
route OUTSIDE1 0.0.0.0 0.0.0.0
route OUTSIDE2 0.0.0.0 0.0.0.0
!
route OUTSIDE1 4.2.2.1 255.255.255.255
route OUTSIDE2 4.2.2.2 255.255.255.255
Is that what you are looking for?
Kind Regards,
Kevin
**Please remember to rate helpful posts as well as mark the question as 'answered' once your issue is resolved. This will help others to find your solution faster.
05-17-2012 10:34 AM
Hi Mserrao,
Please follow the link below, which explains in step by step method and descriptive explantions making primary and backup ISP redundance.
As far as your VPN client are concern, if you have FQDN name for your public address (for vpn client use), then you must associate have both of your public IP(s) (i.e. new or old public IPs) be assign to your vpn's FQDN, so that when one circuit is not available but your vpn-client software will try to second public IP, which is also pointed by FQDN.
Hope this helps.
Thanks
Rizwan Rafeek
05-17-2012 08:22 AM
To setup interface tracking on your ASA...
sla monitor 1
type echo protocol ipIcmpEcho 4.2.2.1 interface OUTSIDE1
frequency 30
!
sla monitor 2
type echo protocol ipIcmpEcho 4.2.2.2 interface OUTSIDE2
frequency 30
!
track 1 rtr 1 reachability
track 2 rtr 2 reachability
!
route OUTSIDE1 0.0.0.0 0.0.0.0
route OUTSIDE2 0.0.0.0 0.0.0.0
!
route OUTSIDE1 4.2.2.1 255.255.255.255
route OUTSIDE2 4.2.2.2 255.255.255.255
Is that what you are looking for?
Kind Regards,
Kevin
**Please remember to rate helpful posts as well as mark the question as 'answered' once your issue is resolved. This will help others to find your solution faster.
05-18-2012 04:52 AM
Thx for your helpful reply
Regards
/mserrao
05-17-2012 10:34 AM
Hi Mserrao,
Please follow the link below, which explains in step by step method and descriptive explantions making primary and backup ISP redundance.
As far as your VPN client are concern, if you have FQDN name for your public address (for vpn client use), then you must associate have both of your public IP(s) (i.e. new or old public IPs) be assign to your vpn's FQDN, so that when one circuit is not available but your vpn-client software will try to second public IP, which is also pointed by FQDN.
Hope this helps.
Thanks
Rizwan Rafeek
05-18-2012 04:53 AM
Thx for your helpful reply
Regards
/mserrao
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide