VMWare ESX 6.5 Hardware Health [Solved]

Version 2

    While working on an Orion implementation, and I ran into the appearance of a bug with VMWare 6.5 related to Hardware health polling. Hardware health in ESX 6.5 appears to be broken, but actually the services needed need to be configured to work correctly. This is a new change done in 6.5.

     

    Issue Identified: VMWare ESX 6.5 Hardware health shows as unknown. Node Shows as Green with Grey child status. Map may show server as green with yellow status.

     

    Error Reported: Hardware Health Unknown. "Polling of chassis (CIM_Chassis class) failed. Unable to connect to the remote server.

     

     

    How to fix:

    On the VMWare C Client (some functions in the C Client do not function with ESX 6.5, but everything we are doing will work)

          Go into Configuration> Security Profile, Properties, select SSH, enable SSH Service

     

    On the VMWare Web Console, go into services and enable SSH

     

     

     

    Next: login via ssh (I used putty)

         Note: This shows what you run and the expected outputs Bold text shows what you need to confirm on the screen to know that the steps are working as expected.

     

    [You run] esxcli system wbem get

       Authorization Model: password

       Enabled: false

       Loglevel: warning

       Port: 5989

       WSManagement Service: true

    [You run] esxcli system wbem set -e 1

         (This is to enable wbem)

    [You run] esxcli system wbem get

       Authorization Model: password

      Enabled: true

       Loglevel: warning

       Port: 5989

       WSManagement Service: true

     

    (Next, I checked the service to make sure it is running)

     

    [You run] /etc/init.d/sfcbd-watchdog status

    sfcbd is running

     

    [You run]  /etc/init.d/sfcbd-watchdog stop

    sfcbd-init: Getting Exclusive access, please wait...

    sfcbd-init: Exclusive access granted.

    sfcbd-init: Request to stop sfcbd-watchdog, pid <ProcessID>

    sfcbd-init: Invoked kill <ProcessID>

    sfcbd-init: stop sfcbd process completed.

    [You run] /etc/init.d/sfcbd-watchdog start

    sfcbd-init: Getting Exclusive access, please wait...

    sfcbd-init: Exclusive access granted.

    sfcbd-init: Request to start sfcbd-watchdog, pid <ProcessID>

    sfcbd-config[84411]: No third party cim providers installed

    sfcbd-init: Start to create indication subscription for hostd SNMPSVC

    sfcbd-init: starting sfcbd

    sfcbd-init: Waiting for sfcb to start up.

    sfcbd-init: Program started normally.

    [You run] /etc/init.d/sfcbd-watchdog status

    sfcbd is running

    [You run] /etc/init.d/sfcbd-watchdog test

    sfcbd-init: Checking core components of sfcbd are running...

    sfcbd-init: Component sfcb-ProviderMa is running.

    sfcbd-init: Component sfcb-HTTP-Daemo is running.

    sfcbd-init: Component sfcb-HTTPS-Daem is running.

    sfcbd-init: All components are running.

    [You run]exit

     

    Wait for the next polling cycle. Other VMWare customers have reported that restarting the server fixes the issue, but we could be talking about resolving production issues. From what I have seen, No restart is required, based on the steps above, but it can take 15-30 minutes to show up.

     

    Pages referenced:

    vCenter Server Appliance 6.5 Hardware Sensors Missing

    https://communities.vmware.com/thread/546989

    How to fix inaccurate Xeon D Hardware Health sensor readings on VMware ESXi 6.5, since sfcbd CIM service is off by defaul

    https://tinkertry.com/fix-xeon-d-inaccurate-cim-data-default-in-vsphere65

    How to disable the CIM agent on the ESX/ESXi host (1025757)

    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1025757