NetOps SNMPv3 Discovery fails for new devices

Products

• CA Performance Management - Usage and Administration
• DX NetOps

Issue/Introduction

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.

Environment

All supported DX NetOps Performance Management releases

Cause

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.

Resolution

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.

This is resolved through defect DE588987/DE152322 in release 23.3.7. Upgrade to 23.3.7 or newer to resolve this issue.

Additional Information

See the 23.3.7 Fixed Issues page where we see this entry.

• Symptom: When you change the SNMPv3 device's engine ID, SNMP queries fail with error usmStatsUnknownEngineIDs. The data collector must restart before it can discover the new engine ID and resume the polling of the device.
• Resolution: With this fix, when the data collector receives error usmStatsUnknownEngineIDs, SNMPv3 error handling now removes the cached engine ID. The data collector now discovers new engine IDs and keeps polling.
• (23.3.7, DE588987, 33632273)