Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

Upgrading vSphere Distributed Switch after upgrading vCenter to 6.7 shows the message “An Upgrade for the vSphere Distributed switch in datacenter is in progress” (66816)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 16744Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

After upgrading to vCenter 6.7 and then attempting vSphere distributed switch upgrade from vDS 6.5 to vDS 6.6 version via web client results in the following message “An Upgrade for the  vSphere Distributed switch in datacenter is in progress”

Purpose

To understand the behavior during VMware vSphere Distributed Switch(VDS) upgrade from vDS 6.5 to vDS 6.6 via Web client as well as via HTML Client

Cause

The property of  VDS  is  out of sync of the real status in vpxd memory and database.

Impact / Risks

No impact

Resolution

This is resolved in 6.7 U2 - 6.7 U2 Release Notes - Resolved Issues - Networking

Download vSphere 6.7 U2

You might see a message An Upgrade for the vSphere Distributed switch in datacenter is in progress even after the upgrade is complete. This happens if no host member is available in the vSphere Distributed Switch configuration, or if a host member has failed to upgrade several times.

This issue is resolved in this release. If you already face the issue that no host member is available in the VDS, you must do the following:

Backup the vCenter database - for more information https://kb.vmware.com/s/article/2091961

From the PostgreSQL database, run the command

update vpx_dvs upgrade_status set upgrade_status=0;

From the the appliance shell, run the command

vmon-cli -r vpxd.

Workaround

Add a new portgroup on the VDS and then delete the newly added portgroup.
This will make the H5 client  to show the synced status.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
vSphere Update manager 无法扫描或修复主机：错误 "vCenter 无法将主机升级代理部署到主机" (67018)

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 vCenter Server Appliance

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server 6.7.x

Take Our Survey

Support Assistant