IP SLA RTT values - UDPEcho Vs. UDPJitter

Unanswered Question
Jun 19th, 2008
User Badges:

Hi,


I setup the following:


R1----R2----R3


R1 configured as source/responder to R3.

R3 configured as source/responder to R1.

R1 configured just to route traffic.


R1 configured with the following:


ip sla monitor 1

type udpEcho dest-ipaddr 192.168.20.1 dest-port 5000

request-data-size 160

ip sla monitor schedule 1 life forever start-time now

ip sla monitor 2

type jitter dest-ipaddr 192.168.20.1 dest-port 5000 num-packets 20 interval 10

request-data-size 160

ip sla monitor schedule 2 life forever start-time now


R3 configured pretty much the same, only in reverse direction:


ip sla monitor responder

ip sla monitor 1

type udpEcho dest-ipaddr 192.168.10.1 dest-port 5000

request-data-size 160

ip sla monitor schedule 1 life forever start-time now

ip sla monitor 2

type jitter dest-ipaddr 192.168.10.1 dest-port 5000 num-packets 20 interval 10

request-data-size 160

ip sla monitor schedule 2 life forever start-time now


Looking at results on R1 for UDPEcho(1) and UDPJitter(2) operations:


BELFAST_SLA#sh ip sla monitor statistics 1

Round trip time (RTT) Index 1

Latest RTT: 166 ms


BELFAST_SLA#sh ip sla monitor statistics 2

Round trip time (RTT) Index 2

Latest RTT: 864 ms


The RTT values for UDPEcho and UDPJitter dont change significantly over time.


Why is there such a difference in the two values?


Thanks,

Mark


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
tstanik Wed, 06/25/2008 - 05:57
User Badges:
  • Bronze, 100 points or more

UDP Jitter measures round-trip delay, one-way delay, one-way jitter, one-way packet loss, and connectivity testing of networks that carry UDP traffic, such as voice. And

UDP Echo measures round-trip delay of UDP traffic.


For the further details follow the URL :

http://www.cisco.com/en/US/docs/ios/12_4/ip_sla/configuration/guide/hsoverv.html#wp1062629


Actions

This Discussion