Cluster and host component utilization warning after host upgrade

Products

• VMware vSAN

Issue/Introduction

Rebooting the ESXi host after the ESXi upgrade, vCenter UI > Cluster > Monitor > vSAN > Skyline Health may report below errors:

• Cluster and host component utilization.

 

• Physical Disk Component Utlization.

 

In the above figure, we could see the Data component Utilization on Witness node is more than 100%

Issue might be reoccurring even after preforming the workaround on these host to fix this issue, using the script 'publishDCEntry.py' provided in the article vSAN Health Service - Cluster and host component utilization

This script would be still present in the OSDATA partition of the hosts, and the below command to execute this script will be present on the /etc/rc.local.d/local.sh of the ESXi hosts, to run this script in a host during the boot process.

 

[Host-01~] cat /etc/rc.local.d/local.sh

#!/bin/sh ++group=host/vim/vmvisor/boot

# local configuration options

# Note: modify at your own risk! If you do/use anything in this

# script that is not part of a stable API (relying on files to be in

# specific places, specific tools, specific output, etc) there is a

# possibility you will end up with a broken system after patching or

# upgrading. Changes are not supported unless under direction of

# VMware support.

# Note: This script will not be run when UEFI secure boot is enabled.

 

nohup python /vmfs/volumes/OSDATA-<UUID>/publishDCEntry.py --interval 900 --maxComponentsPerIter 2000 >/dev/null 2>&1 &

 

exit 0

[Host-01~] 

Environment

VMware vSAN 8.x

Cause

Issue will occur after the reboot during the patch upgrade, if the secured boot is enabled on the ESXi host.
Due to the security hardening of the secure boot, the host will not run the command to execute the script 'publishDCEntry.py' in /etc/rc.local.d/local.sh of the ESXi hosts during the boot process.

Below command from ESX CLI can be used to check Secure boot status of the ESXi host.

[Host-01~] /usr/lib/vmware/secureboot/bin/secureBoot.py --check-status
Enabled
[Host-01~] 

Resolution

Recommended to upgrade the vSphere environment to 8.0 P05 (ESXi 8.0 Update 3e - Build 24674464) or higher, which is having the fix for Witness data component utilization issue.

Please find the below article for your reference:
vSAN Health Service - Cluster and host component utilization

 

Workaround:

Run the below command after every host reboot until the host is upgraded to the fix version.

nohup python /vmfs/volumes/OSDATA-<UUID>/publishDCEntry.py --interval 900 --maxComponentsPerIter 2000 >/dev/null 2>&1 &

Additional Information

Modifying the rc.local or local.sh file in VMware vSphere ESXi to execute commands while booting