IP SLA icmp jitter operation

Hello
I would like to track icmp jitter for end host. I verified in documentation that it can be any host as a destination. But i got error on this operation:
Latest RTT: NoConnection/Busy/Timeout
I verified that there is no firewall between the source and destination and icmp timestamp request works when done manually:
r01#ping
Protocol [ip]:
Target IP address: 10.23.33.6
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]: y
Source address or interface:
Type of service [0]:
Set DF bit in IP header? [no]:
Validate reply data? [no]:
Data pattern [0xABCD]:
Loose, Strict, Record, Timestamp, Verbose[none]: Timestamp
Number of timestamps [ 9 ]:
Loose, Strict, Record, Timestamp, Verbose[TV]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.23.33.6, timeout is 2 seconds:
Packet has IP options: Total option bytes= 40, padded length=40
Timestamp: Type 0. Overflows: 0 length 40, ptr 5
>>Current pointer<<
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Time= 01:00:00.000 CET (00000000)
Reply to request 0 (4 ms). Received packet has no options
Reply to request 1 (4 ms). Received packet has no options
Reply to request 2 (1 ms). Received packet has no options
Reply to request 3 (1 ms). Received packet has no options
Reply to request 4 (1 ms). Received packet has no options
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
r01#sh ip sla statistics 196
IPSLAs Latest Operation Statistics
IPSLA operation id: 196
Type of operation: icmp-jitter
Latest RTT: NoConnection/Busy/Timeout
Latest operation start time: 12:45:21.019 CET Fri Nov 21 2014
Latest operation return code: Timeout
RTT Values:
Number Of RTT: 0 RTT Min/Avg/Max: 0/0/0
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 SD Jitter Samples: 0
Number of DS Jitter Samples: 0
Source to Destination Jitter Min/Avg/Max: 0/0/0
Destination to Source Jitter Min/Avg/Max: 0/0/0
Packet Late Arrival: 0
Out Of Sequence: 0
Source to Destination: 0 Destination to Source 0
In both Directions: 0
Packet Skipped: 0 Packet Unprocessed: 0
Packet Loss: 0
Loss Period Length Min/Max: 0/0
Number of successes: 0
Number of failures: 34
ip sla 197
icmp-jitter 10.23.33.6
frequency 30
ip sla schedule 197 life forever start-time now
Nov 21 12:57:43: IP SLAs(197) Scheduler: saaSchedulerEventWakeup
Nov 21 12:57:43: IP SLAs(197) Scheduler: Starting an operation
Nov 21 12:57:43: IP SLAs(197) icmpjitter operation: Starting icmpjitter operation
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) Scheduler: Updating result
Nov 21 12:57:49: IP SLAs(197) Scheduler: start wakeup timer, delay = 24796
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Nov 21 12:57:49: IP SLAs(197) icmpjitter operation: Timeout
Any help would be appreciated.

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

Similar Messages

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

IP SLA ICMP Path Jitter - Strange results

Hi all,
I'm an intern in a network company, in France. I'm working on the IP SLAs fonctions of Cisco IOS.
I've got some equipments to make some tests :
I've configured the ICMP Path Jitter operation on R1 (a 2800 router), which has the IOS Software C2800NM-ADVIPSERVICESK9-M, 15.1(1)T (fc1) :
ip sla 2
path-jitter 192.168.2.2 source-ip 192.168.1.254
tag ICMP JITTER R1-PC2
frequency 30
ip sla schedule 2 life 150 start-time now
Then, i use a software called PCATTCP to send UDP datagrams from PC2 to PC1. When PC2 send UDP at 2Mb/s or more, the results look like :
IPSLA operation id: 2
       Latest RTT: 319 milliseconds
Latest operation start time: 16:08:11.458 GMT+1 Thu Mar 22 2012
Latest operation return code: OK
---- Path Jitter Statistics ----
Hop IP 10.0.0.2:
Round Trip Time milliseconds:
       Latest RTT: 326 ms
       Number of RTT: 10
       RTT Min/Avg/Max: 319/294/333 ms
Jitter time milliseconds:
       Number of jitter: 7
       Jitter Min/Avg/Max: 2/5/9 ms
Packet Values:
       Packet Loss (Timeouts): 0
       Out of Sequence: 1
       Discarded Samples: 1
Hop IP 192.168.2.2:
Round Trip Time milliseconds:
       Latest RTT: 319 ms
       Number of RTT: 10
       RTT Min/Avg/Max: 315/255/322 ms
Jitter time milliseconds:
       Number of jitter: 5
       Jitter Min/Avg/Max: 3/4/7 ms
Packet Values:
       Packet Loss (Timeouts): 0
       Out of Sequence: 2
       Discarded Samples: 2
Operation time to live: 134 sec
How is it possible to get a minimum value greater than the average ??? I don't understand :/
Thanks.
Regis

