IPSLA UDP-Jitter Issues

Hi guys,
Our customer has a WAN network (DCoS) and has voice protected across it. I work for an integrator assisting the customer with their CPE routers end-to-end. Essentially CPE routers extend PSTN lines end-to-end over voice-ports and voip call legs between locations. On CPE routers we're seeing voice traffic being marked/matched end-to-end. We're pretty sure that the ISP is somehow shaping/causing delays on the voice traffic interstate but now we're trying to gather some evidence.
To help isolate, test and provide evidence we were planning on using UDP-Jitter in IP SLA. I've been trying to get this enabled on live routers without success due to the reason "No connection" in the initiators show output. An example of the "show ip sla statistics" on a production device is shown below:
SITE-1#show ip sla statistics
IPSLAs Latest Operation Statistics
IPSLA operation id: 100
Type of operation: udp-jitter
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 17:26:47 BNE Mon Jul 2 2012
Latest operation return code: No connection
RTT Values:
        Number Of RTT: 0                RTT Min/Avg/Max: 0/0/0 milliseconds
Latency one-way time:
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Jitter Time:
        Number of SD Jitter Samples: 0
        Number of DS Jitter Samples: 0
        Source to Destination Jitter Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Jitter Min/Avg/Max: 0/0/0 milliseconds
Packet Loss Values:
        Loss Source to Destination: 0
        Source to Destination Loss Periods Number: 0
        Source to Destination Loss Period Length Min/Max: 0/0
        Source to Destination Inter Loss Period Length Min/Max: 0/0
        Loss Destination to Source: 0
        Destination to Source Loss Periods Number: 0
        Destination to Source Loss Period Length Min/Max: 0/0
        Destination to Source Inter Loss Period Length Min/Max: 0/0
        Out Of Sequence: 0      Tail Drop: 0
        Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
        Calculated Planning Impairment Factor (ICPIF): 0
        Mean Opinion Score (MOS): 0
Number of successes: 0
Number of failures: 1
Operation time to live: Forever
Number of failures continues to increase every 30 seconds or so. The configuration of SITE-1 is as follows:
SITE-1#show run | sec ip sla
ip sla 100
udp-jitter 10.2.2.2 16584 source-ip 10.1.1.1 source-port 16384
tos 30
owner NetFlow
timeout 60000
ip sla schedule 100 life forever start-time now
The configuration of SITE-2 (IP SLA Responder) is as follows:
SITE-2#show run | sec ip sla
ip sla responder
For the sake of privacy I've adjusted the IPs above as well as the router hostnames. The 10.2.2.2 IP lives on SITE-2's router and 10.1.1.1 lives on SITE-1's router.
If I do the above in GNS it works perfectly so I think something else is going on here. Either I've got a bug (doubt it) or something is preventing the UDP from connecting/responding for the IP SLA. Frustratingly, if I do a "show ip sla responder" on the SITE-2 router... it says it received the packets normally without error:
SITE-2#show ip sla responder
        General IP SLA Responder on Control port 1967
General IP SLA Responder is: Enabled
Number of control message received: 123 Number of errors: 0
Recent sources:
        10.1.1.1 [18:06:35.989 BNE Mon Jul 2 2012]
        10.1.1.1 [18:06:30.989 BNE Mon Jul 2 2012]
        10.1.1.1 [18:06:25.989 BNE Mon Jul 2 2012]
        10.1.1.1 [18:05:35.989 BNE Mon Jul 2 2012]
        10.1.1.1 [18:05:30.989 BNE Mon Jul 2 2012]
Recent error sources:
        Permanent Port IP SLA Responder
