Ad Widget
Collapse
ESXi 4.0 Hardware and Software Monitoring VMWare
Collapse
X
-
@dima_dm: can you post this on the first page..
how to install the vmware VI-Perl-SDK on Debian Squeeze
Debian-User
Sorry for my bad english
Comment
-
This very simple and standard instruction, and don’t require any comment.@dima_dm: can you post this on the first page..
how to install the vmware VI-Perl-SDK on Debian Squeeze
http://www.nagios-portal.org/wbb/ind...ian#post116807
OK. added:
See vSphere SDK for Perl Installation Guide http://www.vmware.com/support/developer/viperltoolkit/Last edited by dima_dm; 15-08-2011, 16:33.Comment
-
When I run:
/usr/bin/wbemcli ei -noverify "https://root:[email protected]/root/hpq:SMX_FAN"
I got:
*
* /usr/bin/wbemcli: Cim: (3) CIM_ERR_INVALID_NAMESPACE: Invalid namespace
*
Any clue?Comment
-
Do you use HP hardware?When I run:
/usr/bin/wbemcli ei -noverify "https://root:[email protected]/root/hpq:SMX_FAN"
I got:
*
* /usr/bin/wbemcli: Cim: (3) CIM_ERR_INVALID_NAMESPACE: Invalid namespace
*
Any clue?
Do you use ESXi 4 or 4.1 with HP agents?Comment
-
i´ve now an problem..
in vmware, i see this:Code:/usr/lib/vmware-viperl/apps/performance/viperformance.pl --host HOST_NAME --server HOST_IP --countertype net --samples 1 --instance "*" --username root --password PASSWORD Error: Permission to perform this operation was denied.
why i dont see zabbix@IP?!Code:Benutzer @IP konnte nicht angemeldet werden: Keine Berechtigung Fehler
Debian-User
Sorry for my bad english
Comment
-
esxi 5.0 is fine, but in our environment the script just takes too much time to finish.
time ./zabbix_perl_api_vmware.pl
0
real 0m23.684s
user 0m8.896s
sys 0m0.125s
sometimes i got errors because some values can't be received within 30 seconds.
7095:20111012:130105.877 Item [esxi2:MaintenanceMode[{$HOST}]] became not supported: Not supported by Zabbix Agent
7095:20111012:130105.877 Item [esxi3:MaintenanceMode[{$HOST}]] became not supported: Not supported by Zabbix Agent
7094:20111012:130606.413 Item [esxi2:MaintenanceMode[{$HOST}]] became supported
7096:20111012:130636.464 Item [esxi2:NET[{$HOST},1,speed]] became not supported: Not supported by Zabbix Agent
7094:20111012:131107.148 Item [esxi3:MaintenanceMode[{$HOST}]] became supported
7094:20111012:131637.783 Item [esxi2:NET[{$HOST},1,speed]] became supported
7095:20111012:131652.814 Item [esxi1:CpuUsed[{$HOST}]] became not supported: Not supported by Zabbix Agent
7096:20111012:132148.248 Item [esxi1:CpuUsed[{$HOST}]] became supported
i'm thinking to move the .pl scripts to cron.
also the 600 seconds polling interval is too much i've changed it to 300 seconds and thinking to decrease it to 150 seconds.
anybody facing the same problem?Comment
-
Hi,
I began to migrate the zabbix_perl_api_vmware.pl to request centrally the ESX hosts via the VCC, please find below the modified script. Some items are not returned, thanks to terminate if you have the ESX knowledge.
The new syntax is now: zabbix_perl_api_vmware_VCC.pl --server <VCC_Name_or_IP> --username <VCC_user> --password <VCC_password> --vihost <ESX_Host_Name_or_IP>
Thanks,
AlainAttached FilesComment
-
I submitted a thread by Vmware about the missing counters returned by zabbix_perl_api_vmware_VCC.pl, the main point is that the number of counters returned by some subroutines like function retrieve_performance (same code as viperformance.pl) is different when lauched from each ESX or through VCenter Server.
Below the thread URL, will post here the answer if any.
Thanks Alain
Comment
Comment