Error "The vNetwork Distributed Switch configuration on some hosts differed from that of the vCenter

[lettech]

Hi all. We have this error on three of our hosts (ESXi 6.7u3) and has been like this for a couple of days. The "rectify" option doesn't do anything in this case and according to the VMware KB I have found, the resolution is to remove and re-add the affected hosts to the vDS. Unfortunately we are about to go into a change freeze.

Can anyone tell me the impact of ignoring this message for 3-4 weeks until we get back in the new year? Will the data center explode or will nothing happen? Seriously, any help would be appreciated.

Cheers. 

[scott28tt]

Expect a moderator to move your thread to the area for vSphere.

[a_p_]

Well, not sure about the impact without knowing the excat reason.

I ran into a similar issue long time ago, and IIRC I was able to resolve the issue by following the steps in Method 2 from https://kb.vmware.com/s/article/76959

Please note, that it might be necessary to reload the VM after editing the .vmx file in step 6.
see https://kb.vmware.com/s/article/1026043 for how to relaod the .vmx file.

André

[lettech]

Thanks Andre, appreciate your reply. I'm aware of the KB article you refer to but after assessment in our case it will be easier to do method one (remove the host from the dVS and re-add) because we have dozens of port groups.

What I am trying to find out is if there is any impact if we ignore the error message until after the holiday change freeze as we don't have resource bandwidth to resolve prior.

[RickVerstegen]

https://kb.vmware.com/s/article/2042692 in the above kb the following is mentioned under impact/risk section: 

Most of the time, this message is benign and can be safely ignored until a maintenance window.

[lettech]

Thanks Rick. Yes it's a synchronization issue between the host proxy switch and the vcenter configuration so it makes sense that it should retain the last known good settings until everything is synced back up. It would seem to me that the only risk should be when future changes are made to the dVS it may not update the affected hosts.

At any rate, I just wanted to semi-verify and grateful for your input.

Thanks very much.