Permanent Port IP SLA Responder is: Enabled
udpEcho Responder:
IP Address             Port
If I enable trace debug ("debug ip sla trace") on SITE-1's router I get the following...
Jul 2 08:13:25.993: IPSLA-INFRA_TRACE:OPER:100 slaSchedulerEventWakeup
Jul 2 08:13:25.993: IPSLA-INFRA_TRACE:OPER:100 Starting an operation
Jul 2 08:13:25.993: IPSLA-OPER_TRACE:OPER:100 Starting jitter operation
Jul 2 08:13:25.993: IPSLA-OPER_TRACE:OPER:100 Ctrl msg: id=116, type=1, len=52, dest_ip=10.2.2.2, enablePort=16584, duration=60200
Jul 2 08:13:25.993: IPSLA-OPER_TRACE:OPER:100 table_id=0, topo_id=65535
Jul 2 08:13:30.993: IPSLA-OPER_TRACE:OPER:100 Timeout
Jul 2 08:13:30.993: IPSLA-OPER_TRACE:OPER:100 Ctrl msg: id=117, type=1, len=52, dest_ip=10.2.2.2, enablePort=16584, duration=60200
Jul 2 08:13:30.993: IPSLA-OPER_TRACE:OPER:100 table_id=0, topo_id=65535
Jul 2 08:13:35.993: IPSLA-OPER_TRACE:OPER:100 Timeout
Jul 2 08:13:35.993: IPSLA-OPER_TRACE:OPER:100 Ctrl msg: id=118, type=1, len=52, dest_ip=10.2.2.2, enablePort=16584, duration=60200
Jul 2 08:13:35.993: IPSLA-OPER_TRACE:OPER:100 table_id=0, topo_id=65535
Jul 2 08:13:40.993: IPSLA-OPER_TRACE:OPER:100 Timeout
Jul 2 08:13:40.993: IPSLA-OPER_TRACE:OPER:100 No connection
Jul 2 08:13:40.993: IPSLA-INFRA_TRACE:OPER:100 Updating result

Checked the ports and found I am using different ones on each VoIP gateway. I just added a new operation with a totally unique port that I know is not in use on the source or destination and it still failed:
voipgw02(config)#ip sla 4033
voipgw02(config-ip-sla)# udp-jitter 10.205.50.5 17333 source-ip 10.225.50.5 codec g711ulaw codec-numpackets 100
voipgw02(config-ip-sla-jitter)# tos 184
voipgw02(config-ip-sla-jitter)# timeout 18000
voipgw02(config-ip-sla-jitter)# threshold 1000
voipgw02(config-ip-sla-jitter)# frequency 30
voipgw02(config-ip-sla-jitter)#ip sla schedule 4033 life forever start-time now ageout 3600
voipgw02#sh ip sla stat
IPSLAs Latest Operation Statistics
IPSLA operation id: 4033
Type of operation: udp-jitter
        Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 21:47:43 EDT Mon Sep 3 2012
Latest operation return code: No connection
RTT Values:
        Number Of RTT: 0                RTT Min/Avg/Max: 0/0/0 milliseconds
Latency one-way time:
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Jitter Time:
        Number of SD Jitter Samples: 0
        Number of DS Jitter Samples: 0
        Source to Destination Jitter Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Jitter Min/Avg/Max: 0/0/0 milliseconds
Packet Loss Values:
        Loss Source to Destination: 0
        Source to Destination Loss Periods Number: 0
        Source to Destination Loss Period Length Min/Max: 0/0
        Source to Destination Inter Loss Period Length Min/Max: 0/0
        Loss Destination to Source: 0
        Destination to Source Loss Periods Number: 0
        Destination to Source Loss Period Length Min/Max: 0/0
        Destination to Source Inter Loss Period Length Min/Max: 0/0
        Out Of Sequence: 0      Tail Drop: 0
        Packet Late Arrival: 0 Packet Skipped: 0
Voice Score Values:
        Calculated Planning Impairment Factor (ICPIF): 0
        Mean Opinion Score (MOS): 0
Number of successes: 0
Number of failures: 1
Operation time to live: Forever
Do you know if there are any licensing issues?
barvoipgw02#show ip sla appl
        IP Service Level Agreements
Version: Round Trip Time MIB 2.2.0, Infrastructure Engine-III
Supported Operation Types:
        icmpEcho, path-echo, path-jitter, udpEcho, tcpConnect, http
        dns, udpJitter, dhcp, ftp, VoIP, rtp, icmpJitter
        802.1agEcho VLAN, Port, 802.1agJitter VLAN, Port, udpApp
        wspApp
