06-14-2016 01:18 PM - edited 03-05-2019 04:13 AM
06-14-2016 01:39 PM
Basic jist looks correct to me. What is not working? What is not happening that you would like to happen?
06-15-2016 12:51 PM
06-15-2016 01:10 PM
When it is in its normal state can you note the output of "show ip sla statistics 10" and "show track 10". Then shutdown Fa0/0 at HW, wait a minute, and note the output of the same two commands again. Then post both outputs here please.
06-16-2016 08:07 AM
06-16-2016 12:57 PM
ip sla itself uses the "routing rules" the router is using for sending test packets.
Everything works perfectly when you use 192.168.5.2 as a test target, because that IP address is on a directly connected interface. If the interface/circuit goes down the router is invalid, and if the interface comes back up the route becomes valid again.
However pinging the server 192.168.1.5 is not the same.
When the circuit is up, you have a default route going via the 192.168.5.0/30 path, and the ping works. When the circuit goes down ip sla fails, and the default route now points to 192.168.4.0/30.
Now this is the catch - when your circuit comes back up your pings will obey the routing table, and keep going down the 192.168.4.0/30 path, which will never work, and hence it will also show as failed and never come back up.
The easiest fix is to put a static permanent route for 192.168.1.5 via 192.168.5.2, so the IP sla traffic for that server always goes via one path, even if it is down. The other option is if 192.168.1.0/24 is only reachable via 192.168.5.2 then add a permanent static route for the whole subnet.
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