Issues with VMware vSphere monitoring

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

So a couple of silly questions for you.

1. Is this a whitebox server or something off the HCL?
2. If it's from the HCL (Hardware Compatibility List) did you build the server with the vendor's specific build disk or is it a GA build?
3. If you look at the Health Status (Host, Configuration Tab then Host Status) do you see that it thinks that there should be two PSU's? Unless of course you have to look at Host\Hardware Status in which case it could well be a branded server build.

I have 3 white (well, black actually) boxes at home, one of which isn't in the cluster and as such isn't managed by vCenter but because mine are generic there are no PSU's listed.

Last question at this stage, was the server designed to ever have a second PSU fitted to it, if so you may be able to disable the PSU setting in the BIOS but you may have to investigate that further with the vendor.

 

That will be why then, as it's expecting to see a 2nd PSU there it's throwing up the alarm, you really need to find if it is in fact using the vendor build or generic, if it's the vendor build it will have the HP drivers, if it's a generic it will have been from an iso from the VMware site.

I would possibly take a closer look at the iLO and see if there is anywhere else that you may be able to turn off the BIOS but if it's using a HP branded build then you may be out of luck as it's expecting the specific server family to have a 2nd psu fitted and that's why it's throwing up the alarm.