Supported Features:
        IPSLAs Event Publisher
IP SLAs low memory water mark: 63126085
Estimated system max number of entries: 46234
Estimated number of configurable operations: 39313
Number of Entries configured : 3
Number of active Entries      : 3
Number of pending Entries     : 0
Number of inactive Entries    : 0
Time of last change in whole IP SLAs: .21:47:43.954 EDT Mon Sep 3 2012

Similar Messages

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:

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

Quality of Service and Jitter issues

I am having poor quality of service (36%) and Jitter issues (36ms). I called Verizon Fios technical support and was told that my connection is fine and that it must be a vendor issue. Only vendor I'm having an issue with is Verizon. If I can't get someone from Verizon that knows what QoS and Jitter is on the phone to help me troubleshoot this issue I'm going to have to cancel my service and find a provider that has someone technical providing tech support.

Upstream jitter
35.7 ms
Downstream jitter
6.0 ms
Upstream packet loss
0.8 %
Downstream packet loss
0.0 %
Upstream packet order
100.0 %
Downstream packet order
100.0 %
Packet discards
5.1 %
MOS
3.4

IP SLA Request size (ARR data portion) UDP Jitter

Looking through the documentation for ip sla udp jitter, Cisco says these are the default values -
"By default, ten packet frames (N), each with a payload size of 10 bytes (S), are generated every 10 ms (T), and the operation is repeated every 60 seconds (F)."
however, looking at sh ip sla configuration on my router I get different values -
ip sla 1001
udp-jitter 2.2.2.2 20000 source-ip 1.1.1.1
ip sla schedule 1001 life 3000 start-time now
sh ip sla configuration
Entry number: 1001
Owner:
Tag:
Operation timeout (milliseconds): 5000
Type of operation to perform: udp-jitter
Target address/Source address: 1.1.1.1/2.2.2.2
Target port/Source port: 20000/0
Type Of Service parameter: 0x0
Request size (ARR data portion): 32
Packet Interval (milliseconds)/Number of packets: 20/10
This is confusing to me. According to this, the operation is sending 10 frames, at 32 bytes each with 20 ms between frames. Is this correct? Or are these default parameters for UDP Jitter? If so, this definitely does not match up with the data presented on cisco.com
thanks,
Alex

Hi Alex ,
for UDP-jitter , Request Data size is :32( By Default) ,however you can change it .
NMS-6500(config-ip-sla-jitter)#request-data-size ?
<16-1500> Number of bytes in payload
for ICMP ECHO ,
Request Data size is :28 ( By Default)
Thanks-
Afroz
[Do rate the useful post]

IP-sla udp-jitter / one-way delay no output

Hi *,
i have a question regarding "ip sla udp-jitter".
On some connectins i get an output for the "show ip sla stat" for the _one-way delay_
on other links i don't get an output. The Configuration is always the same and the Probes are running.
NTP is configured but in my opinion the fact weather i get output for the _one-way delay_
or not depends on the ntp root despersion.
Is there a max allowed time differances between the two routes ?
Here one working / one not working output of the same Router but different peers:
Not working::
Latest operation return code: OK
RTT Values:
Number Of RTT: 100RTT Min/Avg/Max: 11/11/13 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 0
Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Working:
Latest operation return code: OK
RTT Values:
Number Of RTT: 100RTT Min/Avg/Max: 12/13/14 milliseconds
Latency one-way time:
Number of Latency one-way Samples: 100
Source to Destination Latency one way Min/Avg/Max: 6/7/8 milliseconds
Destination to Source Latency one way Min/Avg/Max: 5/6/7 milliseconds
I hope one of you can help me to find / fix the problem,
Thanks in advance / Emanuel

Hi everyone,
I have the same doubt.
I did a ip sla configuration on 1841 and 7206VXR and don't show nothing in one-way delay.
----------------------7206---------------------
-ip sla monitor responder
-ip sla monitor 1
- type jitter dest-ipaddr 10.9.105.14 dest-port 16384 source-ipaddr 10.8.20.102 codec g711alaw
- tos 184
-ip sla monitor schedule 1 start-time now
-ntp peer 10.9.105.14
HOST)#show ip sla sta
Round Trip Time (RTT) for       Index 1
        Latest RTT: 507 milliseconds
