Issies with changing auth/priv to existing host

[Sagimor]

Hello everyone,

So we have been using Zabbix for years now with no issues at all until today.

We have updated the SNMPv3 priv/auth in our devices (Cisco Nexus switches) and since that moment, we are getting at error that the Zabbix fails to authenticate.

It seems that the Zabbix will keep using the old priv/auth for all the hosts despite we have updated all the hosts hours before..
We are using macros that holds the passwords, but even when trying to set the new credentials without macro (clear test string) it still failed to authenticate and kept using old creds.

We did not (yet) try to complete remove the host and re-create it with the new creds, as this will delete all previous data.
We also did not try (yet) to restart the server/service, first we must know if there is a more simple solution.


Zabbix version (a bit old!) is 5.0.11
Any suggestions/ideas will be appreciated.

Thanks a lot.
Sagi.

[Hamardaban]

Your version of zabbix does not support new encryption algorithms (by the way, what parameters are configured on the equipment?)

for 5.0

Authentication protocol	Select authentication protocol - MD5 or SHA.
	.
Privacy protocol	Select privacy protocol - DES or AES.

for 6.0

Authentication protocol	Select authentication protocol - MD5, SHA1, SHA224, SHA256, SHA384 or SHA512.
Privacy protocol	Select privacy protocol - DES, AES128, AES192, AES256, AES192C (Cisco) or AES256C (Cisco)

Update!

[cyber]

Restart proxy/server (whichever is monitoring the devices) after change of snmp credentials. Otherwise it keeps using old ones.

[Sagimor]

Thanks guys,

Hamardaban - We are using auth sha and priv aes. and it worked great, we just could not change the password.
cyber - We though about it, restarting the service but it's big company with a lot of devices being monitored. so that's not at easy task to do - but if no other solution, we will.

[cyber]

Its kind of a beaten path.. we just recently fixed a bunch of snmp templates, which had either typos or just wrong creds in them... it needs a restart after changing creds.. IIRC it caches stuff that is needed for snmpv3 communications (engineid-s, boottimes, creds) and when you change them, only way to re-cache it is restart...

[Markku]

There is the snmp_cache_reload command, doesn't it help?

For server: https://www.zabbix.com/documentation...untime-control
For proxy: https://www.zabbix.com/documentation...untime-control

Markku

[chrullrich]

There is the snmp_cache_reload command, doesn't it help?

For the record: It does.