Cheshire Cat Computing

The confusion here is that there is an agent part (vmware-stats and snmpd.conf) that goes on the ESX server, a Nagios plugin (check_esx2) that goes on the Nagios server or can be used by MRTG, and a MRTG utility (vmware_monitor2.pl) that goes on the MRTG server. I should have been more clear in the instructions.

If you want to use vmware_monitor then all you need is snmpd.conf and vmware-stats on the ESX server and vmware_monitor2 on the MRTG server.

You are calling the script correctly, and it should create the xxx1vm02test.cfg file -- provided that it has successfully managed to read the SNMP on the target server.

Make sure that you have started the snmpd daemon, and the vmware-snmpd daemon, on the ESX server! Read your ESX documentation to find out how to enable and start the SNMP.

Then, on the MRTG server, use snmpwalk to test that you can actually get an SNMP response from the ESX server and also read the ESX MIB tree.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi and thanx for clearing that out.

Now I´m getting there step by step.

I´m getting this output from running the script now, I get nothing but grey in routers2.cgi. Do you have any idé?

[root@xxxxlog1 vmware]# /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl -d -H xxxxvm02 -C xxxxx -D /var/www/html/mrtg/rrdfiles -c /tmp -m /etc/mrtg/xxxxxxx/vmware/xxxxvm02.cfg
(snmp lookup of vmids)
Table retrieved
Highest index is 0
Creating RRD #1
Creating RRD #2
Creating RRD #3
Creating RRD #4
Creating RRD #5
Creating RRD #6
Creating RRD #7
Highest index is 7
Creating RRD #6-x-vmnic2
NET: xxxxIW02(vmnic2): 992212992/2883269632
Creating RRD #5-x-vmnic1
NET: xxxxLOG1(vmnic1): 4871903232/5573081088
Creating RRD #2-x-vmnic1
NET: xxxxAM02(vmnic1): 3872693248/5641920512
Creating RRD #3-x-vmnic4
NET: SSL(vmnic4): 2694607872/36642816
Creating RRD #7-x-vmnic6
NET: xxxxIM02(vmnic6): 5640371200/8225814528
Creating RRD #4-x-vmnic1
NET: xxxxWUS1(vmnic1): 17589774336/12916170752
Creating RRD #2-x-vmhba1-0-0
HBA: xxxxAM02:vmhba1:0:0 = 437504000/100817118208
Creating RRD #3-x-vmhba1-0-0
HBA: SSL:vmhba1:0:0 = 205334528/161741768704
Creating RRD #4-x-vmhba1-0-0
HBA: xxxxWUS1:vmhba1:0:0 = 791966707712/445299467264
Creating RRD #6-x-vmhba1-0-0
HBA: xxxxIW02:vmhba1:0:0 = 3839763456/199387331584
Creating RRD #7-x-vmhba1-0-0
HBA: xxxxIM02:vmhba1:0:0 = 35498472448/861397303296
Creating RRD #5-x-vmhba1-0-0
HBA: xxxxLOG1:vmhba1:0:0 = 38880098304/576716190720
Updating vhost=SSL #3
Time is: 1159428178
Updating CPU to 341779/67632
Updating MEM to 10735616
Updating MEM-PS to 400953344/135917568
Updating MEM-BS to 0/0
Updating NET:vmnic4 to 2694607872:36642816
Updating HBA:vmhba1:0:0 to 205334528:161741768704
Updating vhost=xxxxWUS1 #4
Time is: 1159428178
Updating CPU to 590652/127729
Updating MEM to 102002688
Updating MEM-PS to 467652608/69218304
Updating MEM-BS to 0/0
Updating NET:vmnic1 to 17589774336:12916170752
Updating HBA:vmhba1:0:0 to 791966707712:445299467264
Updating vhost=xxxxLOG1 #5
Time is: 1159428178
Updating CPU to 1348643/983817
Updating MEM to 123478016
Updating MEM-PS to 390316032/146554880
Updating MEM-BS to 0/0
Updating NET:vmnic1 to 4871903232:5573081088
Updating HBA:vmhba1:0:0 to 38880098304:576716190720
Updating vhost=xxxxIM02 #7
Time is: 1159428178
Updating CPU to 742525/170091
Updating MEM to 128847872
Updating MEM-PS to 982794240/90947584
Updating MEM-BS to 0/0
Updating NET:vmnic6 to 5640371200:8225814528
Updating HBA:vmhba1:0:0 to 35498472448:861397303296
Updating vhost=xxxxIW02 #6
Time is: 1159428178
Updating CPU to 388627/116105
Updating MEM to 21471232
Updating MEM-PS to 619466752/454275072
Updating MEM-BS to 0/0
Updating NET:vmnic2 to 992212992:2883269632
Updating HBA:vmhba1:0:0 to 3839763456:199387331584
Updating vhost=xxxxAM02 #2
Time is: 1159428178
Updating CPU to 388118/54879
Updating MEM to 20131840
Updating MEM-PS to 185057280/217595904
Updating MEM-BS to 0/0
Updating NET:vmnic1 to 3872693248:5641920512
Updating HBA:vmhba1:0:0 to 437504000:100817118208
Updating vhost=xxxxIW03_(Testserver_for_IWSS-2.5) #1
Time is: 1159428178
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 87.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 89.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 87.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 89.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 87.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 89.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 87.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 89.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 87.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 89.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 87.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 89.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 82.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 83.
print() on closed filehandle STATE at /etc/mrtg/xxxxxxx/vmware/vmware_monitor2.pl line 85.

