VRRP and IP SLA Reachability Issue

[Techworking]

 I have a multihomed scenario with two routers connected to two different ISP's.

The inside interfaces of the routers have VRRP configured and are both connected to the same switch.

IP SLA reachability is set up to track reachability to 8.8.8.8 in the event of unavailability, the track will go down and  VRRP will flip the IP to the secondary router IP.

However we had an outage the other day on the primary ISP circuit and the failover was not initiated

I turned on  "debug ip icmp"   and no icmp packets is being sent out by ip sla probe to 8.8.8.8

However I can manually ping 8.8.8.8

Also I don't see Track 10 statement  - "Tracked by: Track-list 105" and no changes in 5 weeks

#sh track
Track 10
IP SLA 10 reachability
Reachability is Up
4 changes, last change 5w6d
Latest operation return code: OK
Latest RTT (millisecs) 1
Track 105
List boolean and
Boolean AND is Up
6 changes, last change 5w6d
object 10 Up
Tracked by:
VRRP TenGigabitEthernet0/1/0 180

Here is the primary router configuration:

=====================================

track 10 ip sla 10 reachability
!
track 105 list boolean and
object 10
!
interface TenGigabitEthernet0/1/0
description inside
ip address x.x.x.243 255.255.255.240
no ip redirects
no ip unreachables
ip verify unicast reverse-path
ip route-cache same-interface
load-interval 30
vrrp 180 ip x.x.x.254
vrrp 180 priority 104
vrrp 180 track 105
arp timeout 300

!
ip route 8.8.8.8 255.255.255.255 x.x.x.x
!
ip sla 10
icmp-echo 8.8.8.8 source-interface TenGigabitEthernet0/1/0
threshold 1000
timeout 1000
frequency 15
ip sla schedule 10 start-time now
===========================================

How can I get this to work as expected?

Many thanks

[balaji.bandi]

I do not see any value here for below one : (let me know any reason here ?)

track 105 list boolean and
object 10

Simple Track should able to give you example below :

Primary :

track 10 ip sla 10
!
ip sla 10
icmp-echo 8.8.8.8 source-interface TenGigabitEthernet0/1/0
threshold 1000
timeout 1000
frequency 15
ip sla schedule 10 life forever start-time now
!
interface TenGigabitEthernet0/1/0
vrrp 180 track 10

Secondary :

track 10 ip sla 10
!
ip sla 10
icmp-echo 8.8.8.8 source-interface TenGigabitEthernet0/1/0
threshold 1000
timeout 1000
frequency 15
ip sla schedule 10 life forever start-time now
!
interface TenGigabitEthernet0/1/0
vrrp 180 track 10 descrement 20

[Techworking]

There was another object that was being tracked but has been removed

[balaji.bandi]

oh that makes sense since the config now shown as per the post, so was my suggestion, if you have a condition then it needs to meet the condition before the track trigger, is the condition met?

[Techworking]

Hi Balaji,

Yes the trigger has been met.

When the interface went down, the internet became unreachable.

If it was working correctly the ICMP probes would have triggered.

However as said earlier I am not seeing any ICMP packets being sent out by IP SLA 10

I need help in figuring out why this is happening

[balaji.bandi]

However as said earlier I am not seeing any ICMP packets being sent out by IP SLA 10

as per the below it is right ? or i miss something here ?

#sh track
Track 10
IP SLA 10 reachability
Reachability is Up
4 changes, last change 5w6d
Latest operation return code: OK
Latest RTT (millisecs) 1
Track 105
List boolean and
Boolean AND is Up
6 changes, last change 5w6d
object 10 Up
Tracked by:
VRRP TenGigabitEthernet0/1/0 180