IPM 4.0.1 - Hourly UDP Jitter Max RTT Reporting Problem

Answered Question
Jun 21st, 2009

Hi,

When running an hourly report for a given IP SLA test IPM provides differing results as to what is contained in the minute by minue report run for the same time period.

The RTT max(ms) column in the hourly report features several spikes that can't be found in the minute by minute report. How is IPM rolling up the data to an hour?

Results are attached.

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 7 years 5 months ago

I was able to reproduce this internally on your IOS and 12.4(24)T. I filed CSCta40347 to track this. Please open a service request so your SR can be linked to this bug.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Joe Clarke Sun, 06/21/2009 - 20:22

This data comes from the device. What values do you get walking the rttMonStatsCaptureTable and rttMonJitterStatsTable tables on this device? What version of IOS is this device running?

eidumsigfrid Sun, 06/21/2009 - 21:18

Hi,

I have Cacti running as well now to extract and graph the SNMP data. Cacti shows a max RTT of 29ms for the last hour as compared to IPM's hourly graph which shows a max RTT of 130ms.

When running the minute by minute report for the last hour, IPM data correlates with the data from Cacti.

The router is a Cisco 7206 running IOS 12.4(15)T7.

Joe Clarke Mon, 06/22/2009 - 09:51

Please post the SNMP Walk output. These tables are used by IPM to build the hourly graphs and reports.

Joe Clarke Tue, 06/23/2009 - 16:49

This does appear to indicate a problem on the device. I happen to have a 7200 running 12.4(15)T7, so I'm running some tests locally to see if I can reproduce. It does appear you've found an IOS bug.

Correct Answer
Joe Clarke Fri, 06/26/2009 - 12:20

I was able to reproduce this internally on your IOS and 12.4(24)T. I filed CSCta40347 to track this. Please open a service request so your SR can be linked to this bug.

Actions

This Discussion