After converting ROBO vSAN cluster to standalone cluster, vSAN Cluster experiences Network Partition Issue one vCenter reboot.

Products

• VMware vSAN

Issue/Introduction

The standalone vSAN cluster is converted from ROBO cluster. 

The witness node has been removed from ROBO cluster.

After adding a new host into this cluster, the vSAN cluster experiences network partition issue once vCenter reboots. 

Environment

vSAN 7.x

vSAN 8.x

Cause

This can occur when the witness is not removed properly.

Resolution

1. Check if vSAN unicastagent configuration is correct

https://knowledge.broadcom.com/external/article/326427/configuring-vsan-unicast-networking-from.html

2. Check if there is witness information left via RVC

vsan.stretchedcluster.witness_info .

3. If yes, remove the witness information 

vsan.stretchedcluster.remove_witness .

4. Reboot vCenter

 

Refer to https://knowledge.broadcom.com/external/article/326817