Proxies VMs not getting created as new hosts sharing same name

[javiers]

Okay so basically i have 10 proxies which monitor 10 different esxi hosts, the problem is:

There are some VMs which share the same name and are not getting created, for example Proxy 1 VM DC and Proxy 2 also has a VM named DC but in the frontend only Proxy 1 DC appears to be created as a discovered host.

Any idea on how i could fix it?

Any different idea from modifiying all vms which share the same name?

[medl]

Its sounds kind of adventurous that you have a proxy for each ESX but also makes me curious. What Problem lead you to deploy a Proxy for each ESX?

Anyway, i ran into a similar Issues (Name collision in VMs / Datacenter etc) that i have not yet solved.
Plan was (and still is) to modify the Host Prototype on the VMWare Template to include an additional Prefix / Suffix.
In Template -> Template VM VMWare -> Host Prototypes you will find the Macro that is used and should be able to add your own.

In general if you modify the supplemental Templates its good to clone them and make your own Version.
Otherwise you may run into migration issues.

If you monitor your ESX directly there should also be a (custom?) Template with a Host Prototype.

[javiers]

My bad i miss explained, no i do not run a proxy for every esxi i ment i have 10 proxies distributed in order to monitor my clients LAN.
I run 1 proxy for each client which monitors multiple esxi hosts, but yeah the issue its the same on my frontend only 1 host with the same name is added, so yeah i will try to add prefixes and check again.


Thank yoy for your advice.

[Markku]

If you monitor your ESX directly there should also be a (custom?) Template with a Host Prototype.

Yes: in the ESXi-assigned template you should have a discovery rule for discovering the VMs, and in that rule there is a Host prototype. You can change the Name field to for example {#VM.NAME}(Guest {#VM.ID})

Markku

[javiers]

Thanks for your advice Markku, in the end i did something similar by adding the uuid to the name.

Another question related to this topic, is it possible to add a macro to the name so when host is created it adds the proxy which monitors the original host or something similar?
Like adding the name from the original host ?

Example: Esxi205 has vmware template which discovers the vms and adds its name to the vm , the final result would be VMName Esxi205 on the newly created host.

[Markku]

See the VM discovery key fields documentation for vmware.vm.discovery: https://www.zabbix.com/documentation...scovery_fields

Markku