What’s New in HCX – May 20th (R140)

Here is the latest and greatest, available with HCX R140:

Enhancement to OS-Assisted Migrations (OSAM)

UPDATE TO CERTIFIED OPERATING SYSTEMS

OSAM enables the conversion and migration of KVM and Hyper-V virtual machines into a vSphere environment using the HCX platform and workflows. HCX R140 certifies support for migrating CentOS 6.X virtual machines in Hyper-V environments.

Read the OSAM launch blog.
Read Understanding OS Assisted Migration in VMware docs.

Mobility Optimized Networking

Mobility Optimized Networking (MON) integrates HCX extension, migration and disaster recovery workflows with and HCX Network Extension with NSX-T to enable migrated virtual machines to reach other virtual machines and networks optimally, without tromboning or hair-pinning. I shared (MON diagrams and their editables) last week.

HCX MON for NSX-T targets has a several key improvements over HCX PR for NSX-V:

  • The ability for packets to ride the NE Transport Path. This new approach relaxes the requirement for site to site BGP/dynamic routing that existed with the NSXv Proximity Routing technology. This allows optimized egress patterns in more scenarios.
  • HCX MON can be enabled on existing Network Extensions (PR on the other had needed to be part of the Network Extension, meaning a potential outage to unextend/re-extend).
  • On existing configurations, the HCX MON logic can be rolled in per VM instantly, or using an interesting event. The granularity can help with testing and reducing risk.
Virtual Machines on Network Extensions do not trombone to reach local targets.


MON is an HCX Enterprise feature and is supported in environments with NSX-T running at the destination site, independent of the cloud provider. In existing Network Extensions, you can configure MON per network or per virtual machine, toggle it on or off for existing extended networks, and choose when to switch over: immediately following migration, or upon a specified event.

Extending Networks from Source Sites with both vSphere and NSX-T Distributed Switches

Prior to this update, HCX could be used to extend DVS networks or NSXv/t overlays, but not both (within a single HCX Manager deployment). From R140 onward, both scenarios are supported.

There is a defect related to this change that impacts upgrades and redeployments, if you encounter problems, raise a support request and reference iKB 79289

Detection of High-Activity VMs

HCX migrations have two phases: Transfer and Switchover. Virtual machines experiencing very high disk writes can cause Transfer intervals where the virtual machine change data exceeds the achievable migration throughput.  This high-activity condition can prolong the Switchover phase beyond the scheduled migration window, disrupting the migration operation.  With this release, HCX uses VMware vCenter Server heuristics and internal Recovery Point Objective data to provide early detection of high-activity virtual machines, to calculate the impact on migrations, and generate Critical Alerts for at-risk migrations.

Migration Archival

This release includes the Archive option for clearing migration activity. The Archive option clears all selected migrations. It can be used with failed, cancelled, and completed migrations. Clearing the migration history updates the HCX Dashboard migration counters but does not remove the migration related details from the HCX log files.

Force Cleanup has been added for OSAM migrations.

Following a failed or cancelled migration, you can use the Force Clean selection in the Migration UI to clear internal HCX operations and processes manually from source and destination sites. Originally released with the HCX R138 Service Update with support for Bulk, vMotion, and Replication Assisted Migration, Force Clean is now available with OS Assisted Migration.

HCX Service Mesh Updated to Display Enabled Traffic Engineering Features

The Service Mesh UI now displays enabled Traffic Engineering features (Application Path Resiliency and TCP Flow Conditioning)You also can view which appliances are using the Traffic Engineering features by selecting Appliances in the Service Mesh UI.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s