VMware HCX delivers secure and seamless app mobility and infrastructure hybridity across vSphere 6.0 and later versions, both on-premises and in the cloud. HCX abstracts the distinct private or public vSphere resources and presents a Service Mesh as an end-to-end entity. The HCX Interconnect can then provide high-performance, secure, and optimized multi-site connectivity to achieve infrastructure hybridity and present multiple options for bi-directional virtual machine mobility with technologies that facilitate the modernization of legacy data centers.
Updated on: 07 MAY 2021
VMware HCX 4.0.2 | 07 MAY 2021 | Build 17991614 (Connector), Build 17991554 (Cloud)
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- About VMware HCX
- Before You Begin
- What's New in this Release
- Resolved Issues
- Security Issues
- Deprecation Notices
For more information, see the VMware HCX User Guide in the VMware Documentation Center.
Starting with the HCX 4.0 release, software versioning adheres to X.Y.Z Semantic Versioning, where X is the major version, Y is the minor version, and Z is the maintenance version. For more information about HCX software support, lifecycles, and version skew policies, see VMware HCX Software Support and Version Skew Policy. This document includes the section HCX Support Policy for Vacating Legacy vSphere Environments, with more information available in VMware KB 82702.
For information regarding HCX interoperability, see VMware Product Interoperability Matrix.
Upgrading to 4.0.2 from HCX 3.5.3 R-Releases
Prior to Semantic Versioning, HCX 3.5.3 releases were identified as "R" releases, such as R147. Review the following information prior to upgrading from R-based releases to HCX 4.0.2:
- Upgrading to HCX 4.0.2 is supported only from the following HCX Service Updates: HCX 4.0, HCX4.0.1, and HCX R147.
- HCX Service Update R147 is the oldest version suitable for upgrade. Customers are required to move to R147 or later to support upgrading to HCX 4.0.2.
- Assistance with upgrading from out-of-support releases will be on a best-effort basis.
- VMware sends administrative messages to HCX systems that are running out of support and require upgrade.
Note: 3.5.3/R147 HCX Manager systems will display release code R150 as a prefix to the 4.0.2 version. This is a known condition during the transition.
Early Adoption Features
Early Adoption (EA) denotes an initial release phase where a feature has limited field exposure and it has strong dependencies on the deployment environment for its functionality. While the feature has completed the entire development process and it is fully supported, it is expected to reach maximum stability and performance through subsequent maintenance releases.
VMware HCX 4.0.2 is a maintenance release that provides only fixed issues and UI enhancements. For a list of features introduced in HCX 4.0, refer to the VMware HCX 4.0 Release Notes. These release notes also provide deprecation of support notices for various HCX deployments or functionality.
- During OS Assisted Migration, HCX checks whether the target datastore is accessible by the Sentinel Data Receiver (SDR) appliance. If the datastore is not accessible, the system generates an error message during the validation phase. (2239596)
- The migration progress indicator description has changed to "est. time." For example, in the case of a large migration, if the migration estimation time exceeds 30 days, the migration progress bar displays ">30d est. time." Also, the tool tip describing the migration progress is more specific and indicates that the migration estimate applies only to the migration transfer phase, and does not include the switchover duration in the estimate.
Note: Currently, the migration estimation function is available for only Bulk migrations.
- The VMware Configuration Maximums tool now provides information specific to HCX 4.0.0 and later releases. For more information go to VMware Configuration Maximums and select VMware HCX from product drop-down menu.
Resolved Interconnect Issues
- PR/2739331 – Force removal of Service Mesh at the destination site is unsuccessful when the source site environment is unavailable.
- .PR/2740740 – Network Extension appliance redeployment/upgrade fails in NSX-T environment when Compute Profile has DVPG and NSX-T segments for management network connectivity.
- PR/2750522 – HCX replication server logging facility incorrectly set to “verbose” level by default. It should be set to “info” level.
Resolved Migration Issues
PR/2743865 – Performing a reverse vMotion or Replication Assisted vMotion (RAV) following a forward vMotion or RAV migration for the same Virtual Machine, it may result in a MAC conflict event in vCenter, after the virtual machine is rebooted.
PR/2745681 – In on-premises environments running NSX-V, security tag does not get applied post Cold migration due to tag ID conflict on target.
PR/2745690 – Incorrect security tag assigned to a virtual machine after vMotion relocation due to duplicate tag IDs.
PR/2751983 – During the Service Mesh deployment, in the case where the DVS version is greater than Mobility Agent (MA) host version, it creates an alert on vCenter if the MA host is getting added to the DVS.
PR/2753957 – Multiple cancellation requests for a vMotion migration in a parked state does not initiate a rollback operation and the migration remains unactionable.
PR/2760624 – Existing Sentinel agents may get into a disconnected state and new Sentinel agents may not show in the inventory.
PR/2755573 – A reverse migration fails if it remains waiting for switchover longer than 7 days, after the initial data synchronization.
Resolved Security Issues
- PR/2728310 – Resolved an issue that can expose the HCX XML parser to an XML External Entities attack.
Deprecation of HCX Site Recovery Manager SupportWith this release, HCX no longer issues updates to the HCX SRM integration feature. This feature will be removed in HCX 4.3, and GSS will no longer support service requests related to SRM integration. HCX Disaster Recovery (virtual machine protection) remains supported as part of the core HCX feature set.