Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

IPSLA UDP JITTER Operation Failure

Hi All

I need urgent help, I'm trying to set up an IPSLA operation which is failing and i need urgent help. I read and followed alot of documentation.

When i test UDPJitter trace oprtation this works fine without a problem, however when i try to use.

the basic jitter operation i get operation failures for some reason. Please see below.

This is the topology

R1--------------------R2

Source              Responder

192.168.1.1        192.168.2.7

############

R1#
Mar  1 03:07:22.847: %SYS-5-CONFIG_I: Configured from console by console
R1#debug ip sla monitor trace 122
IP SLA Monitor TRACE debugging for entry 122 is on
R1#debug ip sla monitor trace 122
Mar  1 03:07:29.579: IP SLA Monitor(122) CtrlMsg: Timeout
Mar  1 03:07:29.579: IP SLA Monitor(122) CtrlMsg: Sending msg, ver=1, id=123, le
n=52, cmd=4, ip=192.168.2.7, port=4052, duration=5200ms
R1#debug ip sla monitor error 122
IP SLA Monitor ERROR debugging for entry 122 is on
R1#
Mar  1 03:07:34.583: IP SLA Monitor(122) CtrlMsg: Timeout
Mar  1 03:07:34.583: IP SLA Monitor(122) CtrlMsg: No connection
Mar  1 03:07:34.583: IP SLA Monitor(122) Scheduler: Updating result

*****************
===
R1
===

ip sla monitor 122
type jitter dest-ipaddr 192.168.2.7 dest-port 4052 source-ipaddr 192.168.1.1 co
dec g711alaw codec-numpackets 100 codec-interval 2
ip sla monitor schedule 122 life forever start-time now
ip sla monitor 123
type pathJitter dest-ipaddr 192.168.2.7 num-packets 100 interval 2
ip sla monitor schedule 123 life forever start-time now

==============================

========
R2
======

ip sla monitor responder


R2#show ip sla monitor responder
IP SLA Monitor Responder is: Enabled
Number of control message received: 0 Number of errors: 0
Recent sources:
Recent error sources:

3 REPLIES

Re: IPSLA UDP JITTER Operation Failure

you get "Mar  1 03:07:34.583: IP SLA Monitor(122) CtrlMsg: No connection" so is it possible that there is an ACL or firewall between your 2 routers?

you configured the port UDP  4052 as the destination port, so the control packets should be sent onUDP  4053.

New Member

Re: IPSLA UDP JITTER Operation Failure

Hi Memal

I don't have any firewall between the two devices.

Please tell me what the best configuration is. All i need is to just be able to measure UDP Jitter between 192.168.1.1 Source destination 192.168.2.7

The path jitter operation works without a problem.

Will the below work.

ip sla monitor 122
type jitter dest-ipaddr 192.168.2.7 dest-port 4052 source-ipaddr 192.168.1.1 source-port 4053 codec g711alaw codec-numpackets 100 codec-interval 2
ip sla monitor schedule 122 life forever start-time now
ip sla monitor 123
type pathJitter dest-ipaddr 192.168.2.7 num-packets 100 interval 2
ip sla monitor schedule 123 life forever start-time now

New Member

Re: IPSLA UDP JITTER Operation Failure

Hi Memal

I don't have any firewall between the two devices.

Please tell me what the best configuration is. All i need is to just be able to measure UDP Jitter between 192.168.1.1 Source destination 192.168.2.7

The path jitter operation works without a problem.

Will the below work.

ip sla monitor 122
type jitter dest-ipaddr 192.168.2.7 dest-port 4052 source-ipaddr 192.168.1.1 source-port 4053 codec g711alaw codec-numpackets 100 codec-interval 2
ip sla monitor schedule 122 life forever start-time now
ip sla monitor 123
type pathJitter dest-ipaddr 192.168.2.7 num-packets 100 interval 2
ip sla monitor schedule 123 life forever start-time now

1376
Views
0
Helpful
3
Replies
CreatePlease to create content