Latest operation start time: 10:57:36.619 UTC Sun Oct 10 2010
Latest operation return code: OK
RTT Values:
        Number Of RTT: 1000             RTT Min/Avg/Max: 125/507/846 milliseconds
Latency one-way time:
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0 milliseconds
        Destination to Source Latency one way Min/Avg/Max: 0/0/0 milliseconds
Jitter Time:
        Number of Jitter Samples: 999
        Source to Destination Jitter Min/Avg/Max: 1/1/6 milliseconds
        Destination to Source Jitter Min/Avg/Max: 1/5/23 milliseconds
Packet Loss Values:
        Loss Source to Destination: 0           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
Voice Score Values:
        Calculated Planning Impairment Factor (ICPIF): 17
        Mean Opinion Score (MOS): 3.84
Number of successes: 38
Number of failures: 0
Operation time to live: 1347 sec
-------------------------1841-------------------------------
-ip sla monitor responder
-ip sla monitor 1
- type jitter dest-ipaddr 10.8.20.102 dest-port 16384 source-ipaddr 10.9.105.14 codec g711alaw
- tos 184
-ip sla monitor schedule 1 start-time now
-ntp peer 10.8.20.102
3383)#show ip sla monitor statistic
Round trip time (RTT)   Index 1
        Latest RTT: 614 ms
Latest operation start time: 10:50:50.491 UTC Wed Oct 27 2010
Latest operation return code: OK
RTT Values
        Number Of RTT: 999
        RTT Min/Avg/Max: 347/614/867 ms
Latency one-way time milliseconds
        Number of one-way Samples: 0
        Source to Destination one way Min/Avg/Max: 0/0/0 ms
        Destination to Source one way Min/Avg/Max: 0/0/0 ms
Jitter time milliseconds
        Number of SD Jitter Samples: 997
        Number of DS Jitter Samples: 998
        Source to Destination Jitter Min/Avg/Max: 0/6/19 ms
        Destination to Source Jitter Min/Avg/Max: 0/1/3 ms
Packet Loss Values
        Loss Source to Destination: 1           Loss Destination to Source: 0
        Out Of Sequence: 0      Tail Drop: 0    Packet Late Arrival: 0
Voice Score Values
        Calculated Planning Impairment Factor (ICPIF): 20
MOS score: 3.72
Number of successes: 32
Number of failures: 0
Operation time to live: 1668 sec

Latency and Jitter issue

I am facing Latency and Jitter issue on few sites. What is the best way to test those hop by hop between two sites?

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
If your equipment supports, IP SLA can create an artificial VoIP call flow and it can measure latency and jitter.
Traceroute can be use to obtain (rough) hop-by-hop latencies values.

MSI R9 270X Gaming 2G has the flicker/jitter issue. Does the BIOS update work?

Hey all, my internet research led me here for the flicker/jitter issue as seen in this Youtube video. The video isn't mine, but my issue is similar but worse as the screen with completely black out for a second.
It mostly happens when web browsing, but once in a while it'll happen while gaming. Strangely, it only happens on my primary display, not on my secondary display.
My serial number (minus the last three digits) is: 602-V303-07SB1312029XXX
I can't seem to find if the BIOS flash helped anyone or not, I'm assuming it has though because I haven't read any reports of people looking for more help after the flash.
So here are my questions:
Which vBIOS do I need and where can I find it?
My card has the BIOS switch, which position should it be on for the flash?
Lastly, whats the best method to flash the new BIOS?
Thank you for your time.

You can try flash to the latest UEFI vbios TV303MH.1A0...
This vbios is for all V303-07S card.
the flash method also wrote in this thread.
https://forum-en.msi.com/index.php?topic=182256.msg1309322#msg1309322
Edit: I just check the vBIOS switch, the other vbios should be UEFI already, try switch to the other vbios, and see if the flicker/jitter issue happen?
http://event.msi.com/2014/vga/Hybrid_BIOS/

