Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: ESX discovery rules

  1. #11
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: ESX discovery rules

    "VMware machine "generic-host" does not exist" that's strange. There is no generic-host hostname, only templates. Can you grep this on your configuration to see which service is using it?
    No direct support by personal message. Please open a thread so everyone can see the solution

  2. #12

    Re: ESX discovery rules

    yes ...very strange, thanks for helping me. There is my configuration :

    - lastest curl installation (1 weeks).

    - I used only ESX discovery (not nmap discovery).

    - Debian Squeeze


    resource.cfg:

    Code:
    # VMWare vCenter
    $VCENTER$=192.168.1.xx
    $VCENTERLOGIN$=root
    $VCENTERPASSWORD$=xxxxxxx
    "debian host discovery" (an ESX VM)

    Code:
    define host {
     use  vmware-vm
     host_name  debian
    }
    I add (like Matjaz) -x $PLUGINSDIR$ at the end of vmware_esx_discovery otherwise command didn't start correctyl:
    Code:
    define command{
        command_name    vmware_esx_discovery
        command_line    $USER1$/vmware_discovery_runner.py -V $VCENTER$ -u $VCENTERLOGIN$ -p $VCENTERPASSWORD$ -r "lower|nofqdn" -x $PLUGINSDIR$
    }
    /shinken/etc/packs/virtualization/vmware/esx/templates.cfg :

    Code:
    # ESX one
    define host{
      name      esx
      use      generic-host
      register    0
    }
    shinken/etc/packs/virtualization/vmware/vm/templates.cfg :


    Code:
    # VM template
    define host{
      name      vmware-vm
      use      generic-host
      register    0
    }
    i have 2 Vm (debian, shinken) and my esxI5 server (localhost), there is the WebUI output:
    Code:
    debian Cpu CRITICAL1h 8m CHECK_ESX3.PL CRITICAL - VMware machine "generic-host" does not exist 
    
     Io CRITICAL1h 10m CHECK_ESX3.PL CRITICAL - VMware machine "generic-host" does not exist 
    
     Mem CRITICAL1h 9m CHECK_ESX3.PL CRITICAL - VMware machine "generic-host" does not exist 
    
     Net CRITICAL1h 8m CHECK_ESX3.PL CRITICAL - VMware machine "generic-host" does not exist 
    
    localhost Cpu CRITICAL1h 11m CHECK_ESX3.PL CRITICAL - Host "localhost" does not exist 
    
     Io CRITICAL1h 8m CHECK_ESX3.PL CRITICAL - Host "localhost" does not exist 
    
     LocalMem CRITICAL1h 10m Memory CRITICAL - 99.0% (2330840 kB) used 
    
     Mem CRITICAL1h 8m CHECK_ESX3.PL CRITICAL - Host "localhost" does not exist 
    
     Net CRITICAL1h 10m CHECK_ESX3.PL CRITICAL - Host "localhost" does not exist 
    
    shinken Cpu CRITICAL1h 8m CHECK_ESX3.PL CRITICAL - VMware machine "shinken" does not exist 
    
     Io CRITICAL1h 10m CHECK_ESX3.PL CRITICAL - VMware machine "shinken" does not exist 
    
     Mem CRITICAL1h 10m CHECK_ESX3.PL CRITICAL - VMware machine "shinken" does not exist

    Need something else ?

  3. #13
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: ESX discovery rules

    Can be the alias thing, change HOSTALIAS in esx services pack by HOSTNAME.
    No direct support by personal message. Please open a thread so everyone can see the solution

  4. #14
    Administrator
    Join Date
    Jun 2011
    Posts
    216

    Re: ESX discovery rules

    Careful the parameter are "name" and "alias"

  5. #15

    Re: ESX discovery rules

    hi, sorry naparuba but it's not so clear for me ;D.

    Where i need to change HOSTALIAS by HOSTNAME, in all etc/packs/virtualization/vmware/vm/services/*.cfg ?

    for exemples .. there is my "cpu.cfg"

    Code:
    define service{
      service_description      Cpu
      use      generic-service
      register    0
      host_name   vmware-vm
      check_command check_esx_vm_cpu
    }

  6. #16
    Shinken project leader
    Join Date
    May 2011
    Location
    Bordeaux (France)
    Posts
    2,131

    Re: ESX discovery rules

    Sorry, it's in the check_commands, just a level higher.
    No direct support by personal message. Please open a thread so everyone can see the solution

  7. #17

    Re: ESX discovery rules

    it's works thanks !

    you should update the pack ;D.

    For information, i had another problem .. the VM name is case sentitive, during host definition you need to check the VM name on your ESXi server.



Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •