Funny enough, if I were to bootstrap the VCSA install using the installer into a single host vSAN directly, it comes up just fine into unicast mode without any of the above-mentioned symptoms.
Testing further to migrate the cluster into the earlier VCSA to see if it sticks.
Moving the hosts to the earlier VCSA (in a non-vSAN host) resulted in the same errors and warnings, so that didn't help.
Moving the hosts back to the bootstrapped VCSA works fine.
Moved the bootstrapped VCSA into the same non-vSAN host (as the earlier VCSA) and it continued to work just fine.
Adding a second, separate cluster of 3 hosts in this VCSA and it works fine too.
Compared the services running on the earlier VCSA and the bootstrapped VCSA to no difference.
Gave up, deleted the earlier VCSA.
In a way, it's resolved, but I'm still confused as to what could be the difference that caused this problem to begin with.
It looks like there may be some minute difference in the network config of the new VCSA. Is the bootstrapped VC the same version as the hosts? All hosts and VC running the same major version? Newer hosts + older VC will not play nice.
Maybe some firewall options were enabled in the non-bootstrapped instance?
Glad you have got it working now. Thanks for posting your experience with the deployment.
It’s the same VCSA version and all, as I had reinstalled from scratch since it’s a lab.
I didn’t expect any firewall differences either since the steps I did was all identical, as well as the virtual network setup, down to the same vlan and port config on the physical switch.
Please check output of below cmd and match it , it should match if not then correct it please.
esxcli vsan network list
Also can you confirm build no. for ESXi and vCenter please which you have in your LAB.
Is there any particular reason you are necro'ing this thread that hasn't been active since 2017?
Also, the OP hasn't logged into Communities since May 2019 in case you didn't see.