Ad Widget

**pc99096** · 20-10-2011, 06:51

Originally posted by pc99096

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?

it seems that moving the perl scripts to cron didn't help, i still keep receiving error mesages for random WBEM items:

7096:20111020:041805.112 Item [esxi1:Temperature[{$HOST},11]] became not supported: Not supported by Zabbix Agent
7096:20111020:041805.112 Item [esxi1:Temperature[{$HOST},14]] became not supported: Not supported by Zabbix Agent
7094:20111020:042300.831 Item [esxi1:Temperature[{$HOST},11]] became supported
7097:20111020:042305.845 Item [esxi1:Temperature[{$HOST},14]] became supported
7094:20111020:052804.130 Item [esxi1:Temperature[{$HOST},13]] became not supported: Not supported by Zabbix Agent
7096:20111020:053304.727 Item [esxi1:Temperature[{$HOST},11]] became not supported: Not supported by Zabbix Agent
7096:20111020:053304.727 Item [esxi1:Temperature[{$HOST},13]] became supported
7096:20111020:053304.727 Item [esxi1:Temperature[{$HOST},14]] became not supported: Not supported by Zabbix Agent
7097:20111020:054305.885 Item [esxi1:Temperature[{$HOST},11]] became supported
7097:20111020:054305.885 Item [esxi1:Temperature[{$HOST},14]] became supported
7094:20111020:062807.168 Item [esxi1:Temperature[{$HOST},14]] became not supported: Not supported by Zabbix Agent
7096:20111020:063302.835 Item [esxi1:Temperature[{$HOST},11]] became not supported: Not supported by Zabbix Agent
7094:20111020:064304.117 Item [esxi1:Temperature[{$HOST},11]] became supported
7094:20111020:064304.118 Item [esxi1:Temperature[{$HOST},14]] became supported
7095:20111020:070802.573 Item [esxi1:Temperature[{$HOST},10]] became not supported: Not supported by Zabbix Agent
7094:20111020:071303.156 Item [esxi1:Temperature[{$HOST},10]] became supported
7094:20111020:071303.157 Item [esxi1:Temperature[{$HOST},11]] became not supported: Not supported by Zabbix Agent
7095:20111020:072259.498 Item [esxi1:Temperature[{$HOST},11]] became supported

**dima_dm** · 20-10-2011, 06:57

Originally posted by pc99096

7096:20111020:041805.112 Item [esxi1:Temperature[{$HOST},11]] became not supported: Not supported by Zabbix Agent

Check Macros definition {$HOST} in host config of Zabbix Web interface. In log file instead of {$HOST} must be an IP address of ESXi.
{$HOST} - IP address of ESXi hypervisor
{$HOST}=172.16.36.76

**pc99096** · 20-10-2011, 07:24

Originally posted by dima_dm

Check Macros definition {$HOST} in host config of Zabbix Web interface. In log file instead of {$HOST} must be an IP address of ESXi.
{$HOST} - IP address of ESXi hypervisor
{$HOST}=172.16.36.76

{$HOST}=IP in GUI is set, otherwise it wouldn't work. i'm getting some data from all 4 esxi servers. problem is that from time to time there are these errors, mostly from esxi1.

**dima_dm** · 20-10-2011, 07:58

Originally posted by pc99096

{$HOST}=IP in GUI is set, otherwise it wouldn't work. i'm getting some data from all 4 esxi servers. problem is that from time to time there are these errors, mostly from esxi1.

This macros substitution problem in Zabbix. Try move on Zabbix 1.8.8

**harmonica** · 20-10-2011, 20:38

Hello dima_dm,

I have been testing your scripts in HP ProLiant ML110 G6 Server + ESXi 4.1 with some success. I can get information with zabbix_perl_api_vmware.pl script to monitoring software, but to monitor hardware with zabbix_wbem_vmware.pl, i need HP agents on ESXi Hypervisor compatible with this model of hardware, correct?
On the support website for HP ProLiant ML110 G6 Server (http://h20000.www2.hp.com/bizsupport...625&taskId=135) there is no information for ESXi operating system. Can i conclude that it is not possible to monitor the hardware?
With IPMI i can get some information, but my main intention is to validate the status Array Controller and discs.

Regards

**dima_dm** · 21-10-2011, 07:39

Originally posted by jose_lourdes

Hello dima_dm,
I have been testing your scripts in HP ProLiant ML110 G6 Server + ESXi 4.1 with some success. I can get information with zabbix_perl_api_vmware.pl script to monitoring software, but to monitor hardware with zabbix_wbem_vmware.pl, i need HP agents on ESXi Hypervisor compatible with this model of hardware, correct?

ESXi image from HP already have all HP agents, for all HP platform.

**pc99096** · 21-10-2011, 16:03

Originally posted by dima_dm

This macros substitution problem in Zabbix. Try move on Zabbix 1.8.8

just tried to upgrade to 1.8.8 and unfortunately same errors

**dima_dm** · 23-10-2011, 11:03

Originally posted by pc99096

just tried to upgrade to 1.8.8 and unfortunately same errors

Do you make upgraded zabbix_server daemon? See zabbix_server version in log file.

**pc99096** · 23-10-2011, 11:49

Originally posted by dima_dm

Do you make upgraded zabbix_server daemon? See zabbix_server version in log file.

it says Zabbix 1.8.8 (revision 21965)

**getUP** · 10-11-2011, 19:41

We're using Dell servers instead of HP, but we for now we just want to monitor the software. As I'm not entirely sure how we should configure our items, I tried importing your template. Unfortunately without luck.

I am unsure how to go configuring the items. Clearly we would probably need to use API in all templates, as that would populate the statistic file. I'm unsure how to define the key though. What should be in there?

I have added a host with the details as follows:
Name: vmhost01
IP address: 127.0.0.1

Added the following macro's:
{$HOST} => has the IP of the server
{$PASSWORD} => obviously the password
{$USERNAME} => same here

They are added in that order as well.

The item itself currently only has the following settings:
Host: added to template assigned to host
Description: API
Type: Zabbix agent
Key: API

All other settings are default.

This returns in the following in our zabbix_agentd.log.

Code:

1804:20111110:183556.400 Item [vmhost01:API] error: Not supported by Zabbix Agent

How about do I go to add this to make it dynamic in templates? I'm not sure what I'm doing wrong here.

**pc99096** · 10-11-2011, 20:35

i would really suggest that you start reading this thread from the beginning. the very first post says almost everything about how to make things running.
the zabbix GUI configuration is just the last step.
first you need to install this:

Broadcom Community - VMTN, Mainframe, Symantec, Carbon Black

http://communities.vmware.com/community/vmtn/developer/forums/vsphere_sdk_perl

Broadcom Community - VMTN, Mainframe, Symantec, Carbon Black

then download the zabbix_perl_api_vmware.pl script etc etc.
if you will be able to get some results from the esxi hosts when calling that script from the command line, you can move on and start configuring the zabbix part itself.

**getUP** · 10-11-2011, 20:50

Maybe I was not clear enough. Everything is installed, I've ran the tests from VMWare and they're working fine. I got Zabbix working in the end as well, that is without the unsupported error, though it returns the VMWare client error now.

When I run /usr/lib/vmware-viperl/apps/performance/viperformance.pl I get a perfect reply from the host. For instance:

Code:

Counter: Data transmit rate 
Instance : vmnic5 
Description: Average amount of data transmitted per second 
Units: KBps 
Sample info : 20,2011-11-10T18:14:00Z 
Value: 0

When I add in the information into the perl script to do the command line debugging I always got a perl compilation error at first because it didn't like it that we used an @ in our username, but after changing the double quotes to single quotes that was resolved as well. All our hosts are on a domain.

If we add in wrong details it returns that we have used wrong credentials. When we're using the right ones it always returns 1 on command line or 1 with vmware client error within Zabbix.

**pc99096** · 10-11-2011, 21:08

do you see any vmware*.txt files in /tmp?

**pc99096** · 10-11-2011, 21:23

if the vmware perl api script returns 1, i think you need to check that all perl modules were installed correctly

**getUP** · 10-11-2011, 21:40

The perl modules are installed correctly, when I add the variables statically and remove the check for any arguments it creates a vmware*.txt file.

As soon as I put the check for aguments back in and change the item key in Zabbix to API[{$HOST}, {$PASSWORD}, {$USERNAME}] it returns a method not supported error.

Ad Widget

ESXi 4.0 Hardware and Software Monitoring VMWare

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment