05-14-2013 01:24 AM
Hi,
i want to connect a ASA with two ISPs one for internet traffic one for S2S VPN, there is a dedicatet VPN router on the second link.
In case of an outage of the first link the second shall be active.
route outside 0.0.0.0 0.0.0.0 10.20.20.1 1 track 1route backup 0.0.0.0 0.0.0.0 10.20.30.1 254
route backup 192.168.0.0 255.255.0.0 10.20.30.1
Is this configuration working??
Solved! Go to Solution.
05-14-2013 01:41 AM
Hi,
You will have to configure the "sla monitor" configuration to monitor some destination IP address on the main ISP for the ASA to determine if the connection is working or not. Probably some IP address on the public network.
sla monitor 1
type echo protocol ipIcmpEcho
num-packets
timeout
frequency
sla monitor schedule 1 life forever start-time now
You will also need a configuration related to the command "track"
track 1 rtr 1 reachability
route outside 0.0.0.0 0.0.0.0 10.20.20.1 track 1
route backup 0.0.0.0 0.0.0.0 10.20.30.1 254
The above combined with the routes you mention should be enough regarding the routing. Naturally for every remote L2L VPN network you will always need a specific static route on the ASA towards the backup ISP device.
Also you naturally need to handle the translations on the ASA. Seems both of your ISP links have a separate device in front which holds the public IP addresses. So am I correct to assume you are passing all traffic from the LAN links to the ISP links through the ASA without any kind of NAT and let those routers handle the private to public NAT?
- Jouni
05-14-2013 01:41 AM
Hi,
You will have to configure the "sla monitor" configuration to monitor some destination IP address on the main ISP for the ASA to determine if the connection is working or not. Probably some IP address on the public network.
sla monitor 1
type echo protocol ipIcmpEcho
num-packets
timeout
frequency
sla monitor schedule 1 life forever start-time now
You will also need a configuration related to the command "track"
track 1 rtr 1 reachability
route outside 0.0.0.0 0.0.0.0 10.20.20.1 track 1
route backup 0.0.0.0 0.0.0.0 10.20.30.1 254
The above combined with the routes you mention should be enough regarding the routing. Naturally for every remote L2L VPN network you will always need a specific static route on the ASA towards the backup ISP device.
Also you naturally need to handle the translations on the ASA. Seems both of your ISP links have a separate device in front which holds the public IP addresses. So am I correct to assume you are passing all traffic from the LAN links to the ISP links through the ASA without any kind of NAT and let those routers handle the private to public NAT?
- Jouni
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