[XML] Cisco IP SLA templates (AKA RTR & SAA)

Templates, scripts for templates, scripts and requests for templates.

Moderators: Developers, Moderators

Post Reply
jay
Cacti User
Posts: 390
Joined: Wed Aug 31, 2005 8:55 am
Location: Bristol, England

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by jay »

Looks like it returns HEX

C:\Documents and Settings\bedfordj>snmpwalk -v2c -c <comuunity> <ip address> 1.3.6
.1.4.1.9.9.42.1.2.2.1.2
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.2.1 = STRING: " öÑe"
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.2.2 = STRING: " 1ß±"
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.2.3 = Hex-STRING: 20 23 93 01
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.2.5 = STRING: " 1ߦ"
Cacti Version 0.8.7e, Spine 0.8.7e, Apache 2.2.15, Mysql 5.0.88, PHP 5.2.13, RRDTool 1.2.30, NET-SNMP 5.5
Quad Core AMD Opteron Processor 2384, 2.70Ghz, 2GB RAM , 1 CPU used
Windows Server 2003 (X64), VMWARE ESX
Plugins: Aggregate 0.75

SYSTEM STATS: Time:12.5140 Method:spine Processes:2 Threads:15 Hosts:400 HostsPerProcess:200 DataSources:2909 RRDsProcessed:1384
jay
Cacti User
Posts: 390
Joined: Wed Aug 31, 2005 8:55 am
Location: Bristol, England

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by jay »

It maybe that you need to apply some regex within the snmp_query located in

F:\apache2\htdocs\cacti\resource\snmp_queries

If you look at the one for this template you will see a lot of regex used.

This is way above my pay scale to work out though :wink:
Cacti Version 0.8.7e, Spine 0.8.7e, Apache 2.2.15, Mysql 5.0.88, PHP 5.2.13, RRDTool 1.2.30, NET-SNMP 5.5
Quad Core AMD Opteron Processor 2384, 2.70Ghz, 2GB RAM , 1 CPU used
Windows Server 2003 (X64), VMWARE ESX
Plugins: Aggregate 0.75

SYSTEM STATS: Time:12.5140 Method:spine Processes:2 Threads:15 Hosts:400 HostsPerProcess:200 DataSources:2909 RRDsProcessed:1384
jay
Cacti User
Posts: 390
Joined: Wed Aug 31, 2005 8:55 am
Location: Bristol, England

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by jay »

For those wondering what the figures they are getting back are. It may be worth looking at the stats from the router perspective and then looking at Cacti stats and working it out from there. I don't fully understand all the figures Cacti gives back sometimes but looking at the stats on the router may assist you in this.

The following command shows you the stats:-


show ip sla monitor statistics 600

Round trip time (RTT) Index 600
Latest RTT: 33 ms
Latest operation start time: 15:13:30.947 BST Fri Sep 30 2011
Latest operation return code: OK
RTT Values
Number Of RTT: 1000
RTT Min/Avg/Max: 29/33/47 ms
Latency one-way time milliseconds
Number of one-way Samples: 99
Source to Destination one way Min/Avg/Max: 1/1/7 ms
Destination to Source one way Min/Avg/Max: 36/37/45 ms
Jitter time milliseconds
Number of SD Jitter Samples: 999
Number of DS Jitter Samples: 999
Source to Destination Jitter Min/Avg/Max: 0/2/12 ms
Destination to Source Jitter Min/Avg/Max: 0/1/9 ms
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): 1
MOS score: 4.34
Number of successes: 4
Number of failures: 0
Operation time to live: Forever

Also remember if you want to replicate VOIP traffic correctly and make sure its put into your VOIP queue on your WAN you need to set a TOS value of 184 within your IP SLA configuration. I tested this sometime ago and I made some posts within this topic about it.

ip sla monitor 600
type jitter dest-ipaddr <IP Address> dest-port 16392 source-ipaddr <IP Address> codec g711alaw
tos 184
tag router1_router2_VOIP
ip sla monitor schedule 600 life forever start-time now



Cheers

Jay
Cacti Version 0.8.7e, Spine 0.8.7e, Apache 2.2.15, Mysql 5.0.88, PHP 5.2.13, RRDTool 1.2.30, NET-SNMP 5.5
Quad Core AMD Opteron Processor 2384, 2.70Ghz, 2GB RAM , 1 CPU used
Windows Server 2003 (X64), VMWARE ESX
Plugins: Aggregate 0.75

SYSTEM STATS: Time:12.5140 Method:spine Processes:2 Threads:15 Hosts:400 HostsPerProcess:200 DataSources:2909 RRDsProcessed:1384
nomaxpi
Posts: 3
Joined: Mon Apr 08, 2013 8:41 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by nomaxpi »

jay wrote:It maybe that you need to apply some regex within the snmp_query located in

......

This is way above my pay scale to work out though :wink:
It's not quite above mine :D

I guess a little late is better than never.

For those that still use this template and are having the AdminRttType showing up as just the index number, I have found a fix which requires editing the cisco_saa.xml file.

Scroll down to line #25 which currently reads as follows ... <source>VALUE/REGEXP:([a-zA-Z0-9]{1,})+\(([0-9]{1,})\)$</source>

Change the part in blue to the following ... (([a-zA-Z0-9]{1,})+\([0-9]{1,}\))$

So line #25 should now read as ...

Code: Select all

<source>VALUE/REGEXP:(([a-zA-Z0-9]{1,})+\([0-9]{1,}\))$</source>
And that's all folks. If you now refresh the query, you should have the correct information.

Side note, there's some added functionality I am working on to update this template. Since the creation of this template, many things have changed in IOS v15 in regards to IP SLA. If anyone is interested in the added capabilities, PM me and I'll let you know when I have the additional stuff working. Not sure if the original OP is still maintaining this template or not, but I would be happy to send diff's / merge files once I'm done.

If anyone out there is still following this thread that is ;)
jagarcia233
Posts: 8
Joined: Wed Apr 10, 2013 3:32 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by jagarcia233 »

Hi nomaxpi ,

i have had issues on IOS 15 with ip sla icmp-echo , the OID seem to be old or just not working that i am using. Do you have any new templates that would get IP SLA working on cacti for IOS 15?
nomaxpi
Posts: 3
Joined: Mon Apr 08, 2013 8:41 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by nomaxpi »

jagarcia233 wrote:Hi nomaxpi ,

i have had issues on IOS 15 with ip sla icmp-echo , the OID seem to be old or just not working that i am using. Do you have any new templates that would get IP SLA working on cacti for IOS 15?
Hi,

I do not seem to be having any issues with the current (original) template on v15 (other than some additional features needed). Truncated 'sho ver' below for you to see. In my lab, I have several of the SLA probe types working (including icmp-echo) without any issues.

max-3825-voice-lab#sho ver
Cisco IOS Software, 3800 Software (C3825-ADVENTERPRISEK9-M), Version 15.1(4)M6, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Thu 14-Feb-13 06:18 by prod_rel_team


Can you describe where the error is coming in at? Is it in the snmp-query itself or is it in the graphing portion?

What does a command line snmp-walk show you?

Regards,
Max
jagarcia233
Posts: 8
Joined: Wed Apr 10, 2013 3:32 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by jagarcia233 »

IOS im running
- Cisco IOS Software, C3900 Software (C3900-UNIVERSALK9-M), Version 15.1(4)M4, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2012 by Cisco Systems, Inc.

Platform - Cisco CISCO3925-CHASSIS

Problem - i am not getting graphs ip sla icmp-echo for any device running the above code. all other host's that dont have IOS 15 work fine. If you check the cisco web-site there is no OID for ip sla ICMP-ECHO for the above IOS? so i guess the old OID's for icmp-echo are no good. Can you send me your cisco_saa.xml , thats the file im using for my data queries for IP SLA, maybe something on there is outdated?
nomaxpi
Posts: 3
Joined: Mon Apr 08, 2013 8:41 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by nomaxpi »

I haven't made any modifications to the original cisco_saa.xml file except for the regex statement I posted earlier. I'm using a 3825, but I can't imagine the mib structure changed that much with the ISR G2's.

Try and run this from the command line of your cacti server and see what the output is ...

snmpwalk -v 2c -c COMMUNITY RTR_IPADDRESS CiscoRttMonMib

If you don't have the SLA mibs compiled, you can use this instead

snmpwalk -v 2c -c COMMUNITY RTR_IPADDRESS .1.3.6.1.4.1.9.9.42.1

You can also add a "| grep icmpEcho" to the end of the above commands to just see if the echo probes show up.

Let me know what the output shows.
trungtano
Cacti User
Posts: 90
Joined: Fri Apr 10, 2009 1:57 am
Contact:

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by trungtano »

Great it's work, with command ip sla respond on router
trungtano
Cacti User
Posts: 90
Joined: Fri Apr 10, 2009 1:57 am
Contact:

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by trungtano »

Great it's work. addition command "ip sla responder" on router
havok1977
Posts: 49
Joined: Fri Apr 08, 2005 1:41 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by havok1977 »

Hello

Im trying to graph jitter on a few routers and haven't been succesful so far. The templates have been imported and the queries work but the polled variable remains at zero.

