While I agree with earlier posters tayfundeger and Tibmeister that the Gen8 servers from HPE are no longer on the ESXi 6.7 HCL and you should not run that combination in a production environmen...
See more...
While I agree with earlier posters tayfundeger and Tibmeister that the Gen8 servers from HPE are no longer on the ESXi 6.7 HCL and you should not run that combination in a production environment because it is unsupported, in my opinion JimKnopf99 's issue is more likely the result of changes to the ESXi 6.7 U3 handling of hardware sensors and resultant increased logging of Hardware Sensor Status events - his screenshot shows the 0.23.11 device System Chassis 1 UID in "Unbekannt" or unknown state. This is NOT due to his Gen8 host no longer being on the HCL - I have the same "unknown" status on the same 0.23.11 System Chassis 1 UID device on ALL my Gen9 and Gen10 hosts (that device ID is slightly different on Gen10's - 0.23.1174) that have been upgraded to 6.7 U3. The screenshot below is from a Gen9 BL460c running 6.7 U3, and that Gen9 hardware (and obviously Gen10 as well) is absolutely on the HCL for the 6.7 U1-3 releases. I have all latest firmware, iLo, drivers, and HPE managment .vibs installed on these hosts. JimKnopf99 I would try the workaround described in VMware KB 74608 to disable WBEM services on your host, so long as you can deal with disabling ALL vSphere hardware alerting for these hosts, a workaround which I choose not to implement. It's not an ideal workaround IMO; akin to your car dealer telling you that the workaround to inadvertent check engine light is to snip all the wiring going to your dashboard until they come up with a fix for the root cause. We have been waiting patiently more than 2 months for the first post-U3 patch to be released which hopefully will address this hardware sensor issue. See a longer post with more details here: Too many events "Host hardware sensor state" after ESXi upgrade 6.5 to 6.7U3 Cheers, Patrick