I am building a test environment for a new vSphere 6.0 install to replace the 5.5 infrastructure in use now. I installed the PSC on a VM and it seems to be working fine, but when I try to install vCenter on a different VM it complains that it can't reach the PSC. I can ping the FQDN of both machines from the other, firewall is turned off, tried all the usual things.
The odd thing is, if I just use the server name for the PSC rather than the fully qualified name, it connects, but it complains that the cert on the PSC doesn't match what I entered, which is true, I used the FQDN on the PSC. It will also connect using the ip address, but again the cert doesn't match.
Anyone have any idea why it would act this way? It does not appear to be a DNS issue, pings work correctly with FQDN, nslookup resolves the FQDN correctly.
I appreciate any advice
Matt
Hello, Matt.
It looks like the short name was used during when installing/setting up the PSC. Because of it the certificate was generated within the short name.
The product walkthrough steps 11 & 12 might help you understand what might have happened: Product Walkthroughs.
Check if the hostname on cert is correct.
Thank you for your response. I have screenshots from when I did the installation and I did use the FQDN when I did the PSC install. If I can't figure it out this morning I'm just going to uninstall the PSC and do the install again.
Thanks for your willingness to help
Matt
To clarify what I see, when I use the FQDN, which I have verified as the one I used in the PSC install here's what I get:
When I use just the short name for the PSC server here's what I get:
Which does make sense because I used the FQDN during the install now I'm using the short name. I did do a complete reinstall this morning just to make double sure and still doesn't work.
Matt
Matt, thanks for sharing the screenshots.
Are you doing a deploy with High Availbility mode? Or it is just a single node deploy without a LB?
