Install VCSA on vcenter server question

piaakit
piaakit used Ask the Experts™
on
Dear All,

    currently I have a physical server running 2008 server and vcenter 6.5 in the machine, and 2 esxi 6.5 added to this vcenter, and I’m planning to install VCSA 6.7, Just wonder if there is any issue if I don’t remove vcenter on this machine while installing VCSA 6.7 or it is still ok if I deploy VCSA 6.7 ? any help would be appreciated

keith
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
It will be fine.

If the plan is to use the new VCSA 6.7 to manage the ESXi 6.5 hosts, make sure you remove them from old vCenter Server before adding to the new 6.7.

Author

Commented:
so i need to disconnect the current Esxi host from current vcenter first before install VCSA 6.7 or i can first installed VCSA 6.7 first and add the 2 esxi host after removed them from vcenter, am i correct ?


11

keith
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
Install VCSA 6.7 first.

and then REMOVE the hosts from vCenter 6.5 after you've installed VCSA 6.7, and then add them to VCSA 6.7

Author

Commented:
i have one more question, my 2 esxi is using mgt ip 10.0.0.4 & 10.0.0.6, which is a different ip segment of our production server and user computer ip  10.141.101.0/24, and when i deploy VCSA i'm using 10.141.101.21, and if i add the 2 esxi in VCSA, will there be any issue ? and i was getting error in stage 2 of VCSA, also the hostname of VCSA not yet created in DNS server since i need to inform regional IT team to create it for me as i dont have right to do it, any idea of my case ?


1
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
You MUST ensure that ALL servers, ESXi and vCenter Server have FQDN configured before you install!!!!

*ALWAYS*

Stop and abandoned your install now!

Your VMware vSphere Production environment, is only as good as your networking and DNS infrastructure!
Chris PhillipsTechnical Consultant

Commented:
The VCSA will not complete its installation if you don't have both forward AND reverse DNS entries created prior to deployment.  It is fine to have the VCSA on a different subnet to that of the management addresses of the ESXi hosts.  If there is a firewall between them tough you will need to open certain ports (off the top of my head these will be 80, 443 and 902)

When coming to move the hosts over to the new VCSA you will need to place the host into maintenance mode before being able to disconnect from the current vCenter Server.  You can get around this by just adding the host to the new vCenter.  It will say that it is being managed by a different vCenter but will allow you to switch it over without downtime.  One thing to look at when migrating vCenter servers is if you have DVS switches as these are managed by vCenter so you will need to export and then import them to the new VCSA.  If you have vSS (Standard switches) then you will not need to worry about this

Author

Commented:
but the 2 esxi host is using ip 10.0.0.0/8 and this subnet doesn’t have the gateway and router at the back, the current vcenter server is using ip 10.141.101.0/24 and in the server I added a secondary ip 10.0.0.111 in NIC so it could link up the 2 esxi server, so when deploying VCSA with ip 10.141.101.21, will it be able to add the 2 esxi host into the VCSA ? and the VCSA has FQDN created in A record in DNS
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
To add ESXi servers to vCenter Server, there must be communications between ESXi and vCenter Server.

You add the ESXi servers after deployment. (not during).

If you now have a FQDN, you should be able to complete the VCSA installation.

Author

Commented:
coz the vcenter is window server can added secondary ip in NIC, but in VCSA look like it can not add more than 1 ip addresses, so it couldn’t add ip 10.0.0.111 to communicate with the 2 esxi host
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:

Author

Commented:
I have successfully added the 2nd nic , and i faced another issue, i'm trying to domain the VCSA to domain, and it shows its joined, but after i click on other tab and go back to active directory tab, and it seems go back to the disjoin mode, any idea ?

1
2
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
after you have JOINED - REBOOT immediately...

(Click Acknowledge...select Restart Guest!)

do not change any pages etc or go back....

if this is on your ESXi host, select Restart Guest!

Author

Commented:
the Domain has joined successfully, but when I add identity source, it shows below, any idea ?
1

Author

Commented:
One thing I have done and now realise this is probably the cause of the issue is the System Domain is the same name as the AD Domain. When setting up the vCenter I think I misunderstood the relevance of "Domains", do I need to reinstall the VCSA all over again ?
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
Yes, they cannot be the same.

just leave the defaults, as Administrator@vsphere.local

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial