07-04-2022 07:51 AM
Hi,
While configuring enhanced object tracking with IP SLA icmp-echo leveraging track lists, I understand that each object is completely independent from each other in terms of timings (frequency), states, etc.
Since each tracking is bound to an ip sla operation each of which in turn hold its own state and timeline (each ip sla operation starts when the command start-time is issued).
Per the below example:
!
ip sla 10
icmp-echo 9.9.9.9 source-ip 10.10.10.1
timeout 10000
frequency 30
ip sla schedule 10 life forever start-time now
!
ip sla 11
icmp-echo 1.1.1.1 source-ip 10.10.10.1
timeout 10000
frequency 30
ip sla schedule 11 life forever start-time now
!
!
track 10 ip sla 10 reachability
!
track 11 ip sla 11 reachability
!
track 100 list boolean or
object 10
object 11
!
The below statements are correct:
- Object 10 and 11 are independent from each other in terms of timings, states, and specific attributes to each corresponding ip sla operation.
- Each object is executed on its own timing (per the start-time and frequency parameters)
- Objects on the list are NOT sequential
- Each object holds its last known value (result of the icmp-echo operation) until the next frequency interval triggers the new operation and a new response is received (or not)
I would appreciate if someone from the community can help to confirm my understanding and share corrections/complementary information if relevant.
Thanks and glory to the community
07-04-2022 08:00 AM
can you more elaborate, you use track for reachability "floating route?"
07-04-2022 08:02 AM
correct each sla work on their own, but when you tracking, make sure you doing right OR or AND bolean operation get out of the results :
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