Virtual Machine Disk Partitions

[Kevin Everts_1]

I have 2 ESX 3.0.1 servers running VMM 2.0.1. When I view a virtual machine, SIM doesn't show the drive space that is used in the virtual machine. Under "Virtual Machine Configuration Details", It shows the virtual disk as having a capacity of 0.00 Bytes (0.00 Bytes Unused).

Under "Virtual Machine Disk Partitions", SIM shows No data available.

Is there any way to get this working? I would like to monitor used disk space so that the VM's don't run out.

[Rob Buxton]

I enable WBEM for all of my Virtual Servers and then run a weekly report on all servers pulling out the data from the HPSIM database for devices over a set threshold.
Unfortunately there's still a bug in wbem where the %full figure recorded in the database is always 100% so I need to calculate it manually as the amount used and disk size figures are correct.

This report acts as a good backup for when the threshold alerts are missed.

[Kevin Everts_1]

How did you setup wbem and the report?

[Jesper Taanum-Willumsen]

Hi Kevin

I have got it working on these versions:
Virtualization VMware ESX 3.0 Server (3.0.1)
VMM Agent Version 2.1
I have used the user guide for installation.

I can see the utilisation on my guests (after a reboot) but I can not set up thresholds.

I don't think it's a feature that is offered although it would be nice.

Jesper

[Rob Buxton]

Missed the follow up question.
I enable wbem globally in HPSIM but leave the credentials blank. Options->Protocol settings->Global Protocol Settings, ensure the Enable WBEM box is checked.

The on each virtual server, click on the server name and from Tools & Links tab select System Protocol Settings, check Update values and select the Use values specified below. Enter credentials that allow access to the server.

After the data collection tasks have run, the data tables in the database will be populated and you'll be able to use the standard HPSIM reporting.

In addition you can create an ODBC Connection and use something like MS Excel / MSQuery to pull out data. I use this as a means of determining the SQL I might need.
Once done I wrap that in a perl script and use the OSQL utility to pull the data from the database as part of a weekly scheduled job.