Image

My Cisco device info is:
Cisco Internetwork Operating System Software IOS (tm) C805 Software
(C805-SY6-MW), Version 12.2(15)T16, RELEASE SOFTWARE (fc2)
When running a manual snmpwalk querying for the OID mentioned in the thread I get this:
# snmpwalk -v 2c -c xxxxxxxxxx xxx.xxx.xxx.xx .1.3.6.1.4.1.9.9.42.1
SNMPv2-SMI::enterprises.9.9.42.1.1.1.0 = STRING: "2.2.0 Round Trip Time MIB"
SNMPv2-SMI::enterprises.9.9.42.1.1.2.0 = INTEGER: 16384
SNMPv2-SMI::enterprises.9.9.42.1.1.3.0 = Timeticks: (348334846) 40 days, 7:35:48.46
SNMPv2-SMI::enterprises.9.9.42.1.1.4.0 = INTEGER: 823
SNMPv2-SMI::enterprises.9.9.42.1.1.5.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.6.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.2 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.5 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.6 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.7 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.8 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.9 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.11 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.12 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.2 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.3 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.24 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.25 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.26 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.27 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.29 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.30 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.10.0 = INTEGER: 822
SNMPv2-SMI::enterprises.9.9.42.1.1.11.0 = INTEGER: 1162403
SNMPv2-SMI::enterprises.9.9.42.1.1.12.0 = ""
SNMPv2-SMI::enterprises.9.9.42.1.1.13.0 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.2.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.3.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.4.1 = INTEGER: 9
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.5.1 = INTEGER: 5000
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.6.1 = INTEGER: 60
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.7.1 = INTEGER: 5000
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.8.1 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.9.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.1.1.10.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.1.1 = INTEGER: 27
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.2.1 = Hex-STRING: AC 10 03 46
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.3.1 = INTEGER: 32
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.4.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.5.1 = INTEGER: 100
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.6.1 = Hex-STRING: 00 00 00 00
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.7.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.8.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.9.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.10.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.11.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.12.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.13.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.14.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.15.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.16.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.17.1 = INTEGER: 20
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.18.1 = INTEGER: 3000
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.19.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.20.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.21.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.22.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.23.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.24.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.25.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.2.1.26.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.5.1.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.5.1.2.1 = Timeticks: (1) 0:00:00.01
SNMPv2-SMI::enterprises.9.9.42.1.2.5.1.3.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.1.1 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.2.1 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.3.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.4.1 = INTEGER: 3000
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.5.1 = INTEGER: 5
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.6.1 = INTEGER: 5
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.7.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.6.1.8.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.7.1.1.1 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.7.1.2.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.7.1.3.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.7.1.4.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.7.1.5.1 = INTEGER: 20
SNMPv2-SMI::enterprises.9.9.42.1.2.8.1.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.8.1.2.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.8.1.3.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.8.1.4.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.1.1 = Timeticks: (348334846) 40 days, 7:35:48.46
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.2.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.3.1 = Timeticks: (0) 0:00:00.00
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.4.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.5.1 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.6.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.7.1 = INTEGER: 2
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.8.1 = INTEGER: 4185
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.9.1 = INTEGER: 2147483647
SNMPv2-SMI::enterprises.9.9.42.1.2.9.1.10.1 = INTEGER: 6
SNMPv2-SMI::enterprises.9.9.42.1.2.10.1.1.1 = Gauge32: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.10.1.2.1 = INTEGER: 4
SNMPv2-SMI::enterprises.9.9.42.1.2.10.1.3.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.2.10.1.4.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.2.10.1.5.1 = Timeticks: (398529570) 46 days, 3:01:35.70
SNMPv2-SMI::enterprises.9.9.42.1.2.10.1.6.1 = ""
SNMPv2-SMI::enterprises.9.9.42.1.3.1.1.5.1.2115994994.1.1.1 = INTEGER: 0
SNMPv2-SMI::enterprises.9.9.42.1.3.1.1.5.1.2115994994.1.1.1 = INTEGER: 0
Error: OID not increasing: SNMPv2-SMI::enterprises.9.9.42.1.3.1.1.5.1.2115994994.1.1.1
>= SNMPv2-SMI::enterprises.9.9.42.1.3.1.1.5.1.2115994994.1.1.1

Im wondering if that OID error is causing the issue, any help will be appreciated.
linus
Posts: 1
Joined: Wed May 14, 2014 3:10 am

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by linus »

Hi to all,

I have a Point-to-Point link between two routers; i configured the ip sla udp-jitter to monitor network performance of the link and i imported on cacti the xml files attached on this post

