+ Update documentation

This commit is contained in:
garnier-quentin 2015-07-20 16:27:50 +02:00
parent fe9398e88d
commit 90481a4edf
2 changed files with 88 additions and 1 deletions

View File

@ -65,6 +65,42 @@ In case you have many VirtualCenters, the configuration is (note the use of ","
}
);
'other' and 'default' are containers name.
Client Usage
------------
Check vmtools states of virtual machines (with name matching the regexp 'prd'):
::
$ perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=tools-vm --display-description --vm-hostname='prd' --filter
WARNING: 1 VM with VMTools not installed |
vmtools not installed:
prd-Reporting - 10.0.0.1 [description xxxx]
Check datastore IOPs of virtual machines (with name matching the regexp 'centreon-central-1|Formation'):
::
$ perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=datastore-vm --vm-hostname='centreon-central-1|Formation' --filter
OK: All Datastore IOPS counters are ok | 'riops_Formation-Reporting - 10.30.2.89_R&D-BI'=0.00iops;;;0; 'wiops_Formation-Reporting - 10.30.2.89_R&D-BI'=1.43iops;;;0; 'riops_centreon-central-1_INTEGRATION'=0.00iops;;;0; 'wiops_centreon-central-1_INTEGRATION'=0.60iops;;;0;
'Formation-Reporting - 10.30.2.89' read iops on 'R&D-BI' is 0.00
'Formation-Reporting - 10.30.2.89' write iops on 'R&D-BI' is 1.43
'centreon-central-1' read iops on 'INTEGRATION' is 0.00
'centreon-central-1' write iops on 'INTEGRATION' is 0.60
Check the health of ESX Servers:
::
$ perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=health-host --esx-hostname='.*' --filter --disconnect-status='ok'
OK: All ESX health checks are ok | 'problems_srvi-clus-esx-n2.merethis.net'=0;;;0;299 'problems_srvi-clus-esx-n1.merethis.net'=0;;;0;299 'problems_srvi-clus-esx-n4.merethis.net'=0;;;0;186 'problems_srvi-clus-esx-n3.merethis.net'=0;;;0;186
Checking srvi-clus-esx-n2.merethis.net
299 health checks are green
Checking srvi-clus-esx-n1.merethis.net
299 health checks are green
Checking srvi-clus-esx-n4.merethis.net
186 health checks are green
Checking srvi-clus-esx-n3.merethis.net
186 health checks are green
Troubleshooting
---------------
@ -74,4 +110,12 @@ It is possible to get this kind of errors in the « logs » of « centreon-vm
...SOAP request error - possibly a protocol issue: read failed: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac...
VMWare Perl SDK sometimes generates this error that does not alter the behaviour of the connector. The bug comes from OpenSSL. It should be fix in OpenSSL 1.0.1h (CVE-2010-5298).
VMWare Perl SDK sometimes generates this error that does not alter the behaviour of the connector. The bug comes from OpenSSL. It should be fix in OpenSSL 1.0.1h (CVE-2010-5298).
You can have the following error returns by the connector:
::
# perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin ...
Cannot get value for counters...
Please check that your VirtualCenter and ESX time synchronization. Most of the time, the server with the connector and/or VirtualCenter/ESX are not well synchronized.

View File

@ -66,6 +66,42 @@ Dans le cas ou il y a plusieurs VirtualCenters, la configuration devient (noter
}
);
'other' et 'default' sont des containeurs.
Client Usage
------------
Vérifie l'état des VMTools des machines virtuelles avec 'prd' dans leur nom:
::
$ perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=tools-vm --display-description --vm-hostname='prd' --filter
WARNING: 1 VM with VMTools not installed |
vmtools not installed:
prd-Reporting - 10.0.0.1 [description xxxx]
Vérifie les IOPs des machines virtuelles (avec 'centreon-central-1|Formation' dans leur nom. Cela est une expression régulière) sur leurs datastores:
::
$ perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=datastore-vm --vm-hostname='centreon-central-1|Formation' --filter
OK: All Datastore IOPS counters are ok | 'riops_Formation-Reporting - 10.30.2.89_R&D-BI'=0.00iops;;;0; 'wiops_Formation-Reporting - 10.30.2.89_R&D-BI'=1.43iops;;;0; 'riops_centreon-central-1_INTEGRATION'=0.00iops;;;0; 'wiops_centreon-central-1_INTEGRATION'=0.60iops;;;0;
'Formation-Reporting - 10.30.2.89' read iops on 'R&D-BI' is 0.00
'Formation-Reporting - 10.30.2.89' write iops on 'R&D-BI' is 1.43
'centreon-central-1' read iops on 'INTEGRATION' is 0.00
'centreon-central-1' write iops on 'INTEGRATION' is 0.60
Vérifie l'état de santé des serveurs ESX:
::
$ perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin --custommode=connector --connector-hostname=127.0.0.1 --container=default --verbose --mode=health-host --esx-hostname='.*' --filter --disconnect-status='ok'
OK: All ESX health checks are ok | 'problems_srvi-clus-esx-n2.merethis.net'=0;;;0;299 'problems_srvi-clus-esx-n1.merethis.net'=0;;;0;299 'problems_srvi-clus-esx-n4.merethis.net'=0;;;0;186 'problems_srvi-clus-esx-n3.merethis.net'=0;;;0;186
Checking srvi-clus-esx-n2.merethis.net
299 health checks are green
Checking srvi-clus-esx-n1.merethis.net
299 health checks are green
Checking srvi-clus-esx-n4.merethis.net
186 health checks are green
Checking srvi-clus-esx-n3.merethis.net
186 health checks are green
Troubleshooting
---------------
@ -77,3 +113,10 @@ Il est possible de retrouver des erreurs de ce type dans les « logs » de «
Le SDK Perl VMWare génère cette erreur de temps en temps mais ne bloque pas le fonctionnement du connecteur. Le bug provient d'OpenSSL. Il devrait être fix dans la version 1.0.1h (CVE-2010-5298).
Le connecteur peut retourner l'erreur suivante:
::
# perl centreon_plugins.pl --plugin=apps::vmware::connector::plugin ...
Cannot get value for counters...
Vérifier la synchronisation du temps du VirtualCenter et de ses serveurs ESX. La plupart du temps, le serveur hébergeant le connecteur ou le VirtualCenter/ESX ne sont pas bien synchronisés.