VM Replication Set Up Authentication Fails

[cmhippy]

This was working perfectly fine and for no apparent reason, "broke".

Select a VM to replicate to our vCloud Director DR site.  Select Configure Replication.  Replicate to a cloud provider.  Select our VDC.  Enter User name and Password (since this is the first Replication of the day).

Result:

----------------------------------------------------------------------------------------

Cannot connect to the specified cloud provider. The provider might not be available on the network or a network configuration problem might exist. Verify that your connection settings are correct or contact your service provider.

----------------------------------------------------------------------------------------

If i understand correctly, at this point where it is trying to accept my credentials, it is simply going through the internet for authentication.  Once authenticated, the actual replication will go through our L2C.

The Replication appliance in our on-prem environment seems to be connecting to our VDC.  A curl command seems to indicate so.

Our HCM fleet is also connected and communicating without any problems.  This just occurs when trying to set up a replication.

Any ideas?  So odd.

Thanks in advance.

[mhampto]

Is there anything in the logs that provide more information?  Such as a credential error?

[mjha]

Can you check following things in your on-prem

1: checked for the time sync between Host, vCenter and DR appliance

2: Verify necessary ports are open on VR appliance:

# netstat -tunlp | grep 100[01][0-9]

3: VR appliance is reachable from ESX host on port 10000-10010

# nc -z <DR-App-IPaddress> 10000-10010

4: Curl Results to Service Provider Portal

From VR appliance:

# curl -sk https://VCD-PubURL/api/server_status

# curl -sk https://VCD-PubURL on port 443

# curl -sk https://VCD-CldPrxy-URL/api/server_status

From vCenter:

# curl -sk https://VCD-PubURL/api/server_status

# curl -sk https://VCD-CldPrxy-URL/api/server_status

Also review hms.log and vcta.log from on-premise