Vmware monitoring, duplicate with agent, can't update host

[doum]

Hi,

I have added one of our VCenter in Zabbix.
It has discovered all VM.

after this I deploy the agent on one of the VM.

I have two problem :
- it create as new host, no link with the VM, I think it's normal but this behavior is...underperforming
- more problematic, the auto registration of the agent has working, but now I can't edit the host (to add template and host group for example)
I've got a message : Cannot update host. Host with the same visible name "test server" already exists.

How do you manage your virtual environment in zabbix ?

[doum]

no one encounters the same situation?

[zekaleka]

yes, still facing the same in 7.4.10.

I guess VM discovery should be disabled to not encounter this issue. can't think of better solution.

[jtnfoley]

I've long used VMware integration, VM discovery created all the "Host" entries in Zabbix.
I, too, am now moving to agent-based and have decided to disable discovery... specifically, disabling "Discover VMware VMs FQDN" in both "VMware FQDN" and "VMware" templates.)
My entire environment is static IPs and my logging is IP based, not hostname, so I clone the discovered VM "Host" object and remove the VMWare templates from the clone, add the Linux by Zabbix Agent template, delete the original discovered VM Host object, then save the clone under the same name.
Agent config on the Host native OS is set correctly.

I briefly considered disabling the old Host object and implementing a hostname suffix (in Zabbix, and in the agent config, call the host <hostname>a" eg "dbserver01" becomes "dbserver01a" in Zabbix only!) Being static IPs and not relying on DNS at all, this was definitely an option.
I don't need to keep the VMWare guest performance history for these Hosts, so I can safely use the "delete original and keep the clone under the same name" model.

[mosconi.trt1]

We changed the VM template to prefix each VM with the cluster name