[ZBX-25286] SNMP EngineId not unique log message after IP change on monitored system Created: 2024 Sep 24  Updated: 2025 Mar 04

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: Documentation (D)
Affects Version/s: 5.0.46, 6.0.39, 7.0.10, 7.2.4, 7.4.0alpha1
Fix Version/s: None

Type: Documentation task Priority: Major
Reporter: Dennis Skinner Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Sprint: Support backlog

 Description   

Zabbix Server v7.0.1/Proxy v7.0.3

I believe this is related to this new feature:

https://support.zabbix.com/browse/ZBXNEXT-8823

We have a monitored system that changed IP.  I updated the IP in the SNMP interface for the Host and I thought all was well, but I see now that the SNMP checks are not collecting data and the Proxy that monitors this Host has an error every 5min in the log:

SNMP engineId is not unique across following interfaces: <new IP> (hostname), <old IP> (hostname)

I think this is a bug or there is a process to change IP addresses on SNMP hosts that I have not found in the Docs yet.

Thanks!



 Comments   
Comment by Edgar Akhmetshin [ 2024 Sep 25 ]

Hello Dennis,

Execute on Proxy and check if error exists:

zabbix_proxy -R snmp_cache_reload

Regards,
Edgar

Comment by Dennis Skinner [ 2024 Sep 25 ]

The IP change happened 4 days prior.  What is the cache timeout?

Comment by Dennis Skinner [ 2024 Sep 25 ]

I believe the error went away and I am getting data now after the cache reload.  Is this working as intended?  Is it documented somewhere?  I saw this:

Changes in Authentication protocolAuthentication passphrasePrivacy protocol or Privacy passphrase, made without changing the Security name, will take effect only after the cache on a server/proxy is manually cleared (by using -R snmp_cache_reload) or the server/proxy is restarted. In cases, where Security name is also changed, all parameters will be updated immediately.

It doesn't mention IP changes.

Thanks!

Generated at Sat Apr 26 03:31:53 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.