Hardware monitoring service on this host is not responding or not available

[Tenkian]

This is the error I get when selecting the Hardware Status tab on any of our vSphere servers in vCenter. The servers were upgraded from ESX 3.5 update 4 and the hardware status was working before the upgrade.

When I connect to the vSphere servers individually through the vSphere client I can see the hardware status under configuration > hardware. The problem is only through vCenter.

I have just installed Dell OMSA 6.1 on all our hosts and this has not helpded fix the issue.

Any help on this?

[sheredia12]

I have just experienced the exact same problem. Does anyone have a solution? My two hosts are powered and running just fine.

Error Message: "Hardware monitoring service not responding, the host is not powered on"

[Schorschi]

Open an SR with VMware. This one is going to be a hot topic if a 3rd person can validate the issue. If I have time this week I may see if I can recreate the issue.

[sheredia12]

The hardware status is now working again. Interesting. Nothing has changed in our environment. No host restarts, no services restarts and no patch updates. I'm going monitor until I lose the feature again and check vSphere event logs. Maybe that will give me a clue as to what may be going on.

[Schorschi]

Please open cases with VMware if you have seen this. VMware has had trouble recreating this issue, and thus have not put the resources on this issue, per my understanding, that it really does need. The only way to show VMware that the issue is significant is for everyone to communicate it via SRs.

[IndyGeek]

I just came across this error. Brand new install on 2 Dell R610's. Everything else seems to be just fine. I have one Guest OS running on the new install and its on the host that is giving the error message.

[antivir]

Is your vCenter Hardware status plugin "enabled"? (when you get error)

[IndyGeek]

Yes it is see attached, the Hardware Status works fine on my other host that is the identical hardware.

[Tenkian]

I fixed the issue with a simple firewall rule change. You must ensure you have the following :

Incoming (To ESX Server)

CIM Secure Server 5989 (TCP)

CIM SLP 427 (UDP, TCP)

Outgoing (From ESX Server)

CIM SLP 427 (UDP, TCP)

[IndyGeek]

I am using ESXi not ESX so how do I get to the firewall config with that?

[IndyGeek]

I opened an SR with Support and was able to fix the issue. It was as simple as removing the host from vCenter then re-adding it.

[localj]

Can confirm that removing and re-adding the ESX host solved the issue for me.

2 x ESXi 4.0 on Dell PowerEdge R710

[suda123]

I get this error in my ESX 4 vSphere Env.vCenter

Hardware Status

VMware, Inc.

4.0

Disabled

Displays the hardware status of

hosts (CIM monitoring)

The following error occured while downloading the script

plugin from

-

.xml:

Unable to connect to the remote server

[felix107]

I'm getting the same error too from above. Is there a solution for this?

I noticed that when I have vDS setup and I tried removing one of the esx host I get the following error:

"The resource vim.HostSystem <host name> is in use. Cannot remove the host <host name> because it's part of the DVS dvSwitch"

Does this mean I have to remove it and then I can remove the host to try to fix this plug-in issue that I have.

Thanks.

[Sanderma]

I had the same issue.

removing the host from Virtual Center and adding it solved it for me too.

I got the error after the VMware VirtualCenter Management Webservices didn't start, and had to be started manually.

[ThonyJ]

For me the problem was resolved by disconnecting from the host and then connect again.

[Integr8]

I had this error too but it was nothing to do with a DMZ.

When we upgraded VirtualCenter v2.5 to vCenter 4, it used HTTP Port 85, not 80.

I manually changed the port to Port 80 in vCenter by going through 'Administration -> vCenter Server Settings -> Ports'.

I then rebooted the vCenter Server and can now connect.

Hope that helps...

[vmiadmin]

I had the same issue and after disconnecting and connecting the ESX host from the vi client fixed the issue.

[gajuambi]

I tried

and

but no go.

here the host is not in a DMZ

and its a fresh installation of vsphere 4.1

[alshawwa]

i tried everything listed over here still not working , it wont fix that error msg , vmware tech support didnt get back to me yet , we rand DSET utility and this what happened the hardware monitoring service on this host is not responding

anyone figured that thing out ? other than removing and adding the hosts and restarting management services and reinstalling the esx4 and checking the network setting to make sure its not in dmz and make sure the ports are open ?