Public IPs are automatically assigned after deploying VMware HCX
Article ID: 329819
Updated On:
Products
VMware Cloud on AWS
Issue/Introduction
This article provides information why public IPs are used for VMware HCX.
Symptoms:
When VMware HCX is initially deployed, the following 3 public IP addresses are displayed at [Networking & Security] - [System] - [Public IPs] on VMware Cloud on AWS console.
Symptoms:
When VMware HCX is initially deployed, the following 3 public IP addresses are displayed at [Networking & Security] - [System] - [Public IPs] on VMware Cloud on AWS console.
- HCX
- HCX-Fleet-1
- HCX-Fleet-2
Cause
By default, VMware HCX will use a minimum of 2 Public IP addresses to connect the HCX-WAN-IX and HCX-NET-EXT components for WAN connections. The remaining IP address is for HCX Manager.
When "externalNetwork" profile is chosen while deploying Service Mesh, the public IP addresses are used for uplink interfaces.
When "externalNetwork" profile is chosen while deploying Service Mesh, the public IP addresses are used for uplink interfaces.
Resolution
This behavior is by design.
Workaround:
If you don’t want HCX traffic to flow over Internet and instead want it to flow over Direct Connect (Using Private IPs), please follow the below steps.
Configuring and Managing HCX Interconnect with Multi-Site Services Mesh
https://featurewalkthrough.vmware.com/t/vmware-cloud-on-aws/configuring-and-managing-hcx-interconnect-with-multi-site-services-mesh/35
Workaround:
If you don’t want HCX traffic to flow over Internet and instead want it to flow over Direct Connect (Using Private IPs), please follow the below steps.
Configuring and Managing HCX Interconnect with Multi-Site Services Mesh
https://featurewalkthrough.vmware.com/t/vmware-cloud-on-aws/configuring-and-managing-hcx-interconnect-with-multi-site-services-mesh/35
Feedback
Yes
No
Powered by