Thanks for your answers, I'll try to change the IOS.
I noticed that the problem happens only when there are Out of Sequence packets (ICMP reply not received).
I've done again the tests, and and captured the packets with Wireshark between the two routers. I calculated the average with the values in Wireshark by adding 0 for each Out of Sequence packet, then dividing by the Number of RTT. And I got the average value displayed.
*** For example ***
10 ICMP requests are send.
9 received (ms) : 337; 334; 328; 337; 334; 328; 323; 333; 327. [values obtained with Wireshark]
--> The IP SLA results are :
Round Trip Time milliseconds:
     Number of RTT: 10
     RTT Min/Avg/Max: 324/298/338 ms
Packet Values:
     Packet Loss (Timeouts): 0
     Out of Sequence: 1
     Discarded Samples: 1
Then, let's calculate the average value :
Avg = (337+334+328+337+334+328+323+333+327+0)/10 = 298.1
And that works every time.
Regis

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

Icmp Jitter collector configuration with Cisco LMS

Hi,
I am trying to collect jitter information of cisco Routers which are added in Cisco LMS
I have configured collector icmp jitter for them but somehow no stats are visible in lms and its says in IPM that u have no jitter collectors configured.
Do i need to enable anything on the Router as well to export stats to LMS ?
Thanks

Hi,
show ip sla application
IP Service Level Agreements
Version: Round Trip Time MIB 2.2.0, Infrastructure Engine-II
Time of last change in whole IP SLAs: *07:35:21.730 UTC Thu Mar 13 2014
Estimated system max number of entries: 27977
Estimated number of configurable operations: 27976
Number of Entries configured : 1
Number of active Entries : 1
Number of pending Entries : 0
Number of inactive Entries : 0
Supported Operation Types
Type of Operation to Perform: dhcp
Type of Operation to Perform: dns
Type of Operation to Perform: echo
Type of Operation to Perform: frameRelay
Type of Operation to Perform: ftp
Type of Operation to Perform: http
Type of Operation to Perform: icmpJitter
Type of Operation to Perform: jitter
Type of Operation to Perform: pathEcho
Type of Operation to Perform: pathJitter
Type of Operation to Perform: slm controller
Type of Operation to Perform: slm frame-relay interface
Type of Operation to Perform: slm frame-relay pvc
Type of Operation to Perform: slm interface
Type of Operation to Perform: tcpConnect
Type of Operation to Perform: udpEcho
Type of Operation to Perform: voip
IP SLAs low memory water mark: 38288719
The device is a Cisco 1841

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

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

IPM and config failed status for ICMP jitter collectors.

Hello at all.
We are using IPM 4.2 to configure the collectors on a 7201. We made an upgrade to software 15.0 to solve bug CSCte85239. Then to make the Admin Tag more readable, we have exported all collectors, edited, and then imported. For all ICMP jitter collectors we have received a config failed status. Config failed when we try to add collector using GUI. We are able to manually configure collector. We have already deleted and added the device from IPM.
Any ideas?
Thanks.
Regards.
Andrea

Router sends an inconsistent value error into get-response message: error should be in the PktDataRequestSize.
This variabile cannot be modified using GUI.
Any ideas?
Regards.
Andrea

Ip sla tcp-connect operation mission vrf option

Hi,
Is there any IOS/platform to support IP SLA tcp-connect measure with VRF option?
I tried with ASR1k 12.2(33)XNF1 (IP SLAs, Infrastructure Engine-II) and Cat3560, Cat3750 no success. I use IPM 4.2.1 and/or CLI.
Thanks,
Balazs.

Yes to all of the echo operations. No to jitter. The device can only do UDP Jitter and Path Jitter. You would see icmpJitter if this was supported. Yes to the other operations (i.e. DNS, DHCP, etc.).

There's no SNMP record (on rttMonStatsCollectTable) for IP SLA DNS, FTP operation on IOS 15.3 and above

Hi,
I try to collect data of an IPSLA probe through SNMP on a Cisco 1900 with IOS 155.1T , when I create a DNS and FTP probes and run those probes, I look at rttMonStatsCollectTable (.1.3.6.1.4.1.9.9.42.1.3.2) to get the result as I did before on IOS 12, but there's no record for DNS nor FTP.
The other probe (TCP, UDP ...) has statistic records here, but not for DNS, FTP.
Could you help to show me where to get the result of DNS, FTP probe (number of disconection, timeout, no connection ...) or this is a bug?
Thanks

To get the MOS score i'm using this:
1.3.6.1.4.1.9.9.42.numberoftheoperation and then you must divide it by 100
"ip sla monitor 1" the operation number is 1

IP SLA SNMP TRAP.

Hello.
I'm using CiscoWorks IPM to configure SLA operation and reaction.
I'm receiving SNMP trap but I need to add the Admin Tag ID to the values also.
With actual configuration the tag is provided as an instance.
Many thanks.
Regards.
Andrea

