"The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server" on VDS - NSX backed environment.

Products

• VMware vCenter Server
• VMware NSX

Issue/Introduction

• We see "The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server" alert on VDS that contains NSX segments.
• There will be no port details under show details section of the alert.
• We will not see any missing connectee or ports from the ports view.
• Auto refresh or VM creation and migration on the affected VDS will not resolve the issue.
• The script from KB also temporarily resolves the issue and the issue comes back after a network drop or restart of the host. 
• We see entries from the logs as below :
  

  TIMEXXXXXZ In(166) Hostd[XXXXXX]: [Originator@XXXXX sub=Vimsvc.TaskManager opID=XXXXX sid=XXXXX user=vpxuser:<no user>] Task Created : haTask-ha-host-vim.host.NetworkSystem.invokeHostTransactionCall-XXXXX
  TIMEXXXXXZ Wa(164) Hostd[XXXXX]: [Originator@XXXXX sub=Hostsvc.NetworkProvider opID=XXXXX sid=XXXXX user=vpxuser:<no user>] Error setting vendorData for dvs XXXXX : Unable to set DVS vendor data com.vmware.nsx.ens.loadbal: Status(bad0007)= Bad parameter
  TIMEXXXXXZ Er(163) Hostd[XXXXX]: [Originator@XXXXX sub=Hostsvc.DvsManager opID=XXXXX sid=XXXXX user=vpxuser:<no user>] [HostDvsManager::ApplyDvsInt] ReconfigureDVSInt() caught Fault cause: vim.fault.PlatformConfigFault

Environment

7.x

8.x 

Cause

VC is pushing dummy NSX properties to VCDB. 

The "Dummy NSX property name" can be the following:
==================================================
"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"

Resolution

vCenter 8.0p5 has the fix, but the fix will not automatically clean up the existing dummy NSX properties in VCDB. This needs a DB modification, Please open a ticket with Broadcom technical support in order to resolve the issue.
Refer KB Link : Create Broadcom Support Case