Error when adding vCenters

[DiogoCampregher]

Hello,

When i try to add my vCenters to the vCloud Director in the vSphere Resources, i receive the two messages aletory in the Trust Certificate Headee

ERROR - No IP address found: servername.domainname.net/: Name or service not known

ERROR - Unable to stabilish connection: Connection timed out ( Connection Time Out )

No matter if i try to add using IPAddress, shortname, fdqn, local SSO user, Domain User, lookup services or vsphere-client url.

DNS are OK for all servers. The database servers are in same L2/L3 with the vCenters ( only the Front End Application Cells are in the DM ).

[DjinjiRinji]

Hi.

Did you try to upload your vcenter certs in vCD before attempting the connection?

In case you don't want to upload certs try below command in vcd 10.1 or above 

“/opt/vmware/vcloud-director/bin/cell-management-tool trust-infra-certs --vsphere --unattended”

Security
WARNING: After upgrading to version 10.1, VMware Cloud Director will always verify certificates for any infrastructure endpoints connected to it. This is due to a change in the way VMware Cloud Director manages SSL certificates. If you do not import your certificates into VMware Cloud Director before the upgrade, the vCenter Server and NSX connections might show failed connection errors due to SSL verification issues. In this case, after upgrading, you have two options:
Run the cell management tool trust-infra-certs command to automatically connect and retrieve certificates of all infrastructure endpoints for vCenter Server and NSX Manager instances into the centralized certificate store. See Import Endpoints Certificates from vSphere Resources.
In the Service Provider Admin Portal UI, select each vCenter Server and NSX instance and reenter the credentials while accepting the certificate.
Starting with version 10.1, service providers and tenants can use the VMware Cloud Director API to test connections to remote servers and to verify server identity as part of an SSL handshake. To protect VMware Cloud Director network connections, configure a deny list of internal hosts that are unreachable to tenants who are using the VMware Cloud Director API for connection testing. Configure the deny list after а VMware Cloud Director installation or upgrade and before granting tenants access to VMware Cloud Director. See Configure a Test Connection Deny List.
VMware Cloud Director 10.1 deprecates the behavior to trust all SSL certificates. In this release, vCenter Server and NSX connections do not support this option. For all other connections, trusting all certificates is also deprecated and will become unsupported after VMware Cloud Director 10.1. System Administrators must prepare for this transition.If you use the LDAP for your VMware Cloud Director system organization, you can use the trust-on-first-use dialog in the UI or upload certificates by using the API.
Аudit all uses of this option and supply appropriate certificates by using the UI or the API.
Communicate the changes to the tenants. All tenants that are using custom LDAP with enabled Accept all certificates option must transition away from this configuration. Tenants can either use the trust-on-first-use dialog in the UI or upload certificates through the API.

https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Install-Configure-Upgrad...

[DiogoCampregher]

Hello.

This erro happen due tô "/" at the end of address of vcenter.

ERROR - No IP address found: servername.domainname.net/: Name or service not known

Without the / the error that happen is the TimedOut.

Now i can't unregister the lookup services also, same TimedOut error.

My vcenter use the local certificates. Mu VCD use a CA certificates.

In my lab, i can't see this error when importing the vcenter, only on the Production.

[DjinjiRinji]

The vc registration without '/' is correct

https://your-fqdn should work. I have all my vCD cells this way

Can you upload the content of your cell.log to see all errors you get while doing this?