How to get IP SLA statistics via SNMP? OIDs needed!

Answered Question
Jul 27th, 2010
User Badges:

Hi there,


I'm using Catalyst 3560 with c3560-ipservicesk9-mz.122-53.SE2.bin

IP SLA has been configured and works fine:

~~~~~~~~~~~~~~~~~

ip sla 1

path-jitter 172.16.1.4 source-ip 10.10.2.1 interval 300
request-data-size 1260
tag IP SLA PATH-Jitter MONITORING
ip sla schedule 1 life forever start-time now

~~~~~~~~~~~~~~~~~


I can get all the data via CLI:

~~~~~~~~~~~~~~~~~

SW1#sh ip sla statistics 1

....

Hop IP 172.16.1.4:
Round Trip Time milliseconds:
        Latest RTT: 101 ms
        Number of RTT: 10
        RTT Min/Avg/Max: 97/101/107 ms
Jitter time milliseconds:
        Number of jitter: 9
        Jitter Min/Avg/Max: 2/3/7 ms
Packet Values:
        Packet Loss (Timeouts): 0
        Out of Sequence: 0
        Discarded Samples: 0

~~~~~~~~~~~~~~~~~


I can get "Latest RTT" value via 1.3.6.1.4.1.9.9.42.1.2.10.1.1.x (x is a IP SLA number) OID but I cannot find the OIDs in CISCO-RTTMON-MIB on how to get all other data that I need, like:

RTT Min/Avg/Max: 97/101/107 ms
Jitter Min/Avg/Max: 2/3/7 ms

I've tried all the OIDs from the MIB http://www.mibsearch.com/objview/CISCO-RTTMON-MIB considering jitter but they are all empty.


How can I get all those data via SNMP? What OIDs do I have to use?


Brgds

Correct Answer by Joe Clarke about 6 years 7 months ago

Ah, I see now that you are using pathJitter on this 3560.  Unfortunately, there is no SNMP support for this type of operation yet.  If you were to use a regular UDP jitter operation, then the table I mentioned before would provide the statistics data via SNMP.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Thu, 07/29/2010 - 20:36
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

The objects under the rttMonJitterStatsTable (1.3.6.1.4.1.9.9.42.1.3.5) will give you min/max/avg jitter as well as RTT min and max and the total number of RTT probes.

Joe Clarke Thu, 07/29/2010 - 21:20
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

That's a table.  Are all of the objects in the table returning 0.  Post the SNMP Walk output for the rttMonJitterStatsTable.

ipovarenkin Thu, 07/29/2010 - 22:54
User Badges:

I know that this is the table but unfortunately I have the following:


>snmpwalk -v 2c -c public 192.168.2.1 1.3.6.1.4.1.9.9.42.1.3.5.3
SNMPv2-SMI::enterprises.9.9.42.1.3.5.3 = No Such Object available on this agent at this OID


SNMP agent in this IOS (c3560-ipservicesk9-mz.122-53.SE2, one of the latest) does not have such table.


Is there another solution on how to get IP SLA statistics via SNMP?


The same thing with a router with IOS c180x-adventerprisek9-mz.124-24.T3

>snmpwalk -v 2c -c public 172.16.1.4 1.3.6.1.4.1.9.9.42
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: (0) 0:00:00.00
SNMPv2-SMI::enterprises.9.9.42.1.1.4.0 = INTEGER: 27013
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.7.1.2.13 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.7.1.2.16 = 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.8.1.2.32 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.8.1.2.34 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.10.0 = INTEGER: 27013
SNMPv2-SMI::enterprises.9.9.42.1.1.11.0 = INTEGER: 36885763
SNMPv2-SMI::enterprises.9.9.42.1.1.12.0 = ""
SNMPv2-SMI::enterprises.9.9.42.1.1.13.0 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.42.1.1.15.0 = INTEGER: 0


>

Correct Answer
Joe Clarke Thu, 07/29/2010 - 23:49
User Badges:
  • Cisco Employee,
  • Hall of Fame,

    Founding Member

Ah, I see now that you are using pathJitter on this 3560.  Unfortunately, there is no SNMP support for this type of operation yet.  If you were to use a regular UDP jitter operation, then the table I mentioned before would provide the statistics data via SNMP.

ipovarenkin Fri, 07/30/2010 - 00:03
User Badges:

Thank you very much Joseph!

I can get the same info with udp-jitter and packet size needed!

Actions

This Discussion

Related Content