Removing a network extension prevents further cross-site communications between virtual machines residing on that network. This operation is typical when the source side network is vacated.

You can remove a network extension at any time, but be aware that removing an extended network can impact the network infrastructure. Migrated virtual machines that use a source environment DHCP server or that use statically assigned network services like DNS or NTP can lose those services after unextending a network.

Procedure

  1. In the HCX Manager UI, select Services > Network Extension.

    The system displays a list of site pairs.

  2. Select a Site Pair.
    The system displays the Service Mesh entries for the Site Pair and any existing network extensions.
  3. Using the checkbox, select the network or networks that must be unextended, and click Unextend Networks.
    Alternatively, click the ellipsis menu next to each Source Network entry to see a list of actions.

    Available actions for unextending networks are Unextend Networks and Force Unextend Networks. In most circumstances, use Unextend Networks.

    In cases where Unextend Networks fails due to the state of the Network Extension appliance, use Force Unextend to remove the extension and clear internal operations and processes from the source and the destination sites.

    In cases where the source components are no longer available, Force Unextend allows the Unextend operation, removing Network Extension components from the source and the destination sites.

    In cases when the on-premises site is not available or powered off, the existing extended networks are required to be unextended from target/Cloud Network Extension (NE) interface to ensure the Cloud NSX distributed logical router (DLR) is connected for all extended segments where migrated cloud VMs are hosted. Refer to Restrictions and Limitations for Network Extension for more details.

    After selecting an action, a dialog box appears to confirm the action.

  4. (Optional) For each network that will be unextended, expand the network entry and select Connect cloud network to cloud edge gateway after unextending to connect the remote side gateway.

    Dynamic routing can be activated on the Cloud Edge Gateway as part of the OSPF or the BGP configuration. By default, the cloud segment is left disconnected from the Edge Gateway after removing the network extension. This is done to prevent an Edge Gateway from advertising a route to the cloud segment and causing a potential routing conflict with the network in the on-premises data center. Selecting this option connects the segment to the Cloud Edge Gateway after removing the network extension. If dynamic routing is activated, the network is advertised from the Cloud Edge Gateway. Refer to VMware Cloud on AWS Networking and Security guide to ensure proper routing configuration.

    Note:

    Unextending a network removes the HCX L2 bridged path without removing the NSX Segment or vSphere Port Group, or NSX interface. The NSX router interface remains disconnected when the option Connect cloud network is not used.

  5. To confirm the operation, click Unextend.

Results

HCX removes the network extension.