vm network migrate to different vswitch

[VIRTUALFLARE1]

Hi Admins,

Apologies if I posted this question into a wrong forum.

My environment includes ESXi 6 latest update, vcenter server 6 latest update, web client.

I had my Win2012 VMs on a ESXi 6.0 which were using the VSS vswitch0 for I/O including the Management network. (I believe this is the default mechanism in VMware that if you dont define the different network profiles, the VMs take the default network profile.. ie., VM Network on vswitch0).

As I was trying to segregate the different network profiles, like, vMotion Network, vApp Network, Management network, Storage network etc, I removed the VM Network port group from vswitch0. (I had to power off the VMs to get this task completed). Once I removed the VM Network port group and when I created another port group with the name VM Network by creating a new VSS vswitch2, I was unable to ping any VMs. Also I removed and tried to re-add a new network interface for my VMs but was unable to see any network profiles associated with the VMs.

I have attached the screenshot's of the errors.

Am I missing anything here ?

Regards

Taz~

[npadmani · Accepted solution]

VM Network which you have created on vSwitch2 is not Virtual Machine Port Group, It's VMKernel port that you have created by mistake.

Please remove it if you are not planning to use it.

and add Virtual Machine Port group, then when you edit your VM Settings, under vNIC, you will definitely see that port group name.

At the moment, I see that you don't have any VM Porgroup in your environment.

[VIRTUALFLARE1]

You are right. I was mind struck. I created the VMKernel port which was causing the issue. The minute I re-created a VM Port group, everything became normal.

Appreciate your quick response.

Thanks again!