IPM Statistics

Unanswered Question
Jul 6th, 2009

I created IPM collectors on a hub devices for various remote locations. Upon reviewing IPM collector statistics, I have noticed that the completion summary of each collector has similar graph patterns, which seem kind of odd to me. How can I explain this behavior? Is this possible? Thank you in advance.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Joe Clarke Mon, 07/06/2009 - 09:31

Without any details, I can only guess that the latency between the hub and spokes is about the same. What evidence do you have to contradict what IPM is reporting? What type of collectors are you using? What version of IOS is the source router running? What exactly are the values you are comparing?

santipongv Mon, 07/06/2009 - 09:36

The latency between hub and spokes are not the same. I am using defaultIPecho collector. Source router is running 12.4(18c). I am comparing Completion Summary.

Joe Clarke Mon, 07/06/2009 - 09:40

How have you verified the latency is different than what IPM is reporting? What are the values that IPM is reporting? What are your actual latency values?

santipongv Mon, 07/06/2009 - 09:48

The actual latency value and the one reported by IPM are very close. What I learned was these collectors share similar number of tries (attempts) and number of completions, which make me think that could this be IPM processor problem?

Joe Clarke Mon, 07/06/2009 - 10:06

So you're comparing the actual completion counts? Why would you think they would be different? By default the IP SLA collections will perform an operation every 60 seconds. Assuming there wasn't some kind of error, the operations should all complete.

IPM is simply reporting the data from the device. If you suspect a problem with what the device is reporting, then check the output of "show ip sla monitor collection". The numbers there should agree with what IPM is reporting.


This Discussion