I would check out the logs or if this system has vendor management tools it is worth checking out what has happened if anything. Pegasus does not have the access to the hardware that management tools do. But this is something I would look into.
Edward L. Haletky
VMware Communities User Moderator
Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.
As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization
These are brand new servers, it seems strange that all 3 brand new servers are reporting the same error.
Hi, did anyone find a resolution to this? I've just upgraded some BL460c hosts which are showing the same issue. Others we have the "Health Status" is green. Both sets of hosts function fine and I cannot see anything obvious in the logs or kernel messages. Even the hosts which are fine have an older bios revision!
same issue here, having this error on all of our four Blade 460c G1 Servers.
Resetting the Agents or restarting the Server did not solve the issue.
Has someone any solution for this?
We had the same issue. Try logging into the Onboard Administrator for the chassis and see if there are any errors within the chassis. There was an issue with OA version 2.40 that triggered the errors with the OAs stating that they "non-redundant" even though they were. This can be comfirmed by also using the front panel display to view if there are any errors. Turns out that there was a customer advisory from HP that they pulled version 2.40 and released 2.41. We ended up upgrading to 2.41 and that cleared the error in the chassis, which in turn cleared the errors in the health status for the "Controller access degraded or unavailable Assert." Please let me know if this resolves your issue and kindly award points if successful. Thanks.
thanx for your reply. You've pointed me to the right way. The Chassis reported an Error due different Firmware Versions of the Onboard and the Standby Onboard Administrator. Updating the Standby Onboard Administrator Firmware cleared the error on the chassis and within Virtual Center. Currently we're running Firmware 2.32 for the OA, this seems to be the actual one.
Great to hear that it cleared up your error...It had me go round and round for about an hour think that there must have been something misconfigured with the agent.
As far I know the iLO2 f/w version 1.61 fixes this issue.Please give a try with latest Hp ILO2 fimware. I am not sure whether the OA fimware is having any impact on the ESX "health status",but if the fimware update is also triggering a individal blade iLO 2 fimware updrage, then it will make a difference.
Thanks, no clear answer given but moved on to vSphere now.
In the vSphere client you can choose host, open Configuration->Security Profile->click Properties... link in the Services section and restart CIM Server. You can try to Update information in the Hardware Status pane, but it will be much faster logout of the client and login again.
Or open ssh session and run command /etc/init.d/sfcbd-watchdog restart.
It worked for me.