IP SLA and Tracking

[TRACY HARTMANN]

ip sla 1
icmp-echo 119.29.29.29 source-interface Vlan2
verify-data
frequency 30
ip sla schedule 1 life forever start-time now
ip sla 2
icmp-echo 223.5.5.5 source-interface Vlan2
verify-data
frequency 30
ip sla schedule 2 life forever start-time now

ip route 119.29.29.29/32 10.13.252.26

ip route 223.5.5.5/32 10.13.252.26

track 8 list boolean or
object 1
object 2

track 1 ip sla 1 reachability
delay up 90 down 90

track 2 ip sla 2 reachability
delay up 90 down 90

event manager applet LinkUp
event track 8 state up
action 1.1 cli conf t
action 4.5 cli interface Vlan555
action 4.6 cli no ip policy route-map vr7
action 4.7 cli ip policy route-map vr6
event manager applet Linkdown
event track 8 state down
action 1.1 cli conf t
action 4.5 cli interface Vlan555
action 4.6 cli no ip policy route-map vr6
action 4.7 cli ip policy route-map vr7
action 5.5 cli copy running-config startup-config

I didn't list the route-maps but basically they change the route-map depending if the circuit is up or down.

The interface starts off with the vr6 route-map, if we disconnect the circuit the route-map on the Vlan is changed to Vr7.  However it never goes back.  So if we plug the circuit back in, it never shows up on Tracking however the routes work correctly.  Do I need to add the following to the static routes:

p route 119.29.29.29/32 10.13.252.26  track ?

ip route 223.5.5.5/32 10.13.252.26 null0 ?

Thanks

[MHM Cisco World]

You need two EEM 

One for track UP

Other for track DOWN

MHM

[TRACY HARTMANN]

Sorry I thought I included both, this is what I have:

event manager applet LinkUp
event track 8 state up
action 1.1 cli conf t
action 4.5 cli interface Vlan555
action 4.6 cli no ip policy route-map vr7
action 4.7 cli ip policy route-map vr6

event manager applet Linkdown

event track 8 state down
action 1.1 cli conf t
action 4.5 cli interface Vlan555
action 4.6 cli no ip policy route-map vr6
action 4.7 cli ip policy route-map vr7
action 5.5 cli copy running-config startup-config

[paul driver]

Hello Tracy

---

@TRACY HARTMANN wrote:
The interface starts off with the vr6 route-map, if we disconnect the circuit the route-map on the Vlan is changed to Vr7.  However it never goes back.

You don’t share what your RMs are doing or any alternative nexthop for that matter, however it sounds like IPSLA is able to reach both nexthops via primary/secondary paths as such the tracking is not initiating fallback because it still sees the alternative monitored nexthop as being reachable.

You could try and negate this with the below cfg.

Example:
no ip sla 2
no event manager applet LinkUp
no track 8

access-list 100 permit icmp host <scr vlan2 ip> 119.29.29.29
track 8 rtr 1 reachability

ip route 119.29.29.29/32  <interface> 10.13.252.26 track 8 name primary circuit
ip route 223.5.5.5/32 <interface> 10.13.252.26 track 8 name primary circuit
ip route 119.29.29.29 255.255.255.255 Null0 2
ip route 119.29.29.29/32  <interface> <seconary nexthop> 10 name backup circuit
ip route 223.5.5.5/32 <interface> <seconary nexthop> 10 name backup circuit

route-map ipsla
match ip address 100
set ip next-hop 10.13.252.26
set interface Null0
ip local policy route-map ipsla