vSphere Upgrade Update 2 ESXi 6.0 vCenter Server 6.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
vSphere Upgrade You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2009–2016 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents About vSphere Upgrade 7 Updated Information 9 1 Introduction to vSphere Upgrade 11 vCenter Server Components and Services 12 How vSphere 6.0 Differs from vSphere 5.
vSphere Upgrade Download the vCenter Server for Windows Installer 77 Upgrade vCenter Single Sign-On 5.1 for External Deployment 78 Upgrade vCenter Single Sign-On 5.5 for External Deployment 81 Upgrade vCenter Server 5.0 83 Upgrade vCenter Server 5.1 for Windows 85 Upgrade vCenter Server 5.
Contents 10 After You Upgrade ESXi Hosts 201 About ESXi Evaluation and Licensed Modes 201 Applying Licenses After Upgrading to ESXi 6.
vSphere Upgrade 6 VMware, Inc.
About vSphere Upgrade vSphere Upgrade describes how to upgrade VMware vSphere™ to the current version. To move to the current version of vSphere by performing a fresh installation that does not preserve existing configurations, see the vSphere Installation and Setup documentation. Intended Audience vSphere Upgrade is for anyone who needs to upgrade from earlier versions of vSphere.
vSphere Upgrade 8 VMware, Inc.
Updated Information This vSphere Upgrade is updated with each release of the product or when necessary. This table provides the update history of the vSphere Upgrade. Revision Description EN-001989-04 n n EN-001989-03 n n n n EN-001989-02 n n EN-001989-01 n n n EN-001989-00 VMware, Inc.
vSphere Upgrade 10 VMware, Inc.
Introduction to vSphere Upgrade 1 vSphere 6.0 has many options for upgrading your vSphere deployment. For a successful vSphere upgrade, you must understand the upgrade options, configuration details that impact the upgrade process, and sequence of tasks. The two core components of vSphere are VMware ESXi™ and VMware vCenter Server™. {ESXi is the virtualization platform on which you can create and run virtual machines and virtual appliances.
vSphere Upgrade vCenter Server Components and Services vCenter Server provides a centralized platform for management, operation, resource provisioning, and performance evaluation of virtual machines and hosts. When you upgrade to vCenter Server with an embedded Platform Services Controller, or to vCenter Server Appliance with an embedded Platform Services Controller, vCenter Server, the vCenter Server components, and the services included in the Platform Services Controller are deployed on the same system.
Chapter 1 Introduction to vSphere Upgrade Services Installed with vCenter Server These additional components are installed silently when you install vCenter Server. The components cannot be installed separately as they do not have their own installers. vCenter Inventory Service Inventory Service stores vCenter Server configuration and inventory data, enabling you to search and access inventory objects across vCenter Server instances.
vSphere Upgrade You can deploy a Platform Services Controller instance on the same virtual machine (VM) or physical server as vCenter Server, which is vCenter Server with an embedded Platform Services Controller instance. You can also deploy a Platform Services Controller instance on a separate machine or physical server, which is vCenter Server with an external Platform Services Controller instance. See “vCenter Server Deployment Models,” on page 16. Enhanced Linked Mode Starting with vSphere 6.
Chapter 1 Introduction to vSphere Upgrade During the process of upgrading to vCenter Server 6.0 with an external Platform Services Controller deployment, any vCenter Server 5.1 or 5.5 services that are deployed on a separate VM or physical server from the vCenter Server are migrated to the same VM or physical server as the vCenter Server instance. vCenter Server components can no longer be deployed individually.
vSphere Upgrade vCenter Server Deployment Models You can install vCenter Server on a virtual machine or a physical server running Microsoft Windows Server 2008 SP2 or later, or can deploy the vCenter Server Appliance. The vCenter Server Appliance is a preconfigured Linux-based virtual machine, optimized for running vCenter Server. vSphere 6.0 introduces vCenter Server with an embedded Platform Services Controller and vCenter Server with an external Platform Services Controller.
Chapter 1 Introduction to vSphere Upgrade Installing with an embedded Platform Services Controller has the following disadvantages: n There is a Platform Services Controller for each product which might be more than required. This consumes more resources. n The model is suitable for small-scale environments. vCenter Server with an External Platform Services Controller vCenter Server and the Platform Services Controller are deployed on separate virtual machine or physical server.
vSphere Upgrade Figure 1‑3. Example of a Mixed Operating Systems Environment with an External Platform Services Controller on Windows Windows Virtual Machine or Physical Server Platform Services Controller on Windows Virtual Machine or Physical Server Virtual Machine vCenter Server on Windows vCenter Server Appliance Figure 1‑4.
Chapter 1 Introduction to vSphere Upgrade 5 Upgrade vCenter Server. You can connect vCenter Server instances with external Platform Services Controller instances in an Enhanced Linked Mode configuration. Important Although you can select to join a vCenter Single Sign-On domain, you should consider vCenter Server with an embedded Platform Services Controller as a standalone installation and do not use it for replication of infrastructure data.
vSphere Upgrade d Upgrade ESXi. n “Using vSphere Update Manager to Perform Orchestrated Host Upgrades,” on page 155 n “Installing or Upgrading Hosts by Using a Script,” on page 171 n “Using vSphere Auto Deploy to Reprovision Hosts,” on page 184 n “Upgrading Hosts by Using esxcli Commands,” on page 188 n “Upgrade Hosts Interactively,” on page 200 9 After upgrading ESXi hosts, you must reconnect the hosts to the vCenter Server and reapply the licenses.
Chapter 1 Introduction to vSphere Upgrade If you upgrade an external vCenter Single Sign-On and at least one instance of vCenter Server to version 6.0 while leaving other instances of vCenter Server at version 5.5, expect these results: n Linked Mode no longer functions. n vCenter Server 5.5 instances continue to operate with the upgraded Platform Services Controller as they did before the upgrade without any problems or required reconfiguration. n In a vCenter Server mixed-version 5.5 and 6.
vSphere Upgrade Figure 1‑7. Example Deployment in Transition at Step 1 Transitional Upgrade Environment: Step 1 Platform Services Controller 6.0 vCenter Single Sign-On 5.5 Operating System Operating System vCenter Inventory Service 5.5 vCenter Inventory Service 5.5 vCenter Inventory Service 5.5 vSphere Web Client 5.5 vSphere Web Client 5.5 vSphere Web Client 5.5 vCenter Server 5.5 vCenter Server 5.5 vCenter Server 5.
Chapter 1 Introduction to vSphere Upgrade Figure 1‑9. Example Deployment in Transition at Step 3 Transitional Upgrade Environment: Step 3 Platform Services Controller 6.0 Platform Services Controller 6.0 Operating System Operating System vCenter Server 6.0 Operating System vCenter Inventory Service 5.5 vCenter Inventory Service 5.5 vSphere Web Client 5.5 vSphere Web Client 5.5 vCenter Server 5.5 vCenter Server 5.
vSphere Upgrade n The remaining vSphere Web Client 5.5 instance can no longer view the vCenter Server 6.0 instances. n The vSphere Web Client 5.5 instance can still view the vCenter Server 5.5 instance after the vSphere Web Client 5.5 instance is restarted. n The vSphere Web Client 6.0 instances that are part of the newly upgraded vCenter Server 6.0 instances can view the vCenter Server 5.5 and vCenter Server 6.0 instances. Figure 1‑11.
Chapter 1 Introduction to vSphere Upgrade After the upgrade of the vCenter Server systems completes, the License Services stores the available licenses and manages the license assignments for the entire vSphere environment. If your vSphere environment consists of multiple Platform Services Controllers joined in one vCenter Single Sign-On domain, the License Service in every Platform Services Controller contains a replica of the licensing data for the entire environment.
vSphere Upgrade Who Can Log In After Upgrade of a Simple Install If you upgrade an environment that you provisioned using the Simple Install option, the result is always an installation with an embedded Platform Services Controller. Which users are authorized to log in depends on whether the source environment includes vCenter Single Sign-On. Table 1‑2. Login Privileges After Upgrade of Simple Install Environment Source version Login access for Notes vSphere 5.
Chapter 1 Introduction to vSphere Upgrade Table 1‑3. Login Privileges After Upgrade of Custom Install Environment Source version Login access for Notes vSphere 5.0 vCenter Single Sign-On recognizes local operating system users for the machine where the Platform Services Controller is installed, but not for the machine where vCenter Server is installed. Note Using local operating users for administration is not recommended, especially in federated environments. administrator@vsphere.
vSphere Upgrade When you install vCenter Server or deploy the vCenter Server Appliance with an external Platform Services Controller, you must first install the Platform Services Controller. During installation of the Platform Services Controller, you can select whether to create a new vCenter Single Sign-On domain or join an existing domain.
Chapter 1 Introduction to vSphere Upgrade If you have a simple installation with all vCenter Server 5.1 or 5.5 components on the same system, the vCenter Server 6.0 software upgrades your system to vCenter Server with an embedded Platform Services Controller instance. The software upgrades your vCenter Server common services such as vCenter Single Single-On in the Platform Services Controller instance.
vSphere Upgrade Figure 1‑15. vCenter Server 5.1 or 5.5 with Remote vSphere Auto Deploy Server Before and After Upgrade vCenter Server 5.1 or 5.5 vCenter Server 6.
Chapter 1 Introduction to vSphere Upgrade Figure 1‑17. vCenter Server 5.1 or 5.5 with All Remote Components Before and After Upgrade vCenter Server 5.1 or 5.5 vCenter Inventory Service Operating System vCenter Server Operating System vCenter Server 6.
vSphere Upgrade 32 VMware, Inc.
Upgrade Requirements 2 To upgrade vCenter Server and ESXi instances, your systems must meet specific requirements.
vSphere Upgrade Table 2‑1. Upgrading vCenter Server and Related VMware Products and Components Product or Component Compatibility vCenter Server Verify support for the upgrade path from your current version of vCenter Server to your planned upgrade version. See the VMware Product Interoperability Matrix at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. vCenter Server database Verify that your database is supported for the vCenter Server version that you are upgrading to.
Chapter 2 Upgrade Requirements vCenter Server for Windows Pre-Upgrade Checker When you upgrade vCenter Server and the Platform Services Controller, the installer does a pre-upgrade check, for example, to verify that enough space is available on the virtual machine or physical server where you are upgrading vCenter Server, and verifies that the external database, if any, can be successfully accessed.
vSphere Upgrade Table 2‑2.
Chapter 2 Upgrade Requirements vCenter Server for Windows Database Requirements vCenter Server requires a database to store and organize server data. Each vCenter Server instance must have its own database. For environments with up to 20 hosts and 200 virtual machines, you can use the bundled PostgreSQL database that the vCenter Server installer can install and set up for you during the vCenter Server installation.
vSphere Upgrade vCenter Server Appliance Storage Requirements When you deploy the vCenter Server Appliance, the host on which you deploy the appliance must meet minimum storage requirements. The required storage depends not only on the size of the vSphere environment, but also on the disk provisioning mode. The storage requirements depend on the deployment model that you select to deploy. Table 2‑5.
Chapter 2 Upgrade Requirements vCenter Server Appliance Database Requirements The vCenter Server Appliance requires a database to store and organize server data. Each vCenter Server Appliance instance must have its own database. You can use the bundled PostgreSQL database that is included in the vCenter Server Appliance, which supports up to 1,000 hosts and 10,000 virtual machines. For external databases, the vCenter Server Appliance supports only Oracle databases.
vSphere Upgrade Table 2‑6. Ports Required for Communication Between Components 40 Used for Node-toNode Communication Port Protocol Description Required for 22 TCP/UDP System port for SSHD. Important This port must be open during the upgrade of the appliance. The upgrade process establishes an SSH connection to transfer the data from the existing to the new appliance.
Chapter 2 Upgrade Requirements Table 2‑6. Ports Required for Communication Between Components (Continued) Used for Node-toNode Communication Port Protocol Description Required for 443 TCP The default port that the vCenter Server system uses to listen for connections from the vSphere Web Client. To enable the vCenter Server system to receive data from the vSphere Web Client, open port 443 in the firewall. The vCenter Server system also uses port 443 to monitor data transfer from SDK clients.
vSphere Upgrade Table 2‑6. Ports Required for Communication Between Components (Continued) Used for Node-toNode Communication Port Protocol Description Required for 1514 TCP/UDP vSphere Syslog Collector TLS port for vCenter Server on Windows and vSphere Syslog Service TLS port for vCenter Server Appliance Important You can change this port number during the vCenter Server and Platform Services Controller installations on Windows.
Chapter 2 Upgrade Requirements Table 2‑6. Ports Required for Communication Between Components (Continued) Used for Node-toNode Communication Port Protocol Description Required for 9443 TCP vSphere Web Client HTTPS Windows installations and appliance deployments of vCenter Server No 11711 TCP vCenter Single Sign-On LDAP - For backward compatibility with vSphere 5.5 only. vCenter Single SignOn 5.5 to Platform Services Controller 6.
vSphere Upgrade Table 2‑7. Configuration Notes for Databases Supported with vCenter Server (Continued) Database Type Configuration Notes Microsoft SQL Server 2012 Ensure that the machine has a valid ODBC DSN entry. Note This database is not supported for the vCenter Server Appliance. Microsoft SQL Server 2014 Ensure that the machine has a valid ODBC DSN entry. Note This database is not supported for the vCenter Server Appliance.
Chapter 2 Upgrade Requirements ESXi Booting Requirements vSphere 6.0 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI, you can boot systems from hard drives, CD-ROM drives, or USB media. Network booting or provisioning with VMware Auto Deploy requires the legacy BIOS firmware and is not available with UEFI. ESXi can boot from a disk larger than 2TB provided that the system firmware and the firmware on any addin card that you are using support it.
vSphere Upgrade Table 2‑8. Supported Remote Management Server Models and Minimum Firmware Versions (Continued) Remote Management Server Model Firmware Version Java HP ILO 1.81, 1.92 1.6.0_22, 1.6.0_23 HP ILO 2 1.8, 1.81 1.6.0_20, 1.6.0_23 HP ILO 3 1.28 1.7.0_60-b19 HP ILO 4 1.13 1.7.0_60-b19 IBM RSA 2 1.03, 1.2 1.6.
Chapter 2 Upgrade Requirements Table 2‑9. Recommendations for Enhanced Performance (Continued) System Element Recommendation VMFS5 partitioning The ESXi installer creates the initial VMFS volumes on the first blank local disk found. To add disks or modify the original configuration, use the vSphere Web Client. This practice ensures that the starting sectors of partitions are 64K-aligned, which improves storage performance. Note For SAS-only environments, the installer might not format the disks.
vSphere Upgrade Table 2‑10. Incoming Firewall Connections (Continued) Service Port Comment NSX Distributed Logical Router Service 6999 (UDP) NSX Virtual Distributed Router service. The firewall port associated with this service is opened when NSX VIBs are installed and the VDR module is created. If no VDR instances are associated with the host, the port does not have to be open. This service was called NSX Distributed Logical Router in earlier versions of the product.
Chapter 2 Upgrade Requirements Table 2‑11. Outgoing Firewall Connections (Continued) Service Port Comment NSX Distributed Logical Router Service 6999 (UDP) The firewall port associated with this service is opened when NSX VIBs are installed and the VDR module is created. If no VDR instances are associated with the host, the port does not have to be open.
vSphere Upgrade vSphere Web Client Software Requirements Make sure that your browser supports the vSphere Web Client. The vSphere Web Client 6.0 requires Adobe Flash Player 16 or later. The latest Adobe Flash Player version for Linux systems is 11.2. Therefore, the vSphere Web Client cannot run on Linux platforms. VMware has tested and supports the following guest operating systems and browser versions for the vSphere Web Client. For best performance, use Google Chrome. Table 2‑12.
Chapter 2 Upgrade Requirements Table 2‑14. vSphere Client Minimum Hardware Requirements and Recommendations (Continued) vSphere Client Hardware Requirements and Recommendations Disk Storage 1.5GB free disk space for a complete installation, which includes the following components: n Microsoft .NET 2.0 SP2 n Microsoft .NET 3.0 SP2 n Microsoft .NET 3.5 SP1 n Microsoft Visual J# Remove any previously installed versions of Microsoft Visual J# on the system where you are installing the vSphere Client.
vSphere Upgrade Required Free Space for System Logging If you used Auto Deploy to install your ESXi 6.0 host, or if you set up a log directory separate from the default location in a scratch directory on the VMFS volume, you might need to change your current log size and rotation settings to ensure that enough space is available for system logging . All vSphere components use this infrastructure.
Before Upgrading vCenter Server 3 Ensure that your system is prepared for vCenter Server upgrade by verifying compatibility and completing any necessary database, networking, or other preparation tasks.
vSphere Upgrade 2 Verify that the vCenter Server system is not an Active Directory primary or backup domain controller. 3 Update any ESX/ESXi 4.1 hosts to version 5.x. 4 If you have ESX 4.x hosts that you choose not to upgrade, you must remove them from the vCenter Server inventory. 5 If the vCenter Server 4.x environment that you are upgrading includes Guided Consolidation 4.x, uninstall Guided Consolidation before upgrading to vCenter Server 6.0.
Chapter 3 Before Upgrading vCenter Server 3 If your existing database is Oracle, and you want to upgrade to a newly supported Oracle database, such as Oracle 11g, upgrade your Oracle database before upgrading vCenter Server. You do not need to perform a fresh installation of vCenter Server if your existing database is Oracle. For example, you can upgrade your existing Oracle 9i database to Oracle 11g or Oracle 12c and upgrade vCenter Server 5.x to vCenter Server 6.0.
vSphere Upgrade Prepare Microsoft SQL Server Database Before Upgrading to vCenter Server 6.0 Ensure that your Microsoft SQL Server database meets requirements, that you have the necessary credentials, and that you complete any necessary cleanup or other preparation before upgrading vCenter Server. To remove the DBO role and migrate all objects in the DBO schema to a custom schema, see the VMware knowledge base article at http://kb.vmware.com/kb/1036331.
Chapter 3 Before Upgrading vCenter Server 7 Verify that the sqljdbc4.jar file is added to the CLASSPATH variable on the machine where vCenter Server is to be upgraded. If the sqljdbc4.jar file is not installed on your system, the vCenter Server installer installs it. 8 Verify that your system database source name is using the Microsoft SQL Server Native Client 10 or 11 driver.
vSphere Upgrade 2 Run the following script to create roles and apply privileges. The script is located in the vCenter Server installation package at /installation directory/vCenter- Server/dbschema/DB_and_schema_creation_scripts_MSSQL.txt .
Chapter 3 Before Upgrading vCenter Server go GRANT EXECUTE ON msdb.dbo.sp_add_jobserver TO VC_ADMIN_ROLE go GRANT EXECUTE ON msdb.dbo.sp_add_jobschedule TO VC_ADMIN_ROLE go GRANT EXECUTE ON msdb.dbo.sp_add_category TO VC_ADMIN_ROLE go sp_addrolemember VC_ADMIN_ROLE , [vpxuser] go use master go grant VIEW SERVER STATE to [vpxuser] go GRANT VIEW ANY DEFINITION TO [vpxuser] go Prepare PostgreSQL Database Before Upgrading to vCenter Server 6.
vSphere Upgrade Table 3‑1. Microsoft SQL Database Permissions for vCenter Server Permission Description GRANT ALTER ON SCHEMA :: [VMW] TO VC_ADMIN_ROLE Mandatory when you work with SQL Server custom schema. GRANT REFERENCES ON SCHEMA :: [VMW] TO VC_ADMIN_ROLE Mandatory when you work with SQL Server custom schema. GRANT INSERT ON SCHEMA :: [VMW] TO VC_ADMIN_ROLE Mandatory when you work with SQL Server custom schema. GRANT CREATE TABLE TO VC_ADMIN_ROLE Necessary for creating a table.
Chapter 3 Before Upgrading vCenter Server Table 3‑2. Oracle Database Permissions for vCenter Server Permission Description GRANT CONNECT TO VPXADMIN Necessary for connecting to the Oracle database. GRANT RESOURCE TO VPXADMIN Necessary for creating a trigger, sequence, type, procedure, and so on. By default, the RESOURCE role has the CREATE PROCEDURE, CREATE TABLE, and CREATE SEQUENCE privileges assigned. If the RESOURCE role lacks these privileges, grant them to the vCenter Server database user.
vSphere Upgrade Verify That vCenter Server Can Communicate with the Local Database If your database is located on the same machine on which vCenter Server is to be installed, and you have changed the name of this machine, verify the configuration. Make sure that the vCenter Server DSN is configured to communicate with the new name of the machine. Changing the vCenter Server computer name impacts database communication if the database server is on the same computer with vCenter Server.
Chapter 3 Before Upgrading vCenter Server 2 Verify that DNS reverse lookup returns a fully qualified domain name when queried with the IP address of the vCenter Server. When you upgrade vCenter Server, the installation of the web server component that supports the vSphere Web Client fails if the installer cannot look up the fully qualified domain name of the vCenter Server from its IP address. Reverse lookup is implemented by using PTR records.
vSphere Upgrade 3 Verify that the load balancer is correctly configured based on recommendations in vCenter Server 6.0 Deployment Guide. Prepare ESXi Hosts for vCenter Server Upgrade Before upgrading to vCenter Server 6.0, you must prepare your ESXi hosts. Prerequisites n To upgrade vCenter Server, your ESXi hosts must be at version 5.x. If your ESXi hosts are at an earlier version than 5.0, upgrade them to 5.x. Read and follow all best practices when upgrading your hosts to ESXi 5.x.
Chapter 3 Before Upgrading vCenter Server Host Upgrades and Certificates If you upgrade an ESXi host to ESXi 6.0 or later, the upgrade process replaces self-signed certificates with VMCA-signed certificates. The process retains custom certificates even if those certificates are expired or invalid. The recommended upgrade workflow depends on the current certificates.
vSphere Upgrade Verify Preparations Are Complete for Upgrading vCenter Server Verify that all components of your environment are ready to upgrade vCenter Server. Your pre-upgrade configuration of vCenter Server services impacts your post-upgrade deployment of vCenter Server services. n If you have vCenter Server 5.0, you can choose to configure either an embedded or an external Platform Services Controller instance during the upgrade. See “Upgrade vCenter Server 5.0,” on page 83.
Chapter 3 Before Upgrading vCenter Server 3 n For vCenter Server 5.0, to upgrade to an embedded Platform Services Controller deployment, no pre-upgrade steps are required. n For vCenter Server 5.0, to upgrade to an external Platform Services Controller deployment, you must configure an external Platform Services Controller instance before upgrading vCenter Server.
vSphere Upgrade 3 Click Properties, and click Options. 4 Select NTP Settings. 5 Click Add. 6 In the Add NTP Server dialog box, enter the IP address or fully qualified domain name of the NTP server to synchronize with. 7 Click OK. The host time synchronizes with the NTP server. Downtime During the vCenter Server Upgrade When you upgrade vCenter Server, downtime is required for vCenter Server.
Chapter 3 Before Upgrading vCenter Server Required Information for Upgrading vCenter Server for Windows The vCenter Server upgrade wizard prompts you for the upgrade information. It is a best practice to keep a record of the values that you entered in case you must reinstall the product. You can use this worksheet to record information that you might need when upgrading vCenter Server for Windows in the future.
vSphere Upgrade You can use this worksheet to record the information that you need for upgrading a vCenter Server Appliance version 5.1 Update 3 or 5.5.x. Table 3‑4. Information Required for Upgrading vCenter Server Appliance 5.1.x or 5.5..
Chapter 3 Before Upgrading vCenter Server Table 3‑4. Information Required for Upgrading vCenter Server Appliance 5.1.x or 5.5..x (Continued) Required Information Default Value Enable or disable thin disk mode.
vSphere Upgrade 72 VMware, Inc.
Upgrading and Updating vCenter Server for Windows 4 The vCenter Server upgrade includes a database schema upgrade, migration of vCenter Single Sign-On to Platform Services Controller, and upgrade of the vCenter Server software. This chapter includes the following topics: n “About the vCenter Server 6.0 for Windows Upgrade Process,” on page 73 n “Migration of Distributed vCenter Server for Windows Services During Upgrade to vCenter Server 6.
vSphere Upgrade n When upgrading from a vCenter Server version 5.1 or version 5.5 deployment with vCenter Single Sign-On deployed on a different VM or physical server than vCenter Server, the software upgrades the deployment to vCenter Server with an external Platform Services Controller. n When upgrading multiple instances of vCenter Server, you must upgrade sequentially and upgrade order matters. See “Mixed-Version Transitional Environments During vCenter Server Upgrades,” on page 20 Figure 4‑1.
Chapter 4 Upgrading and Updating vCenter Server for Windows Figure 4‑2. vCenter Server 5.1 or 5.5 for Windows Upgrade Workflow Begin vCenter 5.1 or 5.
vSphere Upgrade n vSphere Auto Deploy n vSphere Syslog Collector n vSphere ESXi Dump Collector vCenter Server and vCenter Single Sign-On are the only services that are not migrated. vCenter Single Sign-On instances are upgraded in place to become part of an external Platform Services Controller if they are deployed on a system other than the system where the vCenter Server resides. Figure 4‑3. Component Services Migrated to vCenter Server Group of Services vCenter Server 5.1 or 5.5 vCenter Server 6.
Chapter 4 Upgrading and Updating vCenter Server for Windows Table 4‑1. vCenter Server 5.x Distributed Service Migration During Upgrade (Continued) Service Location Before Upgrade Service Location After Upgrade vSphere Auto Deploy Not installed on the vCenter Server system Migrated to vCenter Server system vSphere Auto Deploy data is copied to the Auto Deploy 6.0 instance that is installed with vCenter Server 6.0. Repoint vCenter Server DHCP settings to the migrated vSphere Auto Deploy service.
vSphere Upgrade Upgrade vCenter Single Sign-On 5.1 for External Deployment You can upgrade your externally deployed vCenter Single Sign-On 5.1 to an externally deployed Platform Services Controller instance by using the vCenter Server for Windows installer. Figure 4‑4. vCenter Single Sign-On 5.1 Upgrade Workflow for Windows Begin vCenter Single Sign-On 5.
Chapter 4 Upgrading and Updating vCenter Server for Windows Prerequisites n Your current vCenter Single Sign-On must have been installed on a separate virtual machine or physical server from your vCenter Server instance. n Verify that your configuration meets the upgrade requirements. See “vCenter Server for Windows Requirements,” on page 34. n Complete the preparation to upgrade tasks. See Chapter 3, “Before Upgrading vCenter Server,” on page 53.
vSphere Upgrade 8 Configure the install, data, and export directories and click Next. The installer runs disk space and permission checks for the selected directories and displays an error message if the selected directories do not meet the requirements. 9 Review the VMware Customer Experience Improvement Program (CEIP) page and choose if you want to join the program.
Chapter 4 Upgrading and Updating vCenter Server for Windows Upgrade vCenter Single Sign-On 5.5 for External Deployment You can upgrade your externally deployed vCenter Single Sign-On 5.5 to an externally deployed Platform Services Controller instance by using the vCenter Server for Windows installer. Figure 4‑5. vCenter Single Sign-On 5.5 Upgrade Workflow for Windows Begin vCenter Single Sign-On 5.
vSphere Upgrade Prerequisites n Your current vCenter Single Sign-On must have been installed on a separate virtual machine (VM) or physical server from your vCenter Server instance. n Verify your configuration meets the upgrade requirements, see “vCenter Server for Windows Requirements,” on page 34. n Complete the preparation to upgrade tasks. See Chapter 3, “Before Upgrading vCenter Server,” on page 53 n Verify that you have made a backup of your vCenter Server configuration and database.
Chapter 4 Upgrading and Updating vCenter Server for Windows 8 Configure the ports and click Next. Verify that ports 80 and 443 are free and dedicated, so that vCenter Single Sign-On can use these ports. Otherwise, use custom ports during installation. The installer checks the availability of the selected ports and displays an error message if a selected port cannot be used. 9 Configure the install, data, and export directories and click Next.
vSphere Upgrade n Verify that you have made a backup of your vCenter Server configuration and database. n Download the vCenter Server Installer. See “Download the vCenter Server for Windows Installer,” on page 77 Procedure 1 Download the vCenter Server for Windows ISO file. Extract the ISO file locally, or mount the ISO file as a drive. 2 In the software installer, double-click the autorun.exe file to start the installer. 3 Select vCenter Server for Windows and click Install.
Chapter 4 Upgrading and Updating vCenter Server for Windows 11 Review the Summary page to verify that the settings are correct. Verify that you have made a backup of the vCenter Server machine and the vCenter Server database and click Upgrade. A progress indicator displays as the installer starts the upgrade process. When the process is complete, the installer verifies the upgrade. 12 Before clicking Finish, note the post-upgrade steps. 13 Click Finish to complete the upgrade.
vSphere Upgrade Prerequisites n Verify that your configuration meets the upgrade requirements. See “vCenter Server for Windows Requirements,” on page 34. n Complete the preparation to upgrade tasks. See Chapter 3, “Before Upgrading vCenter Server,” on page 53 n Verify that you have made a backup of your vCenter Server configuration and database. n Download the vCenter Server Installer.
Chapter 4 Upgrading and Updating vCenter Server for Windows 11 Click Finish to complete the upgrade. Your vCenter Server for Windows upgrade is complete. For information on post-upgrade tasks, see Chapter 6, “After Upgrading vCenter Server,” on page 113. Upgrade vCenter Server 5.5 for Windows You can upgrade your existing vCenter Server 5.5 deployment by using the vCenter Server for Windows installer. Your vCenter Server 5.
vSphere Upgrade n Verify that you have made a backup of your vCenter Server configuration and database. n To verify that the VMware Directory Service is in a stable state and can stop, manually restart it. The VMware Directory service must stopped for the vCenter Server upgrade software to uninstall vCenter Single Sign-On during the upgrade process. n Download the vCenter Server Installer. See “Download the vCenter Server for Windows Installer,” on page 77. n If your vCenter Single Sign-On 5.
Chapter 4 Upgrading and Updating vCenter Server for Windows 8 Review the VMware Customer Experience Improvement Program (CEIP) page and choose if you want to join the program. For information about the CEIP, see the Configuring Customer Experience Improvement Program section in vCenter Server and Host Management. 9 Review the Summary page to verify that the settings are correct.
vSphere Upgrade 90 VMware, Inc.
Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance 5 You can upgrade the vCenter Server Appliance by using the Client Integration Plug-In. You can update the vCenter Server Appliance and Platform Services Controller appliance with patches by using the Appliance Management Interface or by using the software-packages utility that is available in the appliance shell. Important Upgrades from vCenter Server Appliance 5.
vSphere Upgrade For information about the vCenter Server Appliance upgrade requirements, see “vCenter Server Appliance Requirements,” on page 37. For information about the inputs that are required during the upgrade of the vCenter Server Appliance, see “Required Information for Upgrading the vCenter Server Appliance,” on page 69. The upgrade of the vCenter Server Appliance is a migration of the old version to the latest version, which results in deploying a new vCenter Server Appliance 6.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance Figure 5‑1.
vSphere Upgrade n For vCenter Server Appliance upgrade procedures, see Chapter 5, “Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance,” on page 91. n For vCenter Server Appliance post-upgrade procedures, see Chapter 6, “After Upgrading vCenter Server,” on page 113. Download the vCenter Server Appliance Installer Download the .iso installer for the vCenter Server Appliance and Client Integration Plug-in. Prerequisites Create a My VMware account at https://my.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance Upgrade the vCenter Server Appliance with Embedded vCenter Single Sign-On You can use the Client Integration Plug-In to upgrade a vCenter Server Appliance 5.1 Update 3 and 5.5.x that uses the embedded vCenter Single Sign-On instance to a vCenter Server Appliance 6.0 with an embedded Platform Services Controller. You can deploy version 6.
vSphere Upgrade 5 Read and accept the license agreement, and click Next. 6 Connect to the target server on which you want to deploy the vCenter Server Appliance, and click Next. a Enter the FQDN or IP address of the ESXi host. b Enter the user name and password of a user who has administrative privileges on the ESXi host, for example, the root user. 7 (Optional) Accept the certificate warning, if any, by clicking Yes. 8 Enter a name for the vCenter Server Appliance 6.0.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance c d Under vCenter Server Appliance, enter the required data of the vCenter Server Appliance that you want to upgrade. Option Action vCenter Server IP Address/FQDN Enter the IP address or FQDN of the vCenter Server Appliance that you want to upgrade. vCenter Administrator User Name Enter the vCenter Single Sign-On administrator user name. If you are upgrading vCenter Server Appliance 5.5.
vSphere Upgrade 13 On the Select appliance size page of the wizard, select the vCenter Server Appliance size for the vSphere inventory size and click Next. Option Description Tiny (up to 10 hosts, 100 VMs) Deploys an appliance with 2 CPUs and 8 GB of memory. Small (up to 100 hosts, 1,000 VMs) Deploys an appliance with 4 CPUs and 16 GB of memory. Medium (up to 400 hosts, 4,000 VMs) Deploys an appliance with 8 CPUs and 24 GB of memory.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance Upgrade the vCenter Server Appliance with External vCenter Single Sign-On To upgrade a vCenter Server Appliance 5.5.x that is registered with an external vCenter Single Sign-On instance to a vCenter Server Appliance 6.0 with an external Platform Services Controller, you can use the Client Integration Plug-In. You can deploy version 6.0 of vCenter Server Appliance only on hosts that are running ESXi 5.
vSphere Upgrade Procedure 1 In the software installer directory, double-click vcsa-setup.html. 2 Wait up to three seconds for the browser to detect the Client Integration Plug-in and allow the plug-in to run on the browser when prompted. 3 On the Home page, click Upgrade. 4 In the Supported Upgrade warning message, click OK to start the vCenter Server Appliance upgrade wizard. 5 Read and accept the license agreement, and click Next.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance c d Under vCenter Server Appliance, enter the required data of the vCenter Server Appliance that you want to upgrade. Option Action vCenter Server IP Address/FQDN Enter the IP address or FQDN of the vCenter Server Appliance that you want to upgrade. vCenter Administrator User Name Enter the vCenter Single Sign-On administrator user name. If you are upgrading vCenter Server Appliance 5.5.
vSphere Upgrade 14 Select the temporary network for communication between the vCenter Server Appliance that you want to upgrade and the newly deployed vCenter Server Appliance, select the vCenter Server Appliance IP allocation method, and click Next. The networks displayed in the Choose a temporary network drop-down menu depend on the ESXi network settings. Non-ephemeral distributed virtual port groups are not supported and are not displayed in the drop-down menu.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance n Download Filename Description VMware-vCenter-Server-Applianceproduct_version-build_number-patch-TP.iso Third-party patch for the vCenter Server Appliance and Platform Services Controller appliance, which contains only the fixes related to security and third-party products (e.g. JRE, tcServer, and SLES OS components). VMware-vCenter-Server-Applianceproduct_version-build_number-patch-FP.
vSphere Upgrade Prerequisites Verify that the vCenter Server Appliance is successfully deployed and running. Procedure 1 In a Web browser, go to the vCenter Server Appliance Management Interface, https://appliance-IPaddress-or-FQDN:5480. 2 Log in as root. The default root password is the password you set while deploying the vCenter Server Appliance.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance What to do next “Check for and Install vCenter Server Appliance Patches,” on page 105 Check for and Install vCenter Server Appliance Patches You can check for and install patches either from an ISO image or directly from a repository URL. Important The services running in the appliance become unavailable during the installation of the patches.
vSphere Upgrade 6 If patch installation requires the appliance to reboot, click Summary, and click Reboot to reset the appliance. In the Available updates pane, you can see the changed update status of the appliance. Enable Automatic Checks for vCenter Server Appliance Patches You can configure the vCenter Server Appliance to perform automatic checks for available patches in the configured repository URL at a regular interval.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance View a List of All Installed Patches in the vCenter Server Appliance You can use the software-packages utility to see a list of the patches currently applied to the vCenter Server Appliance. You can also view the list of the installed patches in chronological order and details about a specific patch. Procedure 1 Access the appliance shell and log in as a user who has a super administrator role.
vSphere Upgrade Procedure 1 If you want to configure a custom repository URL, build the repository on your local Web server. a Download the vCenter Server Appliance patch ZIP file from the VMware Web site at https://my.vmware.com/web/vmware/downloads. b On your Web server, create a repository directory under the root. For example, create the vc_update_repo directory. c Extract the ZIP file into the repository directory. The extracted files are in the manifest and package-pool subdirectories.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance Stage Patches to the vCenter Server Appliance Before you install available patches, you can stage the patches to the appliance. You can use the softwarepackages utility to stage patches either from a local repository by attaching an ISO image to the appliance, or from a remote repository directly by using a repository URL.
vSphere Upgrade 5 (Optional) To unstage the staged patches, run the following command: software-packages unstage All directories and files generated by the staging process are removed. What to do next Install the staged patches. See “Install vCenter Server Appliance Patches,” on page 110. Important If you staged the patches from an ISO image, keep the ISO image attached to the CD/DVD drive of the appliance.
Chapter 5 Upgrading and Patching the vCenter Server Appliance and Platform Services Controller Appliance n To install patches directly from the current repository URL, run the following command: software-packages install --url By default the current repository URL is the default VMware repository URL. If you want to install only the third-party patches, use the --thirdParty option.
vSphere Upgrade 112 VMware, Inc.
After Upgrading vCenter Server 6 After you upgrade to vCenter Server, consider the post-upgrade options and requirements. n You can review the database upgrade logs. See “Collect Database Upgrade Logs,” on page 209. n Complete any component reconfigurations that might be required for changes during upgrade. n Verify that you understand the authentication process and identify your identity sources.
vSphere Upgrade If you have a vSphere Web Client service registered to vCenter Server before upgrade, it is upgraded automatically and there is no change of location. If you have a remote vSphere Web Client registered to vCenter Server before upgrade, it is migrated to the machine where vCenter Server is located when it is upgraded.
Chapter 6 After Upgrading vCenter Server Procedure 1 If your vSphere Auto Deploy service was previously installed on a separate machine from vCenter Server, and was relocated during the upgrade process, update your DHCP and TFTP settings to point to your relocated vSphere Auto Deploy service. a Download deploy-tftp.zip and replace the tftp root folder. Your configuration can vary based on your TFTP client. b Reconfigure the DHCP .conf file to use the upgraded vSphere Auto Deploy service and its .
vSphere Upgrade n Verify that the host machine has a supported processor and operating system. n Verify that the host machine has a valid IPv4 address. You can install vSphere Authentication Proxy on a machine in an IPv4-only or IPv4/IPv6 mixed-mode network environment, but you cannot install vSphere Authentication Proxy on a machine in an IPv6-only environment.
Chapter 6 After Upgrading vCenter Server n Verify that the system has an Internet connection. Procedure 1 (Optional) Use Add/Remove Programs from the Windows Control Panel to remove any previous vCenter Server client. You do not need to remove earlier versions of vCenter Server clients. These versions are useful if you must connect to legacy hosts. 2 Run the vSphere Client installer. n Start the vCenter Server installer. In the software installer directory, double-click the autorun.
vSphere Upgrade Table 6‑1. JVM Heap Size Setting for Inventory Service and Profile-Driven Storage Service, with Java Maximum n the wrapper.conf Files Java Option Setting and Default Value maxmemorysize The maximum JVM heap size, in megabytes. This setting controls the maximum size of the Java heap. Tuning this parameter can reduce the overhead of garbage collection, improving server response time and throughput.
Chapter 6 After Upgrading vCenter Server Set the Maximum Number of Database Connections After a vCenter Server Upgrade By default, a vCenter Server creates a maximum of 50 simultaneous database connections. If you configure this value to less than 50 in the previous version of vCenter Server and then perform the upgrade to vCenter Server 5.x, the upgrade restores the default setting of 50.
vSphere Upgrade Authenticating to the vCenter Server Environment In vCenter Server versions 5.1 and later, users authenticate through vCenter Single Sign-On. In vCenter Server versions earlier than vCenter Server 5.1, when a user connects to vCenter Server, vCenter Server authenticates the user by validating the user against an Active Directory domain or the list of local operating system users. The user administrator@your_domain_name has vCenter Single Sign-On administrator privileges by default.
Chapter 6 After Upgrading vCenter Server n Local operating system users. Local operating system users are local to the operating system where the vCenter Single Sign-On server is running. The local operating system identity source exists only in basic vCenter Single Sign-On server deployments and is not available in deployments with multiple vCenter Single Sign-On instances. Only one local operating system identity source is allowed. Shown as localos in the vSphere Web Client.
vSphere Upgrade 3 Copy the text between -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- into the /etc/vmware/ssl/rui.crt file. Include -----BEGIN CERTIFICATE----- and -----END CERTIFICATE-----. 4 Restart the host or send ssl_reset events to all services that use the keys. for s in /etc/init.
Chapter 6 After Upgrading vCenter Server where the square brackets [ ] enclose the command options. Here, psc_fqdn_or_static_ip is the system name used to identify the Platform Services Controller. This system name must be an FQDN or a static IP address. Note The FQDN value is case-sensitive. Use the --dc-port port_number option if the Platform Services Controller runs on a custom HTTPS port. The default value of the HTTPS port is 443.
vSphere Upgrade Table 6‑3.
Chapter 6 After Upgrading vCenter Server 2 Verify that all Platform Services Controller services are running. Option Steps For a vCenter Server Appliance with an embedded Platform Services Controller Run the service-control --status --all command. For a Windows installation of vCenter Server with an embedded Platform Services Controller Select Start > Control Panel > Administrative Tools > Services.
vSphere Upgrade Reconfigure Multiple Joined Instances of vCenter Server with an Embedded Platform Services Controller to vCenter Server with an External Platform Services Controller If you have deployed or installed two or more joined instances of vCenter Server with an embedded Platform Services Controller, you can reconfigure them as multiple vCenter Server instances that are using joined external Platform Services Controller instances. Figure 6‑2.
Chapter 6 After Upgrading vCenter Server Table 6‑4.
vSphere Upgrade 2 Verify that all Platform Services Controller services are running. Option Steps For a vCenter Server Appliance with an embedded Platform Services Controller Run the service-control --status --all command. For a Windows installation of vCenter Server with an embedded Platform Services Controller Select Start > Control Panel > Administrative Tools > Services.
Chapter 6 After Upgrading vCenter Server Table 6‑5. Legend Arrow or line Description Replication agreement between two Platform Services Controller instances vCenter Server registration with an external Platform Services Controller Transition step To configure replication agreement between two Platform Services Controller instances, you can use a connection to any of the vCenter Server or Platform Services Controller instances from the vCenter Single Sign-On domain.
vSphere Upgrade 4 If there is an external Platform Services Controller instance that is not in replication agreement with another external Platform Services Controller instance, run the vdcrepadmin command with the createagreement parameter against this Platform Services Controller instance to join it to another external Platform Services Controller instance. n If you are using a connection to a vCenter Server Appliance or Platform Services Controller appliance, run the following command.
Chapter 6 After Upgrading vCenter Server Reconfigure Each vCenter Server Instance and Repoint It from an Embedded to External Platform Services Controller Instance With the reconfiguration you demote each embedded Platform Services Controller and redirect the vCenter Server instance to use an external Platform Services Controller instance. Figure 6‑4.
vSphere Upgrade Table 6‑6. Legend Arrow or line Description Replication agreement between two Platform Services Controller instances vCenter Server registration with an external Platform Services Controller Transition step Procedure 1 Log in to the vCenter Server instance with an embedded Platform Services Controller.
Chapter 6 After Upgrading vCenter Server For example, if the external Platform Services Controller runs on a custom HTTPS port 449, you must run: cmsso-util reconfigure --repoint-psc psc.acme.local --username administrator --domain-name vsphere.
vSphere Upgrade 134 VMware, Inc.
Upgrading Update Manager 7 You can upgrade to Update Manager 6.0 only from Update Manager version 5.x that are installed on a 64-bit operating system. If you are running Update Manager of a version earlier than 5.x, or Update Manager that runs on a 32-bit platform, you cannot perform an in-place upgrade to Update Manager 6.0. You must use the data migration tool that is provided with Update Manager 5.0 installation media to upgrade your Update Manager system to Update Manager 5.
vSphere Upgrade n Stop the Update Manager service and back up the Update Manager database. The installer upgrades the database schema, making the database irreversibly incompatible with previous Update Manager versions. Procedure 1 Upgrade vCenter Server to a compatible version. Note The vCenter Server installation wizard warns you that Update Manager is not compatible when vCenter Server is upgraded. If prompted, you must restart the machine that is running vCenter Server.
Chapter 7 Upgrading Update Manager 15 Click Finish. You upgraded the Update Manager server. What to do next Upgrade the Update Manager Client plug-in. VMware, Inc.
vSphere Upgrade 138 VMware, Inc.
Before Upgrading Hosts 8 For a successful upgrade of your hosts, understand and prepare for the changes that are involved. This chapter includes the following topics: n “Best Practices for ESXi Upgrades,” on page 139 n “Upgrade Options for ESXi 6.
vSphere Upgrade n Make sure that sufficient disk space is available on the host for the upgrade. n If a SAN is connected to the host, detach the Fibre Channel system before continuing with the upgrade. Do not disable HBA cards in the BIOS. 3 Back up the host before performing an upgrade. If the upgrade fails, you can restore the host. 4 Depending on the upgrade option you choose, you might need to migrate or power off all virtual machines on the host. See the instructions for your upgrade method.
Chapter 8 Before Upgrading Hosts host upgrade, see “Using vSphere Update Manager to Perform Orchestrated Host Upgrades,” on page 155. For instructions about performing an orchestrated virtual machine upgrade, see the Installing and Administering VMware vSphere Update Manager documentation. Upgrade interactively by using an ESXi installer ISO image on CD/DVD or USB flash drive You can run the ESXi 6.0 installer from a CD/DVD or USB flash drive to do an interactive upgrade.
vSphere Upgrade Using Manually Assigned IP Addresses for Upgrades Performed with vSphere Update Manager If you are using vSphere Update Manager to upgrade a host from ESXi 5.x to ESXi 6.0, you must use manually assigned IP addresses for the hosts. Manually assigned IP addresses are also called static IP addresses. IP addresses that are requested by using Dynamic Host Configuration Protocol (DHCP) can cause problems during host upgrades that are performed with vSphere Update Manager.
Chapter 8 Before Upgrading Hosts Prerequisites n Linux machine with superuser access to it n USB flash drive that can be detected by the Linux machine n The ESXi ISO image, VMware-VMvisor-Installer-version_number-build_number.x86_64.iso, which includes the isolinux.cfg file n Syslinux package Procedure 1 If your USB flash drive is not detected as /dev/sdb, or you are not sure how your USB flash drive is detected, determine how it is detected.
vSphere Upgrade 5 Create a destination directory and mount the USB flash drive to it. mkdir /usbdisk mount /dev/sdb1 /usbdisk 6 Create a destination directory and mount the ESXi installer ISO image to it. mkdir /esxi_cdrom mount -o loop VMware-VMvisor-Installer-6.x.x-XXXXXX.x86_64.iso /esxi_cdrom 7 Copy the contents of the ISO image to the USB flash drive. cp -r /esxi_cdrom/* /usbdisk 8 Rename the isolinux.cfg file to syslinux.cfg. mv /usbdisk/isolinux.cfg /usbdisk/syslinux.
Chapter 8 Before Upgrading Hosts d Type p to print the partition table. The result should be similar to the following text: Disk /dev/sdb: 2004 MB, 2004877312 bytes 255 heads, 63 sectors/track, 243 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks /dev/sdb1 1 243 1951866 e 3 Id c System W95 FAT32 (LBA) Type w to write the partition table and quit. Format the USB flash drive with the Fat32 file system. /sbin/mkfs.
vSphere Upgrade 4 Copy the kickstart file to /esxi_cdrom. cp ks_cust.cfg /esxi_cdrom 5 (Optional) Modify the boot.cfg file to specify the location of the installation or upgrade script by using the kernelopt option. You must use uppercase characters to provide the path of the script, for example, kernelopt=runweasel ks=cdrom:/KS_CUST.CFG The installation or upgrade becomes completely automatic, without the need to specify the kickstart file during the installation or upgrade.
Chapter 8 Before Upgrading Hosts If you do not use gPXE, you might experience problems while booting the ESXi installer on a heavily loaded network TFTP is sometimes unreliable for transferring large amounts of data. If you use PXELINUX without gPXE, the pxelinux.0 binary file, the configuration file, the kernel, and other files are transferred by TFTP. If you use gPXE, only the gpxelinux.0 binary file and configuration file are transferred by TFTP.
vSphere Upgrade Sample DHCP Configuration To PXE boot the ESXi installer, the DHCP server must send the address of the TFTP server and a pointer to the pxelinux.0 or gpxelinux.0 directory. The DHCP server is used by the target machine to obtain an IP address. The DHCP server must be able to determine whether the target machine is allowed to boot and the location of the PXELINUX binary (which usually resides on a TFTP server).
Chapter 8 Before Upgrading Hosts next-server xxx.xxx.xx.xx; filename = "pxelinux.0"; } subnet 192.168.48.0 netmask 255.255.255.0 { range 192.168.48.100 192.168.48.250; } When a machine attempts to PXE boot, the DHCP server provides an IP address and the location of the pxelinux.0 binary file on the TFTP server. The IP address assigned is in the range defined in the subnet section of the configuration file.
vSphere Upgrade n DHCP server configured for PXE booting. See “Sample DHCP Configuration,” on page 148. n PXELINUX. n Server with a hardware configuration that is supported with your version of ESXi. See VMware Compatibility Guide at http://www.vmware.com/resources/compatibility/search.php. n Network security policies to allow TFTP traffic (UDP port 69). n (Optional) Installation script, the kickstart file. See “About Installation and Upgrade Scripts,” on page 174.
Chapter 8 Before Upgrading Hosts 7 Name the file with the media access control (MAC) address of the target host machine: 01mac_address_of_target_ESXi_host. For example, 01-23-45-67-89-0a-bc. 8 Save the PXE configuration file in /tftpboot/pxelinux.cfg on the TFTP server. 9 Boot the machine with the network adapter. PXE Boot the ESXi Installer by Using PXELINUX and an isolinux.cfg PXE Configuration File You can PXE boot the ESXi installer by using PXELINUX, and you can use the isolinux.
vSphere Upgrade 5 (Optional) For a scripted installation, in the boot.cfg file, add the kernelopt option on the line after the kernel command to specify the location of the installation script. In the following example, XXX.XXX.XXX.XXX is the IP address of the server where the installation script resides. kernelopt=ks=http://XXX.XXX.XXX.XXX/esxi_ksFiles/ks.cfg 6 Copy the isolinux.cfg file from the ESXi installer ISO image to the /tftpboot/pxelinux.cfg directory. The isolinux.
Chapter 8 Before Upgrading Hosts 2 Modify the boot.cfg file with the information for the HTTP server. Use the following code as a model, where XXX.XXX.XXX.XXX is the HTTP server IP address. The kernelopt line is optional. Include that option to specify the location of the installation script for a scripted installation. title=Loading ESX installer kernel=http://XXX.XXX.XXX.XXX/tboot.b00 kernelopt=ks=http://XXX.XXX.XXX.XXX/esxi_ksFiles/ks.cfg modules=http://XXX.XXX.XXX.XXX/b.b00 --- http://XXX.XXX.XXX.
vSphere Upgrade Procedure 1 Download the ESXi installer from the VMware Web site at https://my.vmware.com/web/vmware/downloads. ESXi is listed under Datacenter & Cloud Infrastructure. 2 Confirm that the md5sum is correct. See the VMware Web site topic Using MD5 Checksums at http://www.vmware.com/download/md5.html. 154 VMware, Inc.
Upgrading Hosts 9 After you upgrade vCenter Server and vSphere Update Manager, upgrade VMware ESXi 5.x hosts to ESXi 6.0. You can upgrade ESXi 5.0.x, ESXi 5.1.x, and ESXi 5.5.x hosts directly to ESXi 6.0. To upgrade hosts, you can use the tools and methods that are described in “Upgrade Options for ESXi 6.0,” on page 140. Caution If you upgrade hosts managed by vCenter Server, you must upgrade to vCenter Server before you upgrade ESXi.
vSphere Upgrade You can use Distributed Resource Scheduler (DRS) to prevent virtual machine downtime during the upgrade process. Update Manager monitors hosts and virtual machines for compliance against your defined upgrade baselines. Noncompliance appears in detailed reports and in the dashboard view. Update Manager supports mass remediation. The following vSphere components are upgraded by Update Manager.
Chapter 9 Upgrading Hosts If FT is turned on for any of the virtual machines on hosts within a cluster, temporarily turn off FT before performing any Update Manager operations on the cluster. If FT is turned on for any of the virtual machines on a host, Update Manager does not remediate that host. Remediate all hosts in a cluster with the same updates, so that FT can be reenabled after the remediation.
vSphere Upgrade 3 Enable Remediation of PXE Booted ESXi Hosts on page 161 You can configure Update Manager to let other software initiate remediation of PXE booted ESXi hosts. The remediation installs patches and software modules on the hosts, but typically the host updates are lost after a reboot. 4 Import Host Upgrade Images and Create Host Upgrade Baselines on page 161 You can create upgrade baselines for ESXi hosts with ESXi 6.0 images that you import to the Update Manager repository.
Chapter 9 Upgrading Hosts Procedure 1 Use the vSphere Client or the vSphere Web Client to connect to a vCenter Server system with which Update Manager is registered. 2 Depending on the client you use to connect to vCenter Server perform the following steps. 3 4 Client Steps vSphere Web Client 1 vSphere Client 1 On the Settings tab, under Manage, click Host/Cluster Settings. Click Edit. On the Configuration tab, under Settings, click ESXi Host/Cluster Settings.
vSphere Upgrade Prerequisites Required privileges: VMware vSphere Update Manager.Configure Procedure 1 Use the vSphere Client or the vSphere Web Client to connect to a vCenter Server system with which Update Manager is registered. 2 Depending on the client you use to connect to vCenter Server perform the following steps. Client Steps vSphere Web Client 1 2 vSphere Client 3 4 160 1 On the Manage tab, under Settings, click Host/Cluster Settings. Click Edit.
Chapter 9 Upgrading Hosts These settings become the default failure response settings. You can specify different settings when you configure individual remediation tasks. Enable Remediation of PXE Booted ESXi Hosts You can configure Update Manager to let other software initiate remediation of PXE booted ESXi hosts. The remediation installs patches and software modules on the hosts, but typically the host updates are lost after a reboot.
vSphere Upgrade Procedure 1 On the ESXi Images tab click Import ESXi Image on the upper-right side. 2 On the Select ESXi Image page of the Import ESXi Image wizard, browse to and select the ESXi image that you want to upload. 3 Click Next. Caution Do not close the import wizard. Closing the import wizard stops the upload process. 4 (Optional) In the Security Warning window, select an option to handle the certificate warning.
Chapter 9 Upgrading Hosts 3 Depending on the client you use to connect to vCenter Server perform the following steps. Client Steps vSphere Web Client 1 2 vSphere Client 1 2 3 On the Host Baselines tab under Manage, click the Create above the Baseline Groups pane. Enter a unique name for the baseline group and click Next. On the Baselines and Groups tab, click the Create above the Baseline Groups pane.
vSphere Upgrade 2 Select the type of object that you want to attach the baseline to. For example, Hosts and Clusters or VMs and Templates. 3 Select the object in the inventory, and click the Update Manager tab. If your vCenter Server system is connected to other vCenter Server systems by a common vCenter Single Sign-On domain, the Update Manager tab is available only for the vCenter Server system with which an Update Manager instance is registered. 4 Click Attach in the upper-right corner.
Chapter 9 Upgrading Hosts Procedure 1 Use the vSphere Client or the vSphere Web Client to connect to a vCenter Server system with which Update Manager is registered. 2 Select the type of object for which you want to view compliance information.
vSphere Upgrade Procedure 1 Use the vSphere Client or the vSphere Web Client to connect to a vCenter Server system with which Update Manager is registered. Client Steps vSphere Web Client 1 2 vSphere Client 1 2 Select Home > Hosts and Clusters. From the inventory object navigator, right-click a datacenter, a cluster, or a host, and select Update Manager > Remediate. If you select a container object, all hosts under the selected object are remediated.
Chapter 9 Upgrading Hosts To reduce the host remediation downtime at the expense of virtual machine availability, you can choose to shut down or suspend virtual machines and virtual appliances before remediation. In a DRS cluster, if you do not power off the virtual machines, the remediation takes longer but the virtual machines are available during the entire remediation process, because they are migrated with vMotion to other hosts.
vSphere Upgrade Option Details Enable parallel remediation for the hosts in the selected clusters. Remediate hosts in clusters in a parallel manner. If the setting is not selected, Update Manager remediates the hosts in a cluster sequentially. By design only one host from a Virtual SAN cluster can be in a maintenance mode at any time. Update Manager remediates hosts that are part of a Virtual SAN cluster sequentially even if you select the option to remediate them in parallel.
Chapter 9 Upgrading Hosts Procedure 1 Use the vSphere Client or the vSphere Web Client to connect to a vCenter Server system with which Update Manager is registered. Client Steps vSphere Web Client 1 2 vSphere Client 1 2 Select Home > Hosts and Clusters. From the inventory object navigator, right-click a datacenter, a cluster, or a host, and select Update Manager > Remediate. If you select a container object, all hosts under the selected object are remediated.
vSphere Upgrade 11 On the Host Remediation Options page, from the Power state drop-down menu, you can select the change in the power state of the virtual machines and virtual appliances that are running on the hosts to be remediated. Option Description Power Off virtual machines Power off all virtual machines and virtual appliances before remediation. Suspend virtual machines Suspend all running virtual machines and virtual appliances before remediation.
Chapter 9 Upgrading Hosts Option Details Disable Fault Tolerance (FT) if it is enabled for the VMs on the selected hosts. If FT is turned on for any of the virtual machines on a host, Update Manager does not remediate that host. For FT to be enabled, the hosts on which the Primary and Secondary virtual machines run must be of the same version and must have the same patches installed. If you apply different patches to these hosts, FT cannot be re-enabled.
vSphere Upgrade Enter Boot Options to Start an Installation or Upgrade Script You can start an installation or upgrade script by typing boot options at the ESXi installer boot command line. At boot time you might need to specify options to access the kickstart file. You can enter boot options by pressing Shift+O in the boot loader. For a PXE boot installation, you can pass options through the kernelopts line of the boot.cfg file. See “About the boot.
Chapter 9 Upgrading Hosts Boot Options When you perform a scripted installation, you might need to specify options at boot time to access the kickstart file. Supported Boot Options Table 9‑1. Boot Options for ESXi Installation Boot Option Description BOOTIF=hwtype-MAC address Similar to the netdevice option, except in the PXELINUX format as described in the IPAPPEND option under SYSLINUX at the syslinux.zytor.com site.
vSphere Upgrade Table 9‑1. Boot Options for ESXi Installation (Continued) Boot Option Description netmask=subnet mask Specifies subnet mask for the network interface that downloads the installation script and the installation media. vlanid=vlanid Configure the network card to be on the specified VLAN. About Installation and Upgrade Scripts The installation/upgrade script is a text file, for example ks.cfg, that contains supported commands.
Chapter 9 Upgrading Hosts clearpart (optional) Clears any existing partitions on the disk. Requires the install command to be specified. Carefully edit the clearpart command in your existing scripts. --drives= Remove partitions on the specified drives. --alldrives Ignores the --drives= requirement and allows clearing of partitions on every drive. --ignoredrives= Removes partitions on all drives except those specified. Required unless the --drives= or --alldrives flag is specified.
vSphere Upgrade 3 USB disks (usb) You can change the order of the disks by using a comma-separated list appended to the argument. If you provide a filter list, the default settings are overridden. You can combine filters to specify a particular disk, including esx for the first disk with ESX installed on it, model and vendor information, or the name of the vmkernel device driver.
Chapter 9 Upgrading Hosts For accepted disk name formats, see “Disk Device Names,” on page 181. --firstdisk= disk-type1, Partitions the first eligible disk found. By default, the eligible disks are set to the following order: [disk-type2,...] 1 Locally attached storage (local) 2 Network storage (remote) 3 USB disks (usb) You can change the order of the disks by using a comma-separated list appended to the argument. If you provide a filter list, the default settings are overridden.
vSphere Upgrade n Finnish n French n German n Greek n Icelandic n Italian n Japanese n Latin American n Norwegian n Polish n Portuguese n Russian n Slovenian n Spanish n Swedish n Swiss French n Swiss German n Turkish n US Dvorak n Ukrainian n United Kingdom serialnum or vmserialnum (optional) Deprecated in ESXi 5.0.x. Supported in ESXi 5.1 and later. Configures licensing. If not included, ESXi installs in evaluation mode.
Chapter 9 Upgrading Hosts --gateway= --nameserver= Designates the default gateway as an IP address, in the form xxx.xxx.xxx.xxx. Used with the --bootproto=static option. Designates the primary name server as an IP address. Used with the -bootproto=static option. Omit this option if you do not intend to use DNS. The --nameserver option can accept two IP addresses. For example: -nameserver="10.126.87.104[,10.126.87.120]" --netmask= Specifies the subnet mask for the installed system, in the form 255.xxx.
vSphere Upgrade rootpw (required) Sets the root password for the system. --iscrypted Specifies that the password is encrypted. password Specifies the password value. upgrade Either the install, upgrade, or installorupgrade command is required to determine which disk to install or upgrade ESXi on. --disk= or --drive= Specifies the disk to partition. In the command --disk=diskname, the diskname can be in any of the forms shown in the following examples: n Path: --disk=/vmfs/devices/disks/mpx.
Chapter 9 Upgrading Hosts %post (optional) Runs the specified script after package installation is complete. If you specify multiple %post sections, they run in the order that they appear in the installation script. --interpreter Specifies an interpreter to use. The default is busybox. =[python|busybox] --timeout=secs Specifies a timeout for running the script. If the script is not finished when the timeout expires, the script is forcefully terminated.
vSphere Upgrade kernelopt=STRING modules=FILEPATH1 --- FILEPATH2... --- FILEPATHn # Any other line must remain unchanged. The commands in boot.cfg configure the boot loader. Table 9‑3. Commands in boot.cfg . Command Description title=STRING Sets the boot loader title to STRING. kernel=FILEPATH Sets the kernel path to FILEPATH. kernelopt=STRING Appends STRING to the kernel boot options. modules=FILEPATH1 --- FILEPATH2... --FILEPATHn Lists the modules to be loaded, separated by three hyphens (---).
Chapter 9 Upgrading Hosts 2 When the ESXi installer window appears, press Shift+O to edit boot options. 3 Type a boot option that calls the default installation or upgrade script or an installation or upgrade script file that you created. The boot option has the form ks=. 4 Press Enter. The installation, upgrade, or migration runs, using the options that you specified.
vSphere Upgrade 2 When the ESXi installer window appears, press Shift+O to edit boot options. 3 Type a boot option that calls the default installation or upgrade script or an installation or upgrade script file that you created. The boot option has the form ks=. 4 Press Enter. The installation, upgrade, or migration runs, using the options that you specified. Performing a Scripted Installation or Upgrade of ESXi by Using PXE to Boot the Installer ESXi 6.
Chapter 9 Upgrading Hosts The Auto Deploy server is automatically upgraded if you upgrade the corresponding vCenter Server system to version 6. Starting with version 6, the Auto Deploy server is always on the same management node as the vCenter Server system. Reprovisioning Hosts vSphere Auto Deploy supports multiple reprovisioning options. You can perform a simple reboot or reprovision with a different image profile or a different host profile.
vSphere Upgrade n During testing, you can apply an image profile to an individual host with the Apply-EsxImageProfile cmdlet and reboot the host so the change takes effect. The Apply-EsxImageProfile cmdlet updates the association between the host and the image profile but does not install VIBs on the host. n In all other cases, use this procedure. Prerequisites n Create the image profile you want boot the host with. Use the Image Builder PowerCLI.
Chapter 9 Upgrading Hosts Prerequisites n Install vSphere PowerCLI and all prerequisite software. For information see vSphere Installation and Setup. n Export the host profile that you want to use. Procedure 1 Run the Connect-VIServer vSphere PowerCLI cmdlet to connect to the vCenter Server system that Auto Deploy is registered with. Connect-VIServer 192.XXX.X.XX The cmdlet might return a server certificate warning. In a production environment, make sure no server certificate warnings result.
vSphere Upgrade Procedure 1 Use vSphere PowerCLI to check which Auto Deploy rules are currently available. Get-DeployRule The system returns the rules and the associated items and patterns. 2 Make a change to one of the available rules. For example, you can change the image profile and the name of the rule. Copy-DeployRule -DeployRule testrule -ReplaceItem MyNewProfile You cannot edit a rule already added to a rule set. Instead, you copy the rule and replace the item or pattern you want to change.
Chapter 9 Upgrading Hosts VIBs, Image Profiles, and Software Depots Upgrading ESXi with esxcli commands requires an understanding of VIBs, image profiles, and software depots. The following technical terms are used throughout the vSphere documentation set in discussions of installation and upgrade tasks. VIB A VIB is an ESXi software package. VMware and its partners package solutions, drivers, CIM providers, and applications that extend the ESXi platform as VIBs. VIBs are available in software depots.
vSphere Upgrade VMware supports the following acceptance levels. VMwareCertified The VMwareCertified acceptance level has the most stringent requirements. VIBs with this level go through thorough testing fully equivalent to VMware in-house Quality Assurance testing for the same technology. Today, only I/O Vendor Program (IOVP) program drivers are published at this level. VMware takes support calls for VIBs with this acceptance level.
Chapter 9 Upgrading Hosts Procedure 1 2 Retrieve the acceptance level for the VIB or image profile.
vSphere Upgrade Procedure 1 Check whether the VIB or image profile that you want to install requires the host to be placed in maintenance mode or to be rebooted after the installation or update. Run one of the following commands.
Chapter 9 Upgrading Hosts Procedure 1 Check whether the host is in maintenance mode. vicfg-hostops --server=server_name --operation info 2 Power off each virtual machines running on the ESXi host.
vSphere Upgrade 2 Find out which VIBs are available in the depot. Option Description from a depot accessible by URL esxcli --server=server_name software sources vib list -depot=http://web_server/depot_name from a local depot ZIP file esxcli --server=server_name software sources vib list -depot=absolute_path_to_depot_zip_file You can specify a proxy server by using the --proxy argument. 3 Update the existing VIBs to include the VIBs in the depot or install new VIBs.
Chapter 9 Upgrading Hosts When you specify a target server by using --server=server_name, the server prompts you for a user name and password. Other connection options, such as a configuration file or session file, are supported. For a list of connection options, see Getting Started with vSphere Command-Line Interfaces, or run esxcli --help at the vCLI command prompt.
vSphere Upgrade Option Description Update the image profile from a ZIP file on the target server, copied into a datastore esxcli --server=server_name software profile update -depot=“[datastore_name]profile_ZIP_file" -profile=profile_name Update the image profile from a ZIP file copied locally and applied on the target server esxcli --server=server_name software profile update -depot=/root_dir/path_to_profile_ZIP_file/profile_ZIP_file --profile=profile_name Install all new VIBs in a specified profile
Chapter 9 Upgrading Hosts n If the update requires a reboot, and if the host belongs to a VMware HA cluster, remove the host from the cluster or disable HA on the cluster. Procedure u Install the ZIP file. esxcli --server=server_name software vib update --depot=/path_to_vib_ZIP/ZIP_file_name.zip Remove VIBs from a Host You can uninstall third-party VIBs or VMware VIBs from your ESXi host. VMware partners prepare third-party VIBs to provide management agents or asynchronously released drivers.
vSphere Upgrade n vendor:name n vendor:name:version For example, the command to remove a VIB specified by vendor, name and version would take this form: esxcli –-server myEsxiHost software vib remove --vibname=PatchVendor:patch42:version3 Note The remove command supports several more options. See the vSphere Command-Line Interface Reference.
Chapter 9 Upgrading Hosts Display the Installed VIBs and Profiles That Will Be Active After the Next Host Reboot You can use the --rebooting-image option to list the VIBs and profiles that are installed on the host and will be active after the next host reboot. When you specify a target server by using --server=server_name, the server prompts you for a user name and password. Other connection options, such as a configuration file or session file, are supported.
vSphere Upgrade Upgrade Hosts Interactively To upgrade ESXi 5.x hosts to ESXi 6.0, you can boot the ESXi installer from a CD, DVD, or USB flash drive. Before upgrading, consider disconnecting the network storage. This action decreases the time it takes the installer to search for available disk drives. When you disconnect network storage, any files on the disconnected disks are unavailable at installation. Do not disconnect a LUN that contains an existing ESXi installation.
After You Upgrade ESXi Hosts 10 To complete a host upgrade, you ensure that the host is reconnected to its managing vCenter Server system and reconfigured if necessary. You also check that the host is licensed correctly. After you upgrade an ESXi host, take the following actions: n View the upgrade logs. You can use the vSphere Web Client to export the log files.
vSphere Upgrade The evaluation period is 60 days and begins when you turn on the ESXi host. At any time during the 60-day evaluation period, you can convert from licensed mode to evaluation mode. The time available in the evaluation period is decreased by the time already used. For example, suppose that you use an ESXi host in evaluation mode for 20 days and then assign a vSphere Standard Edition license key to the host.
Chapter 10 After You Upgrade ESXi Hosts Table 10‑1.
vSphere Upgrade 6 7 (Optional) To overwrite the default log size and log rotation for any of the logs. a Click the name of the log you that want to customize. b Click the Edit icon and enter the number of rotations and log size you want. Click OK. Changes to the syslog options take effect immediately. 204 VMware, Inc.
Upgrading Virtual Machines and VMware Tools 11 After you upgrade ESXi hosts, you can upgrade the virtual machines on the host to take advantage of new features. VMware offers the following tools for upgrading virtual machines: vSphere Web Client Requires you to perform the virtual machine upgrade one step at a time, but does not require vSphere Update Manager. See the information about upgrading virtual machines in the vSphere Virtual Machine Administration documentation.
vSphere Upgrade 206 VMware, Inc.
Troubleshooting a vSphere Upgrade 12 The installation and upgrade software enables you to identify problems on the host machine that can cause an installation, upgrade, or migration to fail. For interactive installations, upgrades, and migrations, the errors or warnings are displayed on the final panel of the installer, where you are asked to confirm or cancel the installation or upgrade. For scripted installations, upgrades, or migrations, the errors or warnings are written to the installation log file.
vSphere Upgrade Collect Installation Logs by Using the Installation Wizard You can use the Setup Interrupted page of the installation wizard to browse to the generated .zip file of the vCenter Server for Windows installation log files. If the installation fails, the Setup Interrupted page appears with the log collection check boxes selected by default. Procedure 1 Leave the check boxes selected and click Finish. The installation files are collected in a .
Chapter 12 Troubleshooting a vSphere Upgrade 5 Export the generated support bundle to the user@x.x.x.x:/tmp folder. scp /var/tmp/vc-etco-vm-vlan11-dhcp-63-151.eng.vmware.com-2014-02-28--21.11.tgz user@x.x.x.x:/tmp 6 Determine which firstboot script failed. cat /var/log/firstboot/firstbootStatus.json What to do next To identify potential causes of the failure, examine the log file of the firstboot script that failed.
vSphere Upgrade Errors and Warnings Returned by the Installation and Upgrade Precheck Script The installation and upgrade precheck script runs tests to identify problems on the host machine that can cause an installation, upgrade, or migration to fail. For interactive installations, upgrades, and migrations, the errors or warnings are displayed on the final panel of the installer, where you are asked to confirm or cancel the installation or upgrade.
Chapter 12 Troubleshooting a vSphere Upgrade Table 12‑1. Error and Warning Codes That Are Returned by the Installation and Upgrade Precheck Script (Continued) Error or Warning Description PARTITION_LAYOUT You can upgrade or migrate software only if at most one VMFS partition on the disk is being upgraded and the VMFS partition must start after sector 1843200. POWERPATH This test checks for installation of EMC PowerPath software, consisting of a CIM module and a kernel module.
vSphere Upgrade Cause vCenter Inventory Service and other vCenter Server services are unregistered from vCenter Single-Sign-On 5.1 or 5.5 during the upgrade to vCenter Server 6.0. If an upgrade failure occurs after the services are unregistered, the registration information is lost. When the upgrade to vCenter Server 6.0 is resumed, the installer sees unregistered services and leaves them unregistered.
Chapter 12 Troubleshooting a vSphere Upgrade Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail vCenter Server installation with a Microsoft SQL database fails when the database is set to compatibility mode with an unsupported version. Problem The following error message appears: The DB User entered does not have the required permissions needed to install and configure vCenter Server with the selected DB.
vSphere Upgrade 214 VMware, Inc.
Index Symbols %include command 174 %post command 174 %pre command 174 Numerics 64-bit processor error 210 A about vSphere Upgrade 7 acceptance levels 189 accepteula command 174 Apply-EsxImageProfile cmdlet 185 attaching baseline 163 baseline group 163 authenticating to vCenter Server 120 Authentication Proxy, See also vSphere Authentication Proxy Auto Deploy rebooting 185 reprovisioning hosts with 185 rule set compliance 187 user input 185 See also vSphere Auto Deploy Auto Deploy rules 186 Auto Deploy,up
vSphere Upgrade download the vCenter Server installer 77 downtime, vCenter Server 68 DRAC 45 dry run for esxcli installation or upgrade 198 dryrun command 174 Dump Collector, See vSphere ESXi Dump Collector DVD, upgrading hosts from 200 E embedded architecture, overview 16 Enhanced Linked Mode, changes 13 errors:install precheck 210 errors:upgrade precheck 210 ESX upgrade, preparation 155 esxcli, upgrading hosts 188 esxcli installation or upgrade, dry run 198 esxcli reboot image 199 ESXi certificates 27 d
Index installing ESXi with software FCoE 153 installing the vSphere Client 116 installorupgrade command 174 insufficient CPU core error 210 insufficient host disk space error 210 insufficient memory error 210 Inventory Service 12 IP addresses 142 ISO image with custom installation scriptwith custom installation script 145 with custom upgrade script 145 J joined instances of vCenter Server Appliance with an embedded Platform Services Controller, repointing to an external Platform Services Controller 126 jo
vSphere Upgrade PowerPath components error 210 pre-upgrade checker 35 pre-upgrade database preparations MSSQL Server 56 Oracle 54 PostgreSQL 59 pre-upgrade tasks, vCenter Server 66 precheck script error 210 predefined software, vCenter Server Appliance 38 prepare ESXi hosts for vCenter Server upgrade 64 PXE, configuration files 149 PXE boot ESXi installer using PXELINUX, setup procedure 149, 151, 152 PXE booted ESXi hosts, enable remediation 161 PXELINUX, boot ESXi installer using 149, 151, 152 R reboot i
Index T TCP ports 51 Test-DeployRuleSetCompliance cmdlet 187 TFTP 146 tftp-hpa 146 tftpd32 146 third-party custom VIBs 141 thumbprint certificates 65 time synchronization requirements 34 tiny environment, required storage space 38 Tomcat 117 transitional environment during upgrade 20 troubleshooting, upgrade 207 troubleshooting:installation 207 troubleshooting:upgrade logs 207 trusted boot mode (tboot) error 210 U UDP ports 51 unsupported device error 210 Update Manager, upgrading 135 updated information
vSphere Upgrade vCenter Inventory Service,restoring after upgrade failure 211 vCenter Server component services, changes 13 vCenter Server database, changes 13 vCenter Server databases preparing 54 requirements 37 vCenter Server upgrade, prerequisites 53 vCenter Server Appliance,Component Manager upgrade error 212 vCenter Server 5.0:upgrade for Windows 83 vCenter Server 5.1,upgrade for Windows 85 vCenter Server 5.5,upgrade for Windows 87 vCenter Server Appliance .
Index VMFS partition layout error 210 VMware ESXi 11 VMware vCenter Server - tc Server settings in vCenter Server 117 VMware Component Manager upgrade error, regenerate certificates 212 VMware Installation Bundles 141 VMware Syslog Service 12 VMware vCenter Server Appliance, software requirements 36 vpxd.certmgmt.mode 65 vSphere Client hardware requirements for in the getting started workflow 50 installing 116 requirements 50, 51 vSphere 6.0,changes from vSphere 5.
vSphere Upgrade 222 VMware, Inc.
