After adding my vCenter server as a compute manager in NSX-T there is an error under Registration Status, it says "Registered With Errors". The details are:
Compute manager failed to get enabled as auth server due to error Unexpected error ResourceAccessException while accessing https://vcenter.mydomain.com/openidconnect/vsphere.local/.well-known/openid-configuration.. Please check the hostname in the url is reachable from nsx.
This error seems like a DNS issue, but I can ping the FQDN from the NSX-T VM. If I open the URL from the error in a browser I see this:
{"response_types_supported":["code","id_token","token id_token"],"jwks_uri":"https:\/\/vCenter.mydomain.com\/openidconnect\/jwks\/vsphere.local","end_session_endpoint":"https:\/\/vCenter.mydomain.com\/openidconnect\/logout\/vsphere.local","subject_types_supported":["public"],"id_token_signing_alg_values_supported":["RS256"],"issuer":"https:\/\/vCenter.mydomain.com\/openidconnect\/vsphere.local","authorization_endpoint":"https:\/\/vCenter.mydomain.com\/openidconnect\/oidc\/authorize\/vsphere.local","token_endpoint":"https:\/\/vCenter.mydomain.com\/openidconnect\/token\/vsphere.local"}
I don't know if that is what is to be expected at the URL or not.
vCenter is 7.0.2.17694817 and NSX-T is 3.1.1.0.0.17483106. vCenter has been in production for many years. NSX-T is a fresh install.
Any suggestions?
Any firewalls between the two, are ports open?
NTP in sync on both appliances?
Does the vCenter use ip address as FQDN ?
Thank for your suggestions.
There is no firewall between vCenter and NSX-T.
I just checked and NTP is enabled and in sync on both.
I was able to install NSX on all the hosts just fine, but this error still persists on the compute manager page.
If I click on the error I see this message and when I select "Resolve" nothing happens.
Thank you for your help! vCenter uses a name for it's FQDN and that is resolvable on NSX-T.