Skip to main content

Convert dvSwitch to vSwitch and back again

 dvSwitch to vSwitch and back again

Creating a Distributed virtual switch and adding a host is fairly straightforward. I have found that once a host is added to a dvSwitch ( or whichever way you wrap your head around the concept ) however that it’s a bit more difficult to convert it back depending upon how many virtual adapters are involved. This post documents the steps to add a host to a Distributed Virtual Switch and migrate 3 VMkernal adapters to it, and then migrate them back to the original Virtual Switch.
CONVERT to dvSwitch

(Fig 1) This screen shows the ESXi-1 host using a vSwitch configured with temporary VMkernal ports. Other than being set for DHCP they’re not used for any true purpose merely to allow for this example.

(Fig 2) As you can see in this screen I already have a dvSwitch configured with various dvPortGroups. The ESXI-2 server is already a participating host. I am going to add the ESXi-1 host and when I do I’m going to migrate the ports to the dvPG-VirtualMachines Port Group. Take notice of this section.
At this point I’m in the Inventory-Networking window and I’m going to click the ‘Add Host’ link in the upper right hand corner.

(Fig 3) The Add host GUI requires a host and desired NIC card selection. For this I’m going to select the vmnic1 and click next.

(Fig 4) Now we’ll migrate the virtual adapters from the Virtual Switch to the dvSwitch. Select the virtual adapters to migrate.

(Fig 5) Assign the migrating adapters to a dv Port Group.

(Fig 6) Here I simply select the dv Port Group identified as ‘dvPG-VirtualMachines’.

(Fig 7) Now you can see the vmk3, vmk4 and vmk5 have imported into the dvPG-VirtualMachines port group on the distributed switch.


So adding a host to dvSwitch is pretty easy. If there were thousands of virtual adapters that needed to be migrated the ease of which this interface makes that process would quickly become obvious. Migrating ports from a dvSwitch back to a standard vSwitch is just as simple however it’s not as automated and can be more time consuming. I haven’t figured out a way to migrate all virtual adapaters back to the vSwitch all at the same time like we did when we migrated the virtual adapters to the dvSwitch.
If someone knows a better or more efficient procedure please let me know.
(Fig 8) To begin the process of migrating the host back to a Standard vSwitch we have to get all the adapters moved off the dvSwitch. To start the process click the Manage Virtual Adapters link in the upper right.

(Fig 9) Each adapter must be selected individually then click ‘Migrate to Virtual Switch’ 
(Fig 10) Select which vSwitch to migrate the virtual adapter to.

There must be a way to migrate all the adapters to a Virtual Switch at the same time but I haven’t been able to figure out how. In this example I had to do this three times to get all the adapters migrated. In a heavy production environment there may be hundreds or thousands of adapters. I could see this taking a really long time. One would obviously drop to command line or script to get this done on a large scale system.
(Fig 11) Once all the virtual adapters have been migrated back to a Virtual Standard Switch the last thing to do is remove the host from the dvSwitch. For this you go back to the Inventory-Network screen ( cntr-shift-H ) and select the Hosts tab.

(Fig 12) To remove the host right click and select ‘Remove from vNetwork Distributed Switch’ In this example I want to remove the ESXi-1 host so I followed this step for this host.

(Fig 13) Going back to the Inventory-Hosts and Clusters screen and Configurations tab you can now see the dvSwitch is no longer associated with the ESXi-1 host.

And that’s how to add a host to a Distributed Virtual Switch migrating the virtual adapters and back again to the originating Virtual Standard Switch.



Popular posts from this blog

Question كيفية عمل share للـ outlook conntact لكل الـ Domain Users

  الحل بسيط جدا عايز الكونتاكت تتحدث دايما بحيث انك لما تضيف يوزر جديد يسمع في الكونتاكت اول حاجه بتدخل علي in office 2003 tools --- email account ---- add address book --- internet directory service (LDAP) type your server name then login info . mark this server require me to logon type any user on active directory and its password then save and close outlook and open it again now you will find all your active directory users in address book

3 things has to be done for better performance

  Tips from Goutham: 3 things has to be done for better performance: By default, XP displays extra graphic objects for menu items which can slow down your display. 1. To turn off these selectively... Right click My Computer Select Properties Click Advanced tab Under Performance, click Settings button To turn them all off, select Adjust for best performance Preference is to leave them all off except for Show shadows under mouse pointer and Show window contents while dragging 2. To speed up the display of the Start Menu Items, turn off the menu shadow. Right click open area of the Desktop Select Properties Click Appearance tab Click Effects button Uncheck Show shadows under menus 3. You can increase system performance by loading more of the system into memory. DO NOT attempt this with less then 512MBs of ram. Your system will become unstable. Click Start Click Run Enter regedit Click OK Go to HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Control Session Manager Memory Management Double cli

The difference between DNS and NDS

  Novell Directory Services(NDS) - Novell Directory Services (NDS) is a popular software product for managing access to computer resources and keeping track of the users of a  network , such as a company's  intranet , from a single point of administration. Using NDS, a network administrator can set up and control a  database  of users and manage them using a  directory  with an easy-to-use graphical user interface ( GUI ). Users of computers at remote locations can be added, updated, and managed centrally. Applications can be distributed electronically and maintained centrally. NDS can be installed to run under  Windows NT , Sun Microsystem's Solaris, and IBM's  OS/390  as well as under Novell's own  NetWare  so that it can be used to control a multi-platform network. NDS is generally considered an industry  benchmark  against which other products, such as Microsoft's Active Directory, must compete. Lucent Technologies plans to integrate NDS into its own QIP product