OK, this is because I didn't trap the case where the script is unable to open the cache file.

If you specify a cache file (using -c) then this is the STATE file it mentions. If not, then it tries to create a file 'cache' in the RRD directory. It may be that this file already exists but is not writeable by this user? Check for this. Also, you could specify the cached state file by using something like '-c /var/tmp/esx-cache' and checking that the file does not exist and can be created by the user which is running the script.

The next version of the script will catch a failed open on the cache file!

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi Again!

Thanx for that, when I removed the -c parameter it works better.

But... I get error messege in routers2.cgi when I press Summary, vmhba1, vmnic1, 2, 3...
It now works fine with CPU and memory.

This is what i get when I press summary

RRD Error: invalid rpn expression in: CDEF:greyout=0,fin1,UN,+,fout1,UN,+,1,1,+,EQ,INF,0,IF,1,1,+,EQ,NEGINF,0,IF

You can visit the configuration verification page here.

RRD: /var/www/html/mrtg/rrdfiles/3-x-vmnic4.rrd
Device: [vmware/xxxvm02.cfg] VMWare server xxxvm02 VHosts
Interface: _xxxvm02-vmnic4
Interfaces: xxxvm02-runningCPU,4-x-vmhba1-0-0,_xxxvm02-vmnic4,3-mem,4-cpu,xxxvm02-5-mem,7-cpu,7-mem,4-mem-bs,_xxxvm02-CPUrdy,xxxvm02-runningCPUrdy,xxxvm02-definedCPUrdy,3-mem-ps,5-x-vmhba1-0-0,_xxxvm02-memsplit5,4-x-vmnic1,2-x-vmhba1-0-0,xxxvm02-5-cpu,_xxxvm02-vmnic2-out,_xxxvm02-runningMEMactive,2-mem-ps,_xxxvm02-vmnic1-out,6-mem-bs,_xxxvm02-vmhba1,2-x-vmnic1,_xxxvm02-vmnic6-in,6-mem-ps,_xxxvm02-vmnic6-out,_xxxvm02-memsplit6,_xxxvm02-CPU,2-mem-bs,xxxvm02-definedCPU,_xxxvm02-MEM,_xxxvm02-vmnic4-in,5-mem-bs,_xxxvm02-runningMEM,_xxxvm02-vmnic1-in,_Network,_xxxvm02-memsplit7,_xxxvm02-vmnic6,5-mem,6-cpu,_xxxvm02-runningCPUrdy,_summary_,_xxxvm02-runningCPU,_xxxvm02-MEMactive,5-x-vmnic1,xxxvm02-definedMEM,6-mem,6-x-vmnic2,2-mem,_xxxvm02-vmhba1:0:0-in,_xxxvm02-vmnic1,xxxvm02-runningMEM,4-mem-ps,_xxxvm02-memsplit2,7-x-vmnic6,2-cpu,3-x-vmnic4,5-cpu,_xxxvm02-memsplit4,3-cpu,4-mem,3-x-vmhba1-0-0,6-x-vmhba1-0-0,_xxxvm02-vmnic2-in,_xxxvm02-vmnic4-out,_xxxvm02-memsplit,3-mem-bs,_xxxvm02-memsplit3,5-mem-ps,7-x-vmhba1-0-0,7-mem-ps,_HBAs,7-mem-bs,_xxxvm02-vmhba1:0:0-out,_xxxvm02-vmnic2
Params: /var/www/html/mrtg/graphs/vmwarexxxvm02.cfg-_xxxvm02-vmnic4-d-l2.png --imgformat PNG --base 1024 --lazy -l 0 --interlaced -F -s end-2000m -u 1 -w 530 -h 200 --x-grid HOUR:1:HOUR:24:HOUR:2:0:%k --title vmnic4 on xxxvm02 --vertical-label per second DEF:in1=/var/www/html/mrtg/rrdfiles/3-x-vmnic4.rrd:ds0:AVERAGE DEF:out1=/var/www/html/mrtg/rrdfiles/3-x-vmnic4.rrd:ds1:AVERAGE CDEF:fin1=in1,8,* CDEF:fout1=out1,8,* DEF:min1=/var/www/html/mrtg/rrdfiles/3-x-vmnic4.rrd:ds0:MAX DEF:mout1=/var/www/html/mrtg/rrdfiles/3-x-vmnic4.rrd:ds1:MAX CDEF:fmin1=min1,8,* CDEF:fmout1=mout1,8,* CDEF:pcin1=fin1,100,*,81920000000,/ CDEF:mpcin1=fmin1,100,*,81920000000,/ CDEF:pcout1=fout1,100,*,81920000000,/ CDEF:mpcout1=fmout1,100,*,81920000000,/ COMMENT:Network usage on SSL/vmnic4 \:\l AREA:fin1#0000ff:Incoming STACK:fout1#00ff00:Outgoing\l GPRINT:fmin1:MAX:Max In\: %6.2lf %s\g GPRINT:mpcin1:MAX: (%2.0lf%%)\g GPRINT:fin1:AVERAGE: Avg In\: %6.2lf %s\g GPRINT:pcin1:AVERAGE: (%2.0lf%%)\g GPRINT:fin1:LAST: Cur In\: %6.2lf %s\g GPRINT:pcin1:LAST: (%2.0lf%%)\g COMMENT:\l GPRINT:fmout1:MAX:Max Out\:%6.2lf %s\g GPRINT:mpcout1:MAX: (%2.0lf%%)\g GPRINT:fout1:AVERAGE: Avg Out\:%6.2lf %s\g GPRINT:pcout1:AVERAGE: (%2.0lf%%)\g GPRINT:fout1:LAST: Cur Out\:%6.2lf %s\g GPRINT:pcout1:LAST: (%2.0lf%%)\g COMMENT:\l CDEF:totin=0,fin1,DUP,UN,EXC,PREV(fin1),DUP,UN,EXC,0,EXC,IF,EXC,IF,+ CDEF:totout=0,fout1,DUP,UN,EXC,PREV(fout1),DUP,UN,EXC,0,EXC,IF,EXC,IF,+ COMMENT:Total values\:\l LINE1:totin#ff0000:Total Incoming CDEF:mtotout=totout,-1,* LINE1:mtotout#00cccc:Total Outgoing\l GPRINT:totin:MAX:Max In\: %6.2lf %s\g GPRINT:totin:AVERAGE: Avg In\: %6.2lf %s\g GPRINT:totin:LAST: Cur In\: %6.2lf %s\l GPRINT:totout:MAX:Max Out\:%6.2lf %s\g GPRINT:totout:AVERAGE: Avg Out\:%6.2lf %s\g GPRINT:totout:LAST: Cur Out\:%6.2lf %s\l CDEF:greyout=0,fin1,UN,+,fout1,UN,+,1,1,+,EQ,INF,0,IF AREA:greyout#d0d0d0 CDEF:mgreyout=CDEF:greyout=0,fin1,UN,+,fout1,UN,+,1,1,+,EQ,INF,0,IF,1,1,+,EQ,NEGINF,0,IF AREA:mgreyout#d0d0d0

What version of routers2 do you have? From the generated code, it looks as if you have 2.15beta7 which occasionally had a problem in mirror graph mode. I would recommend upgrading to the latest 2.17beta7 and this should fix the issue.

Steve

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

They *should* support ESX3 -- I've received a couple of reports from people saying they work under ESX 3 -- but as we dont yet have ESX3 here I can't personally confirm it. I also believe there is a bit of difference to the way you configure SNMP in ESX3.

The scripts parse the column headers in the proc filesystem so as to be able to support the varying proc file layouts through the different versions of ESX. It should work, but until we have ESX3 here I cant personally confirm it.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Final update - the new script, check_vmware, uses the Perl VI API to retrieve data and so works with all versions of ESX. You can obtain this script from the 'Nagios and MRTG plugins' forum: viewforum.php?f=35

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11