SNMPv3 - "Authentication failure (incorrect password, community or key) "

[superset]

Anybody found a fix to this problem? i keep getting "Authentication failure (incorrect password, community or key) " randomly on my SNMPv3 hosts. 1 day it works but then the next day it fails, i'm able to snmpwalk directly from the zabbix server or proxy with the configured values for the host that is failing.

edit:
Forgot to say i'm running version 4.0.10

[ingus.vilnis]

It could be that the SNMPv3 device is not able to return the requested data fast enough to fit in the time window set by Timeout parameter in zabbix_server.conf.

You can try to extend the value for Timeout by few seconds more than you have now (Don't max ir to 30!), restart Zabbix server service to apply and see if the data collection becomes any better.

Apply the same steps if the device is monitored by proxy respectively.

[superset]

My timeout is actually configured for 30.
I just did a wireshark and decryptet the data and it seems like its actually returning data to zabbix.

[superset]

I just tried to change the EngineID on my host and now it seems to work. Seems like its the same old "not a snmpv3 zabbix bug" i ran into. I only have 7 SNMP v3 host on my server so i'm 100% they all had unique engineID's and yet i still ran into this - wonder when they will actually take this serious.

I found inspirtation to this fix by looking at this very old post. https://blog.sys4.de/monitoring-snmp...gineid-en.html

[ingus.vilnis]

Yes, just wanted to say to check for EngineIDs.
Capture all SNMP traffic from your Zabbix and bring specifically the EngineBoots, EngineTime and EngineID fields out in Wireshark. This will help to highlight the issue and spot duplicates.