Incorrect vSAN License Capacity Calculation After SSD Replacement in vSAN ESA cluster.

Products

• VMware vSAN

Issue/Introduction

• After replacing a defective SSD in a vSAN ESA (Express Storage Architecture) cluster, the reported license capacity is calculated incorrectly.
  
  
• The system failed to subtract the capacity of the removed, defective disk.

Environment

VMware vSAN 8.x

VMware vSAN ESA

Cause

• A "stale" disk entry for the removed drive persists in the ESXi configstore, causing the system to continue including the capacity of the defective disk in its calculations.
  
  
  
• To confirm, open an SSH session to the ESXi host and run

# configstorecli config current get -c vsan -g system -k host_config | grep -i name

• Compare no. of disks with:

# vdq -iH

Resolution

Remove the extra capacity disk from configstore:

1. From ESXi host CLI, export the host_config configstore:
   
   # configstorecli config current get -c vsan -g system -k host_config -outfile /tmp/host_config.json
   
   Identify the name and disk_uuid of the removed disk.
   
   
2. Copy the existing host_config configstore and edit with vi:
   
   # cp /tmp/host_config.json /tmp/host_config_new.json
# vi /tmp/host_config_new.json
   
   
3. Remove the lines specific to the vSAN ESA disk in question, example:
   
   {
"name": "######",
"vsan_capacity": 6401252745216,
"disk_uuid": "######-####-####-####-#########"
},
   
   
4. Save the new file & import the new host_config configstore:
   # configstorecli config current set -c vsan -g system -k host_config -infile /tmp/host_config_new.json
   
   
5. Restart hostd and vsanmgmtd services:
   # /etc/init.d/hostd restart
# /etc/init.d/vsanmgmtd restart