Loading...
Loading...
Known affected version(s) that were inferred because the vendor did not provide any: 7.0.3.02300
In some cases, vCenter might retrieve NSX properties from ESXi hosts, save them on the vCenter database and push these NSX properties back to ESXi hosts in various scenarios that can cause the following issues: A virtual switch gets out of sync because vCenter pushes stale NSX properties to an ESXi host. You cannot remove the NSX VIB after you remove a transport node, because vCenter pushes NSX properties back to the virtual switch. After an ESXi host reboot, vCenter feeds stale NSX properties back to the virtual switch. NSX cannot start on a virtual switch due to stale NSX properties. Logs are different in each case, but you can confirm the issue by checking the VPX_DVS_BLOB table in the vCenter DB. If you see NSX properties in the VPX_DVS_BLOB table, the issue exists. Look for properties such as: com.vmware.nsx.kcp.enable com.vmware.nsx.spf.enabled com.vmware.nsx.vdl2.enabled com.vmware.vswitch.disabled com.vmware.host.feature.container com.vmware.nsx.ens.loadbal com.vmware.nsx.ens.overlayl2flow This issue is resolved in this release.
https://techdocs.broadcom.com/us/en/vmware-cis/vsphere/vsphere/7-0/release-notes/vcenter-server-update-and-patch-release-notes/vsphere-vcenter-server-70u3v-release-notes.html
Click on a version to see all relevant bugs
VMware vCenter Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.