"Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs

dleboeuf — Fri, 31 Dec 2021 00:57:01 GMT

Hello everyone,

I am scratching my head at some logs that I am receiving on some Extreme X440G2 switches regarding failed SNMP logins. I have compared both of the SNMP configurations and they both are almost identical minus a few users and one other command, which I will post below. I am trying to figure out what is wrong in the SNMP configuration so that I can stop these logs from blowing up the log file. There are 13 total Extreme switches and currently 9 of them are showing a bunch of these logs. Below is the SNMP configuration on two switches, the first one is a switch that doesn't receive these logs, and the second one is a switch that does receive the logs. I will put a '#' symbol next to the lines that are different.

Switch 1 - No log messages
configure snmpv3 add user "admin" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3 authentication md5 auth-encrypted localized-key 23:24:71:71:37:74:78:7a:2f:71:6e:7a:77:6b:76:56:47:6a:6e:55:6c:4e:55:77:67:6d:67:61:6e:55:42:74:67:30:72:71:68:4a:67:75:65:34:33:4b:64:38:4f:45:49:35:34:6f:77:3d privacy privacy-encrypted localized-key 23:24:6c:33:35:57:61:6d:63:7a:64:72:2b:32:6a:73:6d:42:33:56:47:4b:35:56:67:4a:46:69:56:69:33:61:30:2b:56:7a:6c:4a:70:42:63:43:49:72:58:4a:58:31:78:5a:70:70:59:3d
configure snmpv3 add user "initial" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3
#configure snmpv3 add user "initialmd5" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3 authentication md5 auth-encrypted localized-key 23:24:51:48:72:75:63:53:61:71:6a:35:6b:57:62:36:6c:58:6b:4a:70:32:6d:68:46:6e:54:42:43:63:57:75:61:42:6d:66:6f:32:48:35:50:38:72:4e:4b:6d:39:43:6a:44:69:66:6f:3d
configure snmpv3 add user "initialsha" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3 authentication sha auth-encrypted localized-key 23:24:56:36:78:59:53:45:6d:4b:51:52:6b:48:54:4f:45:7a:58:70:69:69:62:35:4e:6c:58:58:41:56:34:69:64:50:6f:6f:79:51:5a:4f:38:6c:64:48:4e:56:62:46:75:33:54:2f:4d:3d
configure snmpv3 add user "sbfV3admin" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3 authentication md5 auth-encrypted localized-key 23:24:6d:42:65:6f:4f:55:57:31:63:74:56:38:4b:62:46:62:72:39:75:50:76:33:56:5a:31:48:52:75:4f:4f:66:56:4c:46:6d:72:41:39:57:48:7a:65:39:69:4c:77:56:4e:59:4c:55:3d privacy privacy-encrypted localized-key 23:24:66:69:31:37:51:54:68:33:4e:64:77:70:33:72:72:45:76:68:71:58:61:66:54:6a:4a:38:4d:4b:64:42:38:77:6f:7a:58:65:47:36:63:36:66:4d:64:50:69:7a:37:66:4b:72:30:3d
configure snmpv3 add user "initialmd5Priv" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3 authentication md5 auth-encrypted localized-key 23:24:30:41:66:72:6e:57:6e:53:55:76:49:69:45:62:67:35:71:36:6e:68:73:2f:4d:6e:56:44:76:36:77:33:5a:5a:6d:6c:72:61:48:76:45:58:5a:50:62:33:58:38:5a:34:45:64:6b:3d privacy privacy-encrypted localized-key 23:24:49:38:46:69:79:49:35:33:74:46:74:72:31:65:31:62:48:75:43:4e:6f:44:6f:35:64:61:57:63:33:6f:5a:6e:59:49:47:4a:50:4c:2b:69:37:72:6e:47:53:58:64:68:6f:55:67:3d
#configure snmpv3 add user "initialshaPriv" engine-id 80:00:07:7c:03:00:04:96:ae:ba:c3 authentication sha auth-encrypted localized-key 23:24:6d:41:71:6c:44:57:35:63:51:33:79:73:5a:37:71:4a:78:4a:73:7a:33:58:30:38:31:43:46:53:65:6c:59:71:7a:57:6f:4d:79:30:64:77:56:4a:52:76:37:56:5a:49:30:62:51:3d privacy privacy-encrypted localized-key 23:24:32:47:34:44:4b:7a:4a:55:66:4f:72:57:39:2f:67:67:31:39:36:72:46:6f:30:4b:54:30:54:50:51:41:70:48:63:65:77:4d:45:50:41:50:47:39:50:71:4e:7a:4f:76:74:69:4d:3d
configure snmpv3 add group "snmpV3group" user "sbfV3admin" sec-model usm
configure snmpv3 add access "snmpV3group" sec-model usm sec-level priv read-view "defaultAdminView" write-view "defaultAdminView" notify-view "defaultAdminView"
configure snmpv3 add community "private" name "private" user "v1v2c_rw"
enable snmp access
enable snmp access snmp-v1v2c
enable snmp access snmpv3

