Ad Widget

Collapse

Problem monitoring vmware server

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • john_s
    Junior Member
    • Aug 2014
    • 2

    #1

    Problem monitoring vmware server

    I'm trying to monitor a server running esxi 5.0.0 (stand-alone, free hypervisor)
    I installed zabbix and it seems to be running ok. (version 2.2.5)

    I manually added a host configuration for my vmware machine.
    I linked 'Template Virt Vmware' to my host.
    Discovery reported an error - I forget - something about HOST.HOST

    I saw this thread


    It mentioned changing {HOST.HOST} to {$UUID}
    I exported 'Template Virt Vmware Hypervisor', changed {HOST.HOST} to {$UUID}, changed the name to 'Template Virt Vmware Hypervisor2', and imported it.
    I unlinked 'Template Virt Vmware' and linked 'Template Virt Vmware2' to my host.
    I created a macro for my host's UUID.
    It successfully connected to the vmware host and populated a list of the virtual machines (in configuration / host).
    But now there are messages in /var/log/zabbix like this:
    vmware host:vmware.hv.datastore.discovery[{$URL},{HOST.HOST}] changed: unknown hypervisor uuid

    I'm new to zabbix, so can someone explain what is going on?
    Should it work with vmware stand-alone, free hypervisor?
    Do I have something configured wrong?
    Or is that a limitation of the existing system?
    If I want to monitor several vmware servers, do I have to manually set them up with their UUID?
    Any words of wisdom would be greatly appreciated.
    Thanks
  • aib
    Senior Member
    • Jan 2014
    • 1615

    #2
    Well, I did it like it was described in documentation.
    1) Create vSphere host
    2) Add 3 macros:
    - {$USERNAME} - username which has an administrative privileges on VMware
    - {$PASSWORD) - password for username
    - {$URL} - https://10.10.10.10/sdk (where 10.10.10.10 is the address of vSphere host, not VMware supervisor)
    3) Add 3 templates to vSphere host:
    - Template Virt VMware
    - Template Virt VMware Guest
    - Template Virt VMware Hypervisor

    4) Waited for a couple of hours (lunch/over night/take a vacation) and I got all my hypervisors/guest machines discovered)

    Where is your problem on that short way?
    Sincerely yours,
    Aleksey

    Comment

    • john_s
      Junior Member
      • Aug 2014
      • 2

      #3
      still odd

      I deleted the discovered hosts and started over
      I did what you said except in step 3 I just linked the template virt vmware
      (the docs say not to link the other 2)
      After a while it got a list of my vm guests.
      So now I have 2 questions:
      1. The log file has some messages like : vmware.vm.memory.size.private[{$URL},{HOST>HOST}] became not supported: value is not available.
      Is that normal?
      (some of my vm's are off - could that be the cause?)

      2. under configuration / hosts, I have entries for my vm's like this:
      Discover VMware VMs: guest 1
      Discover VMware VMs: guest 2
      On the right hand side, the 'availability' column has 4 greyed out icons.
      Is that right?

      Thanks!

      Comment

      • aib
        Senior Member
        • Jan 2014
        • 1615

        #4
        - Did your discovery process found all Hypervizors?
        - It's correct to have greyed icon "availability", because you don't have any Zabbix Agent installed on Discovered Guests.
        - Yes, some of Items are unavailable in my configuration also. I don't know why.
        Sincerely yours,
        Aleksey

        Comment

        • Pro21
          Junior Member
          • Jun 2008
          • 13

          #5
          Hello,

          Maybe I come after the war but I've fighed a couple of hours before understand how to setup an ESXI monitoring.
          Below a simple process to handle a working monitoring.

          Replace in the template Template Virt VMware Hypervisor all variable {HOST.HOST} by {$UUID}.
          Add macro as explain ($USERNAME, $PASSWORD, $URL) and the last macro $UUID.
          $UUID can be obtain by requesting the hypervisor webservices like https://hostnamme/mob/?moid=ha-host&...are.systemInfo You will see data like uuid "320d4e35-b3fd-11e3-a216-6cae8b33fc28" where string between "" is the data to used in $UUID macro.

          After the trick the monitoring is working ... Last thing change also {HOST.HOST} to {$UUID} in the autodiscover menu of the template.

          Good Luck
          Last edited by Pro21; 08-09-2015, 16:22.

          Comment

          • renanmvc
            Junior Member
            • Feb 2014
            • 12

            #6
            aonde encontro o uuid?

            Originally posted by Pro21
            Hello,

            Maybe I come after the war but I've fighed a couple of hours before understand how to setup an ESXI monitoring.
            Below a simple process to handle a working monitoring.

            Replace in the template Template Virt VMware Hypervisor all variable {HOST.HOST} by {$UUID}.
            Add macro as explain ($USERNAME, $PASSWORD, $URL) and the last macro $UUID.
            $UUID can be obtain by requesting the hypervisor webservices like https://hostnamme/mob/?moid=ha-host&...are.systemInfo You will see data like uuid "320d4e35-b3fd-11e3-a216-6cae8b33fc28" where string between "" is the data to used in $UUID macro.

            After the trick the monitoring is working ... Last thing change also {HOST.HOST} to {$UUID} in the autodiscover menu of the template.

            Good Luck
            aonde encontro esse UUID?
            Esse link acima está indisponível

            Comment

            • spritluo520
              Junior Member
              • Sep 2016
              • 2

              #7
              unknown virtual machine uuid

              hi all:
              My ZABBIX is 2.4.8, I am ready to monitor the esxi host, but there are several monitoring items show "virtual machine UUID unknown", I would ask what is the problem

              Comment

              • hernan
                Member
                • Sep 2016
                • 67

                #8
                Hello guys,

                I have the same error with Zabbix 3.2.4 and VCenter 5.5.

                Can you help me with this?

                Thanks in advance.

                Regards.

                Comment

                • DanielB
                  Junior Member
                  • Jun 2017
                  • 3

                  #9
                  This error only happen in an stand alone ESX host (at least that i have tested). As @Pro21 said, you have to put the UUID as a macro variable, if you get an error trying to enter to the URL https://<hostname>/mob/?moid=ha-host&doPath=hardware.systemInfo, you have check if your ESX has enabled The Managed Object Browser feature (VMWARE KB: https://kb.vmware.com/selfservice/mi...rnalId=2108405). Apart of that, everything is working fine.

                  Thanks @Pro21 for your help.

                  Comment

                  • DanielB
                    Junior Member
                    • Jun 2017
                    • 3

                    #10
                    Originally posted by Pro21
                    Hello,

                    Maybe I come after the war but I've fighed a couple of hours before understand how to setup an ESXI monitoring.
                    Below a simple process to handle a working monitoring.

                    Replace in the template Template Virt VMware Hypervisor all variable {HOST.HOST} by {$UUID}.
                    Add macro as explain ($USERNAME, $PASSWORD, $URL) and the last macro $UUID.
                    $UUID can be obtain by requesting the hypervisor webservices like https://hostnamme/mob/?moid=ha-host&...are.systemInfo You will see data like uuid "320d4e35-b3fd-11e3-a216-6cae8b33fc28" where string between "" is the data to used in $UUID macro.

                    After the trick the monitoring is working ... Last thing change also {HOST.HOST} to {$UUID} in the autodiscover menu of the template.

                    Good Luck
                    This error only happen in an stand alone ESX host (at least that i have tested). As @Pro21 said, you have to put the UUID as a macro variable, if you get an error trying to enter to the URL https://<hostname>/mob/?moid=ha-host&doPath=hardware.systemInfo, you have check if your ESX has enabled The Managed Object Browser feature (VMWARE KB: https://kb.vmware.com/selfservice/mi...rnalId=2108405). Apart of that, everything is working fine.

                    Thanks @Pro21 for your help.

                    Comment

                    • maciejhpl
                      Junior Member
                      • Dec 2017
                      • 1

                      #11
                      Hello,

                      Replace in the template Template Virt VMware Hypervisor all variable {HOST.HOST} by {$UUID}.
                      Add macro as explain ($USERNAME, $PASSWORD, $URL) and the last macro $UUID.
                      $UUID can be obtain by requesting the hypervisor webservices like https://hostnamme/mob/?moid=ha-host&...are.systemInfo You will see data like uuid "320d4e35-b3fd-11e3-a216-6cae8b33fc28" where string between "" is the data to used in $UUID macro.
                      you don't have to do that

                      when you add new host in zabbix

                      Host name: 320d4e35-b3fd-11e3-a216-6cae8b33fc28
                      Visible name: esxi-name

                      {HOST.HOST} = "Host name"

                      Comment

                      • magicker
                        Junior Member
                        • Apr 2019
                        • 5

                        #12
                        if it helps you can get the uuid from the cli of an esxi server with :
                        esxcli system uuid get

                        My problem is that none of these rules seem to get actual information about the metrics of the ESXI host eg cpu / ram etc just info on the guest.. am I missing something?

                        Comment

                        • r3wt3d
                          Junior Member
                          • Feb 2021
                          • 1

                          #13
                          I know it's old thread but there were no correct answer to this problem, so I leave the solution here.

                          You need to write the InstanceUUID to the HOST and not the UUID you can get it from the vCenter vm list.

                          To receive the correct InstanceUUID use this script below I found on the web or get it from /mob.

                          Script:
                          vCenterからESXiと仮想マシンの情報を取得してExcelファイルで出力するツール. Contribute to sky-joker/vmware-InvEx development by creating an account on GitHub.


                          From /mob:

                          Comment

                          • danthemann
                            Junior Member
                            • Mar 2022
                            • 10

                            #14
                            Old thread but this is not working for me.

                            I am still getting the unknown hypervisor UUID after confirming I have the correct Hypervisor UUID, username, password, URL.
                            Click image for larger version

Name:	image.png
Views:	5469
Size:	7.1 KB
ID:	450708
                            Click image for larger version

Name:	image.png
Views:	5556
Size:	33.3 KB
ID:	450709

                            SDK soap is running (on by default)
                            https://SERVERIP/sdk/vimService.wsdl
                            Click image for larger version

Name:	image.png
Views:	5391
Size:	5.8 KB
ID:	450710

                            {$VMWARE.HV.UUID} is correct.

                            UUID is same both from esxcfg-info -u |awk '{print tolower($0)}'
                            ​and web (https://SERVERIP/mob/?moid=ha-host&d...are.systemInfo)

                            Click image for larger version

Name:	image.png
Views:	5387
Size:	27.7 KB
ID:	450711



                            I have waited 24 hours.
                            I have tried removing the template and re-adding.
                            Tried with the VMware template, tried setting the variable as {$VMWARE.UUID} or {$VMWARE.VM.UUID}

                            Tried this on 3 hypervisors.
                            One esx 5.5 and 2 on 6.5.

                            Tried with both read-only accounts and ESX root account.

                            /etc/zabbix/zabbix_server.conf:
                            ​StartVMwareCollectors=5
                            ​VMwareCacheSize=64M


                            any thoughts or suggestions?

                            Comment

                            • danthemann
                              Junior Member
                              • Mar 2022
                              • 10

                              #15
                              Running on Zabbix 6.2.

                              Note, these are standalone ESXi hosts (merely trying to monitor datastores for events).

                              I believe the InstanceUUID solution (one post above mine) will correct if a VM instance UUID has same UUID as a hypervisor.
                              When I navigate the MOB I see no duplicate and would be extremely hesitant to run the reconfigureVM method to change VM instance UUIDs.

                              in 5.5 vsphere client its easy to see the virtual guest (InstanceUUID) to see there is no conflict with the HV UUID.

                              Click image for larger version  Name:	image.png Views:	0 Size:	31.2 KB ID:	450714​​​

                              Anyone else having any problems with VMware hypervisor templates on standalone ESX hosts ?
                              Last edited by danthemann; 31-08-2022, 18:14.

                              Comment

                              Working...