VMware discovery not finding all guests

[jscheller]

I'm running Zabbix 2.4.4 on Cent 6.6 and recently decided to try the native VMware polling functionality. I was able to point the Virt_VMware template to my vsphere system and it successfully found my hypervisors and cluster fine. It promptly found several guests that I have configured but not ALL of them. I've been racking my head trying to figure out why. It discovers new guests as I add them, and the existing guests that it is unable to discover are the same virtual machine version and vmware tools versions as other guests that it discovered fine.

I even went as far to point the template directly to the Hypervisor as opposed to vsphere and it still only discovered the same handful of guests.

Vsphere and my hypervisors are all running 5.5 and fully patched.

I have been unable to find any errors in the zabbix_server log and the VMware poller process or cache is not being heavily utilized.

I'm not sure if my issue is related to VMware and the possibility that these guests may have been cloned at one point or if there is a bug with the discovery rule. I'm curious if anyone else has experienced a similiar issue?

[jscheller]

Wow, no one? I figured someone would have seen something like this previously. I can't be that special.

[acropia]

I just configured VMware discovery this morning, and for quick discovery I decreased the time from 3600 to 300 secs. An hour later I already had hundreds of discovered guests.

I will check again tomorrow and will update over here if hosts are missing at my setup too.

[jscheller]

Figured it out. Kind of stupid really. I have been running and upgrading this Zabbix instance for 5 plus years and as a result, I had the Zabbix agent running directly on the guest OS. Therefore there were duplicate hosts so the discovery was unable to add all the hosts. The hosts that it was able to add were capitalized either in vsphere or in zabbix, so there was no duplicates.

Kind of annoying that nothing showed up in the discovery logs.