I am hoping to have some help, or maybe even a bit of understanding on the various host names in VCSA. My VCSA6 to 6.5 Upgrade "failed" when I received some warnings about host name. First though a brief background.
1. VCSA 6 was installed in a domain lets say JEFF.COM
2. So the VCSA 6 was installed as VCENTER and gets a hostname of VCENTER.JEFF.COM
3. This is also reflected in /etc/hosts on the appliance and all is well.
4. Now I join the appliance to an AD domain called SUBDOM.DOMAIN.JEFF.COM and reboot
5. AD join is working and I can use AD credentials in the SSO
*** this is where I get confused and it gets interesting ***
6. the /etc/hosts now has VCENTER.SUBDOM.DOMAIN.JEFF.COM as the host name. (Why did this change? For kerberos principal name lookup or something?
7. Using some Vami commands it still appears at least parts of the VCSA still see VCENTER.JEFF.COM
8. The appliance is still accessed via https://vcenter.jeff.com
9. Again all is still working.
10. I need to note that VCENTER.SUBDOM.DOMAIN.JEFF.COM is not resolvable at this time. We are working on some issues with our DNS/AD intergration. However everytihng works fine.
***now for the upgrade***
11. During the VCSA 6.5 upgrade for the Source Appliance address I enter VCENTER.JEFF.COM (maybe this is where I went wrong, should I have entered the new FQDN with the AD Domain?
12. I get a warning in stage 2 saying "The newly deployed appliance FQDN will be set to VCENTER.JEFF.COM, although the legacy appliance is set to VCENTER.SUBDOM.DOMAIN.JEFF.COM"
13. And off course gives some resolve errors.
So I guess my questions are please:
1. After you join an appliance to AD, how exactly is the host name changed? Do you need to know access the appliance with the FQDN with the AD domain, just like the /etc/hosts file got updated?
2. Going along with #1, do I need to regenrate any certficiates? We just use the self sign certificates and they seem to still be working.
Just confused. Hope my scenario was clear enough. Thank you.