WRT54GC v2.0 - UDP Traffic issue

Hi, i've bought last week the wireless router WRT54GC v2.0 and it works good for normal navigation, port forwarding, wireless signal, ecc...
I've only a problem, a big problem, it can't handle high UDP traffic, this issue can be experienced, e.g. with Kad network of eMule. I can connect to Kad and i'm not firewalled, but if i try to search something, the search results are always empty or almost empty. If i made the same search connecting with my ISP router it works fine.
I tried with both wireless and wired connection from WRT54GC and the result is the same, so it's not a wireless problem. I tried to disable firewall, playing with settings, using DMZ o port triggering. The result was the same. I've updated the firmware to version 1.01.0 too.
Is there a solution for this problem??
Sorry for my english
Message Edited by RedKite on 08-31-2008 02:39 AM

I am not sure about the workwround ... however you can try filtering the UDP packets that are incoming .....

IPSLA-ICMP Jitter-Packet loss count

Hi,
I wanted to monitor the packet loss in my link using IP SLA. So i configured ipsla jitter and started monitoring it. When i analyze the output i found that ip sla statictics shows heavy drop in my link, but when i ping from the router no drop is observed. Why there is such difference in the out put. I read that normal ping and icmp jitter uses different icmp types messages but now i am confused whether my link proper or not. Which data i should belive.
Here is my config and statistics:
ip sla 2166
icmp-jitter 10.70.194.137 num-packets 100
frequency 300
ip sla schedule 2166 life forever start-time now
Type of operation:              icmpJitter
        Latest RTT: 7 milliseconds
Latest operation start time: 13:56:49.468 IST Sat Dec 24 2011
Latest operation return code: OK
RTT Values:
        Number Of RTT: 92               RTT Min/Avg/Max: 3/7/158
Latency one-way time:
        Number of Latency one-way Samples: 0
        Source to Destination Latency one way Min/Avg/Max: 0/0/0
        Destination to Source Latency one way Min/Avg/Max: 0/0/0
Jitter Time:
        Number of Jitter Samples: 89
        Source to Destination Jitter Min/Avg/Max: 1/4/20
        Destination to Source Jitter Min/Avg/Max: 1/1/1
Packet Late Arrival: 0
Out Of Sequence: 0
        Source to Destination: 0        Destination to Source 0
        In both Directions: 0
Packet Skipped: 0
Packet Loss: 8
        Loss Period Length Min/Max: 1/7
Number of successes: 1
Number of failures: 0
Operation time to live: Forever

Hello mate !
For how long you left the IP sla running ? 24 hours ?
I would disable session time out in your router, set the IP Sla running for 60 minutes for example and in the meantime i would leave a ping running too with high repetition in the background.
I saw you only had 8 pkt loss....   we need two "tools" running for a good comparison, tried what i proposed and let me know.
cheers

IPSLA (Testing Jitter/Delay/Frame-Relay)

hey guys, testing my network using IPSLA but its strange how when i connect a router to the network and input the IPSLA commands it says it fails everytime? Im a student doing my project btw and am unsure why its not sending through the network. I have connectivity and can ping across the entire network. the commands i used were -
ip sla monitor 12
type jitter dest-ipaddr
192.168.0.10 dest-port 5060
frequency 300
exit
ip sla monitor schedule 12 start-time now live forever
then when i use the statistics command to show the output it says failed :S am i missing a step somewhere, or do i have to advertise the router in my network? im very confused :/

Could you include the config for the IP SLA receiver as well if you have it configured?
Excellent reading on the topic: http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/ipsla/configuration/15-mt/sla-15-mt-book/sla_udp_jitter.html

EEM Applet Using IPSLA ED

