Product Announcements

Where is the virtual adapter migrating option in Next Generation Client?

Today while I was working on a LAB, I struggled to find where the migration option is for the vmknics in the new NGC client. In the traditional client, as shown in the screen shot below, you can select the virtual adapter and then either choose to change the properties of the adapter or migrate it to another switch

Traditional Client Screen Shot

If you look under the similar view in NGC, you won’t find that migrate option.

The following screen shot shows the view in the NGC where you pick a Host, click on networking properties, and then select virtual adapters.

NGC – Virtual adapter view

After you click edit you get the following screen with no option to migrate.

NGC – No option to Migrate

So where is the migrate option now? It is available under the virtual switch properties of that host as shown below

NGC – Virtual Switch view where Migration option is available

You can see in the above screen shot that there are two virtual switches configured on this host – VDS-Mgmt and vSwitch0. Currently, the management vmknic is connected to VDS.

Let’s migrate the management vmk0 virtual adapter from the distributed switch to the standard switch. The following are the steps to migrate the virtual adapter from VDS-Mgmt to vSwitch 0.

1)    Select vSwitch 0 and click the migrate icon.

 

NGC – Migration of vmk0 – Step1

2)    Select the vmk0 to migrate and click next

NGC – Migration of vmk0 – Step 2

3) Define the port group on the virtual switch and configure VLAN. Then follow the wizard to complete the migration process.

NGC – Migration of vmk0 – Step 3

As you can tell, I am also used to the traditional client, and old habits die hard !!

In this case I feel the change is for better, because the migration of any physical or virtual adapter is related to virtual switches. So having the migrate option per host at the virtual switch level makes sense.

I hope this is helpful.

Get notification of these blogs postings and more VMware Networking information by following me on Twitter:  @VMWNetworking