[XML] Cisco SAA Jitter/Jitter-error/http template

[yahman]

Hi
thanks for the nice templates.

I

[yahman]

Hi
thanks for the nice templates.

I

[rwintle]

Question.

on the SAA jitter graphs, my measurements seem to indicate a value between 1.00 and 2.00 With an average of 1.12 for Jitter.

The graph has this labeled as "ms" Is this milli or micro seconds? I would expect my jitter to be less than 250 microseconds as these are just point to point links.

Thanks,

--Rod

[hwon]

The ms is milli not micro. Cacti and the script merely displays the data that was retrieved via SNMP with some exceptions for jitter to make the value negative. That being said, depending on your version of IOS, there is a sub command when you configure the probe to gain micro precision which is 'precision microseconds'. Never tried but worth a shot. Be sure to update this forum as now I am curious :>

[rwintle]

These are the readings in my graph..

+ Source -> Destination 1.00
+ Destination -> Source 1.00
- Source -> Destination 1.00
- Destination -> Source 1.00


But, I want less than 250microsecond jitter.. This looks like I'm getting 1 ms?

[hwon]

Is that result after applying the precision microseconds command?

Also, what is the jitter stats when you run show command? Is it reflecting what you are seeing on the cacti?

[msw1970]

Hi

New to this SAA template.

What do I have to enter for Output Type ID, Index Value & Index Type for each graph type.

Thanks

[rwintle]

Here is my show run:

rtr 1
type jitter dest-ipaddr 172.22.225.2 dest-port 14384 num-packets 1000
tag jittertest-ptldme
threshold 100
request-data-size 229
rtr schedule 1 life forever start-time now


The version of IOS I have does not support precision microseconds

I'm looking at doing an upgrade.

[hwon]

Msw1970, when using the SAA template, add the 'Cisco - SAA Statistics' data query from the device like you do for adding new interface statistics. And then click the '*Create Graphs for this host' link in the top right corner. Also make sure your probe entry has a unique tag assigned to it as the script uses tag as the index.

[hwon]

Turns out that to enable the micro precision you need to be running IOS 12.4. Been playing around a bit with the new feature of SAA (Now called IP SLA) and noticed following:

- precision microseconds sub command is only available on certain probe types. I assume it is available on the ones that utilize sla responder (i.e. jitter, path jitter, etc.), but haven't verified.
- Being ultra sensitive, you need to have ntp setup on the routers participating in the ip sla
- Also recommended to setup 'clock tolerance' sub command to find out which RTT packet was out of sync. Thus, I've added a new graph item in the jitter/error stats to display RTT out of Sync.

When you use the newly installed graph templates with micro precision attached to it, make sure you have the probe configured with 'precision microseconds' sub command. Might be a good idea to add a note in the tag to let you identify it as well.

Attached is updated xml files and sample graph with micro seconds precision:

[hwon]

Just realized that cacti can use portion of OID as the index. This way, even if you do not have tag entered for each probe, you can still get the query result. Might be useful for people who uses management s/w to create SLA probes.

I will leave the files I uploaded few days ago, for people who still needs it. But here are the xml files for the one that indexes based on the probe ID.

[pyrorob]

[hwon]

Rob,

I do not know of a way to create that file on the cacti box without console/ssh/telnet access.

[hroyd]

anyone know what the scale represents

what woud 911ms mean? i see the sh ip sla mon oper command gives the number of packets lost. how does this relate to the template

tia

[hroyd]

sooryy, the above is re: the packet loss measurement