u/H0TR0DL1NC0LN

▲ 8 r/vmware

"Cosmetic" Network Error on Hosts After Upgrade to 9.1.x.

Greetings, folks. I'm wondering if anyone else has experienced this and can confirm that the secondary effect is also just cosmetic.

I recently upgraded my entire vSphere environment from 9.0.2 to 9.1, and after the upgrades--to include upgrading the vDSs in my environment--I go into one of the hosts to take a new powered-off snapshot of vCenter for another operation when, lo and behold, I get a banner on my VMs on the host saying "This VM is attached to a network portgroup undefined that doesn't exist. Edit this VM and attach it to a different network."

Odd, I thought, but if you look deeper at the port groups, all of the distributed port groups on your vDS on the host also show VLAN IDs as "Unknown."

This Broadcom article clearly states that the banner symptom is purely cosmetic, but there is no mention about the distributed port group symptoms at all.

"This VM is attached to a network portgroup undefined that doesn't exist. Edit this VM and attach it to a different network." is seen on VM via ESX host client.

So, hivemind, has anyone else been similarly afflicted with this issue and seen both the banner issue and the VLAN IDs being "unknown" on the distributed port groups visible on their hosts? Has that also been "cosmetic" for you? Everything looks tip-top in vCenter, and everything is just working right along as it should. This is a greenfield deployment for me full of new appliances and test VMs from the old environment, so I'm just trying to make sure the field isn't foul before I migrate all of my VMs onto it.

reddit.com
u/H0TR0DL1NC0LN — 3 days ago