Zabbix VMware discovery finds duplicate UUIDs

[nick0909]

Running Zabbix 3.2.1 server with proxies at two sites. Those two sites each have their own VMware clusters with VCenters. When I apply the VMware template to one site's VCenter, it works great, everything is discovered and shows up. When I apply it to the second site it mostly works, but the Hypervisor host discovery gets an error that it can't create the discovered hosts because the name already exists. The discovery template is making the name based on the UUID that comes back from VCenter it seems, and that UUID name is the same at both of our sites.

However, if I log on to each esx host and run "esxcli system uuid get" the UUID that gets returned is not even close to what Zabbix is saying, and they are not duplicates between the two sites. I tried appending {$HV.NAME} to the UUID just so they would get created without conflict but that causes problems later because the hypervisor checks require the UUID and that name field is where Zabbix is storing it, so all the items fail.

Does VCenter make its own UUID's different from the standalone esx host?

Does anyone know the API request Zabbix is making to get the UUID to come back?

Is there a way to change the UUID that VCenter is using/reporting on a host?

Or any other suggestions?

[nick0909]

Here is a report from PowerCLI on the host UUID's as seen by VCenter to illustrate the problem. There are two sites, the UUIDs are duplicate between the two sites.

PowerCLI C:\> Get-VMHost | Select Name,@{n="HostUUID";e={$_.ExtensionData.hardware.s ysteminfo.uuid}}

Name HostUUID
---- --------
SiteOne01.domain.local a61fbb99-aa11-b000-0000-000000000001
SiteOne02.domain.local a61fbb99-aa11-b000-0000-000000000002
SiteOne03.domain.local a61fbb99-aa11-b000-0000-000000000003

SiteTwo01.domain.local a61fbb99-aa11-b000-0000-000000000001
SiteTwo02.domain.local a61fbb99-aa11-b000-0000-000000000002
SiteTwo03.domain.local a61fbb99-aa11-b000-0000-000000000003

[nick0909]

Found the issue, we are using UCS blade center and the UUID pool was the same on both. This is found on the Servers tab, bottom left under Pools > UUID Suffix Pools. Once I changed the pool suffix and restarted a blade, VCenter derived its own new UUID automatically.