Move SNMP device management from SNMPv2 to SNMPv3 in Performance Management
search cancel

Move SNMP device management from SNMPv2 to SNMPv3 in Performance Management

book

Article ID: 278912

calendar_today

Updated On: 02-06-2024

Products

CA Performance Management Network Observability

Issue/Introduction

We currently have 2500 devices in PM and discovered with SNMP V2 Profile. We need to update all our devices in PM to SNMP V3. What is the best way to convert snmpv2 to snmpv3 in PM without delete\rediscovery devices and lost trend data?

Will it work if we just update PM SNMPV2 Discovery Profile with SNMPV3 credentials?

How to update devices from SNMPv2 polling to SNMPv3 polling?

Environment

All supported DX NetOps Performance Management releases

Resolution

There are a few ways to accomplish this. They all require that the device is already using and responding to SNMPv3.

  1. Run a Discovery Profile with the IPs for involved devices. Set the new SNMPv3 Profile with the new credentials for use.
    • Assumes the devices no longer will work with the previous SNMP Profile credentials, the one they currently use.
    • If they still respond to the existing profile used, they'll continue to use it.
  2. Use REST calls to update the profile one device at a time.
  3. Update the SNMPv2 Profile the devices use, setting the new SNMPv3 details and credentials.
    • Assumes all devices currently using the SNMPv2 Profile will now be polled with the new SNMPv3 credentials.
    • After saving the changes for the SNMP Profile from v2 to v3 credentials, the next successful poll cycle should be successful.
    • If some devices fail to be polled ensure they aren't all using duplicate SNMPv3 engineIDs.

Additional Information

As of the 23.3.6 release of DX NetOps Performance Management SNMPv3 devices no longer require a unique engineID. See the 23.3.6 Features and Enhancements entry for the new Enhanced Support for SNMPv3 Device Discovery feature.