I have an 1811, dual WAN. It's setup to failover properly, based on IP SLA and tracking. Fixed IP (184.108.40.206) with my primary ISP. I'm pinging my primary ISP's default gateway (220.127.116.11) for the tracking object. This works as expected. The problem is that when my primary ISP is experiencing heavy traffic, the gateway often stops responding to pings. The connection is still up, and it still passes traffic. But since I stop getting a response to the ping, my router things the connection is down, and switches to the backup ISP.
This is undesirable.
So I tried changing the ping to a different address (e.g., 18.104.22.168). I also changed the appropriate access-list (PingISP_A).
The pings work. If the primary connection is disabled, the router properly fails over. However, when the primary connection is reconnected, the pings do not start working again. I think this is because the route (ip route 0.0.0.0 0.0.0.0 22.214.171.124 10 track 100) is gone from the routing table at this point. Is there any way to get this working? Am I going about it the wrong way?
Current config - works (except for the above issue)
ip address 126.96.36.199 255.255.255.0
ip address dhcp
ip dhcp-client default-router distance 20
ip route 0.0.0.0 0.0.0.0 188.8.131.52 10 track 100
ip route 0.0.0.0 0.0.0.0 dhcp 20
ip local policy route-map LocalPolicy
route-map LocalPolicy permit 10
match ip address PingISP_A
set ip next-hop 184.108.40.206
set interface Null0
ip access-list extended PingISP_A
permit icmp any host 220.127.116.11 echo
ip sla 111
icmp-echo 18.104.22.168 source-interface FastEthernet0
ip sla schedule 111 life forever start-time now
track 100 rtr 111 reachability
delay down 30 up 30