I had a similar Problem after upgrade from 16.x to 22.1. The snmpv3 users have the Row Status "NotInService" (show snmpv3 user). Also I can not create new snmpv3 users.

This wrote GTAC:

This is a known issue and is documented in xos0066086 "User-defined SNMPv3 users do not work after upgrading to ExtremeXOS 22.1 if the SNMPv3 default-users were disabled using the command disable snmpv3 default-user in ExtremeXOS 21.1 or earlier." This happens when the default SNMPv3 user and group are disabled in 21.x or earlier, an upgrade performed to 22.x and the switch is rebooted in 22.x. This happens because these groups and user have been removed in 22.x along with the associated variables. The work around is to reboot back in 21.x, enable the default-user and default-group, run a fresh upgrade to 22.x, reboot into 22.x and disable them from there. The second workaround is to unconfigure the switch and reconfigure it while in 22.x. A fix will be available in 22.2.1

then from my monitoring server i try : "snmpwalk -v 2c -c test X.X.X.X 1.3.6.1.2.1.2.2.1.8"
The v15 switch answers, but not the v16 switch
On the version 16 switch i still have the messages "bad community name"

then from my monitoring server i try : "snmpwalk -v 2c -c test X.X.X.X 1.3.6.1.2.1.2.2.1.8"The v15 switch answers, but not the v16 switchOn the version 16 switch i still have the messages "bad community name"

Best regards,Gabriel

Could you check the users and mib-views? They may need to re-added/enabled per this article:

then from my monitoring server i try : "snmpwalk -v 2c -c test X.X.X.X 1.3.6.1.2.1.2.2.1.8"The v15 switch answers, but not the v16 switchOn the version 16 switch i still have the messages "bad community name"

Cookie policy

Cookie settings

We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.