Discovery Action adds old servers

[jmedlock]

Hello,
I'm sure this question has been asked at nauseam, but I haven't found the thread yet. So if someone can point me to it, that would be awesome. However, for now, I'll just ask again.

I have Zabbix monitoring a large environment, 1,600+ hosts. These are both servers *and* network devices. The issue that I'm running into is, when we decommission a server and/or delete the server, once the discovery rule runs, the server is re-added. What is even more peculiar is, once the server has been decommissioned, the IP address that the server previously held is no longer active. So I'm not sure why Zabbix keeps adding the server(s) back in.

I did figure out that after we decommissioned a server or group of servers, if I delete the Discovery Rule, re-create it and add it to the respective Discovery Action, the host(s) will not re-appear. The issue with this is, we're going to be doing server and network refreshes throughout the rest of 2021. So deleting the Discovery Rule every time a few servers are removed is going to become a nightmare very quickly.

Has anybody come across a way to keep the hosts from re-appearing without having to replace the Discovery Rule?

Thank you very much!

[Markku]

Hi, I don't use discovery but this really sounds interestings so let's see.

Can you tell us details about your configuration, like Zabbix component versions and the discovery rule configuration?

Do discovery runs create any logs that could be helpful?

Can you take packet captures (with tcpdump or wireshark or tshark or similars) of the discovery traffic so that you could see what exactly happens during the discovery of the "ghost hosts"?

Markku

[Hamardaban]

If the host was added as a result of network discovery, it will appear again when you delete it (as it happens in yours system).
Use a different way to add hosts , such as autodiscover.