unicastagent list is missing in new node added to VSAN cluster.

[techlearner123]

HI,

We created a singe node VSAN using esxcli  and deployment Vcenter on top of it and created a cluster with VSAN enabled. . When we were adding the additional nodes on the VSAN cluster  , the unicastagent list is empty in nodes , which create a issue for VSAN Nodes to communicate ?

[TheBobkin]

Hello techlearner123​,

Which nodes don't have complete unicast lists: the first node or any additional nodes? Any set to ignore vCenter unicast updates?

As you didn't create the cluster through vCenter, if there is no data on this cluster (e.g. it is new and blank) then probably best to create a new cluster with the new nodes, migrate the vC to it and then move the first bootstrapped host.

Alternatively unicast agent lists are simple to rebuild (VMware Knowledge Base ) but it is best to ensure that vCenter knows the cluster as well as the nodes do, e.g. vCenter is authoritative in vSAN Health should be green and all nodes with the same information as the vCenter.

Bob