This article will help to mitigate the issue for customers, with management networks conflicting with default docker network used by VMWare Cloud Gateway.
VMWare Cloud Gateway UI is not loading on browser due to network conflict.
VMWare Cloud Gateway uses Docker Engine to host the VMWare Agent Platform(VAP). Docker by default uses 172.17.0.0/16 as the default bridge Network. It also creates and new bridge network that by default uses the next overlapping subnet range (172.18.x.x)
These subnets may conflict with customer's Management network. We need a way override the default base IP Range used by Docker engine in the Gateway.
VMware Engineering is working on this issue to provide further updates.
For now, workaround can be implemented to resolve the issue
Workaround:
Deploy the GW. If the GW is already deployed and registered to Cloud, it needs to be re-deployed.
SSH to GW
Edit "/etc/docker/daemon.json". Specify the IP Range that does not conflict with customer's mgmt network as below:
bip: Base IP Address range used by default bridge network
default-address-pools: IP Range that will be used for any new bridge network that gets created. Here 172.21.0.0/16 denotes the full range of IPs (total 65534), and /24 means the the netmask that will be used for each created network 255.255.255.0). Ref: https://forums.docker.com/t/docker-default-address-pool-customization-question/112969
|
Reboot the GW
SSH back to GW after few seconds, and check if "docker ps" is not showing any error
|
Proceed with GW registration to Cloud
Once the GW Registration is complete, inspect the docker networks. Make sure that default bridge is using the subnet specified in "bip", and aap-custom-net is using subnet specified in "default-address-pools"
|
|
|
If the default bridge network used by VMWare Cloud Gateway conflicts with customer's management network, VMWare Cloud Gateway UI will fail to load on browser. User will not be able to register GW and VC and subscribe to vSphere+
Impacted service is "vSphere+"