Hello wsanders11,
Are you trimming some information from that esxcli vsan cluster get information? I ask as based on the build version you indicated these should also provide info regarding whether Unicast Mode is enabled and Maintenance Mode state.
Has the new node been added to the vSphere-level cluster or is it currently residing somewhere else?
Obviously you should verify your network configuration and ensure that you can ping between the vSAN-enabled interfaces on the existing and new node e.g.:
# vmkping -I vmkX xxx.xxx.xxx.xxx
You could also verify that the new node receives traffic over 12321 using tcpdump-uw
What On-disk format version do the disks have? Some versions can prevent addition to a cluster with newer versions/Unicast - if you are POSITIVE that you won't ever need whatever data was/is on those disks then wipe them via the Web Client: Host > Configure > Storage Adapters > Select adapter > Select disk > All Actions > Erase partitions
If all of the above is okay (e.g. residing in cluster, no partitions on disks) then check the Unicast agent list on the node that it contains the correct info for all other cluster members and that they all contain the new nodes info - if they don't have the correct info then manually add these or remediate the cluster via Cluster > Monitor > vSAN > Health > 'vCenter state is authoritative' > remediate cluster
If remediation via GUI doesn't work then check that this is set to 0 on all nodes:
# esxcfg-advcfg -g /VSAN/IgnoreClusterMemberListUpdates
Probably not part of the problem but why does there appear to be a 1 hour time difference between the nodes there?
Bob
