delete snmp v2 credentials for Assurance

[adrian916]

We no longer use SNMP v2 and now use SNMP v3 in DNA .(The v2 community strings were removed from the switches and the v3 settings applied instead

After re-running discovery, the devices are detected and managed using the v3 credentials.

However, Assurance shows that all but one device is unmonitored. The only monitored device is one where we have not removed the 'public' and 'private' v2 community strings

I cannot delete the SNMP v2 credentials from DNA-C network settings as I get the error:

"Credential {SNMPv2-ro} is associated with Network Settings for site - Global. You must either associate a different credential or create a new credential of the same type and associate it with the site, prior to deletion."

How can I delete these v2 credentials which are now unused, or how can I get Assurance to use the v3 credentials in order to monitor the switches, as these are defined at the Global network settings level

[Preston Chilcote]

Last I saw, snmpv2 is still required for full assurance and telemetry (especially for traps sent to Cisco DNA-Center).  SNMPv3 credentials are used for polling some basic information, like CPU and memory, but Assurance needs more information than that.  I assume SNMPv3 will be supported someday, but it would be useful for you to use the "make a wish" function in the Cisco DNA dashboard to communicate that to our development teams.

[adrian916]

Thanks for that information. At least I'm not going mad trying to find something that isn't there! 

[ChuckMcF]

A few days ago I did a "Make A Wish" for them to quit using SNMPv1 and SNMPv2 and instead allow us to set up credentials for SNMPv3 with AES and SHA (128 and 256 options). Hopefully that is put into a future upgrade. If you make a similar request in Make A Wish it may help move it in priority.

Hope this is helpful,

Chuck

[adrian916]

Thanks. We had a call with cisco TAC and I think they are planning v3 support. In relation to the original post, we had to restart the snmp service from cli in order to pick up the new v2 credentials for assurance as it wasn't happening automatically for some reason (they collected loads of logs for further investigation! )