Hi, 

Everything in the centreon_vmware.json configuration file and in the logs seem normal to me. The listening process is OK too.

To monitor your physical ESX hosts, you don’t need to declare them in the config file, you can get all the information from the vCenter. I mean you could simplify your config file this way:

{
    "vsphere_server": e
        {
            "name": "default",
            "url": "https://x.x.x.x/sdk",
            "username": "xx@xx.local",
            "password": "xxx"
        }
    ],
    "port": 5700
}

And let default (which is the default value) as the container for all your hosts, and just fill the ESXNAME macro.

You may refer to this part of the documentation to configure your hosts correctly and if you have an IT license, remember you can discover your hosts automatically. This will spare you the configuration of your hosts (you just need to configure the daemon as suggested above).

Bonjour ​@omercier 

Merci pour votre contribution concernant la partie VMware.

La configuration dans le fichier centreon_vmware.json a été appliquée.

Le modèle Virt-VMWare2-VCenter-6-custom ne contient pas la macro ESXNAME (mais CENTREONVMWARECONTAINER).
Doit-on utiliser le modèle Virt-VMWare2-ESX-custom pour le vCenter et les ESX associés ?

______________________

Hi ​@omercier 

Thank you for your contribution concerning the VMware part.

The configuration in the centreon_vmware.json file has been applied.

The Virt-VMWare2-VCenter-6-custom template does not contain the ESXNAME macro (but CENTREONVMWARECONTAINER).
Should we use the Virt-VMWare2-ESX-custom template for the vCenter and associated ESXs ?

Hi,

Use:

• Virt-VMWare2-VCenter-6-custom for the vCenter
• Virt-VMWare2-ESX-custom for the ESX hosts with ESXNAME equal to the host’s name
• Virt-VMWare2-VM-custom for the virtual machines with VMNAME equal to the vm’s name

All with the same CENTREONVMWARECONTAINER value: default.

​@dacodac there’s a tutorial here

Merci ​@omercier 
Nous sommes partis sur une découverte automatique. 
Les hôtes ESX ont été découverts.

Cependant un message d'erreur est apparu : 

UNKNOWN: Cannot get counter 'mem.state.latest' for the sampling period '300' (counter level: 2, sampling level: 1)

Après une recherche, nous avons vu qu'il fallait modifier le niveau de 1 à 2 dans les paramètres généraux (Statistiques) depuis l'interface du client vSphere du vCenter.

2.3.0] - unable to check memory/network ESX host · Issue #31 · centreon/centreon-vmware
Nous avons plusieurs valeurs, laquelle est à modifier ?

En parallèle, nous n'avons pas reçu une réponse concernant les messages d'erreur côté plugin Veeam. 

__________________________

Thank you ​@omercier 
We started with automatic discovery. 
ESX hosts have been discovered.

However, an error message appeared: 

UNKNOWN: Cannot get counter 'mem.state.latest' for the sampling period '300' (counter level: 2, sampling level: 1)

After some research, we saw that we needed to change the level from 1 to 2 in the general settings (Statistics) from the vSphere Client interface on the vCenter.

r2.3.0] - unable to check memory/network ESX host · Issue #31 · centreon/centreon-vmware
We have several values, which one should we change ?

At the same time, we haven't received a response regarding the error messages on the Veeam plugin side.

Bonjour, 

Je ne peux pas vous aider si vous ne faites pas attention a la commande.
Si votre process est 290847/perl 
Alors il ne faut pas faire avec “grep 2900847” mais avec “grep 290847”

A+

Bonjour ​@fzim 

Merci pour votre réponse et implication sur ce sujet.
Le processus a évolué entre temps, c'est pour cette raison que je n’ai pas repris la toute première valeur partagée.
A moment où je rédige ce message la sortie est la suivante :

# netstat -tulnp | grep 5700

tcp        0      0 0.0.0.0:5700            0.0.0.0:*               LISTEN      425078/perl

# ps -ef | grep 425078

centreon  425078       1  0 avril08 ?      00:00:04 /usr/bin/perl /usr/bin/centreon_vmware.pl --config-extra=/etc/centreon/centreon_vmware.json --logfile=/var/log/centreon/centreon_vmware.log --severity=info
centreon  425086  425078  0 avril08 ?      00:00:20 /usr/bin/perl /usr/bin/centreon_vmware.pl --config-extra=/etc/centreon/centreon_vmware.json --logfile=/var/log/centreon/centreon_vmware.log --severity=info
root      505097  504622  0 08:13 pts/0    00:00:00 grep --color=auto 425078

_______________

Hi ​@fzim 

Thank you for your response and involvement in this matter.
The process has evolved in the meantime, which is why I haven't included the very first shared value.
At the time of writing the output is as follows :

# netstat -tulnp | grep 5700

tcp 0 0 0.0.0.0:5700 0.0.0.0:* LISTEN 425078/perl

# ps -ef | grep 425078

centreon  425078       1  0 avril08 ?      00:00:04 /usr/bin/perl /usr/bin/centreon_vmware.pl --config-extra=/etc/centreon/centreon_vmware.json --logfile=/var/log/centreon/centreon_vmware.log --severity=info
centreon  425086  425078  0 avril08 ?      00:00:20 /usr/bin/perl /usr/bin/centreon_vmware.pl --config-extra=/etc/centreon/centreon_vmware.json --logfile=/var/log/centreon/centreon_vmware.log --severity=info
root      505097  504622  0 08:13 pts/0    00:00:00 grep --color=auto 425078

Pour Veeam, nous sommes confrontés à ce message d’erreur ​@omercier 

Failed to execute check_centreon_plugins seems more like a script maybe you need a script executable first: failed to lookup error code: 193 (reason: 126)

Version utilisée Veeam Backup and Replication 11.

Répertoire du module PowerShell Veeam C:\Program Files\Veeam\Console\Veeam.Backup.PowerShell

Centreon-NSClient-0.5.2.41-20240909-x64 sur serveur Windows Serveur 2019.

#/usr/lib64/nagios/plugins/check_centreon_nrpe3 -H x.x.x.x -p 5666 -t 55  -c check_centreon_plugins -a 'apps::backup::veeam::local::plugin' 'tape-jobs'  ' \
        --filter-name="" \
        --warning-status="" \
        --critical-status="%\{enabled\} == 1 and not %\{last_result\} =~ /Success|None/i" \
        --warning-total="" \
        --critical-total="" \
        --verbose'

CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).

VEEAM - job-status - CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected). | Community

Merci à vous et à toute la communauté.

______________

For Veeam, we are facing this error message

Failed to execute check_centreon_plugins seems more like a script maybe you need a script executable first: failed to lookup error code: 193 (reason: 126)

Version used Veeam Backup and Replication 11.

Veeam PowerShell module directory C:\Program Files\Veeam\Console\Veeam.Backup.PowerShell

Centreon-NSClient-0.5.2.41-20240909-x64 on Windows Server 2019.

#/usr/lib64/nagios/plugins/check_centreon_nrpe3 -H x.x.x.x -p 5666 -t 55  -c check_centreon_plugins -a 'apps::backup::veeam::local::plugin' 'tape-jobs'  ' \
        --filter-name="" \
        --warning-status="" \
        --critical-status="%\{enabled\} == 1 and not %\{last_result\} =~ /Success|None/i" \
        --warning-total="" \
        --critical-total="" \
        --verbose'

CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected).

VEEAM - job-status - CHECK_NRPE: Receive header underflow - only 0 bytes received (4 expected). | Community

Thanks to you and to the whole community.