[ZBX-16014] Zabbix 4 Error Monitoring VMWARE 6.5 Created: 2019 Apr 17  Updated: 2019 Dec 17  Resolved: 2019 Dec 17

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Templates (T)
Affects Version/s: 4.0.5
Fix Version/s: None

Type: Incident report Priority: Trivial
Reporter: Gerard Assignee: Aigars Kadikis
Resolution: Cannot Reproduce Votes: 0
Labels: template, vmware
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 18.04 LTS
MySQL 8.0.15
Zabbix 4.0.4


Attachments: PNG File image-2019-05-09-14-32-31-240.png     XML File template_vm_vmware.xml     PNG File zabbix.png     PNG File zabbix_latest.png     PNG File zabbix_latest_2.png     PNG File zabbix_latest_3.png     PNG File zabbix_template.png    

 Description   

Hi, i have zabbix with this enviroment:

Ubuntu 18.04 LTS
MySQL 8.0.15
Zabbix 4.0.4

We Have 279 number of hosts actives with 29709 active items and 10520 active triggers with zabbix agent or SNMP without problems.

Our enviroment has 6 ESXi with one VCENTER in 6.5. When we use the three templates of VMWARE

VMware Template Hypervisor
VMware Template Guest
VMware Template

Applied over the same Virtual Center (in our case Windows 2012R2), with correctly the macros configure

Password
User
URL.

Zabbix find our 6 esxi and VM but doesn't extract any data, and in logs says.

 

1975:20190417:105120.855 item "VMWare Virtual Center:vmware.vm.cluster.name[{$URL},{HOST.HOST}]" became not supported: Unknown virtual machine uuid.
 1977:20190417:105125.177 item "VMWare Virtual Center:vmware.vm.hv.name[{$URL},{HOST.HOST}]" became not supported: Unknown virtual machine uuid.
 1975:20190417:105151.482 item "VMWare Virtual Center:vmware.hv.datastore.discovery[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1975:20190417:105152.600 item "VMWare Virtual Center:vmware.hv.cluster.name[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105155.163 item "VMWare Virtual Center:vmware.hv.fullname[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105156.227 item "VMWare Virtual Center:vmware.hv.hw.cpu.freq[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105157.372 item "VMWare Virtual Center:vmware.hv.hw.cpu.model[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105158.561 item "VMWare Virtual Center:vmware.hv.hw.cpu.num[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105159.682 item "VMWare Virtual Center:vmware.hv.hw.cpu.threads[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1977:20190417:105200.739 item "VMWare Virtual Center:vmware.hv.hw.memory[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105201.882 item "VMWare Virtual Center:vmware.hv.hw.model[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105202.948 item "VMWare Virtual Center:vmware.hv.hw.uuid[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1976:20190417:105203.157 item "VMWare Virtual Center:vmware.hv.hw.vendor[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1977:20190417:105211.012 item "VMWare Virtual Center:vmware.hv.uptime[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1977:20190417:105211.286 item "VMWare Virtual Center:vmware.hv.version[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 1974:20190417:105212.582 item "VMWare Virtual Center:vmware.hv.vm.num[{$URL},{HOST.HOST}]" became not supported: Unknown hypervisor uuid.
 

 



 Comments   
Comment by Aigars Kadikis [ 2019 Apr 18 ]

Hello Gerard,

Please go to latest data page, list one of your ESXi, tick:

  • Show items without data
  • Show details

and press search.

This will show all installed items for this Hypervisor. Do you see the correct URL and HOST.HOST expanded for the item? Please attach a screenshot.

Did you installed a VMWare username on password in all three templates (in macro section) or you did provide the credentials in the global level?

Regards,

Comment by Gerard [ 2019 Apr 24 ]

Hi Aigars, 

I Attach the screenshot. I use username and credentials in global variable . I don't undestand why sais unknown UUID if we don't use uuid in any macro or variable.

Comment by Aigars Kadikis [ 2019 Apr 25 ]

Hi,

The item key (in colour green) - can you see the full name after "https://csavvc01.csa.local/sdk,". You can observe the full item key by:

  1. use a triple click on "Cluster name"
  2. hold down the third click
  3. move mouse to green are. it will select "Cluster name" + full item key
  4. copy the content
  5. paste the content in notepad.

Does the content after the comma contain any dashes inside?

Comment by Gerard [ 2019 Apr 29 ]

Hi Aigars, nope, the content only has a comma,

 

vmware.hv.cluster.name[https://csavvc01.csa.local/sdk,csaesxi01.csa.local]

 

If you need more info, I have this valours in server.conf to refers to vmware (we have 6 esxi in our VCenter) 
 

StartVMwareCollectors=13
VMwareFrequency=60
VMwarePerfFrequency=60
VMwareCacheSize=2048M
CacheSize=8G

 
 

Comment by Aigars Kadikis [ 2019 May 03 ]

Hi Gerard,

This look not correct:

vmware.hv.cluster.name[https://csavvc01.csa.local/sdk,csaesxi01.csa.local]

The hypervisor template should not be directly attached (involving your additional work) to any host in Zabbix. By default, if the monitoring happens by utilizing vCenter endpoint (SDK more precisely) then please install global macros:

{$URL} = https://ip.address.goes.here/sdk
{$USERNAME} = administrator@local
{$PASSWORD} = abc123qwe

Then link only one template "Template VM VMware" to the vCenter host/IP. Wait one hour for the discoveries to execute.

Comment by Gerard [ 2019 May 06 ]

OK, I haved UNLINK and CLEARED the three templates from host Virtual Center and only add a template: VM VMware (I changed the name, but is the same) and wait for 2 or 3 hours, and this is the result.

 

I tell you that in this template, we disable Discover VMware VMs, so, we only need to monitoring datastores, networks and some items, but no all VM. But

 

We found 6 esxi with autodiscover, but without data, is the same

 

 

Comment by Aigars Kadikis [ 2019 May 09 ]

Please notice what exact template gets linked through a host prototype section:

Notice what exact macro names are used in this template. Override macros in template level. By default, it should be {$URL}, {$USERNAME}, {$PASSWORD}.

P.S. Here is the stock template for 4.0: https://www.zabbix.org/websvn/wsvn/zabbix.com/tags/4.0.7/templates/classic/template_vm_vmware.xml. (3 in 1). You can delete everything and start from scratch.

Comment by Gerard [ 2019 May 09 ]

I use this macros from GLOBAL and in this template are inherited, but dont worry, I'm going to start again with this template but i can access it and download, i haven't rights

 
You do not have permission to access the requested object. The object is protected against reading, or can not be read by the server.

Please contact the webmaster in case you believe there is an error on the server.
 

can you upload here this template? thanks

Comment by Gerard [ 2019 May 21 ]

Hi, can you uplodat here this templates? thanks

Comment by Aigars Kadikis [ 2019 Nov 22 ]

The link has now changed:

https://git.zabbix.com/projects/ZBX/repos/zabbix/browse/templates/classic?at=refs%2Fheads%2Frelease%2F4.0

Here you go: template_vm_vmware.xml.

Please tell us if this solves inconsistency.

Comment by Aigars Kadikis [ 2019 Dec 17 ]

Closing due to lack of activity.

Generated at Wed May 21 06:20:53 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.