This issue is resolved in ESXi 5.0 Update 2. For more information about this version, see the
ESXi 5.0 Update 2 Release Notes. You can download the latest release from the
VMware Download Center.
To workaround this issue on an earlier version of ESXi 5.0, turn off/on the firewall directly on the host via ssh or console after
hostd has started using these commands:
- # esxcli network firewall set --enabled false
- # esxcli network firewall set --enabled true
This action updates hostd with the correct firewall rule states. Now, compliance will not fail for vpx_Heartbeats, CIMHttpServer and CIMHttpsServer.
Alternately, you can edit the host profile and omit the vpx_Heartbeats, CIMHttpServer and CIMHttpsServer rules.
Note: To ensure you have refreshed the vSphere client, click Refresh under Security Profile.