VMWare ESX 6.7 Hardware Health

terryp@ofcu.com  wrote: 6.5 Fix does not resolve issue on 6.7. sfcbd-watchdog is running and port 5989 is open. Still get this error. Hardware polling failed: Polling of chassis (CIM_Chassis class) failed. The underlying connection was closed: An unexpected error occurred on a send. We have 3 ESXi 6.7 host and soon will have another one. Has anyone have a solution?

the 6.5 Fix that you're referring to - are you talking about the fix detailed here?

VMWare ESX 6.5 Hardware Health [Solved]

Yes, I am referred to that posting. It did NOT resolve the issue.

6.7 has a bug from VMware end.. they are yet to resolve it and supposed to be in the next release but no updates...

We have most of the hosts on 6.7 and as an alternate we are doing hardware monitoring via ILO by setting SNMP on it....

pratikmehta003  wrote: 6.7 has a bug from VMware end.. they are yet to resolve it and supposed to be in the next release but no updates... We have most of the hosts on 6.7 and as an alternate we are doing hardware monitoring via ILO by setting SNMP on it....

I'm curious if you have a VMware ticket for the known issue?

serena​ I dont have the ticket number as it was raised by the concerned team which is at different location...

But below 2 links might help you which i had received over email from my team few months back. The team was not able to see the hardware status even on Vcenter...

The first one is detailed in this kb below and has been confirmed should be resolved in 6.7 U1 due to be released later this year:
https://kb.vmware.com/s/article/57171

The second possible issue is caused by the version of iLo in use and is resolved by downgrading the iLo to version 1.2:
https://kb.vmware.com/s/article/53134

Is there any update to this issue? When will this be resolved?

Or is there a workaround to disable the cim polling for this node until the patch arrives?

this is a bug at Vmware side so not sure when they would resolve..

Regarding disabling of CIM polling, not sure...@serena any thoughts?

demollib  wrote: Is there any update to this issue? When will this be resolved? Or is there a workaround to disable the cim polling for this node until the patch arrives?

My recommendation is to file a support ticket to allow us access to your diagnostics. Submit a Ticket | SolarWinds Customer Portal  If it's a VMware issue, we can help you determine that so a support ticket can be created for VMware to address the limitation. 

It is solved for me

The problem was, since v6.7 -> TLS is disabled by default

i had to edit /etc/sfcb/sfcb.cfg and add the line: enableTLSv1: true

saved the file and restarted the service with: /etc/init.d/sfcbd-watchdog restart

why is TLS needed here?

And were these changes recommended by VMWare? And did this solve your hardware polling issue for all ESX?

We have more than 50 ESX servers where we are facing issues and currently doing hardware monitoring via ILO which is using up additional licenses...