The vSAN capacity for cluster cannot be determined when running FoundationCoreAndTiBUsage script
Article ID: 406501
Updated On:
Products
Issue/Introduction
Getting error message when running script FoundationCoreAndTiBUsage.psm1 against one of our vSAN clusters.
Error message is: The vSAN capacity for cluster CL101 cannot be determined because of the stale PDL devices in this cluster. Contact Global Support team for assistance.
This allowed for successful measuring of the Disks in use for vSAN licensing.
However the disks remained listed in the configstore.
disks cannot be seen in ESXi storage or vSAN commands
non existing disks on host ##### that need to be removed from the host config store.
"name": "naa.###############
"name": "naa.###############
"name": "naa.###############
"name": "naa.###############
"name": "naa.###############
"name": "naa.###############
"name": "naa.###############
"name": "naa.###############
Environment
vSAN 8.0X
Cause
The disks had a hardware failure and have been replaced. However, the signature/disk IDs of the disks remain in the Configstore. There is no functional impact to the hosts having stale names but when measuring storage use the drives will impact the initial script.
Resolution
To locate and remove - The below esxcli cmd can list all devices in the host:
esxcli storage core device capacity list
Please check if the above disks are listed.
1. If the disk is listed in above cmd, it indicates the disk is available in the host, but not used by vSAN. Follow standard process for removing unused/non-partitioned disks from the ESXi host.
2. If the disk that the script list are not listed in the above command. Please continue below to use configstorecli instructions to remove the entry.
The command will remove the disks from the configstore.
configstorecli config current delete -c vsan -g system -k host_config -p disks/<disk_index>
(disk_index is the index of the disk by the get cmd output)
configstorecli config current get -c vsan -g system -k host_config -p disks
Taking below output as an example:
$ configstorecli config current get -c vsan -g system -k host_config -p disks
[
{
"disk_uuid": "52cb7602-ac94-a91c-ae0b-00ea5334bca9",
"name": "mpx.vmhba0:C0:T1:L0",
"vsan_capacity": 48318382080
},
{
"name": "mpx.vmhba0:C0:T2:L0",
"tags": [
"capacityFlash"
]
},
{
"name": "mpx.vmhba0:C0:T3:L0",
"tags": [
"capacityFlash"
]
}
]
The index of disk mpx.vmhba0:C0:T3:L0 in the output array is 2 (starting from 0), so if you want to remove the entry, run the delete cmd
$ configstorecli config current delete -c vsan -g system -k host_config -p disks/2
Repeat the use of the command with the corresponding disk names that have been safely identified.
Please reach out to Broadcom Global Support if you have any questions or concerns about following the proceedure.
Additional Information
Feedback