Hi Joseph.
Another issue with IPM now!
Importing collectors from file (icmp-jitter operations): it creates collectors successfully but all with config failed status.
If I define one collector manually, on 7201 with 15.0, all run ok.
I can successfully import other collectors with echo operation.
Ideas?
Thanks.
Regards.
Andrea

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]

Extremely high jitter in SLA

Hello,
We recently switched to a T1 connection for a remote site, all of a sudden the Jitter Time in our IP SLA jumped to as high as 77 million (from 1 or 2... not million, just one or two). Does anything look wrong? Here's the config & stat output:
ip sla 10
icmp-jitter 10.xx.xx.xx num-packets 20 interval 40
frequency 600
ip sla schedule 10 life forever start-time now
Round Trip Time (RTT) for       Index 10
Type of operation:              icmpJitter
        Latest RTT: 8 milliseconds
Latest operation start time: *22:36:54.404 UTC Thu Dec 9 2010
Latest operation return code: Over threshold
RTT Values:
        Number Of RTT: 20               RTT Min/Avg/Max: 8/8/11
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: 19
        Source to Destination Jitter Min/Avg/Max: 77815000/77815000/77815000
        Destination to Source Jitter Min/Avg/Max: 77815000/77815000/77815001
Packet Late Arrival: 0
Out Of Sequence: 0
        Source to Destination: 0        Destination to Source 0
        In both Directions: 10
Packet Skipped: 0
Packet Loss: 0
        Loss Period Length Min/Max: 0/0
Number of successes: 0
Number of failures: 1
Operation time to live: Forever
Thank you for any input!
James

Version 12.3(8r)YH12 (model 1811 remote site), Version 12.4(13r)T11 (model 3825, primary router). There are two IP SLAs configured. The second one (IP SLA 20) is normal. Here's the statistics for the second one to compare. The funny part is the route to the IP address in the IP SLA 20 goes through the first IP address (primary router) in IP SLA 10.
Round Trip Time (RTT) for       Index 20
Type of operation:              icmpJitter
        Latest RTT: 19 milliseconds
Latest operation start time: 13:52:25.339 UTC Mon Dec 13 2010
Latest operation return code: OK
RTT Values:
        Number Of RTT: 20               RTT Min/Avg/Max: 19/19/31
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: 19
        Source to Destination Jitter Min/Avg/Max: 0/0/0
        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 1
        In both Directions: 0
Packet Skipped: 0
Packet Loss: 0
        Loss Period Length Min/Max: 0/0
Number of successes: 3
Number of failures: 0
Operation time to live: Forever
The routers' times are not set with NTP. They are set manually, the remote site was about a few minutes off (compared to the primary router). I've manually set it to within 1 second time now. But that didn't fix the issue.
Any other settings that could affect this?
Thanks again for the help!
James

WAAS and IP SLA operation

we are currently using the IP SLA udp jitter measurement to monitor our voice paths accross the WAN. If we implement a partial WAAS across the same WAN the voice traffic will be acellerated but not the IP SLA jitter measurement. Does this mean that when WAAS is implemented IP SLA is limited in its use?

Hi Steve,
The answer to your question depends on 1) how you deploy WAAS and 2) how you use IP SLA. If you deploy WAAS using WCCP for interception, UDP traffic will never be intercepted. If the WAAS device is deployed inline, all traffic flows through the WAAS device, so an IP SLA probe using UDP will be subject to WAAS pass-through handling behavior.
What are you trying to measure with regards to WAAS?
Zach

I want to use RTTMON MIBS for ICMP Latency

Hi,
I am using The Cisco 2811 Routers for Branch Officies and that use "ip sla" and EEM configuration for monitoring.
I find OID match Name and Stirng list.
is The following configuration true?
What can I use digit instead of rttMonLatestJitterOperOWMaxSD?
ip sla monitor 111
type echo protocol ipIcmpEcho x.x.x.x source-ipaddr y.y.y.y
request-data-size 1500
frequency 30
ip sla monitor schedule 111 life forever start-time now
event manager applet blabla
event snmp oid rttMonLatestJitterOperOWMaxSD.111 get-type exact entry-op eq entry-val 1 exit-op eq exit-val 2 poll-interval 5
action 1.0 syslog priority critical msg "BlaBla"
action 1.1 snmp-trap strdata "EEM detected BlaBla Latency"

You will need to use a jitter operation to be able to use this object. Right now you're just doing an ICMP echo. For that, you could monitor rttMonLatestRttOperSense (1.3.6.1.4.1.9.9.42.1.2.10.1.2.111). If the value is something other than 1, then an error occurred (e.g. the round-trip response time was over the threshold, a timeout occurred, etc.).

IP SLA icmp jitter operation

Similar Messages

Maybe you are looking for