-
Bug in Cluster mem.usage.average Statistic in vSphere 4.0 U1
Posted on February 23rd, 2010 3 commentsA while back I posted a script on a basic capacity report I run each month to get an overview of CPU and Memory usage in our various clusters. Since upgrading to vSphere 4.0 U1 I noticed some strange behavior in the results for memory, i.e. they came back at pretty close to 0% (typically between 0.05 and 0.06%) for the average memory usage in a cluster which typically were quite heavily used. On investigating further this also appeared the same in the GUI.
Using Get-Stat, mem.usage.average comes back at 0% where it should be a significant value:
The same in the GUI, the other cluster memory stats have significant values, but Memory Usage Average flatlines along the bottom of the graph:
This stat shows normal behaviour against host machines. I reported it to VMware who confirmed it to be a bug in 4.0 U1.
Thought I would share in case anyone else spends some time scratching their head and checking maths in scripts like I did. I’ll post back when there is a fix.
Update 19/05/2010:
Just got a follow up email from VMware Support that this bug will be fixed in VC 4.0 U3 – no release date for that yet.
3 responses to “Bug in Cluster mem.usage.average Statistic in vSphere 4.0 U1”
-
I got 0,02% in my VC
Sounds we need to use consumed/total metric
-
Jonathan Medd February 24th, 2010 at 20:48
Thanks for the comment. VMware says the figure may just be out by a factor of 100 so not too difficult to temporarily fix in my script.
Sent them some more screenshots today so hopefully it will get fixed soon.
-
Your post give me a great idea : a capacity planner script in powershell
http://www.hypervisor.fr/?p=1890
Leave a reply
-
Subscribe in iTunes to the Get-Scripting Podcast
AD PowerShell Quick Reference Guide
NiTRo February 24th, 2010 at 19:33