Both physical and virtual vCenter Server installations are compatible.
If the VCS is v5.0 or 5.1 upgrade to 5.5 first and then migrate.
One key addition is the inclusion of Update Manager bundled into the VCSA, as well as vCenter High Availability, Backup and Restore, and other features. In vSphere 6.0 the VCSA reached feature parity with its Windows counterpart, 6.5 begins to pave the way for VCSA to become the preferred deployment method for vCenter Server. The VCSA scales up to 2000 hosts and 35,000 virtual machines.
Furthermore the embedded Postgre database means VMware have full control of the software stack, resulting in significant optimisation for vSphere environments and quicker release of security patches and bug fixes. Since the OS has been developed by VMware it benefits from enhanced performance and boot times over the previous Linux based appliance. Update 12.2016: Changing IP address is supported since VCSA 6.5.The VCSA is a pre-configured virtual appliance as of v6.5 the operating environment is built on Project Photon OS 1.0. If you go to VAMI and click Networking amd then Edit: you can notice that FQDN is not possible to be changed. It's really important to deploy vCenter Appliance (VCSA) using FQDN, no IP Address. Wait when vCenter Appliance is restarted and services are running (e.g.Via VAMI, please click Summary and then Reboot: Reboot VCSA via VAMI or SSH ( reboot).Log in to VCSA via VAMI ( using root account and change IP address to a new one.Ĭlick Networking and then Edit: Type a new IP address and click OK to save.Modify A record on your DNS server to point to a new IP address.change IP address and save by wq! (vi editor basics available here). Log in to VCSA using SSH (if you do not know/remember the root password please follow this guide to reset it) and modify /etc/hosts.To change IP address of VCSA 6.x you need to follow the below steps: If you deploy VCSA using IP address as FQDN, you can not change IP address.
Changing IP address is possible (however officially not supported) and it's straightforward if you deployed VCSA correctly - using FQDN. Recently, I have had to change IP addresse of some vCenter Appliances (VCSA) 6.0 U2 in our environment.