“In the ghetto, we use one vCenter vApp to migrate another vCenter vApp to Distributed vSwitches”
Or something like that. The background, was I needed to move some hosts and VMs in my home lab to vDS to take advantage of their awesomeness along side vCloud Director. However, as my primary vCenter lived on those hosts as well… what was I to do?
Taking a tip form here (thanks!), the procedure was thus:
I said in the ghetto, and I mean it. This worked for me, it may not for you. Also, doing it this way for more than a small handful of hosts could be quite cumbersome. Also, all that other “YMMV” stuff here.
- In Fusion or Workstation, import the vCenter 5.1 vApp, power it on, etc.
- Add your hosts into the new vCenter.
- Create vDS
- Migrate the host and VM Networking
- Now, this is where it gets fun. In the web client, browse to the vDS you created, and export:
- Export all the things:
- Save the file, and on the other side, import it:
- Once imported, verify she’s there:
- Move your hosts back to the original vCenter.
Again YMMV, but there it is, using one vCenter vApp to bootstrap vDS for another.
2 thoughts on “Migrate to Distributed vSwitches with the vCenter vApp”
nice find 🙂
how to do #4
Comments are closed.