Ad Widget

Collapse

Zabbix 2.2 - VMware discovery not working

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dedisoft
    Junior Member
    • Dec 2013
    • 18

    #1

    Zabbix 2.2 - VMware discovery not working

    Hello all,

    I've read some posts and the manual to configure Zabbix to monitor an ESXi 5.5.

    Zabbix is on physical server, not virtualized.

    I've assigned the Hypervisor Template, modified Zabbix server configuration with 2 collectors, and created the needed macros.

    I've checked HTTPS access with a browser (using Zabbix credential), and the information returned was ok.

    But discovery seems to not work, on Zabbix server log file I can see :

    vmware.hv.datastore.discovery[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.cluster.name[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.fullname[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.cpu.freq[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.cpu.model[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.cpu.num[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.cpu.threads[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.memory[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.model[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.uuid[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.hw.vendor[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.uptime[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.version[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported
    vmware.hv.vm.num[{$URL},{HOST.HOST}]] became not supported: Simple check is not supported

    We actually use self signed certificate on ESXi, is this can be the reason of these errors ?

    Regards,
  • dedisoft
    Junior Member
    • Dec 2013
    • 18

    #2
    Strange behavior I've modified nothing and all VMs are discovered now...

    Comment

    • tchjts1
      Senior Member
      • May 2008
      • 1605

      #3
      Interesting.

      But... anything associated with Discovery rules can take upwards of an hour to actually kick in. That will also be the case if you make any changes or additions to them as well.

      Comment

      • dedisoft
        Junior Member
        • Dec 2013
        • 18

        #4
        Originally posted by tchjts1
        anything associated with Discovery rules can take upwards of an hour to actually kick in.
        I agrees but why having these messages :

        [QUOTE]became not supported: Simple check is not supported[QUOTE]

        ?

        Comment

        • tchjts1
          Senior Member
          • May 2008
          • 1605

          #5
          I think that when you assign a template to a host, or add a new item, Zabbix assumes at first it is Supported. But then when the item doesn't send data back in the specified period of time, it goes into the Unsupported state.

          Probably a more appropriate status would be "Pending" if an item is part of a Discovery rule, then go to Unsupported after like an hour of no data.

          Comment

          Working...