Ghost Networks sticking with VMs (even after deleting NIC)

[EnormousBeans]

Hello,

I am running into network issues with my VMs. I am using ESXi 5 hosts clustered together using vsphere 5. I have some VMs that when I change their NICs from one network to another (i.e. "Private" to "Private Test"), instead of substituting the old network for the new one, the new one is added and the old network remains. However, the assigned NIC is still assigned to the new network, and now, I have no way of removing the old network from the VM. (See attached image)

Additionally, I then tried re-assigned the NIC from "Private Test" back to "Private" and in the summary tab, the number of assigned networks went back to 1, and the VM now only had "Private" as a assigned network.

I then tried to delete the NIC altogether, hoping that would de-assign the VM from the "Private" network. Well, that did not work either. Now, even without a NIC, the summary tab of the VM still shows it being assigned to the "Private" network.

I am sure someone has posted something about this kind of bug before. So, can someone please point me in the right direction.

Thanks

Abraham

[jeff9565]

Abraham,

When you change the NIC from the old network to the new network, are you still able to ping the IP address from the old network?

Jeff

[EnormousBeans]

No I am not. It appears the issue is only in vsphere. The VMs function idealy when you change or re-assign virtual networks.

[jeff9565]

I have seen GUI errors before and I know this may sound weird but after you do your switch, close your vSphere client and re-open it.  Let me know if it still shows the two networks.

Jeff

[Kahonu84]

Same thing when you direct connect to the host?

[merse]

I'm having the same issue - even when I remove the vNIC from the VM, two ghost networks remain.

However this only appears in vCenter, not direct to host.

I hope it's just a bug that they're not being refreshed and aren't actually connected to these other networks...?

m

[VirtuallyMikeB]

Good day,

Is vCenter fully patched, then?

Cheers,

Mike

http://VirtuallyMikeBrown.com

https://twitter.com/#!/VirtuallyMikeB

http://LinkedIn.com/in/michaelbbrown

[Aviator20111014]

Hi *,

same problem here when switching between standard port group and distributed port group. (vCenter Server 5.0.0 - 623373).

Cheers

David

[Aviator20111014 · Accepted solution]

Hi,

I just tested some things. Have you checked if your VMs have Snapshots?

All of my VMs showing ghost networks had snapshots. Deleting the snapshots removed the ghost networks.

Cheers

David

[akshunj]

I agree with Dave's assessment that removing any snapshots will correct this. I experienced the same problem and determined the cause was due to a snapshot. 

[sivaksk147]

Hi,

Your Right Dvaid ! i agree to your point....

[EnormousBeans]

Removing the Snapshots did the trick!

Thank you all very much for your time and help

Abraham

[PJudgeAAM]

Great find, thanks!

Cured a problem I was seeing on an ESXi 4.1 box being migrated over to 5

[SuperVertrix]

I just want to add that you're correct. I was able to get rid of the VM machine with the ghost network after doing this.

Cheers!

SuperVertrix!

[labtech1]

THANK YOU THANK YOU THANK YOU. I did not think about snapshots..