Page History

Overview

The VMware module will connect to a vSphere server.

• it will detect automatically any new Virtual machines and ESX hypervisors.
• it will collect data from the ESX and Vitual machines.

Configuration

To define a VMware source module:

1. You must declare Configure the VMware module in the filefile /etc/shinken/synchronizersmodule/synchronizersync-mastervmware.cfg.
   to define the behaviour of the module
2. Then configure the source in the file /etc/shinken/sources/sync-vmware.cfg
   to enable the source. and call the module configured in step 1.
3. Then configure you must declare the VMware source in the file file /etc/shinken/modulesynchronizers/syncsynchronizer-vmwaremaster.cfg
   to define the behaviour of the module (linked to the module defined
   .
   
   
   

sources/sync-vmware.cfg

module/sync-vmware.cfg

Here is the list of parameters required by the module to be updated the in cfg file.

Here there an example of the module definition:

define module{
  enable           1
  module_name      sync-vmware
  module_type      sync-vmware
  check_esx_path   /var/lib/shinken/libexec/synchronizer/esx_discovery.pl
  vcenter          myesx.ovh.com
  user             admin
  password         XYZ
  esx_templates    esx
  vm_templates     vmware-vm
}

Automatic templates for Virtual Server based on their OS

Some host templates are automatically added to the detected Virtual Server, based on the value set on the vSphere data
(VM definition and/or the VMware tools).

Here is the list of the host templates that may be automatically attached to a host detected in an ESX:

• centos

• debian

• debian5

• debian6

• fedora

• linux

• oracle-linux

• redhat

• redhat4

• redhat5

• redhat6

• windows

• windows-datacenter

• windows-enterprise

• windows2000

• windows2003

• windows2008

• windows2008r2

• windows2012

• windows7

• windowsnt

• windowsvista

• windowsxp

Mutilple vSphere

=> Define an additional VMware source module. You can have has many VMware source module as you needAs a source/module can talk to one vSphere server only, in order to take data from numerous vSphere servers, you must define as many source/module as your vSpheres instances.

To add an ESX to link your monitoring environmentsolution to a new vSphere, you must:

1. Duplicate the cfg file
   source and modules configuration files (.cfg), for example:
   
   • /etc/shinken/modules/for exemple, sync-vmware.cfg => /etc/shinken/modules/sync-vmware-EU.cfg
   • /etc/shinken/sources/sync-vmware.cfg => /etc/shinken/sources/sync-vmware-EU.cfg
     
     
     
2. Update parameters inside your new module in the file /etc/shinken/modules/sync-vmware-EU.cfg pointing to the new ESXvSphere server:
   • at least, you need to change module_name and vcenter parameters
     
     • => module_name    sync-vmware_EU
     • => vcenter               myesx-EU.ovh.com
3. Update parameters inside your new source in the file /etc/shinken/sources/sync-vmware-EU.cfg pointing to your new module:
   • at least, you need to change source_name and modules parameters
     
     • => source_name    sync-vmware_EU
     • => modules             sync-vmware_EU
   
   
   
4. Declare your new source in the synchronizer daemon. Edit the file /etc/shinken/synchronizers/synchronizer-master.cfg

   • Edit the line sources   :

     • sources               syncui,cfg-file-shinken,active-dir,sync-vmware,sync-vmware-EU,cfg-file-nagios,discovery
       
       

5. Restart Then you can restart the synchronizer

   • => service shinken restart synchronizersynchronizer