[XML] Cisco SAA Jitter/Jitter-error/http template
Moderators: Developers, Moderators
problem with html template
Hi
thanks for the nice templates.
I
thanks for the nice templates.
I
HTML Template
Hi
thanks for the nice templates.
I
thanks for the nice templates.
I
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
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
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 :>
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.
Micro seconds precision
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:
- 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:
- Attachments
-
- Jitter graph using 'Cisco - SAA Jitter Statistics (Micro Sec, Micro Precision)' data query
- saa_jitter.png (64.83 KiB) Viewed 14100 times
-
- Jitter/Error graph using 'Cisco - SAA Jitter/Error Statistics (Micro Sec, Micro Precision)' data query
- saa_jitter-error.png (81.6 KiB) Viewed 14100 times
Last edited by hwon on Tue Feb 06, 2007 2:55 pm, edited 1 time in total.
Update: numeric index
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.
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.
Re: More templates and some fixes
I know this post is old but I was wondering if there were any updates to it that might make it easier to import.hwon wrote:It seems like there are few users who has trouble importing xml files. The cisco_saa.xml file is not meant to be imported via cacti import xml interface. You need to manually copy it over to a sub directory under cacti. Follow below instructions:
<snip>
I am testing out a 'virtual appliance' and it doesn't appear that I have direct access to the OS.
Thanks,
--->Rob
packet loss measurement
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
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
Who is online
Users browsing this forum: No registered users and 0 guests