Is there a work-around for SNMP Duplicate EngineID in DX NetOps?

Products

• CA Performance Management
• Network Observability

Issue/Introduction

The following errors are seen in the karaf log of the Data Collector in CA Performance Management (CAPM):

2024-01-12T10:43:04,902 | ERROR | Response Pool.0  | MPv3Proxy                        | m.ca.im.dm.snmp.snmp4j.MPv3Proxy  936 | 55 - com.ca.im.data-collection-manager.snmp - 23.3.3.RELEASE-7 |  | Duplicate EngineID xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx, IP(s) associated [XXX.XXX.XXX.1/161, XXX.XXX.XXX.2/161]

And

2024-01-14T11:30:03,683 | WARN  | Response Pool.0  | SnmpSession                      | .dm.snmp.collector.SnmpSession$1  290 | 55 - com.ca.im.data-collection-manager.snmp - 23.3.3.RELEASE-7 |  | SNMPv3 usmStatsNotInTimeWindows, clearing engineTime for XXX.XXX.XXX.1/161

These are caused by duplicate Engine ID in devices polled using SNMPv3 and effectively prevent discovery and polling of the devices with this issue.

Other than fixing the device configuration, is there a work-around for SNMP Duplicate EngineID in CAPM such as a way to disable the duplicate engineID checking?

Environment

DX NetOps Spectrum & CAPM all releases

Resolution

There is no work-around for duplicate EngineID in either Spectrum or CAPM other than moving the device to another DC (in CAPM) or SDC (in Spectrum) in the IP Domain and ensuring there is no other device with the same EngineID already present.

The issue needs to be fixed in the device's SNMPv3 configuration.