Changing Fully Qualified Domain Name (FQDN) of VMware Cloud Gateway (vSphere+)

Products

• VMware Cloud on AWS

Issue/Introduction

This article helps customers who do not want to redeploy VMware cloud gateway and want to correct the hostname on the deployed appliance before they have registered the gateway.

Symptoms:

Users can deploy VMware cloud gateway appliance with an invalid Fully Qualified Domain Name (FQDN) or Hostname.

Users will face DNS Check failure when Registering VMware Cloud Gateway to VMware Cloud: 
Error message- Hostname XXXX is unable to resolve to IP XXX.XXX.XXX.XXX

Environment

VMware vSphere+ Cloud Services

Cause

User error while deploying the VMware cloud gateway appliance

Resolution

Re-deploy the gateway appliance and ensure that the DNS can resolve hostname to IP address successfully.

Note: This KB is not applicable to change the FQDN after Gateway appliance is registered with VMware cloud.

Workaround:

1. Re-set hostname using. /opt/vmware/share/vami/vami_set_hostname <NEW_FQDN>

   Usage example: /opt/vmware/share/vami/vami_set_hostname w4-gw-test.eng.vmware.com

2. Re-generate certificate using. python /usr/sbin/create-gw-cert.py -h <NEW_FQDN>

   Usage example: python /usr/sbin/create-gw-cert.py -h w4-gw-test.eng.vmware.com

3. Restart gps_envoy service using command: service-control --restart gps_envoy

4. Reattempt the VMware Gateway Registration.