How I can configure ip sla and jitter

[webstd.design]

I want to monitor some IP Phones by Jitter parameter. Can I do this by ip sla? If yes, could some body provide me some useful configs?

thank you a lot!

[Joe Clarke]

IP SLA is not available in IP phones. In order to use the IP SLA jitter operation, you need to have an IOS source device, and an IOS responder (target) device. The source will send jitter probes to the responder, and the responder will send acknowledgment data back to the source. This document should help you configure it on your IOS source device:

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

That said, assuming your router is running 12.4(6)T or higher, you can use the new ICMP jitter feature. This feature does not require the IP SLA responder, so an IP phone could be your target device. However, it will not provide the same voice-like simulation that the UDP jitter operation does. More on ICMP jitter can be found at:

http://www.cisco.com/en/US/docs/ios/12_4t/12_4t11/hticmpjt.html

[Lucien Avramov]

On the router/switching side you can not measure the jitter on the phone themselves, however you can measure the VOIP jitter between routers / switches.

White paper:

http://www.cisco.com/en/US/technologies/tk648/tk362/tk920/technologies_white_paper0900aecd801752ec.html

Config guide:

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

[webstd.design]

I didn't understand one thing.

There is configuration of IP SLA but I didn't find how I can monitor/collect statistcs information without access on router

[Lucien Avramov]

On the source router, you can issue the show ip sla statistics and see the results.

Command reference:

http://www.cisco.com/en/US/docs/ios/ipsla/command/reference/sla_04.html

Also you can have the router to send for example snmp traps with the RTTMON mib to a server.

[Joe Clarke]

You can use SNMP and the CISCO-RTTMON-MIB to monitor IP SLA collectors without logging in directly to the source device. The MIB can be quite daunting, though, so there are a few tools available which make use of it. Cisco makes Internetwork Performance Monitor (IPM) which is part of the LAN Management Solution Suite (http://www.cisco.com/go/lms/ ). You can download a 90-day eval from that link. IPM allows for both configuring and monitoring of IP SLA collectors.

SolarWinds has a free IP SLA monitor (http://www.solarwinds.com/products/freetools/ip_sla_monitor/).

There are also Open Source alternatives as well. One such alternative is Smoke Ping (http://oss.oetiker.ch/smokeping/) which is very extensible, and can do other SNMP monitoring in addition to IP SLA.

[webstd.design]

I think I did something wrong:

ip sla 1

udp-jitter 10.10.10.10 2000

owner admin

frequency 30

history enhanced interval 900 buckets 100

ip sla schedule 1 life forever start-time now

R0#sh ip sla statistics

Round Trip Time (RTT) for Index 10

Latest RTT: NoConnection/Busy/Timeout

Latest operation start time: *00:24:48.487 UTC Fri Mar 1 2002

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 Loss Destination to Source: 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

debug ip sla

*Mar 1 00:28:23.487: IP SLAs(10) CtrlMsg: Timeout

*Mar 1 00:28:23.487: IP SLAs(10) CtrlMsg: Sending msg, ver=1, id=23, len=52, cmd=4, ip=10.10.10.11, port=16384, duration=25000ms

R0#

*Mar 1 00:28:28.499: IP SLAs(10) CtrlMsg: Timeout

*Mar 1 00:28:28.499: IP SLAs(10) CtrlMsg: Sending msg, ver=1, id=24, len=52, cmd=4, ip=10.10.10.11, port=16384, duration=25000ms

R0#

*Mar 1 00:28:33.515: IP SLAs(10) CtrlMsg: Timeout

*Mar 1 00:28:33.515: IP SLAs(10) CtrlMsg: No connection

*Mar 1 00:28:33.515: IP SLAs hash remove: 10.10.10.10 61414

*Mar 1 00:28:33.519: IP SLAs(10) Scheduler: Updating result

*Mar 1 00:28:33.519: IP SLAs(10) Scheduler: start wakeup timer, delay = 14964

[Lucien Avramov]

do you have the ip sla responder configured on the other router? 10.10.10.10 ?

What device is 10.10.10.10?

Are you trying to configure ICMP jitter to the phone or VOIP jitter between two routers?

Post your show version of this router as well.

[webstd.design]

-10.10.10.11---10.10.10.10-

Router1:

ip sla 10

udp-jitter 10.10.10.11 16384 source-ip 10.10.10.10 codec g711alaw advantage-factor 10

frequency 30

history enhanced interval 900 buckets 100

ip sla schedule 10 life forever start-time now

Router0:

ip sla responder udp-echo ipaddress 10.10.10.11 port 16384

IOS Version 12.4(15)T9,

[Joe Clarke]

The device 10.10.10.11 must be an IOS device, and must have the following configured:

ip sla responder

If not running later 12.3T or 12.4 mainline, then it should have the following configured:

ip sla monitor responder

Other versions will need:

rtr responder

The three commands do the same thing: they enable the IP SLA responder in order to process the UDP jitter probe packets.

[Lucien Avramov · Accepted solution]

on router 0, only use the command ip sla responder, remove the rest.

on router 1, the ip in the udp-jitter should be the router 0 ip and not himself

on router 1, you need to delete the ip sla 10 operation and recreate it to make the modifications for the ip addressing

[webstd.design]

How I can modify ip sla without deleting one? :))

R0(config)#ip sla 11

Entry already running and cannot be modified

(only can delete (no) and start over)

(check to see if the probe has finished exiting)

[Lucien Avramov]

that is not possible to do once the ip sla operation is running, you can cut and paste the config from the show run and edit in notepad.

But, you can not modify an ip sla operation once you entered the command ip sla schedule.

in your case, you need to do a no ip sla 11

and then recreate this operation, pasting the values from notepad for example