discovery adds two agent interfaces

[tvtue]

Hi zabbix users,
we have a strange problem. We've setup a discovery to add hosts to zabbix, put them in a certain group and link a certain template to it.
This all works but the hosts ends up having two agent interfaces. One of them with an IP we have never uses anywhere before.
We've checked the network setup of the host where the agent is running. Everything is ok there.

Has somebody seen this behaviour before or has a pointer where this could come from?

Thanks and regards
Timo

[tchjts1]

I see that every now and then in my 2.0.9 setup. I think one of 2 things cause it in my case.

1. They change the IP of the host being monitored, so then it is "rediscovered" and Zabbix doesn't delete the old IP.

2. There is a same-named host on the network somewhere and both are trying to register in Zabbix as that host name but with different IP's. Perhaps a lab machine or a template type machine that they do new builds from.

[tvtue]

Just for the record

We were testing things in and out. Shut one machine down and waiting for the next discovery run, etc.

Finally we solved this issue just by modifying the discovery. We changed the "Device uniqueness criteria" from Zabbix agent "agent.hostname" to IP address.

I don't know why this happened but I have the "feeling" that it came in with the upgrade from zabbix server form 2.2 to 2.4. It was just an idea of my workmate. I myself would have never thought of the discovery as the culprit.

Anyway it works now, thanks

Timo