Symptoms:
Currently, there is no resolution.
Workaround:
First, identify the list of ESXi hosts contributing to the cluster's error by reviewing the NSX Manager logs (vsm.log) looking for the message highlighted in the Symptoms section.
Once the ESXi hosts are identified, there are two possible workarounds for this issue.