While migrating from a Windows vCenter Server to a 6.5 vCenter Appliance, one or more services fail to start.

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

While migrating from a Windows vCenter to a 6.5 vSphere Appliance one or more services fail to start during the second phase of the process.

Environment

VMware vCenter Server Appliance 6.5.x

Cause

This can occur when the Windows vCenter relies on host file entries to resolve the FQDN of multiple ESXi hosts rather than forward & reverse DNS records. The host file entries from the source vCenter are not imported until after the firstboot process has completed.

The VPXD process then tries to start during firstboot but as it is unable to resolve the FQDN of the ESXi hosts, the delay can cause the VPXD service to appear unresponsive to services which depend on it. 

The resulting timeout or failure of the dependant services which cause the Phase 2 to be declared a failure.

Resolution

VMware is currently investigating a permanent solution for this issue.

Workaround:
To workaround this issue perform one of the following steps. 

1. Ensure all ESXi hosts which are going to be managed by the vCenter have a valid forward & reverse DNS record. 
2. Test and confirm that all records are working by using nslookup.  

OR. 

1. After the initial Phase 1 has completed connected to the new vCenter Server Appliance and manually add the FQDN for the ESXi hosts to the /etc/hosts file. 
2. Complete the Phase 2 process.