Data Collector stop collecting IPSLA metrics when sysUpTime roll over on a device

Document ID : KB000103915
Last Modified Date : 02/07/2018
Show Technical Document Details
Issue:
A problem can be seen, where manual stop and start polling on a device is needed because the RTT Jitter Tests configured on the router shows no data anymore, and CA Performance Management stops collecting IPSLA metrics data. 
Sometimes this may appear to happen after a reload/restart of the affected device, but further investigation and troubleshooting showed this is caused by sysUpTime metric value wrapping. 
Environment:
CA Performance Management 3.x
Cause:
There are two major issues that cause this behavior.
1) The sysUpTime rollover detection didn’t work fine once hit 2^31 sysUpTime values, because CA Performance Management is using an SNMP4j OID class that was wrongly evaluating sysUpTime. This has now been fixed and changed to use ObjectID class instead, which handles it appropriately. 
2) Even if CA Performance Management did detect the rollover correctly, there were still some flaws in the dynamic index detection logic which caused the agent may still be using the same entry until the IPSLA agent created a new entry with lesser sysUpTime values. 
Resolution:

This problem is now resolved in CA Performance Management 3.6.0, and in release 3.5.0 with the installation of the June monthly update kit: 
Symptom: The Data Collector would stop collection IPSLA metrics once sysUpTime rolled over on a device. 
Resolution: Refactored dynamic index discovery logic to correctly handle sysUpTime rollover and continue collecting metrics.
(3.5.0_June_Update, DE364949)


If encountering this problem, to receive the CA PM 3.5.0 June update kit, open a support Case to have the installation files made available for download. 
 
This will bring CA PM components to the following build versions:
CA Performance Center 3.5.0.272
CA Data Aggregator  3.5.0.282