A cloud administrator is looking to migrate several dozen workloads from their on-premises location to a VMware public cloud using the vMotion feature of VMware HCX. A total of three networks will need to be stretched for the migration. They will also be utilizing the capabilities of the WAN appliance to optimize migration traffic.
Based on this scenario, how many IP addresses would need to be reserved for the on-premises deployment of VMware HCX?
To deploy VMware HCX on-premises, the required IP addresses are as follows: one for the HCX Manager, one for the HCX Interconnect (IX), one for the HCX Network Extension (NE), and one for the On-Premises vMotion Network. These four IP addresses cover all necessary components for the HCX deployment and network extension, as a single NE appliance can extend multiple networks without requiring additional IP addresses for each network.
I think the correct answer is 4: HCX Manager - 1 IP address HCX Interconnect (IX) - 1 IP address HCX Network Extension (NE) - 1 IP address (1 NE appliance can extend 8 networks) 1 IP address for the On-Premises vMotion Network The HCX-WAN-OPT appliance doesn't require an IP address, it automatically uses the Management Network segment configured during the HCX-WAN-IX deployment. It is auto-assigned special use HCX internal RFC-5735 addresses for communications with the HCX-WAN-IX
5 IP's based on https://repost.aws/articles/AROT7OId_pT7mwsyzOZlhbqA/articles/AROT7OId_pT7mwsyzOZlhbqA/hybrid-cloud-extension-hcx-install-guide-for-vmware-cloud-on-aws? where we can find: Deploy HCX On-Premises You will need the following before you can deploy HCX on premises • 3 private IP Addresses from the on premises Management Network, these are for the HCX Manager, HCX Interconnect and HCX Network Extension appliances • 1 private IP address from the On-Premises vMotion Network and probably fifth IP will be IP for HCX WAN Optimizer.
I think it's 5 IPs required for on-prem HCX Manager - 1 IP address HCX Interconnect (IX) - 1 IP address HCX Network Extension (NE) - 3 IP addresses (1 IP address for each of the three networks that need to be stretched) HCX WAN Optimization (WANOP) - 1 IP address
but it says that the deploy is on-prem, so they are the one-sided IPs. I would say 1 management ip, another for vmotion, another for the network extension, another for the wan optimization, 4 IP
I also think is 4 IPs: "Deploy HCX On-Premises You will need the following before you can deploy HCX on premises 3 private IP Addresses from the on premises Management Network, these are for the HCX Manager, HCX Interconnect and HCX Network Extension appliances 1 private IP address from the On-Premises vMotion Network" https://repost.aws/articles/AROT7OId_pT7mwsyzOZlhbqA/hybrid-cloud-extension-hcx-install-guide-for-v-mware-cloud-on-aws
Sorry can I correct myself again? I pick A. four this time HCX Manager - 1 IP address HCX Interconnect (IX) - 1 IP address HCX Network Extension (NE) - 1 IP address (1 NE can extend up to 8 networks, see below) HCX WAN Optimization (WANOP) - 1 IP address Extending Layer 2 Networks into AWS with Hybrid Cloud Extensions (HCX) https://repost.aws/articles/ARNqhoIYwFRk2-alghYZsNaw/extending-layer-2-networks-into-aws-with-hybrid-cloud-extensions-hcx See step 9
maybe 6 because two IP addres for WAN two for VMotion and two for management of the HCX appliance
I agree with 5 IPs HCX Manager - 1 IP address HCX Interconnect (IX) - 1 IP address HCX Network Extension (NE) - 1 IP addresse HCX WAN Optimization (WANOP) - 1 IP address 1 IP address for the On-Premises vMotion Network
Sorry I failed simple maths on my answer below lol, 1 + 1 + 3 + 1 = 6 I am suggesting six IP is the answer