Announcement

Collapse
No announcement yet.

Problem monitoring vmware server

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    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
    https://www.zabbix.com/forum/showthr...ghlight=vmware

    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

    #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


      #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


        #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


          #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


            #6
            aonde encontro o uuid?

            Originally posted by Pro21 View Post
            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


              #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


                #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


                  #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


                    #10
                    Originally posted by Pro21 View Post
                    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


                      #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

                      Working...
                      X