After reading the docs on the IPSLA ED, I decided to write the following applet just to see if I understand how to use it.
ip sla responder
ip sla enable reaction-alerts
ip sla 1
udp-jitter 210.210.210.1 16384 num-packets 100 interval 20
request-data-size 172
tos 176
ip sla schedule 1 start-time now life forever
ip sla reaction-configuration 1 react jitterDSAvg threshold-value 35 30 threshold-type consecutive 3
ip sla reaction-configuration 1 react jitterSDAvg threshold-value 35 30 threshold-type consecutive 3
ip sla reaction-configuration 1 react rtt threshold-value 225 200 threshold-type consecutive 3
ip sla reaction-configuration 1 react packetLossSD threshold-value 2 1 threshold-type consecutive 3
ip sla reaction-configuration 1 react packetLossDS threshold-value 2 1 threshold-type consecutive 3
event manager applet VoIP-Test-Alert
description "Send syslog msg if rrt delay > 225 or jitter > 35 ms or packet loss > 2%”
event tag e1 ipsla operation-id 1 reaction-type jitterDSAvg
event tag e2 ipsla operation-id 1 reaction-type jitterSDAvg
event tag e3 ipsla operation-id 1 reaction-type rtt
event tag e4 ipsla operation-id 1 reaction-type packetLossSD
event tag e5 ipsla operation-id 1 reaction-type packetLossDS
trigger occurs 1 period 360
correlate event e1 or event e2 or event e3 or event e4 or event e5
action 1.0 if $_ipsla_measured_threshold_value gt $_ipsla_threshold_rising
action 2.0 syslog priority notification msg "$_ipsla_react_type = $_ipsla_measured_threshold_value is over threshold $_ipsla_threshold_rising to destination $_ipsla_dest_ip_addr”
action 3.0 end
Seems to work but I cannot figure whether using applets if it is possible to expend this by having another applet realize that all my reactions for IP SLA 1 are under their falling theshold and thus issue a syslog message that all is A-OK.
thx in advance for any suggestions.

Thank you. That would do it for that but now I have another issue.
I want to expand my applet so only one applet would be all that is needed to alert for ip sla tests to multiple targets so I tried yesterday to expand my applet to somethink like the following:
event manager applet VoIP-Test-Alert
description "Send syslog msg if rrt delay > 225 or jitter > 35 ms or packet loss > 2%”
event tag e1 ipsla group-name 1 reaction-type jitterDSAvg
event tag e2 ipsla group-name 1 reaction-type jitterSDAvg
event tag e3 ipsla group-name 1 reaction-type rtt
event tag e4 ipsla group-name 1 reaction-type packetLossSD
event tag e5 ipsla group-name 1 reaction-type packetLossDS
trigger occurs 1 period 360
correlate event e1 or event e2 or event e3 or event e4 or event e5
I then used the ip sla schedule command to put ip sla operation-id 1 into schedule group id 1. But when I tested, I got the Ip SLA threshold exceeded syslog messages but my applet failed to trigger.
I am not understading something here in regards to IP SLA ED use of group-name. In IP SLA schedule group ids are integers while in the applet group-name are strings. Thus I suspect I am not correctly creating the ip sla group correctly.
Thanks in advance again for any help.

Cisco LMS Prime: No IPSLA Statistics in Device Center

Hello,
i set up a shadow IPSLA router to measure UDP jitter in our network, which is working fine. I'd like to ask why the statistics are not showing up in the Device Center Performace details.
I configured also a SNMP poller to poll the collector information from the RTTMON mib.
thanks
alex

Yes I did get that issue resolved with the Help of TAC. They said that I was hitting a particular bug: CSCtc21648
No idea if you are hitting the same bug or not but here is the information that I was given.
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtc21648
Bug Details
RME links and info missing from Device Center after upgrade
Symptom:
The Resource Manager Essentials tasks and reports are missing from the Device Center. Additionally, all RME-related device information is also omitted.
Conditions:
This occurs after applying the RME 4.3.1 EnergyWise service pack.
Workaround:
A workaround is available by contacting the TAC

SLA ICMP-Jitter Operation problems

