cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1090
Views
0
Helpful
1
Replies

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.

 

 

 

1 Reply 1

Few outputs :

 

R1#sh ip sla statistics
Round Trip Time (RTT) for       Index 2
        Latest RTT: 84 milliseconds
Latest operation start time: *00:13:15.951 UTC Fri Mar 1 2002
Latest operation return code: OK
Operation time to live: 0
R1#

 

R1#show ip sla statistics details

Round Trip Time (RTT) for       Index 2
        Latest RTT: 95 milliseconds
Latest operation start time: *00:14:10.795 UTC Fri Mar 1 2002
Latest operation return code: OK
Over thresholds occurred: FALSE
Operation time to live: 43 sec
Operational state of entry: Active
Last time this entry was reset: Never

!

 

R1#sh ip sla configuration 2
IP SLAs, Infrastructure Engine-II.
Entry number: 2
Owner:
Tag:
Type of operation to perform: path-echo
Target address/Source address: 172.16.1.1/192.168.1.1
Request size (ARR data portion): 28
Operation timeout (milliseconds): 2000
Type Of Service parameters: 0x0
Verify data: No
Loose Source Routing: Disabled
Vrf Name:
LSR Path:
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): 60
   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 paths kept: 5
   Number of statistic hops kept: 16
   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
   Number of history Samples kept: 16
   History Filter Type: None


R1#

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: