Migrate vmk0 from stamdard switch to distributed switch

[JDMils_Interact]

I just migrated 4 hosts from 5.5 to 6.0U3 and three worked fine, the last one HOST05, upgraded but I lost the network connections. I thus re-installed the V6.0U3 OS from an ISO and am in the middle of setting it back up for the cluster and found the following, strange setup:

All existing hosts have the vmk0, the Management kernel on VLAN036, on the DV switch. They have a secondary management IP allocated as vmk2 on VLAN037 on the standard switch.

My new host HOST05 has the vmk0 (VLAN036) on the local switch and the vmk5 (secondary Management IP) on VLAN037 on the same standard switch.

My question is, how do I move vmk0 from the standard switch to the DV switch?

I tried to migrate vmk0 from the standard switch to the DV switch using:

- Select DV switch.

- Manage Virtual Adapters.

- Add.

- Migrate existing virtual adapters.

- Select "Management Network" (which is vmk0), change destination port group to port group with VLAN036 on DV switch.

- Finish

Error:

Call "HostNetworkSystem.UpdateNetworkConfig" for object "networkSystem-973651" on vCenter Server "MyvCenterServer.mydomain.local" failed.

Network configuration change disconnected the host 'HOST05.mydomain.local' from vCenter server and has been rolled back.

A change in the network configuration disconnected the host 'HOST05.mydomain.local' from vCenter Server. The change has been rolled back.

I tried the same from the web client with the same result.

So it looks like it won't migrate the vm kernel due to the loss of comms between the vCenter server and host. So how do I do this?

I tried launching the thick client and attaching directly to the host and using the above method, but when it comes to choosing the destination port group to attach the vmk0 kernel to, I get nothing in the drop-down.

[diegodco31]

Hi

The distributed port group to where you're migrating the management interface is already configured with appropriated VLAN (including on physical switch) ?

[JDMils_Interact]

The physical switches do have the VLAN as this host was working OK before it was upgrade from 5.5 to 6.0.

The VLAN is VLAN036 on the standard switch and is called MY_VLAN36 on the DV switch- both have the same VLAN designation.

The other three hosts all have vmk0 on the dv switch.

[HassanAlKak88]

Hello,

Kindly follow the below procedure:

1. In the vSphere Web Client, navigate to the distributed switch.
2. From the Actions menu, select Add and Manage Hosts.
3. In Select task, select Manage host networking and click Next.
4. In Select hosts, click Attached hosts and select from the hosts that are associated with the distributed switch.
5. Click Next.
6. In Select network adapter tasks, select Manage VMkernel adapters and click Next.
7. In Manage VMkernel network adapters, select the adapter and click Assign port group.
8. Select a distributed port group and click OK.
9. Click Next.
10. Review the impacted services as well as the level of impact.
11. Click Next and click Finish.

Please consider marking this answer "CORRECT" or "Helpful" if you think your question have been answered correctly.

Cheers,

VCIX6-NV|VCP-NV|VCP-DC|

@KakHassan

linkedin.com/in/hassanalkak

[JDMils_Interact]

Thanks Hassan, I tried those steps and still get the same error:

A change in the network configuration disconnected the host 'MyvCenterServer.mydomain.local' from vCenter Server. The change has been rolled back.

When I added the host to the cluster, I added it with the IP address assigned to vmk0, so that is now the main IP for this host as vCenter sees it so I assume this is why the error occurs. I tried to add the host using the secondary IP (vmk5) but there is no DNS for that IP and I verified this with the other hosts in the same cluster.

[JDMils_Interact]

So, it's been done already on the other hosts, I just have no info on how to do it- I guess I'll have to log a support call for this?

[Christopher Dooks]

In my 6.7 homelab with two hosts, I could not migrate the host which had the vCenter appliance on.

What I did is migrate the host without the appliance on over to the vDs and new port group.

I then vMotioned the vCSA over to the new host, putting it on the new port group.

After that I was able to migrate the original host.

[RajeevVCP4]

You mean to say earlier host 5 was on DVS now it is on SVS ?

If yes , disconnect host from vcenter server remove from Vcenter server then add host

It will work if stale entry is there of this host.

[JDMils_Interact]

I rebuilt the host using the 6.0.0 6921384 ISO so it is now the same version as the upgraded hosts (which were upgraded from 5.5 to 6.0.0 6921384). All hosts had their main management IP as vmk0 which was on the distributed switch, and a secondary management IP vmk5 on the standard switch. I'm not sure how this was setup.

When I setup HOST05, it automatically created a primary management IP vmk0 on the standard switch and I would like to move this to the distributed switch to match the other hosts, but I cannot figger out a way to do this. I tried removing the host from vCenter and re-adding it but that does not change the setup.

[Christopher Dooks]

What method have you tried?

[JDMils_Interact]

I used the Add Host method from the client to add the host, and when added, vmk0 is on the standard switch.

[Christopher Dooks]

Does the host which you are migrating have the vCenter server on it?

Does the standard switch management port group have a VLAN assigned, and if so is the distributed port group that you are migrating to have the same VLAN tag?