I am trying to figure out why the SLA is flapping between 10.1.2.2 and 10.1.3.2 every 15 seconds. The delay is below 60 Milliseconds and it still flaps to 2nd static route 10.1.3.2. Also, even if I shut down the interface on R2 , 10.1.2.2 still shows up in the routing table during the consistent flapping. I do have EIGRP configured as well. But I would think that the static entries would take precedence over the dynamic route since it has a lower AD. Here is the SLA configuration I have !
ip sla 1
icmp-echo 10.1.6.2 source-ip 10.1.1.1
track 1 ip sla 1
delay down 5 up 5
ip sla schedule 1 life forever start-time now
ip route 10.1.6.0 255.255.255.0 10.1.2.2 track 1
ip route 10.1.6.0 255.255.255.0 10.1.3.2 2
However I am getting this response even if the connection to router 2 to is down.
Router(config)# *Jan 2 17:00:03.150: %TRACK-6-STATE: 1 ip sla 1 state Down -> Up
Router(config)# *Jan 2 17:00:18.158: %TRACK-6-STATE: 1 ip sla 1 state Up -> Down
Router(config)# *Jan 2 17:00:33.166: %TRACK-6-STATE: 1 ip sla 1 state Down -> Up
Router(config)# *Jan 2 17:00:48.176: %TRACK-6-STATE: 1 ip sla 1 state Up -> Down
Router(config)# *Jan 2 17:01:03.180: %TRACK-6-STATE: 1 ip sla 1 state Down -> Up
Try changing the sla destination to the 10.1.4.2, as in that case any reachabilty issue to that destination will lose connectivity to 10.1.6.2 on that route path only, Because as it stands currently the ip sla is seeing 10.1.6.2 via its alternative route path as being up so sla transitions up again because thr ip sla source/destination is reachable, then the cycle continues.....