For monitor standalone ESXi, mou must previously get UUID of ESXi host and then set it as variable in Zabbix and modify "VMWare Hypervisor" template, because Zabbix uses UUID, not hostname, for identify ESXi host.
Ad Widget
Collapse
VMWare monitoring, Timeout was reached
Collapse
X
-
Resolved/problem isolated
Hi.
I have just setup a new vcenter on a windows 2008 R2 server and - bing - Everything works!
Im not sure, but i think the problem can be isolated to only affect the virtual appliance.Comment
-
Well i don't agree on that - I don't say that it's a Zabbix bug. It could be a unexpected behavior in the vSphere vCenter Appliance.
Im my case the environment is exactly the same, 60 VM's, 6 Hosts - The only thing changed is replacing the vCenter from the appliance version to the Windows version.Comment
-
With VCSA 5.5 => Timeout was reached but with VCSA 5.1 all items are ok
Perhaps two ways to resolve it : SSO has been changed since 5.1 / upgrade curl ?Comment
-
I was unable to connect directly to a 5.1 ESXi Host, but when I brought up the 5.5 appliance and added server to that, I'm not able to get zabbix to pull information from vcenter 5.5
I can see info from the hypervisor and VM's in "latest data" but there is no hypervisor category and no vm's listed in graphs. I would love to figure this out... Been at it for 3 days and there is absolutely no helpful information online. = \Comment
-
I'm trying to configure this at the moment so sorry about the bump.
I am able to ping and connect to the VC and each ESX host however I can't get zabbix to show any data.
The error i get is "failed to query VMware service: Cannot parse performance counter list." the start item is replaced by whichever item is failing and at the moment it is all of them.
I don't get it, how can I test to see if my user is able to query the VC?
I am running Zabbix 2.4.5 and VC 5.5Comment
Comment