SNMP v3 Issues

[cyber]

Engine-id is related to v3.

But as this is an old topic with somebody elses issues, maybe you start your own and describe a bit more closely, what exactly is not working and give us a bit more background, errors etc...

[bonethugs]

My problem is similar to the reported in the OP. We have configured some devices (switches, or appliances) to communicate with our zabbix 6.0.12 via snmpv3 with AES/SHA cyphers.
In zabbix I can see that the SNMP icon turns green for all devices and it says it's OK, but the items became not supported after 1 min with error: Authentication failure (incorrect password, community or key)
Doing a snmpwalk/snmpget via CLI is working fine and the data is retrieved OK.
We also did a packet capture and we can see that the switches/appliances are sending the information to zabbix correctly, but the item it's in error state without modify it's value.
We can confirm that engineID is different for all SNMPv3 monitored devices, so we don't know how to do to fix this issue... we don't know where it's exactly the problem but matches this post issues.

[bonethugs]

I've been doing some tests.... we have a zabbix server 6.0.12 in ubuntu but we have a zabbix proxy in same version in Oracle Linux. The snmpv3 devices were monitored via that proxy. I've just changed the devices to be monitored by the server instead of the proxy and everything started working... so it seems some different package is causing the issue. I'm not sure it could be related to "snmp-utils", "openssl" or something like that. Can you help me to troubleshoot this further?

Thanks in advance

[cyber]

Maybe something with AES/SHA versions, 128/256 etc... If its possible, apply all the updates to that linux box, check for the required versions of libraries etc... This is pretty basic stuff, I can recommend. For me this is too much for just guessing.. This requires someone who is more comfortable with all the utils versions etc... But my gut feeling says, you are aiming in correct direction..

[bonethugs]

Good news! I've found the problem... it's related with this: https://support.zabbix.com/browse/ZBX-20845

Executing "zabbix_proxy -R snmp_cache_reload" in Zabbix Proxy fixed the issues.

[cyber]

Hmm... I did not recommend restarting proxy (or reload cache) as it seemed so obvious thing to try.. You need to do it every time you update snmp credentials...