08-29-2013 07:15 AM - edited 03-07-2019 03:12 PM
Hi,
We are getting following logs on regular interval for ip sla
003902: Aug 27 13:54:03.494 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Down->Up
003903: Aug 27 14:05:08.585 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Up->Down
003904: Aug 27 14:05:13.586 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Down->Up
003905: Aug 27 17:06:29.975 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Up->Down
003906: Aug 27 17:06:34.973 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Down->Up
003902: Aug 27 13:54:03.494 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Down->Up
003903: Aug 27 14:05:08.585 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Up->Down
003904: Aug 27 14:05:13.586 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Down->Up
003905: Aug 27 17:06:29.975 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Up->Down
003906: Aug 27 17:06:34.973 IST: %TRACKING-5-STATE: 10 rtr 10 reachability Down->Up
Physical setup: Cisco 3845 router(soruce IP of IP SLA)--bluecoat packetshaper---L2 cisco switch---l3 cisco switch(Destination IP of IP SLA)--
IP SLA Config
==========
track 10 rtr 10 reachability
ip route vrf LEGACYMAN 10.191.192.0 255.255.192.0 10.191.193.1 track 10
ip sla 10
icmp-echo 10.191.193.28 source-ip 10.191.193.16
timeout 4000
vrf CHECK
frequency 5
ip sla schedule 10 life forever start-time now
Pls suggest for the flap reason.
Br/Subhojit
09-02-2013 01:06 AM
Hi expert,
pls respond
09-02-2013 04:18 AM
Hello subhojit halder,
Please, collect the following outputs:
# show ip sla monitor configuration 10
# show ip route vrf CHECK 10.191.193.28
And verify correct behavior of regular ping:
# ping vrf CHECK 10.191.193.28 source 10.191.193.16
Another question is you are tracking under vrf CHECK, but setup static route for vrf LEGACYMAN, is it an expected design?
Thank you
--
Best regards,
Dmitry Skotnikov
09-02-2013 09:27 AM
Hi,
Vrf name is LEGACYMAN, sorry for the type-o
Pls find the outout as suggested
BG1RT0501#show ip sla configuration 10
IP SLAs, Infrastructure Engine-II.
Entry number: 10
Owner:
Tag:
Type of operation to perform: icmp-echo
Target address/Source address: 10.191.193.28/10.191.193.16
Operation timeout (milliseconds): 4000
Type Of Service parameters: 0x0
Vrf Name: LEGACYMAN
Request size (ARR data portion): 28
Verify data: No
Schedule:
Operation frequency (seconds): 5 (not considered if randomly scheduled)
Next Scheduled Start Time: Start Time already passed
Group Scheduled : FALSE
Randomly Scheduled : FALSE
Life (seconds): Forever
Entry Ageout (seconds): never
Recurring (Starting Everyday): FALSE
Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 5000
Distribution Statistics:
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 4294967295
History Statistics:
Number of history Lives kept: 0
Number of history Buckets kept: 15
History Filter Type: None
Enhanced History:
BG1RT0501#show ip route vrf LEGACYMAN 10.191.193.28
Routing entry for 10.191.193.0/27
Known via "connected", distance 0, metric 0 (connected, via interface)
Routing Descriptor Blocks:
* directly connected, via FastEthernet0/1/1.508
Route metric is 0, traffic share count is 1
BG1RT0501#ping vrf LEGACYMAN 10.191.193.28 source 10.191.193.16 repeat 1000
Type escape sequence to abort.
Sending 1000, 100-byte ICMP Echos to 10.191.193.28, timeout is 2 seconds:
Packet sent with a source address of 10.191.193.16
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!
Success rate is 100 percent (1000/1000), round-trip min/avg/max = 1/1/8 ms
BG1RT0501#
03-23-2017 02:50 AM
Hello
Just like to add, you can also tray increasing the track delay as default I believe is 5 secs
track 10
delay 30 down
res
Paul
09-10-2019 05:30 AM
i am getting these logs ..what should i do to resolve it
Sep 10 08:12:38: %TRACKING-5-STATE: 10 rtr 100 reachability Down->Up
Sep 10 08:17:08: %TRACKING-5-STATE: 10 rtr 100 reachability Up->Down
Sep 10 08:17:38: %TRACKING-5-STATE: 10 rtr 100 reachability Down->Up
Sep 10 08:21:38: %TRACKING-5-STATE: 10 rtr 100 reachability Up->Down
Sep 10 08:22:08: %TRACKING-5-STATE: 10 rtr 100 reachability Down->Up
Sep 10 08:23:43: %TRACKING-5-STATE: 20 rtr 200 reachability Up->Down
Sep 10 08:24:08: %TRACKING-5-STATE: 20 rtr 200 reachability Down->Up
03-22-2017 10:56 PM
I think I see what the problem is. Sorry to solve it after 4 years. But do let me know if I got it or not . I will really appreciate it.
In your case your saying:
ip sla 10
icmp-echo 10.191.193.28 source-ip 10.191.193.16
timeout 4000
vrf CHECK
frequency 5
So here you are saying ''timeout if u dont get a response within 4 seconds and you do that test every 5 seconds . So you're timing out before u send out the echo/ping requests. So you're timeout has to be more then the frequency by my understanding. Let me know how you resolved it.
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