The HCX Mobility Optimized Networking (MON) feature routes network traffic based on locality of the source and destination virtual machines. MON operation requires specific configuration of the HCX Network Extension parameters and the network environment between the source and the destination sites.

General Requirements for MON

To get started, MON requires an HCX Enterprise license or activation.

Requirements for MON-Enabled Virtual Machines

  • VMware Tools must be installed.

  • All vNICs must be attached to the same extended L2 network segment.
  • All IP addresses configured, on a single or multiple vNICs, must be on the same subnet for the extended L2 network segment.

Environmental Requirements for MON

  • All NSX requirements for network extension are met. See Requirements for Network Extension

  • An NSX Tier-1 router connected to a Tier-0 router must exist in the cloud environment prior to enabling this feature.

    Note:

    Layer-2 network extensions can only terminate on a Tier-1 router.

  • The default Gateway IP and the DHCP Server IP cannot be the same. The Gateway for the extended segment can provide DHCP services but must have a different IP address used for the DHCP server.

  • Some third-party implementations of First Hop Redundancy Protocol (FHRP) are not compatible with MON. Under these conditions, the on-premises Default Gateway Router MAC address cannot be identified, so cloud VMs with MON enabled cannot communicate with it. See VMware KB 85849.

Limitations of MON

  • MON does not provide traffic optimization from MON-enabled virtual machines to virtual machines on other extended networks without MON.

  • MON provides optimization in the Cloud. MON does not provide optimization in the source.

  • For additional information related to running MON on VMware Cloud on AWS, see HCX Mobility Optimized Networking for VMware Cloud on AWS.