For upgrades to the vCenter Server Appliance, you can deploy a new version of the appliance and import the network identity of your existing vCenter Server Appliance.

Before you begin

  • Verify that the clocks of all machines on the vSphere network are synchronized. See Synchronizing Clocks on the vSphere Network.

  • If your vCenter Server Appliance uses an external instance of vCenter Single Sign-On, upgrade Single Sign-On to the same version as the vCenter Server Appliance version that you are upgrading to.

  • Verify that the vCenter Server SSL certificate for your existing vCenter Server Appliance is configured correctly. See VMware Knowledge Base article 2057223.

  • Back up the vCenter Server database.

  • Create a snapshot of the vCenter Server Appliance.

About this task

Note:

The upgrade from version 5.0 to 5.5 differs slightly from the upgrade from version 5.1 to 5.5. Options for setting roles are not available during the upgrade from version 5.1 to 5.5.

VMware product versions are numbered with two digits, for example, vSphere 5.5. A release that changes either digit, for example, from 4.1 to 5.0, or from 5.1 to 5.5, involves major changes in the software, and requires an upgrade from the previous version. A release that makes a smaller change, requiring only an update, is indicated by an update number, for example, vSphere 5.1 Update 1.

For updates to the vCenter Server Appliance, for example, from version 5.1 to version 5.1 Update 1, see Update the VMware vCenter Server Appliance from a VMware.com Repository, Update the VMware vCenter Server Appliance from a Zipped Update Bundle, and Update the VMware vCenter Server Appliance from the CD-ROM Drive.

Versions 5.0 Update 1 and later, 5.1.x, and 5.5 of the vCenter Server Appliance use PostgreSQL for the embedded database instead of IBM DB2, which was used in vCenter Server Appliance 5.0. If you use the embedded database with the vCenter Server Appliance, when you upgrade from version 5.0 to version 5.5, the embedded IBM DB2 database is migrated to a PostgreSQL database. The configuration state of your existing database is preserved and the schema is upgraded to be compatible with vCenter Server Appliance 5.5.

Note:

vCenter Server 5.5 supports connection between vCenter Server and vCenter Server components by IP address only if the IP address is IPv4-compliant. To connect to a vCenter Server system in an IPv6 environment, you must use the fully qualified domain name (FQDN) or host name of the vCenter Server. The best practice is to use the FQDN, which works in all cases, instead of the IP address, which can change if assigned by DHCP.

Version 5.5 of the vCenter Server Appliance is deployed with virtual hardware version 7, which supports eight virtual CPUs per virtual machine in ESXi. Depending on the hosts that you will manage with the vCenter Server Appliance, you might want to upgrade the ESXi hosts and update the hardware version of the vCenter Server Appliance to support more virtual CPUs:

  • ESXi 4.x supports up to virtual hardware version 7 with up to 8 virtual CPUs per virtual machine.

  • ESXi 5.0.x supports up to virtual hardware version 8 with up to 32 virtual CPUs per virtual machine.

  • ESXi 5.1.x supports up to virtual hardware version 9 with up to 64 virtual CPUs per virtual machine.

Caution:

If you update the vCenter Server appliance to hardware version 10, you cannot edit the virtual machine settings for the appliance using the vSphere Client. This might cause difficulties in managing the vCenter Server Appliance, because you cannot use the vSphere Web Client to connect directly to the host on which the vCenter Server Appliance resides to manage it. Do not upgrade the vCenter Server Appliance to hardware version 10.

To update the virtual hardware version of a virtual machine, see the information about virtual machine compatibility levels in the vSphere Virtual Machine Administration documentation.

Note:

If your upgrade reconfigures the appliance to use an external vCenter Single Sign-On instance on a Microsoft Windows host, after the upgrade, you cannot log in as root unless you add a user by that name to the vCenter Single Sign-On host. Windows does not include a root user by default.

Procedure

  1. Deploy the new version of the vCenter Server Appliance.

    The new appliance has a default network configuration, and the vCenter Server service is unconfigured and disabled. You do not need to configure NFS on the new appliance. This configuration is copied automatically on upgrade.

  2. Make sure that the new appliance has at least the same amount of RAM and number of CPUs as the old appliance.
  3. If you added additional disks or increased the size of the VMDKs of the old appliance, reconfigure the new appliance to have at least the same disk space as the old appliance.
  4. Connect to both the old and new appliances in separate browser windows.
  5. In the new appliance, in the vCenter Server Setup wizard, accept the end user license agreement.

    The wizard is started automatically on first login. On subsequent logins, you can start the wizard manually, by clicking the Launch button in the Utilities section of the startup page.

  6. In the new appliance, in the Configure Options panel, select Upgrade from previous version.
  7. In the new appliance, click Next.
  8. If you are upgrading from version 5.0.x: in the old appliance, in the Upgrade tab, select source for the appliance role, and click Set role.
  9. In the new appliance, copy the local appliance key.
  10. Import the key that you copied in the previous step into the old appliance.
    • If you are upgrading from version 5.0.x: in the old appliance, go to the Upgrade tab, Establish Trust subtab. Paste the key into the Remote Appliance Key field and click Import remote key.

    • If you are upgrading from version 5.1.x: in the old appliance, paste the key into the Upgrade key box, and click Import key and stop vCenter Server.

  11. In the old appliance, copy the local appliance key.
  12. In the new appliance, paste the key that you copied in the previous step into the Upgrade key box and click Next.

    The setup performs a check on the SSL certificate of the old appliance. If problems are found, the Setup wizard displays a panel that explains the problem and provides an option to generate a new self-signed certificate for the new appliance.

  13. If you want to keep the current certificate and manually correct any resulting problems, uncheck the checkbox Replace the vCenter SSL certificate.

    If you are upgrading from a version 5.1.x appliance, the existing Single Sign-On configuration will be used for the upgraded appliance. Proceed to 15. If you are upgrading from a version 5.0 appliance, the wizard displays the SSO Settings panel.

  14. If you are upgrading from a version 5.0 appliance, in the SSO settings panel, choose whether to use an external instance of Single Sign-On, or the embedded version.

    If you choose an external Single Sign-On instance, a check is performed to ensure that the external Single Sign-On version is 5.5. If the version is earlier than 5.5, an error message is displayed and the upgrade will not proceed.

  15. In the new appliance, click Next.
  16. Review the list of hosts managed by the source appliance and select the hosts on which to run pre-upgrade checks.

    To minimize the chance of problems with the upgrade, run the pre-upgrade checks on all hosts, or at least on the most important hosts.

  17. Review the pre-upgrade check of the source appliance hosts and correct any errors before proceeding.
  18. Confirm that you have taken a backup or snapshot of the source appliance and external database, and click Next.

    The new appliance shuts down the old appliance and assumes the network identity of the old appliance. If the old appliance was configured to use dynamic addressing, the new appliance will also use dynamic addressing. When the import is complete, the new vCenter Server Appliance starts.

  19. When the upgrade is complete, click Close.

Results

The vCenter Server Appliance is upgraded and the new appliance will reboot.