search cancel

IPSLA Stops reporting after update to released 20.2

book

Article ID: 203432

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration DX NetOps

Issue/Introduction

After updated the PM, we don't see any more Jitter data reported on the dashboard. The error is " No Data to display". We Updated the Response Path Test Jitter in the DA but all still shown Inactive and the SNMP Pool rate status shown "tree-null". Please advise. The polling configuration also looks like the following

Polling Config Item ID=10616218
Poll Group ID=-1
Normalized Facet Type=SNMP
Certification Facet Type=null
PollingConfig's DcmID=tiro:4417d63f-6eac-4e65-b3f5-303605df8987
Polled Items(326)
    Item ID=1427446, Name=Cisco Rttmon Jitter Precision: 0.0.0.0-192.168.238.216 : 3654710, Index List={[3654710, 3654710]}  **WARNING: Polling Configuration index list doesn't match with polled item index list {[]}**
    Item ID=1427445, Name=Cisco Rttmon Jitter Precision: 0.0.0.0-192.168.238.160 : 3654550, Index List={[3654550, 3654550]}  **WARNING: Polling Configuration index list doesn't match with polled item index list {[]}**
    Item ID=1427442, Name=Cisco Rttmon Jitter Precision: 0.0.0.0-192.168.237.120 : 2654890, Index List={[2654890, 2654890]}  **WARNING: Polling Configuration index list doesn't match with polled item index list {[]}**

Environment

Release : 20.2.1

Component : IM Reporting / Admin / Configuration

Cause

  • Symptom:
     Cisco ISPLA polling can fail with NullPointerException if component IndexList has unexpected format for a given AttributeGroup.
     
     
    Resolution:
     Cisco IPSLA poller gracefully handles the unexpected component IndexList format, log an appropriate message, and ensure data from the other valid AttributeGroups can be collected.
     
    (20.2.2, DE472770)

    Resolution

    Upgrade to 20.2.2 or higher