Troubleshooting connectivity using curl commands in VMware vCloud Connector 1.5.x

Products

• VMware vCloud Director 5.x

Issue/Introduction

This document provides information on testing the full path of connectivity from source to destination in VMware vCloud Connector (vCC) 1.5.x.

Environment

VMware vCloud Connector 1.5.x

Resolution

To troubleshoot vCC Connectivity issues, read this overview of VMware vCloud Connector architecture

• Nodes in vCC should be public facing, or NAT connected, and must be open to TCP port 8443 two way.
• DNS is not required unless all configuration completed in the vCC Server Node configuration uses IPs (including the connection to the remote vCloud Director Org.
• If you are able to successfully add a Node to your vCC Server, this does not prove that you can add a Cloud using the vSphere plugin or cloud interface. VMware vCloud Connector Checks connection to Nodes when you add them, but the connection to the vCenter Server or vCloud Director is not verified until you add the cloud.
  

VMware vCloud Connector data path explanation

To troubleshoot connectivity, understand how the environment is configured. The path for transfer would be from source vCenter/vCloud Director to destination vCenter/vCloud Director. The method that vCC uses to transfer is as follows:

1. vCC Server starts an OVF export from the source vCenter or vCD and directs it to export the OVF to the transfer space on the source Node. This step is complete at 33%.
2. vCC Server directs the source Node to transfer the OVF to the destination Node using TCP port 8443. This step is complete at 66%.
3. vCC Server directs the destination Node to set up an OVF upload to the destination vCenter or vCD. This step is complete at 100%.
   

Curl commands run from the vCC Server are vCC Nodes and can be used to test connectivity between components. These are the curl commands:

1. To test connectivity from vCC Server or Node to vCC Node:
   
   curl -k -v https://<node</SPAN> name or IP address>:8443/agent/Status
   
   
   Note: Look at the beginning of the data that is output for Connected Successfully to <vcc address ip name node or> port 8443</vcc>. Ignore any http or https failures in the output, as these are irrelevant.
   
   
2. To test connectivity from the vCC Server or Node to vCenter Server:
   
   curl -k -v https://<vCenter name or IP address>/mob
   
   Note: Look at the beginning of the data that is output for Trying <vCenter name or IP address>... connected. Ignore any http or https failures in the output, as these are irrelevant.
   
   
3. To test connectivity from the vCC Server or Node to vCloud Director:
   
   curl -k -v https://<vCD name or IP address>/api/versions
   
   Note: Look at the beginning of the data that is output for Trying <vCD name or IP address>... connected. Ignore any http or https failures in the output, as these are irrelevant.

If during connect you see the error Couldn't connect to host, you must review the port and network configuration to establish connectivity.

Begin by verifying that:

• all vCC servers are configured properly in their network settings.
• all vCC servers can ping one another.