I'm trying to guage network performance using the UDP-jitter and ICMP-jitter operations for a specific network segment. We have a voice encoders that stream the audio over IP using UDP across the network. The issue we are experiencing is out-of-sequence packets; these packets show up as artefacts on the receiving end audio output. I understand that UDP is a connectionless protocol that doesn't provide any mechanism for sequencing. This is where teh SLA monitors come in.
I'm seeing statistics across the monitors that are inconsistent with each other. They aren't off just a little from each other; they are off quite a bit. The UDP-jitter operation (40006) isn't reporting any out-of-sequence packets (I can only see the last two hours, so I just changed the history to 24 hours). Operations 40001 and 40002 (ICMP-jitter) seem to report no packets as out-of-sequence or all packets as out-of-sequence. Operation 40002 is reporting around 50% packet loss. This is a false report. Operation 40006 is reporting 0% packet loss and the CODECs would be unusable if this were the case. Operations 50001 and 50002 were just configured so I don't have much history on them. Operation 50001 seems to be running clean, but 50002 has a lot of unprocessed packets.
You may have noticed that the operations that traverse the satellite link have a TOS of 172 (DSCP 43). This is done to ensure the the SLA monitor doesn't step on the CODEC traffic (DSCP EF, which is assigned to the LLQ). That's not to say that the traffic isn't prioritized; it is guaranteed bandwidth across the link. Also, there is no congestion on the network. I have also checked QoS policy-maps and there are no drops for the assoiciated queues. The circuits are up and stable. One circuit is a little dirty, but it the error rate is pretty low 0.003%.
So, my question is two part:
1. Why am I recieving out-of-sequence packets?
2. Has anyone else had this problem or a similar problem with the ICMP-jitter operation?
I have included a basic diagram and the statistics I have been able to collect thus far.

Hi Jorge
According to Cisco documentation icmp-jitter should work on any IP Device.
I have a similar issue.
1. I can run icmp-jitter successfully to non cisco routers
2. it fails to run to a generic ip device.
Imran

Ipsla ipm

Hello,
I try to make a collector in Ciscoworks IPM and i always get the same error.
I choose source and target devices, operation (udp jitter) and i can't
go further.. i always get the same error:
it says:
Only Responder - enabled devices permitted for selected operation(s)
. Please enable IPSLA responder for the selected Target device and then click Update IPSLA Config button on the Device Management page.
Do i need to enable something on each devices before configuring collectors ?
both switches are at ios 12.2(44)
thanks for your help

You need to connect to your desired target device(s), and configure:
ip sla responder
Or, for older code:
ip sla monitor responder
Or, for even older code:
rtr responder
Depending on your version of IPM, you may then need to delete this device from IPM, and resync it. The latest version of IPM will let you resync with the device to learn that the responder is enabled.

Motion blur issue once exported to DVD through Encore

I have 59.94 HD footage. I edit it, export it through Adobe Media Encoder to Mpeg-2 DVD at 29.97, drop-frame, lower field dominance. I then import that .m2v file into Encore, and then export to DVD, without re-transcoding or encoding anything. The DVD plays back with a 24p-like jitter, or blur to it. I do not understand this. After encoding the .m2v file, I went back and played that on windows media player, and other media players, and the video played back as it should originally, very smooth. Why is it that in between creating the .m2v and exporting the DVD in Encore, I am getting this 24p-like blur/jitter to the video? Does it matter that some of these videos I am putting to DVD-DL and are quite large? Hope someone can help. Thanks. Any other info needed, I will supply for you.

Matrox, velocity and anyother hardware based NLEs use a 720 x 486 timeline. I've exported countless SD files through AME and the m2v files played fine through a Windows media and VLC, They also imported and burned to DVD with Encore flawlessly. SD is not the issue at all.
The problem is as stated in the original posting is.
I export the HD timeline(59.94) through AME as a MPEG2-DVD (29.97 Lower field) and the file plays fine in the WIndows Media Player and VLC. No jitter. Perfect
It's when I put the m2v encoded from a HD (720 x 1280 59,94 frame rate as a MPEG2-DVD in AME ) in encore ( do not transcode ) and then burn to a DL DVD. When the DVD is played back, the jitter issue arises.

IPSLA UDP-Jitter Issues

Similar Messages

Maybe you are looking for