No data on some devices after upgrade to DX Netops Performance Management 20.2.9 or 20.2.10
search cancel

No data on some devices after upgrade to DX Netops Performance Management 20.2.9 or 20.2.10


Article ID: 219137


Updated On:


CA Performance Management - Usage and Administration


After upgrading to DX Netops Performance Management 20.2.9 or 20.2.10 there is no SNMP data for some devices

We are still seeing reachability statistics which are ICMP based, but not SNMP based metrics.

In the /opt/IMDataCollector/apache-karaf-2.4.3/data/log/Exception.log we see errors similar to:

YYYY-MM-DD HH:MM:SS,###| ERROR | ExceptionLog | A NEW application exception occurred (Key=#################) : Failed to load # items of type {}SNMPv3Profile on listener$ListenerProxy : no authOid for authProtocol=NONE | ( 
java.lang.IllegalArgumentException: no authOid for authProtocol=NONE
 at java.util.concurrent.ThreadPoolExecutor.runWorker([:1.8.0_282]
 at java.util.concurrent.ThreadPoolExecutor$[:1.8.0_282]


Release : 20.2.9,20.2.10,21.2.1

Component : Polling


Defect: DE508219

This can be seen when there are one or more SNMP V3 SNMP profiles that are configured for no authentication.

This can cause SNMP profiles that are loaded after that SNMP profile to fail to load.


This issue has been fixed in DX Netops Performance Management 21.2.2 and later:

From 21.2.2 Fixed Issues:

Symptom: When SHA256/512 support was added to SNMPv3 authentication protocols, using NoAuthPriv now causes a "java.lang.IllegalArgumentException: no authOid for authProtocol=NONE" in the DC. It fails to load the NoAuthPriv SNMPv3 profiles and subsequent SNMPv3 profiles on DC restart, and can cause all polling to stop for those v3 devices.

Resolution: Removed the exception being thrown when an NoAuthPriv SNMPv3 profile is loaded.

(21.2.2, DE508219, 32694524,32770712)

Additional Information


If you are able to delete the SNMP profiles which are configured for no authentication (No devices are using the profiles) then doing so and restarting the Data Collector(s) will allow the SNMP profiles to load.

If you are not able to delete the noted SNMP profiles, please contact technical support for further guidance.