fletch8527
Contributor
Contributor

ESXi 6.7 Portgroup Weirdness

Jump to solution

Recently I noticed that when I pull up a VM running on my ESXi 6.7 host that they have a yellow bar that states:

This VM is attached to a network portgroup LAN that doesn't exist. Edit this VM and attach it to a different network.

The weird thing is that the portgroup actually exists. But when I open the portgroup it shows no VMs assigned to it. When I pull up the console for the VM I confirmed that its network connection is actually working. But if I attempt to edit the VM it will auto switch the portgroup the the NIC to some other one.

I ended up making a new portgroup with the same VLAN and switched my VMs over to that new portgroup. Once they were all moved over and confirmed working I deleted the original portgroup that wasnt working. Then I went back to a VM and got that damn yellow bar again but this time it was saying that the new portgroup doesnt exists.

Any Ideas?

0 Kudos
1 Solution

Accepted Solutions
patrickds
Expert
Expert

I had a similar issue, check here:

https://communities.vmware.com/thread/599236

UI lets you pick an existing portgroup when creating a vmkernel nic, even one with VMs attached to it, giving strange results for the VMs.

So make sure you haven't accidentally converted your VM Port group into a vmkernel port group.

View solution in original post

0 Kudos
4 Replies
RickVerstegen
Expert
Expert

Can you try deleting the network adapter and re add it. Do it first with a test virtual machine.

Blog: https://rickverstegen84.wordpress.com/ Twitter: https://twitter.com/verstegenrick
0 Kudos
fletch8527
Contributor
Contributor

No luck. When I remove the network adapter then re-add it, I do not have an option to select that portgroup anymore. The strange part is that its works fine until I attempt to edit the VM as it will auto select a different portgroup. It complains that the portgroup is not available but it actually works fine.

0 Kudos
patrickds
Expert
Expert

I had a similar issue, check here:

https://communities.vmware.com/thread/599236

UI lets you pick an existing portgroup when creating a vmkernel nic, even one with VMs attached to it, giving strange results for the VMs.

So make sure you haven't accidentally converted your VM Port group into a vmkernel port group.

View solution in original post

0 Kudos
fletch8527
Contributor
Contributor

sorry about the long delay getting back to you (new born at home and configuring my sever/lab is far down the list). This was exactly my problem. I created a new port group for my VMK adapter, the messages went away.

0 Kudos