Hello,
We have a puzzling issue with 2 of our vCenter appliances. The hardware tab has no data, or at best shows sensors with no data. (note this is not the same as VMware KB: In the vSphere Web Client in vCenter Server 6.0 the Hardware Status tab reports: No host ...)
My dev vCenter appliance started showing this behavior in December. Worked fine for about 2 months post upgrade from 5.5. We've had a case with support open since then with no results.
This past weekend, we migrated our production hosts to a clean install 6 appliance, and now this appliance is showing the issue.
Before the migration to the clean prod install, the hardware status tab was working for host that tested the migration. This is no longer the case.
If I use the fat client and log into a host directly, the hardware status is working. The issue is with the vCenter appliances themselves.
Has anyone else ever seen this behavior?
Thank you in advance.
Hi,
Yes. Hardware status tab showing inconsistent data is a known issue going on vCenter 6. Both Windows and appliance. I believe we have an open bug for this.
You can try the following work around. If this does not work, there is nothing much to do other than to wait for the fix
Suhas
Anyone know if this has been fixed yet? Maybe in Update 2?
Having same problem. I got issues from upgrading 5.5 to 6.0 u2. And 2nd center i had a Version before U2 and same Problem.
I idnt had Issue before.
Vmware gaved me following KB
But i get Kind of Security Error. This i didnt got before.
So i will try to install from Scratch to see if its upgrade related.
Maybe this KB working for you
Best regards
Max
Hi
I ran into the problem some months ago, after upgrading vCenter server from version 5.5 to version 6.0, keeping and migrating the SQL database in version 5.5 to a new Windows server and separated for vcenter server.. Everything was fine, except the hardware sensors.
There was not a problem with permissions, because If I reset sensors and update manually, vCenter can collect the hardware information. It looks more a problem related to CIM-client timer, but as vCenter 6 has completely changed its structure, is not possible to implement any workaround as in the version 5.
Since our ESX servers are HP, I opened a case with VMware and another with HP. At the beginning and due to the fact that vCenter 6 was a quite new version, VMware was not able to look for the root of the cause. I will be doing some test with them, during long time, and they suggested to do a reset in the inventory services.
I have to say that the soft reset did not improve anything, and the hard reset I didn´t do it in production VCenter because it is a little destructive.
I had to the chance to reproduce the same problem in a test environment and the reset of inventory services, didn´t work at all.
2 months later, I opened a case with HP, and after a deep investigation in my vCenter server, HP along with VMware, were able to reproduce the problem in their labs ,and the best of it, it that HP has confirmed that VMware and HP have recognized that there is a real problem related to vCenter 6, and the problem will be solved in the verion 6.0U3 . ![]()
Then....let´s wait for the new vCenter release in order to find out if the hardware sensors are finally able to refresh automatically without problems.
I wanted to share this information for those who are suffering the same problem.
Regards
Ha,
Many thx for that Info Piki.
i'am wondering everytime about such But Topics like that.
As i opend a Support Ticket > and they was not able to Support on that Issue. they gaved me the KB for resetting the Provider.
But i told them that i have there a "SecurityError" once trying to do that. and this is everytime happending once i do an Upgrade. With fresh Install this is not happening.
they didn't told me info about kind of U3 Fix
.
so make me little angry if something is known > and on the Support line they not having that Kind of Infos.
thx
Max
currently i'am query the CIM over nagios with http://www.claudiokuenzler.com/nagios-plugins/check_esxi_hardware.php#.VzTMrvmLSUk
works quit good.
Best regards
Max
Hi again
Hi again, After insisting a lot and waiting for a long time for receiving news, It looks that the VMWare engineers, were able to reproduce the same problem in their labs find the root of the cause and solve it with something, that it looks it will be implemented in the next release U3.
That´s the reason why I am still optimistic about this problem and they probably don´t want to publish anything until be completly sure.
We will see, This information was gave me nearly 2 months ago, then....we are nearer to know if this will be true ![]()
Regards
Piki
Hi Madmax, Do you know if "check_esxi_hardware.py" works correclty, running under Windows server and with ESXi version 6.0 and HP?
I have been testing but with not successful result.
Thanks in advance
Hi Piki.
sry i didn't tested from Windows. normally needing python,pywbem and setuptools
http://www.peppercrew.nl/index.php/2011/04/installing-python-and-pywbem/
setuptools 22.0.0 : Python Package Index
you should be able to start script > but maybe you needing additional fittings.
Best regards
Max
When working with VMware Global Support Services (GSS), please point to this post:
so they can review PR 1569119 which was the omnibus PR covering this issue and the fix is in 6.0U3.
See also : https://kb.vmware.com/kb/2145704
