HCX supports extending networks from VMware vSphere Distributed Switches, NSX segments, and NSXv logical switches.

The following information and requirements apply when extending networks:

  • General Requirements:
    • Never extend the networks used to create the network profiles.
    • Never use HCX to extend the vSphere Management network or other VMkernel networks (for example: vMotion, vSAN, replication) to the remote site.
  • Networks with NSX-T Data Center at the source:
    Note: Registering NSX-T in an HCX Connector is optional, except when extending NSX networks or migrating NSX Security Tags. If NSX-T is registered, the following requirements apply:
    • The NSX-T Manager must be registered during the HCX Manager deployment.
    • The NSX-T Manager must be Version 2.4 or higher.
    • NSX-T Overlay or VLAN Transport Zones must be configured in the vCenter Server where the network originates.
      • The ESX hosts where the NSX-T segment originates must be configured as NSX-T transport nodes.
      • NSX-T Overlay and NSX-T VLAN networks can be extended.
  • Networks with NSX-T Data Center at the destination:
    • HCX connects to Tier-1 Gateways and Segments created in the Networking tab (policy UI). NSX configurations created in the manager tab cannot be used with HCX Network Extension and Migration operations.
    • Additional network extension appliances are required when extending more than 8 networks.
    • NSX-T Overlay must be configured in the destination vCenter Server or SDDC.
    • NSX-T Overlay and NSX-T VLAN networks are always created as NSX Overlay networks at the destination. HCX network extension is always to NSX Overlay networks. Pre-created segments in the vSphere Distributed Switch, CVDS, or VLAN transport zone, cannot be used as a destination.
  • Networks with NSX-T Data Center at the source and the destination:
    • HCX only supports Tier-1 Gateways and extension of NSX-T segments that are created with the NSX-T Policy UI/API.
    Note: In addition to these requirements for both sites, individual requirements for networks with NSX-T at the source and the individual requirements for networks with NSX-T at the destination also apply.
  • Networks with NSX for vSphere at the destination:
    • Use a Distributed Logical Router (DLR) or Edge Services Gateway (ESG) to connect the extended network.
      Note: If a single Edge Services Gateway is used for more than 8 networks, HCX will create and use a trunk interface.
  • Networks with Virtual Distributed Switch:
    • vSphere Distributed Switch 5.5 or higher is required.
  • NSX for vSphere Logical Switches:
    • The NSX-V Manager must be registered during the HCX Manager deployment.
    • The NSX-V Manager must be Version 6.4.8 or higher.