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

Upgrading to DVS 6.6 known issues (52621)

Last Updated: 2/10/2021Categories: TroubleshootingTotal Views: 30749Language:
Chinese (Simplified)JapaneseEnglish

31 like this article

Subscribe to get an email
newsletter with new updates

31 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.

Purpose

VMware vSphere 6.7 comes with a new version of DVS, 6.6. VMware recommends the following:

Perform the upgrade to DVS 6.6 during a maintenance window.

NOTE: Upgrading a DVS affects all hosts on the DVS at once. To avoid possible issues to all hosts, make a new DVS at the appropriate version level, then move hosts and objects from your current DVS over to the new DVS after creation.

Change the DRS mode to manual before initiating the upgrade and skipping DRS recommendation for the duration of the upgrade. You can reset the DRS mode to its previous state once the DVS upgrade is complete.

Important: Upgrading to DVS version 6.6 is not supported with NSX for vSphere while running vCenter Server 6.7 and should not be attempted until you completed your upgrade to vCenter 6.7 Update 1.

Resolution

Note: NSX customers should upgrade to vCenter Server 6.7 Update 1 prior to upgrading vSphere Distributed Switches. VMware does not recommend to run a VM migration using vMotion or change the DRS to manual during the DVS upgrade to 6.6.

DVS upgrade to version 6.6 might fail if there are vMotion tasks running in parallel or Attempting multiple DVS upgrades to version 6.6 may cause some of them to fail

Symptoms:

The DVS 6.6 upgrade operations fails.

VDS status in the UI displays the message similar to:

Out of sync

You see a message in the UI as well as in the vpxd logs similar to:

Cannot complete a vSphere Distributed Switch operation for one or more host members.

Also, the DVS summary contains the message similar to:

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

Important:

If a vMotion operations are happening in parallel, the dvports of the DVS are subject to change (may be added / removed). This could lead to a an issue with the dvport configuration during the DVS upgrade.

If multiple DVS’es are being upgraded subsequently (with some of the DVS upgrades pending), some of the DVS Upgrades may fail with timeout. This occurs since the upgrade of these DVS’es may take some time to complete due to having a large number of ports allocated on them.

To resolve this issue:

Click on the DVS summary in the vCenter Server UI.

You should see this message:

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

Click the Rectify option displayed as part of the message. Alternatively, wait for the vCenter Server to rectify the DVS. This is done periodically every couple of minutes.

Note: If the DVS fails to auto sync with the Rectify button, see "The vSphere Distributed Switch configuration on some hosts differed from that of VMware vCenter (2042692).

vMotion operation fails with timeout if a vMotion task is happening during DVS 6.6 Upgrade

To resolve this issue, retry the vMotion operations once the DVS upgrade completes.

VMs and vmknics lose network connectivity if LAG ports are connected to DVS after VMs are connected and the DVS is upgraded

To resolve this issue, trigger reconfiguration of the affected VM by changing any DVPortgroup setting in the vCenter Server UI or through the API.

DVS upgrade to version 6.6 fails if the VMs vNIC portgroup is configured with PVLAN feature

To resolve this issue, migrate the virtual machines using vMotion out of the host, or power off the virtual machines. DVS upgrade should naturally proceed after 30 minutes.

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

VMware vCenter Server

Related Versions:

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

VMware vCenter Server 6.7.x

VMware vCenter Server 6.5.x

Take Our Survey

Support Assistant