VxRail: Verify vSAN on-disk format version when using a shared witness to deploy vSAN 2-node cluster

When deploying a vSAN 2-node cluster with customer-provided vCenter and shared witness, the deployment fails with error "Failed to convert standard cluster to stretched cluster LAG-NAM."

Check VxRail manager /var/log/microservice_log/dayone.log, there is vim.fault.VsanFault about "cannot meet the capability requirement of shared witness."

2022-05-05-14:01:57 microservice.do-cluster "[2022-05-05 14:01:57,066: WARNING/MainProcess] pyVmomi.VmomiSupport.vim.fault.VsanFault: (vim.fault.VsanFault) {"
2022-05-05-14:01:57 microservice.do-cluster "   dynamicType = <unset>,"
2022-05-05-14:01:57 microservice.do-cluster "   dynamicProperty = (vmodl.DynamicProperty) [],"
2022-05-05-14:01:57 microservice.do-cluster "   msg = 'cannot meet the capability requirement of shared witness.'"

2. Check vSAN on-disk format version support matrix to determine which ESXi version is compatible with the shared witness vSAN on-disk format version.
 

3. If the vSAN on-disk format version of the shared witness is not supported by the ESXi node, there are two options to resolve the issue:

Option 1. Upgrade the ESXi node version to support the shared witness vSAN on-disk format.

Engage Dell Support engineer to upgrade the ESXi node using "Rapid Appliance Self-Recovery (RASR) Factory Image Upgrade Procedure"

Then deploy the vSAN 2-node cluster with the new code version.

Option 2. Use a standalone witness to deploy the vSAN 2-node cluster.