Ad Widget

Collapse

discovered virtual machines in zabbix 2.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dcvetkov
    Junior Member
    • Nov 2013
    • 3

    #1

    discovered virtual machines in zabbix 2.2

    Hi everybody!

    I am trying Zabbix first time. I set up Zabbix 2.2 because of its new VMware futures. I’ve successfully add my vCenter host, and Zabbix discovered all ESXi hosts with virtual machines. For example in hosts list I have: “Discover VMware VMs: dc1”.

    DC1 – is a Windows host. Now I have a problem – I cannot add agent interface to dc1, I cannot add Windows template to dc1, and of course, I cannot add another host manually with the same name.

    Please, help me. What should I do to monitor DC1 with standard Windows template through agent interface?
  • dcvetkov
    Junior Member
    • Nov 2013
    • 3

    #2
    Nobody answers because of my bad english or because of silly question?

    Comment

    • tchjts1
      Senior Member
      • May 2008
      • 1605

      #3
      Your English is fine, and it isn't a silly question.

      VMWare monitoring is new functionality that was just released, so you will either have to wait until someone else experiences this, or if you feel that it is a bug, you can open a ticket in bug tracker here: https://support.zabbix.com/

      You have to create an account. It doesn't hook in to your forum account.

      Comment

      • captainmish
        Junior Member
        • Nov 2013
        • 6

        #4
        I'm having the same issue - I found that if I clone the discovered host, give it a different name and hostname, i can use this as a "normal" host, but now I see 2 entries for the host: 1 for discovered, 1 for the clone I made. Is there a better way to modify discovered hosts?

        Comment

        • TribesTom
          Junior Member
          • Nov 2013
          • 4

          #5
          I have the same problem here

          Post here but no response : https://www.zabbix.com/forum/showthread.php?t=43348

          Comment

          • bsteph
            Junior Member
            • Sep 2012
            • 15

            #6
            Ditto here but I think I have a workaround

            I ran into the same problem but here's how I'm working around it. In the "discovered" hosts, created by the vmware discovery, I grab the hostname that looks like a uuid, then in the real host I create a macro {$HOSTUUID} and set it equal to the UUID. I add in the other macros (url, username and password). In the template I replace HOST.HOST with {$HOSTUUID} and that seems to work.

            Comment

            Working...