Prepare for HCX migration
Before you connect VMware HCX to your Amazon Elastic VMware Service environment, check that the HCX VLAN subnet is ready and create the HCX uplink port group. You can do the AWS checks with the console or the AWS CLI. The port group step is in the vSphere Client.
Before you begin
-
You have chosen private or internet connectivity and meet the HCX requirements. For more information, see Plan HCX connectivity.
-
For internet connectivity, you have associated Elastic IP addresses with the public HCX VLAN subnet. For instructions, see Configure HCX public internet connectivity.
Step 1. Check the status of the HCX VLAN subnet
Amazon EVS creates a VLAN subnet for HCX as part of every environment deployment. Check that it is ready.
To check the HCX VLAN subnet in the Amazon EVS console or with the AWS CLI, choose the tab for the method that you use.
Example
Step 2. Check that the HCX VLAN subnet has a network ACL
Check that the HCX VLAN subnet is associated with a network ACL. To create one, see Create a network ACL for VLAN subnet traffic.
Associating an Elastic IP address with a VLAN subnet gives direct internet access to all resources on that subnet. Security groups don’t apply to traffic on Amazon EVS VLAN subnets, so use a network access control list (ACL) to restrict access. For more information, see Create a network ACL for VLAN subnet traffic.
To check the network ACL in the Amazon VPC console or with the AWS CLI, choose the tab for the method that you use.
Example
Step 3. Check the route table association
Amazon EVS requires that every VLAN subnet is explicitly associated with a route table in your VPC. A VLAN subnet without an explicit association uses the main route table implicitly. In that case, Amazon EVS doesn’t work correctly. For internet connectivity, the public HCX VLAN subnet must be associated with a public route table that has an internet gateway as a target.
To check the route table association in the Amazon VPC console or with the AWS CLI, choose the tab for the method that you use.
Example
For more information, see Associate VLAN subnets with a route table.
Step 4. (Internet connectivity) Check the Elastic IP address associations
For internet connectivity, each HCX network appliance needs an Elastic IP address from the IPAM pool, associated with the public HCX VLAN subnet. You need at least two, one for the HCX Manager and one for the HCX Interconnect (HCX-IX) appliance. HCX internet connectivity fails if fewer than two Elastic IP addresses from the IPAM pool are associated with the public HCX VLAN subnet.
To check the associations in the Amazon EVS console or with the AWS CLI, choose the tab for the method that you use.
Example
To add missing associations, see Configure HCX public internet connectivity.
Step 5. Create a distributed port group with the HCX uplink VLAN ID
In the vSphere Client, do the following:
-
Add a distributed port group to the vSphere Distributed Switch. Follow the steps in Add a Distributed Port Group
in the Broadcom documentation. -
For the VLAN setting, enter the HCX VLAN ID that you found in Step 1.
-
In the failover settings, set
uplink1as an active uplink anduplink2as a standby uplink. This gives active/standby failover.
You have checked the HCX VLAN subnet and created the HCX uplink port group.
Next step
Turn on the optional HCX features and verify HCX connectivity. For instructions, see Optimize and verify HCX migration.