search cancel

NetOps SNMPv3 Discovery fails for new devices


Article ID: 255968


Updated On:


CA Performance Management - Usage and Administration DX NetOps


Discovery of Devices fails in PM -  trace from Checkpoint device shows SNMP request does not contain UserName. Sapwalk from Data collector does function with same credentials.

DX NetOps Performance Management Data Aggregator Discovery Profile runs fail to discover new devices using SNMPv3.

The credentials in the SNMP Profile are the same that are successfully used with sapwalk2 and snmpwalk commands on the Data Collector CLI. The same credentials are also used successfully in Spectrum.

The engineID in use is unique.

Packet captures suggest the wrong user name is being passed during SNMP communication attempts.


All supported DX NetOps Performance Management releases


The IP and/or SNMPv3 engineID used by the new devices are those used previously by old devices. This information was incorrectly retained in the DX NetOps Performance Management Data Collector memory and caused the discovery failure.


To resolve this requires a Data Collector dcmd service stop and restart. This clears the memory cache it maintains and allows the discovery to complete successfully.

See the Restart the Data Collector documentation topic for commands.

DE552983 has been opened for this to be resolved in a future release. When the release a fix will be included in is determined, this article will be updated. Last update date: 12/09/22