Move from standard vSwitch to Distributed Switch on VMware vSphere 8

In this video, I will show you how to configure and move from a standard vSwitch to a Distributed Switch on VMware vSphere 8.

[@michaelpietrzak2067]

Great production value. Nicely done.

[@anacletyakilembe4934]

very nice and well explained !

[@just01guy96]

Thanks!

[@OrgNetworks]

Thank you.

[@clintleffingwell8129]

Fantastic video; very clear and easy to follow. You did not show this part; but after you removed the uplinks from the old vSwitch and added them to the new VDS, would you then go back and delete the old vSwitch?

[@vikash-tech-wizard]

You can delete the vSwitch, make sure that nothing is using it before you do. For troubleshooting reasons you could decide to leave it in.

[@clintleffingwell8129]

@@vikash-tech-wizard Following up on this, after a call earlei this week with a former senior VMware support engineer (and now TAM), he recommended to keep your management traffic on the vSwitch and local to the host, in case your vCenter goes down or loses connectivity, but move all the other traffic to the VDS. Just food for thought.

[@a8eoi13]

Hi I have a vswitch0 that only has ONE physical nic and I need to transfer everything from this vswitch0 (Management and VM Network) to the DSwitch in my vCenter. Am I right in assuming that if I just transfer the vmkernels and virtual machines first after adding the hosts to the DSwitch that I can then transfer the physical nic, with only minor downtime but it'll regain connectivity once migrated?

[@vikash-tech-wizard]

You could try that but I have not tested that setup. Make sure you are not doing it in a production environment and keep in mind that when it fails, you might look into resetting the networking stack in the esxi host. Goodluck

[@devendrapatil07]

Hi, have you try this thing, its failing in my case with error - An error occurred while communicating with the remote host. Network configuration change disconnected the host 'sandbox3-node3.vclass.local' from vCenter server and has been rolled back. Cause: A change in the network configuration disconnected the host 'sandbox3-node3.vclass.local' from vCenter Server. The change has been rolled back.