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

NSX Requirements for HCX integration (71398)

Last Updated: 7/3/2023Categories: InformationalTotal Views: 16461Language:
Chinese (Simplified)JapaneseEnglish

6 like this article

Subscribe to get an email
newsletter with new updates

6 people found this helpful Please provide article feedback:

Purpose

The purpose of this article is to describe the NSX requirements for HCX integration

Resolution

Target side

For Deployment:

NSX Manager installed and configured in the target Virtual Center. Minimum supported versions:

NSX-T 3.0 or higher

NSX Manager should be registered in HCX Cloud Manager's Appliance-Management(9443) UI. NSX admin credentials are required.

NSX-V at cloud is officially unsupported for HCX cloud manager running 4.4.x or later.

The cluster where HCX appliances will be deployed should be NSX host prepared.

An NSX Transport Zone capable of creating Overlay networks in the cluster where HCX appliances will be deployed.

For Network Extension:

For HCX Cloud version running 4.3.x and below, NSX-V at cloud should have an NSX Edge or DLR to connect the extended network.

NSX-V at Cloud is unsupported with Network Extension HA feature. Only Standalone NE appliance should be used for extension.

For NSX-V at cloud, the Proximity Routing feature is already deprecated with HCX cloud.

NSX-T should have a Tier-1 router to connect the extended network.

If using Mobility Optimize Networking (MON) feature, a Tier-0 router must be configured.

For migrating VMs to an NSX logical network:

The cluster where the VMs are being migrated into should be NSX host prepared.

An NSX Transport Zone capable of creating Overlay networks in the cluster where the VMs are being migrated into.

For migrating VMs into a VLAN based network:

No other requirements.

Source side

NSX-V installed and configured in the source vCenter should have a minimum supported versions 6.4.0 or higher. Refer to Interop Matrix.

NSX registration with HCX is required on the source side only for the following use cases:

Extend NSX logical networks

Migrate NSX Tags

If registered, the same NSX requirements listed for the target side are applicable to the source side.

NSX-V can be registered with HCX at source/connector side for DC evacuation and V2T migration projects.

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
•
客户采购计划 - 计划的定义和策略 (71392)

KB
•
客户采购计划常见问题解答 – 一般信息 (71394)

KB
•
Customer Purchasing Program FAQ - お客様固有の質問 (71393)

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 NSX for vSphere

VMware NSX Data Center for vSphere

VMware HCX

Related Versions:

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant