Configure Oracle Cloud VMware Solution HCX Components

To implement HCX, the following prerequisites must be met before performing the migration steps.

Configuration for the Source Site (On-Premises SDDC)

The following table provides the prerequisites and environment details for the on-premises SDDC.

Resource	Requirements
vSphere version	5.0 and later
vSphere/ESXi cluster networks	Identify the ESXi Management, vMotion, and Replication port groups (if they exist) required for network profile. Create missing network port groups, if needed. Identify virtual standard switch (VSS) port groups or distributed port groups (DPG) names, VLANs, and subnets. If these networks vary from cluster to cluster, additional configuration is needed. Identify available IP addresses. (HCX participates in these networks.)
NSX version and configurations	NSX is not required at the source site. However, verify the details of the NSX requirements for HCX appliance deployments in the VMware HCX product documentation. NSX is required only when HCX is used to extend NSX networks. NSX Manager URL and admin credentials.
DNS and NTP	Verify that DNS is configured according to the requirement listed in the Configure DNS for Oracle Cloud VMware Solution section. Ensure that NTP is configured with all the components deployed.
vCenter and SSO	vCenter IP address or FQDN SSO IP address or FQDN
Site-to-site connectivity (on-premises to Oracle Cloud VMware Solution)	The on-premises SDDC is connected to the Oracle Cloud VMware Solution environment through a FastConnect dedicated link of 1 Gbps or 10 Gbps for best performance.
HCX network port requirements	For detailed firewall port opening requirements, see HCX port requirements in the VMware documentation.

Configuration for the Target Site (Oracle Cloud VMware Solution)

Oracle Cloud VMware Solution deployment is one-click fully automated and ready to use. As part of the automation, the following network settings are configured by default.

VLANs	Network Security Groups (NSGs)	Route Tables
VLAN-S-vSphere VLAN-S-NSX VTEP VLAN-S-vSAN VLAN-S-vMotion VLAN-S-NSX Edge Uplink 1 VLAN-S-NSX Edge Uplink 2 VLAN-S-NSX Edge VTEP VLAN-S-HCX	NSG for VLAN-S-vMotion NSG for VLAN-S-vSphere NSG for VLAN-S-vSAN NSG for VLAN-S-NSX Edge Uplink 1 NSG for VLAN-S-NSX VTEP NSG for VLAN-S-NSX Edge VTEP NSG for VLAN-S-HCX	Route table for VLAN-V-vMotion Route table for VLAN-V-vSphere Route table for VLAN-V-NSX Edge Uplink 2 Route table for VLAN-V-NSX Edge Uplink 1 Route table for Subnet-V Default route table for VMware-SDDC-VCN Route table for VLAN-V-HCX

Subnet-V is the default subnet that’s created as part of the Oracle Cloud VMware Solution network setup. It is used to host the VMware ESXi hosts. A separate security list called Security List for Subnet-V is created for Subnet-V.

You need three separate port groups/VLANs for HCX implementation. However, you can also choose to have the same VLAN-S-vSphere port group for HCX-Management, HCX-vMotion, and HCX-Replication, and as an uplink interface. You can’t use existing ESXi Management or ESXi vMotion networks because the IP addresses are reserved from these VLANs for VMware SDDC cluster expansion.

If you plan to use segregated networking for this implementation, you must create the following VLANs and associated NSGs and route tables. The decision to use an existing VLAN-S-vSphere for all networks or to create separate VLANs for each depends solely on your architectural requirement.

VLANs	NSGs	Route Tables
VLAN-S-HCX-vMotion VLAN-S-HCX-Replication	NSG for VLAN-S-HCX-vMotion NSG for VLAN-S-HCX-Replication	Route table for VLAN-V-HCX-vMotion Route table for VLAN-V-HCX-Replication

Access and Management

Ensure that the required permissions are available to perform VMware HCX operations on premises and in Oracle Cloud VMware Solution. The default vCenter administrator can perform the HCX operations.

Network Connection Between Sites

For information about network connectivity between on-premises VMware environment and Oracle Cloud VMware Solution over FastConnect, see the FastConnect documentation.

DNS Configuration

To ensure that both sites can communicate with each other using FQDN, ensure that both the primary and destination DNS servers have all the forward and reverse lookup entries for both sites’ VMware components that are part of the HCX implementation, such as vCenter, HCX , NSX, and Platform Services Controller (if it’s external). See the Configure DNS for Oracle Cloud VMware Solution section.