I have a site with an ASA5505 and 2 isp connections but the catch is the 2 isp's are giving me a dynamic IP so I am unable to use this
how do my routes differ? etc.?
Why is this not going to work?
As soon as you always have the interface up and working it should succed on the monitoring process.
You will have 2 ISP default gateways Ip addresses right?
So that is all you need, then select a target to monitor the SLA process.
I can't see how this will work because with the dynamic ip from the isp I don't have a default gateway defined but rather I have ''ip address dhcp setroute' on the outside vlan and that is taking care of my default gateway. Also if I have no default gateway defined how do I apply ipsla and tracking, on which route?
can you please post a sample config if you don't mind
so its DHCP for the ISP not for your interface.
That is different, I think you will need to have unless one destination ip address for the default gateway so you can use it to track it as there is no metric option on the following command:
interface gigabitEthernet 0/0
ip address dhcp setroute
Rigth now I think that is the only option you have to make SLA work.
Here are the requirements for SLA on an ASA
Choose a monitoring target that can respond to ICMP echo requests. The target can be any network object that you choose, but a target that is closely tied to your ISP connection is recommended. Some possible monitoring targets include:
This document assumes that the security appliance is fully operational and configured to allow the Cisco ASDM to make configuration changes.