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

Cross vDS vMotion of a VM between clusters fails during the compatibility check (52248)

Last Updated: 11/8/2023Categories: TroubleshootingTotal Views: 27573Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Cross vSphere Distributed Switch (vDS) vMotion of a VM between clusters fails during the compatibility check.

You see this error in Virtual Machine migration wizard in the vSphere Web Client:
Incorrect destination network is selected. Review compatibility section for more details.

The compatibility field displays a message similar to:
"Currently connected network interface" 'Network adapter (X)' cannot use network 'DPortGroup (Y) (DSwitch (Z))', because "the destination distributed switch has a different version or vendor than the source distributed switch".

Cause

This issue occurs because the vCenter Server performs network compatibility checks when initiating a vMotion to prevent configuration issues between distributed switches that are on different versions.

Impact / Risks

Cannot cross vDS vMotion or vMotion a VM.

Resolution

This is an expected behavior in a mixed VMware vSphere/vDS version environment as compatibility checks require the source and destination vDS are of the same version.

For cross vDS vMotion to be successful, the source and destination vDS should be on the same version.

To resolve this issue, ensure the source and destination vDS are of the same version.

For example:

Source vDS version 6.0.0 vMotion to destination vDS version 6.0.0

Source vDS version 6.5.0 vMotion to destination vDS version 6.5.0

Workaround

There are 2 available options to work around this issue:

Workaround 1: When cross migrating VMs from a source vSphere 6 cluster to a destination vSphere 6.5 cluster, a standard vSwitch can be created on the vSphere 6.5 cluster. VMs on the source 6.0 cluster must also be migrated to a standard switch to provide a supported migration path. Afterwards, the VMs can be migrated to the vDS that is on version 6.5.

Workaround 2: When cross migrating VMs from a source vSphere 6 cluster to a destination vSphere 6.5 cluster, a vDS of the version 6.0.0 can be created on the destination vSphere 6.5 cluster. After a successful VM migration, the vDS version 6.0.0 can be upgraded to version 6.5.0.

Related Information

For more information about Network Compatability checks during vMotion between vCenter instances, see the Network Compatibility Checks During vMotion Between vCenter Server Instances section in the vCenter Server 6.5 and Host Management guide.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
vRealize Operations からのソリューションの削除 (2114441)

KB
•
在 Cloud Director 中添加/更新网卡时出现“双堆栈网卡需要 IPv4 和 IPv6 地址”错误 (79344)

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

Results 1-3 of 3

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

VMware NSX for vSphere

Related Versions:

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.0

VMware vCenter Server 6.5.x

VMware vCenter Server 6.0.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

VMware NSX for vSphere 6.1.x

VMware NSX for vSphere 6.0.x

Take Our Survey

Support Assistant