Yesterday night, I was setting up a new VSAN cluster on Ravello and got hit with a network issue: Apparently my network was partitioned! The network for all hosts has been setup similarly on all hosts, so the network partition issue didn’t make much sense. MGMT Kernel: MGMT and vMotion traffic vmk0 10.1.0.1x VSAN Kernel: VSAN traffic vmk1 10.1.0.2x Unfortunately esxi004.vmusketeers.local had been added to a separate partition! Rather than checking each host separately, I used the VSAN PowerCLI commands to figure out if my hosts were properly configured for VSAN networking. PS C:\Windows\system32> $vsanhealth.networkhealth HostResult : {VMware.VimAutomation.Storage.Impl.V1.Vsan.Health.VsanHostNetworkHealthResultImpl, VMware.VimAutomation.Storage.Impl.V1.Vsan.Health.VsanHostNetworkHealthResultImpl, VMware.VimAutomation.Storage.Impl.V1.Vsan.Health.VsanHostNetworkHealthResultImpl, VMware.VimAutomation.Storage.Impl.V1.Vsan.Health.VsanHostNetworkHealthResultImpl} HostCommunicationFailure : HostDisconnected : HostInEsxMaintenanceMode : HostInVsanMaintenanceMode : HostWithVsanDisabled : IssueFound : True LargePingTestSuccess : False MatchingIPSubnets : True MatchingMulticastConfig […]