search cancel

Data Aggregator SNMPv3 discovery requires unique snmpEngineId

book

Article ID: 32071

calendar_today

Updated On:

Products

CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

Discovery of SNMPv3 devices is failing to discover all devices.

Only one out of 2 or more of the devices is discovered.

When this problem is observed, no clear or obvious error messages are being observed.

Environment

Release: 21.2.x, 22.2.x

Infrastructure Management-Data Aggregator
Component:

Cause

CAPM requires a unique SNMPv3 engineID for each V3 device.

 

The reason for this is because SNMPv3 relies on all devices having a unique SNMP Engine ID value being set on them.

This is an industry standard defined in RFC 3411, section 3.1.1.1.

To pull the v3 engine ID's from PM, Run this on the DC:

curl -vk -u admin:admin http://127.0.0.1:8681/debug/dispatcher/container/com.ca.im.data-collection-manager.snmp/bean/snmpSession >/tmp/bean

** Please note - this url is only available from localhost for security reasons, so you cannot hit this with a REST client or a browser. **

If multiple devices are using the same engine ID, they will be listed as IP,IP,IP…..

 

Resolution

Fix the configuration of your SNMPv3 devices so that each one has a unique engineID.

Alternatively, you could move the non-unique engineID device to a different data collector (DC).

 

Additional Information

https://tools.ietf.org/html/rfc3411#section-3.1.1.1