'Cluster Partition' 'vSAN cluster configuration consistency" warnings on Oracle Cloud vSAN clusters.
Article ID: 326638
Updated On:
Products
Issue/Introduction
Symptoms:
The VMware solution is deployed on Oracle Cloud.
The vSAN Host is configured to PXE boot (boots from Network Share).
Each time the Host is getting rebooted, it will not rejoin the Cluster and VMs might become inaccessible.
You might see in Skyline Health the following alerts:
Environment
VMware vSAN 7.0.x
VMware vSAN cluster deployed on Oracle Cloud.
Cause
This is a known issue with Oracle-created vSAN clusters as Oracle deploys its vSAN Hosts via PXE boot.
Once the vSAN Host(s) is rebooted the vSAN unicastagent table will not update after the Host is removed from Maintenance mode.
This is due to Oracle using the -i switch for the command esxcli vsan cluster unicastagent add to bind an interface for the outgoing Network interface resulting in duplicate entries in the unicastagent list.
Resolution
This issue is fixed in ESXi 7.0.2.
If assistance required on this or looking for a workaround, please contact Broadcom Support.
Feedback
