vSphere+ Cloud Gateway pre-check fails with connectivity & latency error fails when it has proxy enabled

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• If the customer has a proxy enabled on the gateway appliance and then during gateway registration, the reachability prechecks fail and/or latency check fails due to 100ms restriction
• The proxy setting when viewed on the VAMI UI of the gateway which can be accessed via https://<GATEWAY_IP>:5480/#/ui/networking has HTTPS activated and the URL field has a value which includes https://<PROXY_URL>

Environment

VMware vSphere+ Cloud Services

Resolution

This is a known issue. VMware is currently working towards finding a resolution

Workaround:

1. Modify the URL for the HTTPS proxy from https://<PROXY_URL> to http://<PROXY_URL>
2. Retry the prechecks on the UI. If it fails again then proceed to 'Step 3'
3. SSH into the gateway appliance and run the following commands:
   3.1 cd /home/
   3.2 mkdir gps
   3.3 chown gps:aap gps/
   3.4 echo "proxy=http://<PROXY_URL>:<PROXY_PORT>" > /home/gps/.curlrc
4. Retry the prechecks. If it fails again then raise a support request

 

Additional Information

Troubleshooting Pre-check failures while registering Cloud Gateway:
 

1. Ensure that forward & Reverse lookup works fine.
2. Run this command from the cloud gateway console to verify if the connection is established:

curl -o /dev/null -s -w "%{http_code}" https://console.cloud.vmware.com/csp/gateway/portal/ -x <<PROXY:port>>

curl -o /dev/null -s -w "%{http_code}" https://console.cloud.vmware.com/csp/gateway/portal/  -------------→ If using not Proxy.

         3.  Run this command from the cloud gateway console to verify the timeout:

curl -k -o /dev/null -s --write-out "%{time_total}" https://vcgw-updates.vmware.com

0.061518  -------> Time taken to connect to the update repo.

           4. Run this command from the cloud gateway console to verify if the connection to the vmc ui is established:

curl -o /dev/null -s -w "%{http_code}" https://vmc.vmware.com/api/fabric/gateway/health -x <<PROXY:port>>
000

curl -o /dev/null -s -w "%{http_code}" https://vmc.vmware.com/api/fabric/gateway/health
000

             5. Run tracetoute vcgw-updates.vmware.comto confirm if the proxy route is indeed taken.    --------------→ If using Proxy.

              6. Ensure that the latency is lower than 100 ms at all times.

Impact/Risks:
Gateway registration prechecks fail as a result of this issue