WilliamLam.com

Logging into vCenter when vCenter Cloud Gateway (VCGW) is disconnected from vSphere+ Cloud Service

by // 2 Comments

As part of setting up access to the vSphere+ / vSAN+ Cloud Service, a vCenter Cloud Gateway (VCGW) is deployed into your on-premises infrastructure and serves as a gateway between your vCenter Server(s) and the VMware Cloud Console.

If the VCGW has connectivity issues to the VMware Cloud Console for whatever reason, your infrastructure and workloads continue to run but you will not be able to perform any operations through the VMware Cloud Console until connectivity is restored.

However, if you attempt to login into your on-premises vCenter Server(s) using the vSphere UI, you may be surprised to find the following error message.


The message may looking alarming at first about not being able to login, but can still login even if connectivity between the VCGW and VMware Cloud Console has been lost.

While I will agree the user experience may not very intuitive, the hint is in the URL link below where it says "Still having connection problems?"

[Read more...]

Quick Tip - Avoid network conflicts with Docker Bridge Network on the vCenter Cloud Gateway for vSphere+/vSAN+

by // Leave a Comment

The new vSphere+/vSAN+ cloud service is now generally available for all customers! For those interested, I recently wrote about my first experience using the new vSphere+vSAN+ service with my vSphere Homelab environment, which I will also be updating based on the generally available service.

In addition to the resources above and in the VMC Cloud Console, here is a link to the official vSphere+/vSAN+ documentation including pre-req.

During my initial deployment of the vCenter Cloud Gateway (VCGW) used by the vSphere+/vSAN+ service, I did not run into any issues but upon deploying my second VCGW for a different environment, I ran into some networking issues. After a bit of debugging, I came to learn  that the VCGW application and services are composed of various Docker containers and there was a network conflict with the default Docker Bridge Network that the VCGW has been configured by default with.

[Read more...]

How to change the default CPU and Memory requirements for deploying the VMC vCenter Cloud Gateway

by // 3 Comments

When deploying the VMware Cloud on AWS (VMC) vCenter Cloud Gateway (VCG), there is a minimum amount of vCPU and memory that is required for deployment. For customers who wish to evaluate this solution for non-production usage, such as a lab environment, it would be nice to be able to reduce the requirements purely for testing purposes. Today, the vCPU and Memory is not configurable and is currently encoded within a JSON configuration file as well as the VCG OVA. The fact that this is not part of the installer itself but within the OVA means we can actually change the default 🙂 Below are the instructions for updating the vCPU and Memory requirements for the VCG.

Step 1 - Download the VCG ISO from MyVMware and extract the ISO.

[Read more...]