vsanmgmtd stops running after shutting down the vSAN cluster via vCenter vSAN Cluster Shutdown Wizard

Products

• VMware vSAN

Issue/Introduction

To remediate the corrupted vsanperf.conf and recover the vSAN management service.

Symptoms:

• The vCenter Server is deployed on the vSAN cluster.
• vSAN is running 7.0 U3c or higher.
• After shutting down the cluster using the vSAN cluster shutdown wizard, some hosts are experiencing issues with vsanmgmtd not running after subsequent cluster shutdowns. In some cases, vsanmgmtd might switch between "running" and "stopped" state due to automated service restarts.
• On those hosts, there are duplicate entries in /etc/vmware/vsan/vsanperf.conf, where the keys of those duplicate entries only differ in capitalization.
• The keys affected by this issue could be 'vc_vm_moId', 'allowSelfContain', and 'infra_vm_moIds'.

Environment

VMware vSAN 7.0.x
VMware vSAN 8.0.x

Cause

If some configurations of the vSAN performance service have been modified, the capitalization of the keys in the previously persisted options used by the shutdown wizard will change. The shutdown wizard does not handle this scenario properly.

Resolution

Upgrade vCenter/ESXi 7.0 U3o or 8.0 U1c or higher.

Workaround:
If the cluster has already hit this issue prior to upgrading to a fixed-in version engage vSAN support for assistance with remediating this issue.

Additional Information

Impact/Risks:
vsanmgmtd crashes and fails to start.