I have the same problem. would realy like to know if you found out anything.
The same problem my friend!! Can you help me?
Thx in advanced
My solution to this "problem" is the following:
- Create a "dummy" vSphere Cluster in vCenter
- Add your new ESXi Host to this "dummy" cluster
- Make sure that your new ESXi Host is a member of the same dvSwitch, as the other "VXLAN" ESXi Hosts
- In vCNS Manager do a preparation of this "dummy" cluster, with the same settings as the original cluster
- Give the newly created "vmk Virtual Adapter" on the new ESXi Host a static IP, if needed
- In vCenter, put the new ESXi Host in Maintenance Mode and move it to the original "VXLAN" cluster
- Take the new ESXi Host out of Maintenance Mode
- Delete the "dummy" vSphere Cluster in vCenter
- In vCNS Manager, do a refresh in the upper left corner of the vCNS Manager window
- In the Preparation view, the "dummy" cluster should now be gone
- Test your Connectivity
- In the "Network Scope" view
- Click your Network Scope
- Select the "Clusters" pane, of the selected Network Scope
- Select one of your ESXi Hosts, and click the "Gear" icon, to test connectivity
thank you so much!!!
it,s later for me but your help is GREAT!!!
I Don, t forget your great solution.
You are more than welcome.
I have a blog post about this coming, just need to find the time to finish it up.
U saved me...Thanks alot
I had the same issue. Normally vShield should start the prepare process automatically once you add hosts to a prepared cluster. But it seems that this doesn't always work. What helped in my case was rebooting the vShield Manager. After it came back online it detected the new hosts and started the prepare task right away.
Thought I leave this here for all the poor souls that still run a vShield instance.