On my link, i have to monitor the following parameters:

The link shall have a round-trip latency not greater than 200 ms.
Jitter on the link shall not be greater than 20 ms.
Ethernet frame drop rate shall not be higher than 3%.
The end-to-end availability of the Communication Link shall be no less than 99.5%, measured on a monthly basis

Could you advice to me which cacti graph template i have to use to monitor the above parameters?

thanks a lot
susmadel
Posts: 2
Joined: Mon Aug 18, 2014 4:08 pm

Re:

Post by susmadel »

marmoci wrote:
hwon wrote:The loss is number of packets. I don't remember what 'm' is but probably means millionth. The reason you get a very small value is due to averaging of the value based on the time. Assuming your graph was span of 24 hours, then you need to multiply that with 24 hours (In seconds). Might need some corrections from cacti experts but something like:

34.44 / 1000000 * 24 * 60 * 60 ~= 3 packets.
\

i think 34.44 is maximum value, not the average.
any comment?
I was wondering if a solution had been posted to this? I would like to calculate this value as a percentage, but not sure that makes sense based on the statement above. Thanks in advance for your help with this.
Loneept
Posts: 2
Joined: Fri Oct 17, 2014 7:25 am

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by Loneept »

Hello,

I made this work on common IOS, this is great !

However, I am now trying to make this work on ASR9001 (IOS XR) and have some trouble adapting the XML (I am really new to cacti).

The first thing I had to do was changing the OID <rttMonCtrlAdminTag> from .1.3.6.1.4.1.9.9.42.1.2.1.1.2 to .1.3.6.1.4.1.9.9.42.1.2.1.1.3, or I had no results in the SNMPWalk.

But I still have this thing in the Data Query Debug Information :

Code: Select all

+ Running data query [11].
+ Found type = '3' [SNMP Query].
+ Found data query XML file at '/var/www/cacti/resource/snmp_queries/cisco_saa.xml'
+ XML file parsed ok.
+ <oid_num_indexes> missing in XML file, 'Index Count Changed' emulated by counting oid_index entries
+ Executing SNMP walk for list of indexes @ '.1.3.6.1.4.1.9.9.42.1.2.1.1.3' Index Count: 2
+ Index found at OID: 'iso.3.6.1.4.1.9.9.42.1.2.1.1.3.3' value: '3'
+ Index found at OID: 'iso.3.6.1.4.1.9.9.42.1.2.1.1.3.4' value: '4'
+ Located input field 'rttMonCtrlAdminTag' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.2.1.1.3'
+ Found item [rttMonCtrlAdminTag='3'] index: 3 [from value]
+ Found item [rttMonCtrlAdminTag='4'] index: 4 [from value]
+ Located input field 'rttMonEchoAdminProtocol' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.2.2.1.1'
+ Found item [rttMonEchoAdminProtocol='2'] index: 3 [from value]
+ Found item [rttMonEchoAdminProtocol='3'] index: 4 [from value]
+ Located input field 'rttMonEchoAdminPktDataRequestSize' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.2.2.1.3'
+ Found item [rttMonEchoAdminPktDataRequestSize='36'] index: 3 [from value]
+ Found item [rttMonEchoAdminPktDataRequestSize='16'] index: 4 [from value]
+ Located input field 'rttMonCtrlAdminThreshold' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.2.1.1.5'
+ Located input field 'rttMonCtrlAdminRttType' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.2.1.1.4'
+ Found item [rttMonCtrlAdminRttType='1'] index: 3 [from value]
+ Found item [rttMonCtrlAdminRttType='5'] index: 4 [from value]
+ Located input field 'rttMonLatestJitterOperNumOfRTT' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.5.2.1.1'
+ Located input field 'rttMonLatestHTTPOperMessageBodyOctets' [walk]
+ Executing SNMP walk for data @ '.1.3.6.1.4.1.9.9.42.1.5.1.1.5'
And Cacti is not detecting SLA I have configured ...

I think the line "<oid_num_indexes> missing in XML file" might be a clue, but I have no idea how to solve this, and why it is so different between IOS and IOS XR.

Does anyone has ever made this work on IOS XR ?
Does anyone has any tip, or ways to look at to try and solve this ?

Thanks for your help,
Loneept
green1981
Posts: 2
Joined: Fri Nov 14, 2014 12:32 pm

Re: [XML] Cisco IP SLA templates (AKA RTR & SAA)

Post by green1981 »

I am experiencing the same issue trying to get this to work in IOS XR. Have you made any more progress in getting this to work.

Thanks,
Post Reply

Who is online

Users browsing this forum: No registered users and 2 guests