Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

ESXi hosts showing out of sync with distributed switch (76959)

Last Updated: 2/22/2024Categories: How toTotal Views: 115439Language:
Chinese (Simplified)JapaneseEnglish

15 like this article

Subscribe to get an email
newsletter with new updates

15 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

One or more ESXi hosts connected to a vDS show as being out of sync with vCenter:

In vCenter > Networking > vDS > Summary, you see the warning:

The vSphere Distributed Switch configuration on some hosts differed from that of the vCenter Server.

Purpose

This article contains steps to resolve dvPort conflicts between ESXi and vCenter when the "Out of Sync" error is because of a VM.

If the below KB does not apply, see The vSphere Distributed Switch configuration on some hosts differed from that of VMware vCenter- "Out of Sync"

Resolution

======================================================================
NOTE: For a VCF Environment: The safest way to resolve the out-of-sync error would be to remove the host, decommission and recommission using the built-in VCF workflows. The workarounds mentioned below could result in an undesired results for that ESXi host between the SDDC manager, vCenter and NSX inventories.
======================================================================

Process to gather important information:

Information gathering steps are explained below:

If you click on "Show Details" next to the message above, the hosts and dvPort numbers that are out of sync are listed.

Make a note of these dvPorts/Hosts

Navigate to vCenter > Networking > vDS > Ports

Scroll down the "Port ID" column to find one of the dvPorts from Step #2

Make a note of the portgroup listed in the "Port Group" column, there may be no VM listed in the "Connectee" column.

When no VM is listed:

If no VM is listed in the "Connectee" column, there are three ways to potentially resolve the issue.

Method 1

Method 2

Method 3

Method 1:

In most cases, the easiest way to clear this message it to remove the host from the vDS entirely. After removal, it can then be brought back in to the vDS and the message will clear. This involves a networking change, so it is recommended to do this step during a maintenance window, if possible.

Move all attached virtual machines to another host or to a standard switch.

A new standard switch can be built using one of the physical adapters that passes the correct VLANs from the vDS. See the note below on Load Balancing information.

Move all vmkernels from the vDS to a standard switch.

Again, a new standard switch can be built using one of the physical adapters that passes the correct VLANs from the vDS. See the note below on Load Balancing information.

Remove any remaining physical adapters from the vDS.

Remove the host from the vDS. Click Home > Networking. Right click the vDS, click Add and Manage Hosts > Remove Hosts, and follow the wizard. (Note: may need to also remove the host from inventory for some issues)

Add the host back to the vDS along with its vmkernels, physical adapters, and VMs.

Note: if you need to use the same physical adapters from the current vDS on the standard switch, check the Load Balancing on the distributed switch. To do this, click Home > Networking, then click the vDS that is being cleared. Next, click the three dots next to the port group you are copying, then click View Settings > Policies and scroll down to Load Balancing. If the Load Balancing is set to IP Hash, this setting must be broken on the physical switch in order to use these physical adapters on the standard switch.

Method 2:

Using one of the ports listed in the error, follow the steps in the diagram below. Once the steps are completed, wait for several minutes, then check if the error is still present.

Method 3:

Create a new blank VM (no OS needed)

Edit the VM and add the VM to the PortGroup that you identified in Step #5 of the "Information Gathering Steps", click Ok

SSH into the host with the blank VM

Navigate to the blank VM's .vmx file

Edit the .vmx file with "vi" editor

Change the value of "ethernet0.dvs.portId" to the port number from Step #2 above

Power the VM up

Migrate the VM to the host listed in Step #2

Migrate the VM back off this host

Refresh the vCenter Client

When VM is listed:

If there is a VM using the dvPort in the "Connectee" column, try the following:

Create a new portgroup with identical settings (VLAN, Teaming Policy, etc) to the portgroup from Step #5

Edit the VM, and put it in the new portgroup

After a short wait, refresh the vSphere Client to see if the host is in sync

If the host is still out of sync, migrate the VM to a different host in the cluster

If the host is still out of sync, try Method #1 or #2 above now that the dvPort is unused by a VM

Note: The vMotions on/off the problematic hosts are critical.  The goal is to perform a task (related to the dvPort in conflict) that both ESXi and vCenter are aware of to force them both to re-synchronize.

Related Information

The vSphere Distributed Switch(vDS) configuration on some hosts differed from that of VMware vCenter Server

Removing a host from a virtual distributed switch in vSphere fails with the error: The resource 'port-id' is in use

VMware Skyline Health Diagnostics for vSphere - FAQ

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

Related Versions:

Take Our Survey

Support Assistant