Switch 2 - Receiving the log messages
#configure snmpv3 engine-id 03:02:04:96:ae:bb:e2
configure snmpv3 add user "admin" engine-id 80:00:07:7c:03:02:04:96:ae:bb:e2 authentication md5 auth-encrypted localized-key 23:24:4b:46:53:71:62:74:53:51:77:70:6a:79:4f:39:33:39:2b:30:71:68:30:48:4a:33:79:73:69:73:4c:43:57:6c:48:71:68:35:78:31:4e:55:6b:2f:42:2b:2f:42:61:6a:39:49:45:3d privacy privacy-encrypted localized-key 23:24:2f:41:58:49:64:78:67:58:6b:6b:4a:52:4f:69:76:43:5a:37:4f:46:51:7a:67:35:73:36:6a:7a:72:41:6b:52:66:64:36:41:4d:58:55:44:44:62:4f:2b:4e:62:6e:76:6f:59:77:3d
configure snmpv3 add user "initial" engine-id 80:00:07:7c:03:02:04:96:ae:bb:e2
configure snmpv3 add user "initialsha" engine-id 80:00:07:7c:03:02:04:96:ae:bb:e2 authentication sha auth-encrypted localized-key 23:24:75:53:5a:53:32:51:30:38:70:50:6b:6e:56:4f:6d:51:72:59:2b:54:63:4e:38:65:66:36:50:37:4e:73:73:50:45:6b:44:69:38:34:53:75:54:42:33:62:43:30:75:5a:36:2f:73:3d
configure snmpv3 add user "sbfV3admin" engine-id 80:00:07:7c:03:02:04:96:ae:bb:e2 authentication md5 auth-encrypted localized-key 23:24:6e:48:61:71:34:45:5a:65:33:52:73:42:76:65:46:6b:30:61:44:4e:4c:65:51:46:64:6c:67:63:73:61:4c:33:2b:77:44:45:48:4a:61:68:48:4c:66:38:30:43:41:76:53:37:73:3d privacy privacy-encrypted localized-key 23:24:4c:43:46:41:31:6c:45:37:33:4a:6b:43:65:77:7a:4a:4d:70:4b:45:49:2f:52:73:79:75:71:33:64:61:73:48:62:36:34:54:45:67:32:65:41:68:4e:43:6a:64:49:56:67:4f:67:3d
configure snmpv3 add user "initialmd5Priv" engine-id 80:00:07:7c:03:02:04:96:ae:bb:e2 authentication md5 auth-encrypted localized-key 23:24:4c:72:78:6c:50:51:69:57:45:72:77:2b:73:39:55:68:72:68:44:48:72:65:5a:4c:4d:35:46:2b:2f:4b:78:6b:76:52:52:56:38:69:4d:35:52:30:34:63:62:44:32:4b:4a:62:38:3d privacy privacy-encrypted localized-key 23:24:62:73:4c:61:55:46:76:72:35:6c:48:77:4b:37:45:6b:59:32:63:74:4b:4f:6a:78:4f:41:32:78:41:35:39:4e:30:65:73:62:68:67:78:75:34:34:7a:43:61:4f:42:53:78:43:6b:3d
configure snmpv3 add group "snmpV3group" user "sbfV3admin" sec-model usm
configure snmpv3 add access "snmpV3group" sec-model usm sec-level priv read-view "defaultAdminView" write-view "defaultAdminView" notify-view "defaultAdminView"
configure snmpv3 add community "private" name "private" user "v1v2c_rw"
enable snmp access
enable snmp access snmp-v1v2cenable snmp access snmpv3

Let me know if there is something missing/incorrect in the configs that would be causing the log messages to populate. They both are getting polled by the same SNMP devices.

Thanks!

Re: "Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs

CThompsonEXOS — Fri, 31 Dec 2021 17:41:19 GMT

Hi,

What exact logs are you seeing? NVM that as they are in your subject

Below is an article explaining more information about certain logs and how to troubleshoot them if you are polling from XMC:

https://extremeportal.force.com/ExtrArticleDetail?an=000101034

In the event something was entered wrong you can also use this script to reconfigure/delete the SNMPv3 configuration:
https://github.com/extremenetworks/ExtremeScripting/tree/master/EXOS/Python/snmpassist

Thanks,
Chris Thompson

Re: "Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs

FredrikB1 — Fri, 21 Jan 2022 14:27:57 GMT

Do you still see this problem? In EXOS release 22.4 (if memory serves me right) SNMP broadcast packets were picked up by the SNMP.Master process even though they shouldn't. What EXOS are you on and is it the same on all switches?

topic Re: "Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs in ExtremeSwitching (EXOS/Switch Engine)

"Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs

Re: "Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs

Re: "Login failed through SNMPv1/2c - bad community name x.x.x.x" Logs