Error: "Cannot connect to host" when deploying a VM from Template in Cloud Director.

Products

• VMware Cloud Director

Issue/Introduction

• You cannot deploy a VM from Template in Cloud Director
• Creating a new blank VM succeeds in Cloud Director
• Cloud Director task will fail with "com.vmware.vim.binding.vim.fault.HostConnectFault".
• In the vCenter VPXD.log you see the message

opID-vcd-<requestId>...Cross-VC <operation> <object> on <source host> in pool <resource pool> with ds <datastore> to <destination host> in pool <resource pool> with ds <datastore>

• In the ESXi Hostd.log you see the error

[NFC ERROR]Nfc_BindAndEstablishAuthdCnx3: Failed to create a connection with server <Host IP>: Failed to connect to server <Host IP>:902

 

Environment

VMware Cloud Director 10.x

Resolution

This issue will occur when the relevant ports are not opened between the Source and Destination ESXi Hosts.

For vMotion and xvMotion, ports 902, 443 and 8000 are required between certain endpoints. See VMware Ports and Protocols for more information.

If the network configuration cannot be adjusted, the vApp template can be placed in the destination to workaround this requirement.

Additional Information

For more information regarding the requirements for cross vCenter migration and cloning, please refer to the following:

Cross vCenter Migration and Clone requirements in VMware vSphere 6.x and later

For additional assistance with investigating network connectivity, please review the document below:

Troubleshooting network and TCP/UDP port connectivity issues on ESXi