SNMP "bad community name" errors after upgrade

[Gabriel3]

Hello,

I upgraded a Summit X460-48p from version 15.1.4.3 to 16.1.3.6.

After the upgrade, our monitoring servers (cacti, zabbix) are not able to get SNMP information from the switch anymore (SNMP v2c, readonly community).

In the switch logs, i see a lot of error messages " snmpMaster: Login failed through SNMPv1/v2c - bad community name (x.x.x.x)" with the IP address of the monitoring servers.

Except the upgrade, nothing has changed in the configuration of the switch and the monitoring servers.

I have compared the configuration of the upgraded switch with another switch (not upgraded yet), i see some minor differences, but nothing obvious that could explain the SNMP failures.

I also checked this post (https://community.extremenetworks.com/extreme/topics/snmp-read-problems-bad-community-name-since-xos...) but it seems i don't have the same problem, as my configuration still has the "configure snmpv3 add user" commands

Maybe someone in the community has already experienced this issue.

Thanks for your help.
Best regards
Gabriel

[Ty_Izzet]

Gabriel, the message reports a bad v1/v2 community. The following commands will help determine which community's are being used:

show snmpv3 community
show conf "snmp" detail | inc community
show management

As mentioned, try to delete and recreate the communities. the following articles will help:

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-remove-default-SNMP-credentials-in-...
https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-the-SNMP-community-names

Also, review the show management outputs counters for Authentication Errors, and or, Errors. It may also be worth trying to remove the device from the NMS/MiB Browser and re-adding it there too.

[OscarK]

If you recreate the snmp user, does it work ?