cancel
Showing results for 
Search instead for 
Did you mean: 
cancel

Who Me Too'd this topic

IP SLA Path Echo Issue

I have below setup :

 

R1->R2->R3-R4

 

R1 : Loopback 0 (192.168.1.1)

R1 till R4 is in /30 subnet (10.11.x/30) means R1 to R2 (10.1.1.1->2), R2 to R3  ((10.1.1.5->6) etc.

R4 Loopback 0 (172.16.1.1)

!

R1#ping 172.16.1.1 source Loopback0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.1, timeout is 2 seconds:
Packet sent with a source address of 192.168.1.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 68/88/108 ms
R1#

!

!

!
ip sla 2
path-echo 172.16.1.1 source-ip 192.168.1.1
timeout 2000
frequency 5
!
ip sla schedule 2 start-time now life forever
!

While running debug gets continues below messages...

debug ip sla trace says

!

*Mar  1 00:06:55.039: IP SLAs(2) pathEcho operation: Sending Packet to 172.16.1.1 with ttl = 59
*Mar  1 00:06:55.131: IP SLAs(2) pathEcho operation: Return Value of U for target 10.1.1.10
*Mar  1 00:06:55.959: IP SLAs(2) pathEcho operation: Sending Packet to 172.16.1.1 with ttl = 64
*Mar  1 00:06:56.047: IP SLAs(2) pathEcho operation: Return Value of U for target 10.1.1.10
*Mar  1 00:06:56.047: IP SLAs(2) pathEcho operation: Error Adding Hop - 10.1.1.10
*Mar  1 00:06:56.051: IP SLAs(2) pathEcho operation: Sending Packet to 172.16.1.1 with ttl = 64
*Mar  1 00:06:56.135: IP SLAs(2) pathEcho operation: Return Value of U for target 10.1.1.10
*Mar  1 00:06:56.135: IP SLAs(2) pathEcho operation: Error Adding Hop - 10.1.1.10
*Mar  1 00:06:56.175: IP SLAs(2) pathEcho operation: Hop 10.1.1.2        Response Time 43
*Mar  1 00:06:56.223: IP SLAs(2) pathEcho operation: Hop 10.1.1.6        Response Time 47
*Mar  1 00:06:56.323: IP SLAs(2) pathEcho operation: Hop 10.1.1.10       Response Time 97
*Mar  1 00:06:56.323: IP SLAs(2) Scheduler: Updating result
*Mar  1 00:06:56.327: IP SLAs(2) Scheduler: life left 18332
*Mar  1 00:06:56.327: IP SLAs(2) Scheduler: is it random? 0
*Mar  1 00:06:56.327: IP SLAs(2) Scheduler: start wakeup timer, delay = 3332
*Mar  1 00:06:59.659: IP SLAs(2) Scheduler: saaSchedulerEventWakeup
*Mar  1 00:06:59.659: IP SLAs(2) Scheduler: Starting an operation
*Mar  1 00:06:59.663: IP SLAs(2) pathEcho operation: Sending a pathEcho operation
*Mar  1 00:06:59.663: IP SLAs(2) pathEcho operation: Sending Packet to 172.16.1.1 with ttl = 1
*Mar  1 00:06:59.675: IP SLAs(2) pathEcho operation: Return Value of ! for target 10.1.1.2
*Mar  1 00:06:59.675: IP SLAs(2) pathEcho operation: Adding hop - 10.1.1.2
*Mar  1 00:06:59.679: IP SLAs(2) pathEcho operation: Sending Packet to 172.16.1.1 with ttl = 2
*Mar  1 00:06:59.727: IP SLAs(2) pathEcho operation: Return Value of ! for target 10.1.1.6
*Mar  1 00:06:59.915: IP SLAs(2) pathEcho operation: Sending Packet to 172.16.1.1 with ttl = 4
*Mar  1 00:07:00.003: IP SLAs(2) pathEcho operation: Return Value of U for target 10.1.1.10
*Mar  1 00:07:00.007: IP SLAs(2) pathEcho operation: Error Adding Hop - 10.1.1.10

!

 

Means out of 100, 90 times fails. What could be the reason ? Highlighted one where it got success.

 

 

 

Who Me Too'd this topic