Support for VMware checks was not compiled in zabbix 3.0.7

[vsimoes]

I recently deployed Zabbix 3.0.7 and i am facing an issue when trying to monitor VMWare ESXi 5.5 hosts through SNMP.

"Support for VMware checks was not compiled in."

This happens for some itens, like CPU Usage and others, but the datastore free space for example is working just fine.

I am using Zabbix VMWare built-in template.

Check this image

[glebs.ivanovskis]

Have you compiled Zabbix yourself or installed from packages?

[Atsushi]

If you installed from the source, did you specify the option(--with-libcurl and --with-libxml2) when running configure?

It can be confirmed in the log when starting Zabbix server.
If it is a Zabbix server that can be monitored by VMware, the following log will be output.

  2898:20170220:095155.111 VMware monitoring:         YES

Make sure to set StartVMwareCollectors in zabbix_sever.conf even if it is YES.

And, The Template Virt VMware will then use VMware's service interface instead of SNMP.

https://www.zabbix.com/documentation/3.0/manual/vm_monitoring

[vsimoes]

Rpm

Have you compiled Zabbix yourself or installed from packages?

Hello brother, i did used this RPM:

rpm -ivh http://repo.zabbix.com/zabbix/3.0/rh...el7.noarch.rpm

[vsimoes]

Check this out

If you installed from the source, did you specify the option(--with-libcurl and --with-libxml2) when running configure?

I used this RPM, i did not specify anything:

rpm -ivh http://repo.zabbix.com/zabbix/3.0/rh...el7.noarch.rpm

It can be confirmed in the log when starting Zabbix server.
If it is a Zabbix server that can be monitored by VMware, the following log will be output.

  2898:20170220:095155.111 VMware monitoring:         YES

Ok, there is the log:

****** Enabled features ******
808:20170301:161403.733 SNMP monitoring: YES
808:20170301:161403.733 IPMI monitoring: YES
808:20170301:161403.733 Web monitoring: YES
808:20170301:161403.733 VMware monitoring: YES
808:20170301:161403.733 SMTP authentication: YES
808:20170301:161403.733 Jabber notifications: YES
808:20170301:161403.733 Ez Texting notifications: YES
808:20170301:161403.733 ODBC: YES
808:20170301:161403.733 SSH2 support: YES
808:20170301:161403.733 IPv6 support: YES
808:20170301:161403.733 TLS support: YES
808:20170301:161403.733 ******************************

Make sure to set StartVMwareCollectors in zabbix_sever.conf even if it is YES.

Here is the server.conf (vmware lines)

### Option: StartVMwareCollectors
# Number of pre-forked vmware collector instances.
#
# Mandatory: no
# Range: 0-250
# Default:
StartVMwareCollectors=1

### Option: VMwareFrequency
# How often Zabbix will connect to VMware service to obtain a new data.
#
# Mandatory: no
# Range: 10-86400
# Default:
VMwareFrequency=10

### Option: VMwarePerfFrequency
# How often Zabbix will connect to VMware service to obtain performance data.
#
# Mandatory: no
# Range: 10-86400
# Default:
VMwarePerfFrequency=15

And, The Template Virt VMware will then use VMware's service interface instead of SNMP.

I am using SNMP set on host configuration, it might be the problem?

Check the image: http://imgur.com/a/3eDoj

https://www.zabbix.com/documentation.../vm_monitoring

I am gonna try this!

[vsimoes]

Proxy maybe?

Guys, something i forgot to share: I am using PFSense Proxy and in the proxy i got the following log message:

**** Enabled features ****
31698:20170301:140849.115 SNMP monitoring: YES
31698:20170301:140849.115 IPMI monitoring: NO
31698:20170301:140849.115 Web monitoring: YES
31698:20170301:140849.115 VMware monitoring: NO
31698:20170301:140849.115 ODBC: YES
31698:20170301:140849.115 SSH2 support: NO
31698:20170301:140849.115 IPv6 support: YES
31698:20170301:140849.115 TLS support: YES
31698:20170301:140849.115 **************************

The problem might be the proxy that do not support vmware monitoring? The thing is, does PFSense Zabbix Proxy support it at all?

[Atsushi]

If you are monitoring via that Proxy, I think that you can not monitoring of VMware.

[vsimoes]

Conclusion

All right, after a long and deep research i could find the following conclusion:

We cannot use PFSense as proxy if you have VMWare, their current proxy package does not support vmware, so the solution i found was to have a centos dedicated proxy for vmware hosts.