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

Versions of HCX before 3.5.1 experiencing Interoperability issues with vDS 7.0 in vSphere 7 (79178)

Last Updated: 6/27/2022Categories: AlertsTotal Views: 1270Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

If you have already upgraded to a 7.0 vDS you may see the following in versions of HCX before 3.5.1:

After upgrading the Distributed Switch (vDS) to 7.0 you receive errors like:

"Cannot migrate <VM name> using selected migration as it is connected to port group on distributed switch of version 7.0.0"

Cause

vMotion, Cold Migration, and RAV features in versions of HCX before 3.5.1 are not supported on vDS 7.0.

Those versions have issues working with the new vDS 7.0 switch in vSphere 7.

Resolution

The resolution is to upgrade to HCX 3.5.1 or newer

Workaround

Use vDS 6.6 as the highest vSwitch version before HCX 3.5.1.

Because a vDS cannot be downgraded gracefully, the vDS must be recreated as a vDS 6.6 or earlier in order to restore connectivity to HCX infrastructure.

This may involve HCX or VM downtime depending on the architecture.

Warning, if you are using a LAG on the hosts contact VMware Support Networking team for assistance as the process is different.

Create new vDS as version 6.5 or 6.6

Ensure that the MTU matches the value for the existing vDS

Networking > Configure > Settings > Properties > Edit

In the Advanced section verify the MTU value

Add the required hosts to the new vDS and move one physical NIC to the new vDS

Right click on the new vDS and select Add and Manage Hosts

Select Add hosts

On the Select hosts page, click New hosts, select from the hosts in your data center, click OK, and then click Next.

On the Select network adapter tasks page, select the tasks for configuring network adapters to the distributed switch and click Next

On the Manage physical network adapters page, configure physical NICs on the distributed switch.

From the On other switches/unclaimed list, select a physical NIC.

If you select physical NICs that are already connected to other switches, they are migrated to the current distributed switch.

Click Assign uplink.

On the Manage VMkernel adapters, click next

Click Finish

Recreate all required port groups on the new vDS

On the vSphere Client Home page, click Networking and navigate to the distributed switch.

Right-click the distributed switch and select Distributed port group > New distributed port group.

On the Name and location page, enter the name of the new distributed port group, or accept the generated name, and click Next

Ensure the VLAN matches the existing port group

Migrate the VMs from the old 7.0 vDS to the new 6.5/6.6 vDS

the vSphere Client, navigate to a data center.

Right-click the data center in the navigator and select Migrate VMs to Another Network.

Select a source network.

Use Browse to select a destination network and click Next.

Select virtual machines from the list to migrate from the source network to the destination network and click Next.

Review your selections and click Finish.

From here verify all of the HCX services have been moved in to the new vDS
Reconfigure the HCX Services to use the new 6.5/6.6 vDS

the HCX Network Profile

In the HCX Manager:

Navigate to the Network Profiles interface:

the vSphere Client, navigate To HCX > Interconnect > Multi-Site Service Mesh > Network Profiles.

At the destination site, navigate to https://hcx-cloud-ip-or-fqdn > Multi-Site Service Mesh > Network Profiles

Edit the Netowrk profile

Select a vCenter Server and existing Network.

Select a vCenter Server from the drop-down menu.

Select Distributed Port Group, Standard Switch Port Group, or NSX Logical Switch to filter the available networks by type.

Select the copy of the original network on the new vDS

Unextend all networks and update any Network Extensions to the new vDS as needed

This will redeploy the NE appliances to the new vDS

Reconfigure the IX Migration Service to use the new vDS

Once all workloads have been moved to the new vDS, move the last of the physical NICs to the new vDS

From vCenter

Right click on the new vDS and select Add and Manage Hosts

Select Manage host networking

On the Select hosts page, click Attached hosts, select from the hosts that are associated with the distributed switch and click OK

Click Next

On the Manage physical adapters page, select a physical NIC from the On other switches/unclaimed list to assign an uplink to the adapter

Select all remaining pNICs from the 7.0 vDS

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
Workspace ONE Content 3.22.1 for Android リリースのお知らせ (79224)

KB
•
VMware Intelligent Hub 20.04.1 for iOS リリースのお知らせ (79195)

KB
•
CRSVC-11528：「デバイス削除」などのデバイス管理操作が断続的に失敗する (79114)

KB
•
Workspace ONE SDK 20.4 for Android リリースのお知らせ (79124)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware HCX

Related Versions:

Take Our Survey

Support Assistant