When using dedupe enabled Disk Group and encounters PDL of capacity disk, vsan capacity license information incorrectly remains after recreation of DG.

Products

• VMware vSAN

Issue/Introduction

When using dedupe enabled Disk Group and encounters PDL of capacity disk, vsan capacity license information incorrectly remains after recreation of DG.

The remained entry can be confirmed by below command.

# configstorecli config current get -c vsan -g system -k host_config

:::
      {
         "disk_uuid": "########-###-####-####-############",
         "name": "naa.################",                                          #<- capacity disk became PDL and physically removed
         "tags": [
            "capacityFlash"
         ],
         "vsan_capacity": 1920383410176
      },
:::

Environment

VMware vSAN

Cause

There is a product misbehavior that fails to cleanup vsan capacity license information after capacity disk PDL on dedupe enabled DG.

Broadcom engineering team is aware of this issue, and an improvement to avoid this issue will be provided in future release.

Resolution

If it happens, below command will cleanup stale license capacity information.

esxcli vsan storage remove -u <remained capacity disk uuid>

After removing the information, execute configstorecli again to confirm its related license information is removed.

configstorecli config current get -c vsan -g system -k host_config