vSphere Upgrade Update 2 vSphere 5.5 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–2014 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 1 Overview of the Upgrade Process 9 How vSphere 5.x Differs from vSphere 4.
vSphere Upgrade DNS Load Balancing Solutions and vCenter Server Datastore Naming 56 About the vCenter Host Agent Pre-Upgrade Checker 57 Downtime During the vCenter Server Upgrade 58 Download the vCenter Server Installer 59 Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail 59 4 Upgrading vCenter Server 61 vCenter Server Upgrade and Sign-On Process for Environments that Do Not Include vCenter Single Sign-On 62 vCenter Server Upgrade and Sign-
Contents 7 Upgrading and Migrating Your Hosts 143 Preparing to Upgrade Hosts 143 Performing the Upgrade or Migration 166 After You Upgrade or Migrate Hosts 213 8 Upgrading Virtual Machines and VMware Tools 215 9 Example Upgrade Scenarios 217 Moving Virtual Machines Using vMotion During an Upgrade 217 Moving Powered Off or Suspended Virtual Machines During an Upgrade with vCenter Server 218 Migrating ESX 4.x or ESXi 4.x Hosts to ESXi 5.
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.
Overview of the Upgrade Process 1 Upgrading is a multistage process in which procedures must be performed in a particular order. Follow the process outlined in this high-level overview to ensure a smooth upgrade with a minimum of system downtime. IMPORTANT Make sure that you understand the entire upgrade process before you attempt to upgrade. If you do not follow the safeguards, you might lose data and access to your servers. Without planning, you might incur more downtime than is necessary.
vSphere Upgrade 3 Make sure your system meets vSphere hardware and software requirements. See Chapter 2, “System Requirements,” on page 13. 4 Upgrade vCenter Single Sign-On, vCenter Inventory Service, vCenter Server, and the vSphere Web Client. IMPORTANT If you use vCenter Server Heartbeat in your vSphere deployment, use the vSphere Server Heartbeatinstallation and upgrade documentation to upgrade vCenter Server and related components. See Chapter 4, “Upgrading vCenter Server,” on page 61.
Chapter 1 Overview of the Upgrade Process How vSphere 5.x Differs from vSphere 4.x vSphere 5.x is a major upgrade from vSphere 4.x. The following changes from vSphere 4.x affect vSphere installation and setup. For a complete list of new features in vSphere 5.x, see the release notes for version 5.x releases. Service Console is removed ESXi does not include a Service Console.
vSphere Upgrade Newly installed vSphere 5.x hosts use VMFS5, an updated version of the VMware File System for vSphere 5.x. Unlike earlier versions, ESXi 5.x does not create VMFS partitions in second and successive disks. Upgraded systems do not use GUID Partition Tables (GPT), but retain the older MSDOS-based partition label. VMware vCenter Server Appliance As an alternative to installing vCenter Server on a Windows machine, vSphere 5.x provides the VMware vCenter Server Appliance.
System Requirements 2 Systems running vCenter Server and ESXi instances must meet specific hardware and operating system requirements. If you are using Auto Deploy to provision ESXi hosts, see also the information about preparing for VMware Auto Deploy in the vSphere Installation and Setup documentation.
vSphere Upgrade n ESXi supports a broad range of x64 multicore processors. For a complete list of supported processors, see the VMware compatibility guide at http://www.vmware.com/resources/compatibility. n ESXi requires a minimum of 4GB of physical RAM. Provide at least 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments.
Chapter 2 System Requirements n USB devices. Supported for installing ESXi. n Software Fibre Channel over Ethernet (FCoE). See “Installing and Booting ESXi with Software FCoE,” on page 165. ESXi Booting Requirements vSphere 5.5 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.
vSphere Upgrade Table 2‑1. Recommendations for Enhanced Performance 16 System Element Recommendation RAM ESXi hosts require more RAM than typical servers. Provide at least 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments. An ESXi host must have sufficient RAM to run concurrent virtual machines. The following examples are provided to help you calculate the RAM required by the virtual machines running on the ESXi host.
Chapter 2 System Requirements Hardware Requirements for vCenter Server, the vSphere Web Client , vCenter Inventory Service, and vCenter Single Sign-On vCenter Server host machines must meet hardware requirements.
vSphere Upgrade Table 2‑3. Minimum Hardware Requirements for vCenter Single Sign-On, Running on a Separate Host Machine from vCenter Server vCenter Single Sign-On Hardware Requirement Processor Intel or AMD x64 processor with two or more logical cores, each with a speed of 2GHz. Memory 3GB. If vCenter Single Sign-On runs on the same host machine as vCenter Server, see Table 2-2 or Table 2-5. Disk storage 2GB. Network speed 1Gbps Table 2‑4.
Chapter 2 System Requirements Table 2‑5. Minimum Hardware Requirements for vCenter Server (Continued) vCenter Server Hardware Requirement Memory The amount of memory needed depends on your vCenter Server configuration. n If vCenter Server is installed on a different host machine than vCenter Single Sign-On and vCenter Inventory Service, 4GB of RAM are required.
vSphere Upgrade vSphere Web Client Hardware Requirements The vSphere Web Client has two components: A Java server and an Adobe Flex client application running in a browser. Table 2‑6.
Chapter 2 System Requirements VMware vCenter Server Appliance Hardware Requirements and Recommendations Table 2‑8. Hardware Requirements for VMware vCenter Server Appliance VMware vCenter Server Appliance Hardware Requirement Disk storage on the host machine For most deployments, the vCenter Server Appliance requires at least 70GB of disk space, and is limited to a maximum size of 125GB. The required disk space depends on the size of your vCenter Server inventory.
vSphere Upgrade vCenter Server Software Requirements Make sure that your operating system supports vCenter Server. vCenter Server requires a 64-bit operating system, and the 64-bit system DSN is required for vCenter Server to connect to its database. For a list of supported operating systems, see the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility.
Chapter 2 System Requirements Later versions of these browsers are likely to work, but have not been tested. The vSphere Web Client requires the Adobe Flash Player version 11.5.0 or later to be installed with the appropriate plug-in for your browser. Providing Sufficient Space for System Logging ESXi 5.x uses a new log infrastructure.
vSphere Upgrade Table 2‑12. Ports Required for Communication Between Components 24 Port Description 22 SSH Server (vSphere Client) 53 DNS Client 80 vCenter Server requires port 80 for direct HTTP connections. Port 80 redirects requests to HTTPS port 443. This redirection is useful if you accidentally use http://server instead of https://server.
Chapter 2 System Requirements Table 2‑12. Ports Required for Communication Between Components (Continued) Port Description 2049 Transactions from NFS storage devices This port is used on the VMkernel interface.
vSphere Upgrade To have the vCenter Server system use a different port to receive vSphere Web Client data, see the vCenter Server and Host Management documentation. For a discussion of firewall configuration, see the vSphere Security documentation. Required Ports for the vCenter Server Appliance The VMware vCenter Server system must be able to send data to every managed host and receive data from every vSphere Web Client.
Chapter 2 System Requirements Conflict Between vCenter Server and IIS for Port 80 vCenter Server and Microsoft Internet Information Service (IIS) both use port 80 as the default port for direct HTTP connections. This conflict can cause vCenter Server to fail to restart after the installation of vSphere Authentication Proxy. Problem vCenter Server fails to restart after the installation of vSphere Authentication Proxy is complete.
vSphere Upgrade Supported Remote Management Server Models and Minimum Firmware Versions You can use remote management applications to install ESXi or for remote management of hosts. Table 2‑14. Supported Remote Management Server Models and Firmware Versions Remote Controller Make and Model Firmware Version Java Dell DRAC 6 1.54 (Build 15), 1.70 (Build 21) 1.6.0_24 Dell DRAC 5 1.0, 1.45, 1.51 1.6.0_20,1.6.0_203 Dell DRAC 4 1.75 1.6.0_23 HP ILO 1.81, 1.92 1.6.0_22, 1.6.0_23 HP ILO 2 1.8, 1.
Chapter 2 System Requirements Supported Operating Systems and Database Formats Update Manager works with specific databases and operating systems. The Update Manager server requires a 64-bit Windows system. NOTE Make sure the system on which you are installing the Update Manager server is not an Active Directory domain controller. The Update Manager plug-in requires the vSphere Client, and works with the same operating systems as the vSphere Client.
vSphere Upgrade 30 VMware, Inc.
Preparing for the Upgrade to vCenter Server 3 Before you upgrade to vCenter Server, make sure your system is properly prepared. To ensure that your system is prepared for the upgrade, read all the subtopics in this section.
vSphere Upgrade n “Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail,” on page 59 About the vCenter Server Upgrade VMware supports in-place upgrades on 64-bit systems from vCenter Server 4.x, vCenter Server 5.0.x, and vCenter Server 5.1.x to vCenter Server 5.5. Unlike versions before vCenter Server 5.1, vCenter Server 5.5 does not support directly migrating an existing, 5.0.
Chapter 3 Preparing for the Upgrade to vCenter Server If you upgrade vCenter Single Sign-On and vCenter Server, vCenter Single Sign-On recognizes existing local operating system users. In addition, the user administrator@vsphere.local can log in to vCenter Single SignOn and vCenter Server as an administrator user. If your previous installation included an Active Directory domain as an identity source, that identity source is still available after the upgrade.
vSphere Upgrade Table 3‑1.
Chapter 3 Preparing for the Upgrade to vCenter Server See “vCenter Single Sign-On and High Availability,” on page 35 for high availability options. Multiple Single Sign-On instances in different locations This mode is designed for vCenter Server deployments with multiple physical locations. Multisite deployment is required when a single administrator needs to administer vCenter Server instances that are deployed on geographically dispersed sites in Linked Mode.
vSphere Upgrade Options for Protecting vCenter Single Sign-On and vCenter Server The following options vary in the level of protection afforded, and in the recovery time required. Backup and restore Backup and restore should be an essential part of any availability solution, providing a granular recovery method, by tape, disk, or snapshot. However, the recovery time is typically measured in hours or days and requires manual intervention. Any backup solution must be independent of vCenter Server.
Chapter 3 Preparing for the Upgrade to vCenter Server vCenter Server Heartbeat is the only solution for availability if vCenter Single Sign-On is on a physical server. With either vSphere HA or vCenter Server Heartbeat, this deployment provides complete protection of the centralized vCenter Single Sign-On environment.
vSphere Upgrade In vSphere 5.1.x and 5.5, when you install vCenter Server, you must provide the default (initial) vCenter Server administrator user or group. For deployments where vCenter Server and vCenter Single Sign-On are on the same host machine, you can designate the local operating system group Administrators as vCenter Server administrative users. This option is the default. This behavior is unchanged from vCenter Server 5.0.
Chapter 3 Preparing for the Upgrade to vCenter Server Identity Sources for vCenter Server with vCenter Single Sign-On Identity sources allow you to attach one or more domains to vCenter Single Sign-On. A domain is a repository for users and groups that the vCenter Single Sign-On server can use for user authentication. An identity source is a collection of user and group data.
vSphere Upgrade n n Users who are in a domain that has been added to vCenter Single Sign-On as an identity source but is not the default domain can log in to vCenter Server but must specify the domain in one of the following ways. n Including a domain name prefix, for example, MYDOMAIN\user1 n Including the domain, for example, user1@mydomain.com Users who are in a domain that is not a vCenter Single Sign-On identity source cannot log in to vCenter Server.
Chapter 3 Preparing for the Upgrade to vCenter Server Required Information for Installing or Upgrading vCenter Single SignOn, Inventory Service, vCenter Server, and the vSphere Web Client Prepare for the vCenter Server installation by recording the values that vCenter Server and related components require. The vCenter Single Sign-On, vSphere Web Client, vCenter Inventory Service, and vCenter Server installation wizards prompt you for the installation or upgrade information.
vSphere Upgrade Table 3‑3. Information Required for vCenter Single Sign-On Installation. (Continued) Required Information Default Your Entry Password for the vCenter Single Sign-On administrator account in the default domain. You must use the same vCenter Single Sign-On password name when you install or upgrade vCenter Single Sign-On, Inventory Service, vCenter Server, and the vSphere Web Client. IMPORTANT Be sure to record the password.
Chapter 3 Preparing for the Upgrade to vCenter Server Table 3‑4. Information Required for the vSphere Web Client Installation (Continued) Required Information Default Your Entry Password for the vCenter Single Sign-On administrator account in the default domain. You must use the same vCenter Single Sign-On password when you install or upgrade vCenter Single Sign-On, Inventory Service, vCenter Server, and the vSphere Web Client. IMPORTANT Be sure to record the password.
vSphere Upgrade Table 3‑5. Information Required for vCenter Inventory Service Installation or Upgrade (Continued) Required Information Default User name for the vCenter Single Sign-On administrator user account. You must use the same vCenter Single Sign-On user name and password name when you install vCenter Single Sign-On, and install or upgrade Inventory Service, vCenter Server, and the vSphere Web Client. administrator Your Entry Lookup Service URL.
Chapter 3 Preparing for the Upgrade to vCenter Server Table 3‑6. Information Required for vCenter Server Installation or Upgrade (Continued) Required Information Default Your Entry Fully qualified domain name of Directory Services for the vCenter Server group. The FQDN of a remote instance of vCenter Server. Required if this instance of vCenter Server is joining a group. The local and remote instances will be members of a Linked Mode group.
vSphere Upgrade Table 3‑6. Information Required for vCenter Server Installation or Upgrade (Continued) Required Information Default Your Entry Inventory size. The inventory size of your vCenter Server deployment: n Small (less than 100 hosts or 1000 virtual machines. n Medium (100-400 hosts or 1000-4000 virtual machines. n Large (more than 400 hosts or 4000 virtual machines.
Chapter 3 Preparing for the Upgrade to vCenter Server 2 3 n Read the VMware vSphere Release Notes for known installation issues. n If your vSphere installation is in a VMware View environment, see “Upgrading vSphere Components Separately in a Horizon View Environment,” on page 220. Prepare your system for the upgrade. n Make sure your system meets requirements for the vCenter Server version that you are upgrading to.
vSphere Upgrade Prerequisites for the vCenter Server Upgrade Before you begin the upgrade to vCenter Server, make sure you prepare the vCenter Server system and the database. Prerequisites for Understanding and Preparing for the Upgrade Process n vCenter Server 5.5 requires vCenter Single Sign-On and Inventory Service. Install or update these components in this order: vCenter Single Sign-On, the vSphere Web Client, Inventory Service, and vCenter Server.
Chapter 3 Preparing for the Upgrade to vCenter Server n The installation path of the previous version of vCenter Server must be compatible with the installation requirements for Microsoft Active Directory Application Mode (ADAM/AD LDS). The installation path cannot contain any of the following characters: non-ASCII characters, commas (,), periods (.), exclamation points (!), pound signs (#), at signs (@), or percentage signs (%).
vSphere Upgrade Prerequisites for All vCenter Server Databases n If your database server is not supported by vCenter Server, perform a database upgrade to a supported version or import your database into a supported version. See “Supported Database Upgrades,” on page 53. n Perform a complete backup of the vCenter Server database before you begin the upgrade. If you choose to remove the DBO role, you can migrate all objects in the DBO schema to a custom schema.
Chapter 3 Preparing for the Upgrade to vCenter Server Prerequisites for Oracle Databases n To use a newly supported Oracle database, such as Oracle 11g, you do not need to perform a clean installation of vCenter Server if your existing database is also Oracle. For example, you can upgrade your existing Oracle 9i database to Oracle 11g and then upgrade vCenter Server 4.x to vCenter Server 5.5. n The JDBC driver file must be included in the CLASSPATH variable.
vSphere Upgrade Table 3‑7. Configuration Notes for Databases Supported with vCenter Server Database Type Configuration Notes Microsoft SQL Server 2008 R2 Express Bundled database that you can use for small deployments of up to 5 hosts and 50 virtual machines. SQL Server Collation Model: SQL_Latin1_General_CP1_CI_AS. ODBC System DSN minimum version: SQL Native Client 10.0 (version 2009.100.4000.00), which you can obtain as a free download from the microsoft.com Download Center.
Chapter 3 Preparing for the Upgrade to vCenter Server Supported Database Upgrades When you upgrade to vCenter Server 5.5, make sure that the upgraded version supports your database. For a list of the specific database versions supported for the version of vCenter Server that you are upgrading to, see the VMware Product Interoperability Matrix at http://www.vmware.com/resources/compatibility/sim/interop_matrix.php. NOTE The version 5.5 vCenter Server Appliance uses a PostgreSQL for the embedded database.
vSphere Upgrade Synchronize ESX and ESXi Clocks with a Network Time Server Before you install vCenter Single Sign-On, the vSphere Web Client, or the vCenter Server appliance, make sure all machines on the vSphere network have their clocks synchronized. Procedure 1 From the vSphere Web Client, connect to the vCenter Server. 2 Select the host in the inventory. 3 Select the Manage tab. 4 Select Settings. 5 In the System section, select Time Configuration. 6 Click Edit and set up the NTP server.
Chapter 3 Preparing for the Upgrade to vCenter Server JDBC URL Formats for the vCenter Server Database The vCenter Server installer generates and validates the JDBC URL for the vCenter Server database. If the installer fails to connect to the database using the generated JDBC URL, the installer will prompt you to specify the JDBC URL. JDBC URL Note for All Databases NOTE The domain name cannot contain the exclamation point character (!). Java interprets the exclamation point as a jar file separator.
vSphere Upgrade n This format requires host name and address, port (default 1521) and SID (for example, "ORCL"): jdbc:oracle:thin:@host:port:SID n This format is for a fully configured Oracle client with Oracle Net, which is useful for non-TCP configuration or Oracle RAC (real application clusters): jdbc:oracle:thin:@tnsname n The following example is for an Oracle RAC with a thin driver, without the full Oracle client installed: jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=rac1-vip)(PO
Chapter 3 Preparing for the Upgrade to vCenter Server The upgrade to vCenter Server 5.x might also fail from a lack of sufficient memory if you use a DNS load balancing solution with shared datastores. In a large vCenter Server database, the conversion of datastore paths to the new format can require a large amount of memory. See the VMware Knowledge Base article at http://kb.vmware.com/kb/2015055.
vSphere Upgrade Procedure 1 In the software installer directory, double-click the autorun.exe file to start the installer. 2 Select Host Agent Pre-Upgrade Checker and click Install. 3 Select the DSN for the vCenter Server system you are upgrading from and select the login credentials that are appropriate for that DSN. If you are not sure which credential type to select, check which authentication type is configured for the DSN (Control Panel > Administrative Tools > ODBC Data Sources > System DSN).
Chapter 3 Preparing for the Upgrade to vCenter Server Download the vCenter Server Installer Download the installer for vCenter Server, the vSphere Web Client, and associated vCenter components and support tools. Prerequisites Create a My VMware account at https://my.vmware.com/web/vmware/. Procedure 1 Download the vCenter Server installer from the VMware Web site at https://my.vmware.com/web/vmware/downloads. vCenter Server is part of VMware vSphere, listed under Datacenter & Cloud Infrastructure.
vSphere Upgrade 60 VMware, Inc.
Upgrading vCenter Server 4 The vCenter Server upgrade includes a database schema upgrade and an upgrade of the vCenter Server software. vSphere 5.1 introduced vCenter Single Sign-On as part of the vCenter Server management infrastructure. This change affects vCenter Server installation, upgrading, and operation. See “How vCenter Single Sign-On Affects vCenter Server Upgrades,” on page 32.
vSphere Upgrade vCenter Server Upgrade and Sign-On Process for Environments that Do Not Include vCenter Single Sign-On The upgrade process differs based on several factors. Understand the complete upgrade, vCenter Single Sign-On setup, and permission assignment process before you start. This topic explains how to perform the upgrade and user management if you upgrade from vSphere 5.0 or earlier, which does not include vCenter Single Sign-On. If you are upgrading from vSphere 5.
Chapter 4 Upgrading vCenter Server n 2 3 If your current environment is not distributed over several machines or several locations, you can distribute the upgrade over multiple machines with a custom install (step 4) or continue placing all vCenter components on the same machine (step 2). If all vCenter Server components are on the same host machine, you can upgrade with Simple Install. See “Use Simple Install to Upgrade vCenter Server and Required Components,” on page 65.
vSphere Upgrade vCenter Server Upgrade and Sign-On Process for Environments with vCenter Single Sign-On The upgrade process differs based on several factors. Understand the complete upgrade, vCenter Single Sign-On setup, and permission assignment process before you start. This topic explains how to perform the upgrade and user management if you upgrade from vSphere 5.1.x, which includes an earlier version of vCenter Single Sign-On. If you are upgrading from vSphere 5.1.
Chapter 4 Upgrading vCenter Server With vSphere 5.5, multiple vCenter Server systems can use a single vCenter Single Sign-On system. 2 n If your current environment uses vCenter Single Sign-On multisite, resynchronize your environment. See Knowledge Base articles http://kb.vmware.com/kb/2042849 and http://kb.vmware.com/kb/2038677, and start a Custom Install upgrade. See “Use Custom Install to Upgrade Version 5.0.x and Earlier vCenter Server and Required Components,” on page 69.
vSphere Upgrade Alternatively, you can upgrade vCenter Server components separately, for installations in which the location and configuration of the components is customized. See “Use Custom Install to Upgrade a Basic vCenter Single Sign-On Deployment of Version 5.1.x vCenter Server and Required Components,” on page 78, “Use Custom Install to Upgrade vCenter Server from a Version 5.1.
Chapter 4 Upgrading vCenter Server You can use Simple Install for the first vCenter Single Sign-On and vCenter Server in a deployment with multiple vCenter Servers. Succeeding instances of vCenter Single Sign-On and vCenter Server in the same deployment must be installed by using Custom Install. For more information about vCenter Single Sign-On, see “How vCenter Single Sign-On Affects vCenter Server Upgrades,” on page 32 and the vSphere Security documentation. NOTE vCenter Server 5.
vSphere Upgrade No input is required for a Simple Install upgrade of the vSphere Web Client. NOTE After each component is installed or upgraded, the installer might take a few minutes to start the installer for the next component. Upgrade vCenter Inventory Service as Part of vCenter Server Simple Install You can Install or upgrade vCenter Single Sign-On, the vSphere Web Client, vCenter Inventory Service, and vCenter Server together on a single host machine using the vCenter Server Simple Install option.
Chapter 4 Upgrading vCenter Server 5 Select how to upgrade vCenter Agent. Option Description Automatic To automatically upgrade vCenter Agent on all the hosts in the vCenter Server inventory. Manual If one of the following applies: n You need to control the timing of vCenter Agent upgrades on specific hosts. n vCenter Agent is installed on each host in the inventory to enable vCenter Server to manage the host. vCenter Agent must be upgraded when vCenter Server is upgraded.
vSphere Upgrade For most basic vCenter Single Sign-On deployments, if all components are on the same host machine, you can upgrade vCenter Single Sign-On, the vSphere Web Client, Inventory Service, and vCenter Server together on a single host machine using the vCenter Server Simple Install option. See “Use Simple Install to Upgrade vCenter Server and Required Components,” on page 65. NOTE vCenter Server 5.
Chapter 4 Upgrading vCenter Server For more information about vCenter Single Sign-On, see “How vCenter Single Sign-On Affects vCenter Server Upgrades,” on page 32and the vSphere Security documentation. 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.
vSphere Upgrade After vCenter Single Sign-On is installed or upgraded, the following default identity sources and users are available: localos All local operating system users. These users can be granted permissions to vCenter Server. If you are upgrading, those users who already have permissions keep those permissions. vsphere.local Contains all users who have administrator access to the vCenter Single SignOn server. Initially, only the user administrator is defined.
Chapter 4 Upgrading vCenter Server 7 Select an existing site as the partner or enter a new site. 8 Click Install. (Optional) Install an Additional vCenter Single Sign-On Node at a New Site Create an additional vCenter Single Sign-On node for a multisite vCenter Single Sign-On installation. An additional node can be useful if you need multiple vCenter Server instances in different locations. Authentication information is replicated between vCenter single Sign-On instances that are related.
vSphere Upgrade Install or Upgrade the vSphere Web Client The vSphere Web Client lets you connect to a vCenter Server system to manage your vSphere deployment through a browser. If an earlier version of the vSphere Web Client is installed, this procedure upgrades the vSphere Web Client. 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.
Chapter 4 Upgrading vCenter Server 7 Click Install. 8 Start the vSphere Web Client by taking one of the following actions. n If you are starting the vSphere Web Client for the first time, open a supported browser, and go to https://vSphere_Web_Client_host_name_or_IP:9443/vsphere-client. n In subsequent sessions, you can start the vSphere Web Client from the Windows Start menu, by selecting Programs > VMware > VMware vSphere Web Client > vSphere Web Client.
vSphere Upgrade Upgrade vCenter Server Separately by Using Custom Install You can upgrade vCenter Server separately after installing vCenter Single Sign-On, and upgrading Inventory Service. Alternatively, you can upgrade vCenter Server as part of a Simple Install. See “Use Simple Install to Upgrade vCenter Server and Required Components,” on page 65 and “How vCenter Single Sign-On Affects vCenter Server Upgrades,” on page 32. This procedure requires downtime for the vCenter Server that you are upgrading.
Chapter 4 Upgrading vCenter Server 7 Select how to upgrade vCenter Agent. Option Description Automatic To automatically upgrade vCenter Agent on all the hosts in the vCenter Server inventory. Manual If one of the following applies: n You need to control the timing of vCenter Agent upgrades on specific hosts. n vCenter Agent is installed on each host in the inventory to enable vCenter Server to manage the host. vCenter Agent must be upgraded when vCenter Server is upgraded.
vSphere Upgrade 14 Click Install. Installation might take several minutes. Multiple progress bars appear during the installation of the selected components. What to do next Review the topics in Chapter 5, “After You Upgrade vCenter Server,” on page 127 for other postupgrade actions you might want to take. Use Custom Install to Upgrade a Basic vCenter Single Sign-On Deployment of Version 5.1.
Chapter 4 Upgrading vCenter Server Install or Upgrade vCenter Single Sign-On in a Basic Deployment Create or upgrade vCenter Single Sign-On in a vCenter Single Sign-On installation. These instructions let you install or upgrade vCenter Single Sign-On only. You must install or upgrade vCenter Single Sign-On and upgrade Inventory Service before upgrading vCenter Server.
vSphere Upgrade 9 Enter the site name for vCenter Single Sign-On. The site name becomes important if you are using vCenter Single Sign-On in multiple locations. Choose your own name for the vCenter Single Sign-On site. NOTE You cannot change the site name at a later time. 10 Review the installation options and click Install. vCenter Single Sign-On is installed or upgraded.
Chapter 4 Upgrading vCenter Server Procedure 1 In the software installer directory, double-click the autorun.exe file to start the installer. 2 Select vSphere Web Client and click Install. 3 Follow the prompts in the installation wizard to choose the installer language, and agree to the end user patent and license agreements. 4 Either accept the default destination folder or click Change to select another location.
vSphere Upgrade n See “Prerequisites for the vCenter Server Upgrade,” on page 48 n Download the vCenter Server Installer. n Upgrade vCenter Single Sign-On. Procedure 1 In the software installer directory, double-click the autorun.exe file to start the installer. 2 Select vCenter Inventory Service and click Install. 3 Follow the prompts in the installation wizard to choose the installer language, and agree to the end user patent and license agreements.
Chapter 4 Upgrading vCenter Server 5 Select whether to upgrade the vCenter Server database. n Select Upgrade existing vCenter Server database to continue with the upgrade to vCenter Server. n Select Do not upgrade existing vCenter Server database if you do not have a backup copy of your database. You cannot continue the upgrade. 6 Click I have taken a backup of the existing vCenter Server database and SSL certificates. 7 Select how to upgrade vCenter Agent.
vSphere Upgrade 12 Enter the information to register vCenter Server with vCenter Single Sign-On. The vCenter Single Sign-On administrator user name is administrator@vsphere.local, and the password must match the password you entered when you installed vCenter Single Sign-On. The Lookup Service URL takes the form https://SSO_host_FQDN_or_IP:7444/lookupservice/sdk, where 7444 is the default vCenter Single Sign-On HTTPS port number.
Chapter 4 Upgrading vCenter Server n Verify that the load balancer in your existing vCenter Single Sign-On high availability deployment is configured as described in VMware Knowledge Base articles 2034157 and 2033588 . Procedure 1 Upgrade the First vCenter Single Sign-On Node in a High Availability Installation on page 85 Upgrade the first node in a vCenter Single Sign-On installation for high availability.
vSphere Upgrade After vCenter Single Sign-On is installed or upgraded, the following default identity sources and users are available: localos All local operating system users. These users can be granted permissions to vCenter Server. If you are upgrading, those users who already have permissions keep those permissions. vsphere.local Contains all users who have administrator access to the vCenter Single SignOn server. Initially, only the user administrator is defined.
Chapter 4 Upgrading vCenter Server Reconfigure the Load Balancer After Upgrading a vCenter Single Sign-On High Availability Deployment to Version 5.5 After you upgrade both nodes of a 5.1.x vCenter Single Sign-On high availability deployment to version 5.5, reconfigure the load balancer. Prerequisites Upgrade both vCenter Single Sign-On nodes to version 5.5. Procedure 1 In the httpd.conf file of the load balancer, in the section Configure the STS for clustering, change values from ims to sts.
vSphere Upgrade 4 Edit the file sts.properties to replace the vCenter Single Sign-On hostname with the load balancer hostname. Use the following example as a model: [service] friendlyName=The security token service interface of the SSO server version=1.5 ownerId= type=urn:sso:sts description=The security token service interface of the SSO server productId=product:sso viSite=SSO node1 site name [endpoint0] uri=https://loadbalancer fqdn.com:7444/sts/STSService/vsphere.local ssl=C:\updateInfo\cacert.
Chapter 4 Upgrading vCenter Server 7 For each of the service ID, run the command ssolscli.cmd updateService: ssolscli.cmd updateService -d https://sso1.example.com/lookupservice/sdk -u Administrator@vsphere.local -p password -si sts_id -ip sts.properties ssolscli.cmd updateService -d https://sso1.example.com/lookupservice/sdk -u Administrator@vsphere.local -p password -si admin_id -ip admin.properties ssolscli.cmd updateService -d https://sso1.example.com/lookupservice/sdk -u Administrator@vsphere.
vSphere Upgrade 4 Either accept the default destination folder or click Change to select another location. The installation path cannot contain any of the following characters: non-ASCII characters, commas (,), periods (.), exclamation points (!), pound signs (#), at signs (@), or percentage signs (%). If 8.3 name creation is disabled on the host machine, do not install the vSphere Web Clientin a directory that does not have an 8.3 short name or has a name that contains spaces.
Chapter 4 Upgrading vCenter Server Procedure 1 In the software installer directory, double-click the autorun.exe file to start the installer. 2 Select vCenter Inventory Service and click Install. 3 Follow the prompts in the installation wizard to choose the installer language, and agree to the end user patent and license agreements. 4 If you are upgrading or reinstalling an existing instance of Inventory Service, choose whether to keep the existing database or replace it with a new empty database.
vSphere Upgrade 6 Click I have taken a backup of the existing vCenter Server database and SSL certificates. 7 Select how to upgrade vCenter Agent. Option Description Automatic To automatically upgrade vCenter Agent on all the hosts in the vCenter Server inventory. Manual If one of the following applies: n You need to control the timing of vCenter Agent upgrades on specific hosts. n vCenter Agent is installed on each host in the inventory to enable vCenter Server to manage the host.
Chapter 4 Upgrading vCenter Server 14 Click Install. Installation might take several minutes. Multiple progress bars appear during the installation of the selected components. What to do next Review the topics in Chapter 5, “After You Upgrade vCenter Server,” on page 127 for other postupgrade actions you might want to take. Use Custom Install to Upgrade vCenter Server from a Version 5.1.x Multisite vCenter Single Sign-On Deployment The vCenter Server 5.1.
vSphere Upgrade 5 Install or Upgrade an Additional Single Sign-On Server for a Multisite vCenter Single Sign-On Installation on page 99 Create or upgrade an additional vCenter Single Sign-On server for a multisite vCenter Single Sign-On installation. 6 Install or Upgrade the vSphere Web Client on page 100 The vSphere Web Client lets you connect to a vCenter Server system to manage your vSphere deployment through a browser.
Chapter 4 Upgrading vCenter Server The first vCenter Single Sign-On multisite server is installed or upgraded. After vCenter Single Sign-On is installed or upgraded, the following default identity sources and users are available: localos All local operating system users. These users can be granted permissions to vCenter Server. If you are upgrading, those users who already have permissions keep those permissions. vsphere.
vSphere Upgrade If 8.3 name creation is disabled on the host machine, do not install the vSphere Web Clientin a directory that does not have an 8.3 short name or has a name that contains spaces. This situation will make the vSphere Web Client inaccessible. 5 Accept or change the default port settings. 6 Enter the information to register the vSphere Web Client with vCenter Single Sign-On. The vCenter Single Sign-On administrator user name is administrator@vsphere.
Chapter 4 Upgrading vCenter Server 3 Follow the prompts in the installation wizard to choose the installer language, and agree to the end user patent and license agreements. 4 If you are upgrading or reinstalling an existing instance of Inventory Service, choose whether to keep the existing database or replace it with a new empty database. 5 Click Install. Inventory Service is upgraded.
vSphere Upgrade 7 Select how to upgrade vCenter Agent. Option Description Automatic To automatically upgrade vCenter Agent on all the hosts in the vCenter Server inventory. Manual If one of the following applies: n You need to control the timing of vCenter Agent upgrades on specific hosts. n vCenter Agent is installed on each host in the inventory to enable vCenter Server to manage the host. vCenter Agent must be upgraded when vCenter Server is upgraded.
Chapter 4 Upgrading vCenter Server 14 Click Install. Installation might take several minutes. Multiple progress bars appear during the installation of the selected components. What to do next Review the topics in Chapter 5, “After You Upgrade vCenter Server,” on page 127 for other postupgrade actions you might want to take.
vSphere Upgrade What to do next Repeat this procedure for each additional multisite node. Install or Upgrade the vSphere Web Client The vSphere Web Client lets you connect to a vCenter Server system to manage your vSphere deployment through a browser. If an earlier version of the vSphere Web Client is installed, this procedure upgrades the vSphere Web Client. NOTE vCenter Server 5.
Chapter 4 Upgrading vCenter Server 6 Enter the information to register the vSphere Web Client with vCenter Single Sign-On. The vCenter Single Sign-On administrator user name is administrator@vsphere.local, and the password must match the password you entered for the administrator user when you installed vCenter Single Sign-On. The Lookup Service URL takes the form https://SSO_host_FQDN_or_IP: 7444/lookupservice/sdk, where 7444 is the default vCenter Single Sign-On HTTPS port number.
vSphere Upgrade Inventory Service is upgraded. Upgrade vCenter Server Separately by Using Custom Install You can upgrade vCenter Server separately after installing vCenter Single Sign-On, and upgrading Inventory Service. Alternatively, you can upgrade vCenter Server as part of a Simple Install. See “Use Simple Install to Upgrade vCenter Server and Required Components,” on page 65 and “How vCenter Single Sign-On Affects vCenter Server Upgrades,” on page 32.
Chapter 4 Upgrading vCenter Server 7 Select how to upgrade vCenter Agent. Option Description Automatic To automatically upgrade vCenter Agent on all the hosts in the vCenter Server inventory. Manual If one of the following applies: n You need to control the timing of vCenter Agent upgrades on specific hosts. n vCenter Agent is installed on each host in the inventory to enable vCenter Server to manage the host. vCenter Agent must be upgraded when vCenter Server is upgraded.
vSphere Upgrade 14 Click Install. Installation might take several minutes. Multiple progress bars appear during the installation of the selected components. What to do next Review the topics in Chapter 5, “After You Upgrade vCenter Server,” on page 127 for other postupgrade actions you might want to take. Add a vCenter Single Sign-On Identity Source Users can log in to vCenter Server only if they are in a domain that has been added as a vCenter Single SignOn identity source.
Chapter 4 Upgrading vCenter Server 6 Click OK. What to do next When an identity source is added, all users can be authenticated but have the No access permission. A user with vCenter Server Modify.permissions privileges can assign permissions to users or groups of users to enable them to log in to vCenter Server. See “Assign Permissions in the vSphere Web Client,” on page 106.
vSphere Upgrade Table 4‑2. Active Directory as an LDAP Server and OpenLDAP Settings Field Description Name Name of the identity source. Base DN for users Base domain name for users. Domain name FDQN of the domain, for example, example.com. Do not provide an IP address in this field. Domain alias For Active Directory identity sources, the domain's NetBIOS name. Add the NetBIOS name of the Active Directory domain as an alias of the identity source if you are using SSPI authentications.
Chapter 4 Upgrading vCenter Server 5 Identify the user or group that will have the permission. a Select the domain where the user or group is located from the Domain drop-down menu. b Type a name in the Search box or select a name from the list. The system searches user names, group names, and descriptions. c Select the user or group and click Add. The name is added to either the Users or Groups list. 6 d (Optional) Click Check Names to verify that the user or group exists in the database.
vSphere Upgrade Figure 4‑3. vSphere Inventory Hierarchy root folder data center folder data center VM folder host folder template host virtual machine vApp network folder standard switch resource pool cluster virtual machine resource pool datastore folder VDS distributed port group datastore datastore cluster vApp vApp virtual machine resource pool virtual machine Most inventory objects inherit permissions from a single parent object in the hierarchy.
Chapter 4 Upgrading vCenter Server Global entities n Resource pools n Templates n Virtual machines n vSphere vApps Global entities derive permissions from the root vCenter Server system. n Custom fields n Licenses n Roles n Statistics intervals n Sessions Migrate vCenter Server and Components from a Windows Server 2003 Host vCenter Server 5.5 does not support Windows Server 2003 as a host machine, and does not support upgrades from Windows Server 2003 hosts.
vSphere Upgrade 6 Migrate vCenter Server Data from a Windows Server 2003 Host on page 115 When you migrate from a Windows Server 2003 host to a host that is supported for vCenter Single Sign-On 5.5, you can also migrate the vCenter Server database and SSL certificates. 7 Install vCenter Server in a Migration from a Windows Server 2003 Host on page 116 After you migrate vCenter Server SSL certificates from a Windows Server 2003 host to a host that is supported for vCenter Server 5.
Chapter 4 Upgrading vCenter Server 7 Enter the site name for vCenter Single Sign-On. The site name becomes important if you are using vCenter Single Sign-On in multiple locations. Choose your own name for the vCenter Single Sign-On site. NOTE You cannot change the site name at a later time. 8 Review the installation options and click Install. vCenter Single Sign-On is installed.
vSphere Upgrade 5 Accept or change the default port settings. 6 Enter the information to register the vSphere Web Client with vCenter Single Sign-On. The vCenter Single Sign-On administrator user name is administrator@vsphere.local, and the password must match the password you entered for the administrator user when you installed vCenter Single Sign-On.
Chapter 4 Upgrading vCenter Server 3 Copy the vSphere Web Client ssl folder to the new host, at C:\ProgramData\VMware\vSphere Web Client\ssl. For version 5.0.x installations, the folder is located at C:\Program Files\VMware\Infrastructure\vSphere Web Client\DMServer\config\ssl. For version 5.1.x installations, the folder is located at C:\Documents and Settings\All Users\Application Data\VMware\vSphere Web Client\ssl.
vSphere Upgrade 5 Copy all data files from the Inventory Service\datafolder For version 5.0.x installations, the folder is located at C:\Program Files\VMware\Infrastructure\Inventory Service\data. For version 5.1.x installations, the folder is located at C:\Documents and Settings\All Users\Application Data\VMware\Infrastructure\Inventory Service\data.
Chapter 4 Upgrading vCenter Server 9 Enter the information to register Inventory Service with vCenter Single Sign-On. The vCenter Single Sign-On administrator user name is administrator@vsphere.local, and the password must match the password you entered when you installed vCenter Single Sign-On. The Lookup Service URL takes the form https://SSO_host_FQDN_or_IP:7444/lookupservice/sdk, where 7444 is the default vCenter Single Sign-On HTTPS port number.
vSphere Upgrade Install vCenter Server in a Migration from a Windows Server 2003 Host After you migrate vCenter Server SSL certificates from a Windows Server 2003 host to a host that is supported for vCenter Server 5.5, you can install vCenter Server on the new host. If you do not enter a license key, vCenter Server will be in evaluation mode, which allows you to use the full feature set for a 60-day evaluation period.
Chapter 4 Upgrading vCenter Server 8 Select Create a standalone VMware vCenter Server instance or Join a VMware vCenter Group using Linked Mode to share information. Joining a Linked Mode group enables the vSphere Web Client to view, search, and manage data across multiple vCenter Server systems. NOTE This option does not appear if you are upgrading the VirtualCenter or vCenter Server database schema. You can join a Linked Mode group after the installation is complete.
vSphere Upgrade vCenter Server is installed with the migrated SSL certifiicates and vCenter Server database from your Windows Server 2003 installation. What to do next After you complete the installation, use the vSphere Web Client to connect to vCenter Server. Review the topics in Chapter 5, “After You Upgrade vCenter Server,” on page 127 for other postinstallation actions you might want to take.
Chapter 4 Upgrading vCenter Server Elevate Administrators Group Privileges to Administrator Level in Windows Server 2008 Installing a vCenter Server update on Windows Server 2008 or later with User Account Control (UAC) turned on requires the logged in user to have Administrator-level privileges. You can elevate the privileges of Administrators group members to the Administrator level. Alternatively, you can turn off UAC in the User Accounts control panel, and turn it back on after the update is complete.
vSphere Upgrade 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.
Chapter 4 Upgrading vCenter Server 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.
vSphere Upgrade 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.
Chapter 4 Upgrading vCenter Server n Back up the vCenter Server database. Procedure 1 Download the zipped updated bundle from the VMware.com Web site. 2 On your chosen Web server, create a repository directory under the root: for example, vc_update_repo. 3 Extract the zipped bundle into the repository directory. The extracted files are in two subdirectories: manifest and package-pool. 4 Open the management vCenter Virtual Appliance Web interface on port 5480. 5 In the Update tab, click Settings.
vSphere Upgrade Install or Upgrade vCenter Server Java Components Separately The required vCenter Server Java Components (JRE) are installed or upgraded silently when you install or upgrade vCenter Server. You can also install or upgrade vCenter Server Java Components separately. By using the separate installer, you can update or upgrade JRE to a version that is released asynchronously from vCenter Server releases.
Chapter 4 Upgrading vCenter Server Update the Java Components and vCenter Server tc Server with VIMPatch You can separately update the Java version of all vCenter Server components depending on JRE server by using the VIMPatch ISO file. You can also upgrade the vCenter Server tc Server by using the same patch.
vSphere Upgrade 4 Reboot the vCenter Server machine before upgrading. This releases any locked files that are used by the Tomcat process, and enables the vCenter Server installer to stop the Tomcat service for the upgrade. Alternatively, you can restart the vCenter Server machine and restart the upgrade process, but select the option not to overwrite the vCenter Server data. 126 VMware, Inc.
After You Upgrade vCenter Server 5 After you upgrade to vCenter Server, consider the postupgrade options and requirements. n To view the database upgrade log, open %TEMP%\VCDatabaseUpgrade.log. n Upgrade any additional modules that are linked to this instance of vCenter Server, such as vSphere Update Manager. n On the VMware Web site, log in to your account page to access the license portal. From the license portal, upgrade your vCenter Server license.
vSphere Upgrade Install or Upgrade the vSphere Web Client The vSphere Web Client lets you connect to a vCenter Server system to manage your vSphere deployment through a browser. If an earlier version of the vSphere Web Client is installed, this procedure upgrades the vSphere Web Client. 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.
Chapter 5 After You Upgrade vCenter Server 7 Click Install. 8 Start the vSphere Web Client by taking one of the following actions. n If you are starting the vSphere Web Client for the first time, open a supported browser, and go to https://vSphere_Web_Client_host_name_or_IP:9443/vsphere-client. n In subsequent sessions, you can start the vSphere Web Client from the Windows Start menu, by selecting Programs > VMware > VMware vSphere Web Client > vSphere Web Client.
vSphere Upgrade n Verify that the host machine has Windows Installer 3.0 or later. n Verify that the host machine has a supported processor and operating system. The vSphere ESXi Dump Collector supports the same processors and operating systems as vCenter Server. See “vCenter Server Software Requirements,” on page 22 and “Hardware Requirements for vCenter Server, the vSphere Web Client, vCenter Inventory Service, and vCenter Single Sign-On,” on page 17.
Chapter 5 After You Upgrade vCenter Server You can install vSphere Syslog Collector on the same machine as the associated vCenter Server, or on a different machine that has network connection to the vCenter Server. The vSphere Syslog Collector service binds to an IPv4 address for communication with vCenter Server, and does not support IPv6.
vSphere Upgrade You must install the vSphere Auto Deploy server separately for each instance of vCenter Server that you plan to use the vSphere Auto Deploy with. vSphere Auto Deploy is not supported with vCenter Server versions earlier than version 5.0. You must upgrade vSphere Auto Deploy when you upgrade vCenter Server. vSphere Auto Deploy is supported only in the same version as the corresponding vCenter Server. vSphere Auto Deploy supports both IPv4 and IPv6.
Chapter 5 After You Upgrade vCenter Server Prerequisites n Install vSphere Auto Deploy. See “Install or Upgrade vSphere Auto Deploy,” on page 131. n Verify that you have administrator privileges. n Verify that the host machine has Windows Installer 3.0 or later. n Verify that the host machine has a supported processor and operating system. vSphere Authentication Proxy supports the same processors and operating systems as vCenter Server.
vSphere Upgrade Enable IPv6 Support for vCenter Inventory Service vCenter Inventory Service does not support binding on IPv6 interfaces by default. When you install vCenter Server, vCenter Inventory Service supports only IPv4 by default. You can enable IPv6 support for vCenter Inventory Service by modifying the Inventory Service dataservice.properties file. Procedure 1 Stop the vCenter Inventory Service. a From the Administrative Tools control panel, select Services.
Chapter 5 After You Upgrade vCenter Server Linked Mode Prerequisites for vCenter Server Prepare the vCenter Server system for joining a Linked Mode group. Before joining a vCenter Server to a Linked Mode group, review “Linked Mode Considerations for vCenter Server,” on page 134. All the requirements for standalone vCenter Server systems apply to Linked Mode systems.
vSphere Upgrade Procedure 1 From the Start menu, select All Programs > VMware > vCenter Server Linked Mode Configuration. 2 Click Next. 3 Select Modify linked mode configuration and click Next. 4 Click Join vCenter Server instance to an existing linked mode group or another instance and click Next. 5 Type the server name and LDAP port number of any remote vCenter Server that is or will be a member of the group and click Next.
Chapter 5 After You Upgrade vCenter Server Configuring VMware vCenter Server - tc Server Settings in vCenter Server Starting with vCenter Server 5.1, VMware Tomcat Server settings can no longer be configured through the Windows user interface. vCenter Server versions 5.1 and later use VMware vCenter Server - tc Server, an enterprise version of Apache Tomcat 7. Tomcat version 7 does not provide a control panel in the Windows user interface.
vSphere Upgrade Table 5‑3. vCenter Server Port and Security Settings in the server.xml and catalina.properties Files (Continued) vCenter Server Port or Security Setting Setting and Default Value Web services HTTPS bio-vmssl.http.port=8080 Web services HTTPS bio-vmssl.https.port=8443 SSL certificate biovmssl.keyFile.name=C:\ProgramData\VMware\VMware VirtualCenter\SSL\rui.pfx SSL certificate password bio-vmssl.SSL.password=testpassword AJP port bio-vmssl.ajp.
Upgrading Update Manager 6 You can upgrade to Update Manager 5.5 from Update Manager version 4.x, Update Manager 5.0 and Update Manager 5.1 that are installed on a 64-bit operating system. Direct upgrades from Update Manager 1.0 Update 6 and earlier, and Update Manager systems that are installed on a 32-bit platform are not supported. If you are running an earlier version of Update Manager on a 32-bit platform, you cannot perform an inplace upgrade to Update Manager 5.5.
vSphere Upgrade Upgrade the Update Manager Server To upgrade an instance of Update Manager that is installed on a 64-bit machine, you must first upgrade vCenter Server to a compatible version. The Update Manager 5.5 release allows upgrades from Update Manager 1.0 Update 6, Update Manager 4.x, Update Manager 5.0, and Update Manager 5.1. Prerequisites n Ensure that you grant the database user the required set of privileges.
Chapter 6 Upgrading Update Manager 11 On the Database Upgrade page, select Yes, I want to upgrade my Update Manager database and I have taken a backup of the existing Update Manager database, and click Next. 12 (Optional) On the Database re-initialization warning page, select to keep your existing remote database if it is already upgraded to the latest schema. If you replace your existing database with an empty one, you lose all of your existing data.
vSphere Upgrade 142 VMware, Inc.
Upgrading and Migrating Your Hosts 7 After you upgrade vCenter Server, and vSphere Update Manager if you are using Update Manager, upgrade or migrate VMware ESX 4.x and ESXi 4.x hosts, or update ESXi 5.0.x hosts, to ESXi 5.x. These topics are intended for administrators who are upgrading ESX, ESXi, and virtual machines from ESX 4.x/ESXi 4.x, or updating ESXi 5.0.x, to ESXi 5.x.
vSphere Upgrade n Make sure your system hardware complies with ESXi requirements. See Chapter 2, “System Requirements,” on page 13 and the VMware Compatibility Guide, at http://www.vmware.com/resources/compatibility/search.php. Check for system compatibility, I/O compatibility (network and HBA cards), storage compatibility, and backup software compatibility. n Make sure that sufficient disk space is available on the host for the upgrade or migration. Migrating from ESX 4.x to ESXi 5.
Chapter 7 Upgrading and Migrating Your Hosts Table 7‑1. Files Migrated During Migration or Upgrade to ESXi File Migrated Comments /etc/sfcb/sfcb.cfg Migrated. /var/lib/sfcb/registration/repository/root/inte rop/* Migrated. /etc/logrotate.conf Not migrated. ESXi Logrotation is incompatible with prior versions. /etc/localtime Not migrated. Timezones are not supported in ESXi. /etc/ntp.conf Migrated. /etc/ntp.drift Migrated. /etc/ntp.keys Migrated. /etc/syslog.
vSphere Upgrade Table 7‑1. Files Migrated During Migration or Upgrade to ESXi (Continued) File Migrated Comments /etc/login.defs Not migrated. This file controls settings like maildir, password aging controls, uid and gid min/max settings, and the user deletion command. /etc/pam.d/* Partially migrated. Needed for authentication and authorization. NOTE Custom edits made to settings in /etc/pam.d/system-auth in ESX 4.x are reset to the default values by the upgrade to ESXi 5.x.
Chapter 7 Upgrading and Migrating Your Hosts Table 7‑1. Files Migrated During Migration or Upgrade to ESXi (Continued) File Migrated Comments /etc/shadow /etc/groups Not migrated. Firewall Configuration Changes After Migration or Upgrade to ESXi 5.x The migration or upgrade from ESX/ESXi 4.x to ESXi 5.x results in several changes to the host firewall configuration. When you migrate from ESX 4.x to ESXi 5.x, the ESX 4.x rulesets list is replaced by the new rulesets list in ESXi 5.x.
vSphere Upgrade Networking Changes in ESXi 5.x Some ESX 4.x and ESXi 4.x network settings stored in /etc/sysconfig/network are migrated in the upgrade or migration to ESXi 5.x. In the migration to ESXi 5.x, ESX Service Console virtual NICs (vswifs) are converted to ESXi virtual NICs (vmks). The distributed port group or dvPort that the virtual NICs connect to is also migrated. The Service Console port group is renamed as the Management Network port group.
Chapter 7 Upgrading and Migrating Your Hosts Partitioning Changes from ESX 4.x to ESXi 5.x The ESXi partition scheme used in ESXi 5.x differs from that of earlier ESX and ESXi versions. ESXi 5.x does not have the Service Console partition found in ESX. How these changes affect your host depends on whether you are upgrading to ESXi 5.x or performing a fresh installation. Partitioning in New ESXi 5.
vSphere Upgrade ESXi 5.5 Upgrade Options VMware provides several ways to upgrade ESX/ESXi hosts. vSphere Update Manager vSphere Update Manager is software for upgrading, migrating, updating, and patching clustered hosts, virtual machines, and guest operating systems. Update Manager orchestrates host and virtual machine upgrades. If your site uses vCenter Server, VMware recommends that you use Update Manager.
Chapter 7 Upgrading and Migrating Your Hosts Table 7‑2. ESXi 5.5.x Upgrade Methods Upgrade from ESX or ESXi 4.x to ESXi 5.5.x Upgrade from ESXi 5.0.x to ESXi 5.5.x Upgrade from ESXi 5.1.x to ESXi 5.5.x Upgrade from ESXi 5.5.0 to ESXi 5.5.x vSphere Update Manager yes yes yes yes Interactive upgrade from CD, DVD, or USB drive yes yes yes yes Scripted upgrade yes yes yes yes vSphere Auto Deploy no yes, if the ESXi 5.0.x host was deployed using Auto Deploy yes, if the ESXi 5.1.
vSphere Upgrade Table 7‑3. ESX/ESXi 4.0 U3 and 4.1 U1 Third-Party VIBs That Cannot Be Migrated to ESXi 5.x. ESX/ESXi Release Bulletin ID VIB ID 4.1 Upgrade 1 ESX410-201101224-UG cross_vmware-esx-drivers-netvxge_400.2.0.28.21239-1OEM If your system does not include any hardware that requires this Neterion driver, you can ignore the error message. 4.1 Upgrade 1 ESX410-201101223-UG cross_vmware-esx-driversscsi-3w-9xxx_400.2.26.08.
Chapter 7 Upgrading and Migrating Your Hosts Table 7‑4. Supported Scenarios for Upgrade or Migration to 5.5.x. (Continued) Scenario for Upgrade or Migration to 5.5.x Support 4.x ESX or ESXi host, interactive migration or upgrade Supported. See “Upgrade or Migrate Hosts Interactively,” on page 180. The installer wizard offers the choice to upgrade or perform a fresh installation. If you upgrade, ESX partitions and configuration files are converted to be compatible with ESXi. 4.
vSphere Upgrade Table 7‑4. Supported Scenarios for Upgrade or Migration to 5.5.x. (Continued) Scenario for Upgrade or Migration to 5.5.x Support 5.1.x ESXi host Methods supported for direct upgrade to 5.5.x are: n vSphere Update Manager. n Interactive upgrade from CD, DVD, or USB drive. n Scripted upgrade. n Auto Deploy. If the ESXi 5.1.x host was deployed using Auto Deploy, you can use Auto Deploy to reprovision the host with an 5.5.x image. n esxcli. 5.5.
Chapter 7 Upgrading and Migrating Your Hosts 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. 3 Burn the ISO image to a CD or DVD.
vSphere Upgrade e 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 f 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.vfat -F 32 -n USB /dev/sdb1 4 Run the following commands.
Chapter 7 Upgrading and Migrating Your Hosts n USB flash drive Procedure 1 Attach the USB flash drive to a Linux machine that has access to the installation or upgrade script. 2 Create a partition table. /sbin/fdisk /dev/sdb a Type d to delete partitions until they are all deleted. b Type n to create primary partition 1 that extends over the entire disk. c Type t to set the type to an appropriate setting for the FAT32 file system, such as c. d Type p to print the partition table.
vSphere Upgrade Procedure 1 Download the ESXi ISO image from the VMware Web site. 2 Mount the ISO image into a folder: mount -o loop VMware-VMvisor-Installer-5.x.x-XXXXXX.x86_64.iso /esxi_cdrom_mount XXXXXX is the ESXi build number for the version that you are installing or upgrading to. 3 Copy the contents of cdrom to another folder: cp -r /esxi_cdrom_mount /esxi_cdrom 4 Copy the kickstart file to /esxi_cdrom cp ks_cust.cfg /esxi_cdrom 5 (Optional) Modify the boot.
Chapter 7 Upgrading and Migrating Your Hosts The PXELINUX and gPXE environments allow your target machine to boot the ESXi installer. PXELINUX is part of the SYSLINUX package, which can be found at http://www.kernel.org/pub/linux/utils/boot/syslinux/, although many Linux distributions include it. Many versions of PXELINUX also include gPXE. Some distributions, such as Red Hat Enterprise Linux version 5.3, include earlier versions of PXELINUX that do not include gPXE.
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 7 Upgrading and Migrating Your Hosts 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 PXELINUX n Server with a hardware configuration that is supported with your version of ESXi. See the Hardware 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 184. n Network adapter with PXE support on the target ESXi host n IPv4 networking.
Chapter 7 Upgrading and Migrating Your Hosts 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 using PXELINUX, and use the isolinux.cfg file as the PXE configuration file. See also “About Installation and Upgrade Scripts,” on page 184 and “About the boot.
vSphere Upgrade 6 Copy the isolinux.cfg file from the ESXi installer ISO image to the /tftpboot/pxelinux.cfg directory. The isolinux.cfg file contains the following code, where XXXXXX is the build number of the ESXi installer image: DEFAULT menu.c32 MENU TITLE ESXi-5.x.x-XXXXXX-full Boot Menu NOHALT 1 PROMPT 0 TIMEOUT 80 LABEL install KERNEL mboot.c32 APPEND -c location of boot.cfg MENU LABEL ESXi-5.x.
Chapter 7 Upgrading and Migrating Your Hosts http://XXX.XXX.XXX.XXX/k.b00 --- http://XXX.XXX.XXX.XXX/a.b00 --http://XXX.XXX.XXX.XXX/s.v00 --- http://XXX.XXX.XXX.XXX/weaselin.t00 --http://XXX.XXX.XXX.XXX/tools.t00 --- http://XXX.XXX.XXX.XXX/imgdb.tgz --http://XXX.XXX.XXX.XXX/imgpayld.tgz 3 gPXE boot the host and press Ctrl+B to access the GPT menu. 4 Enter the following commands to boot with the ESXi installer, where XXX.XXX.XXX.XXX is the HTTP server IP address.
vSphere Upgrade Performing the Upgrade or Migration Several tools are available to upgrade and migrate hosts. You can use different upgrade tools based depending on the type of host you are upgrading (ESX or ESXi) and whether the hosts are managed by vCenter Server. You can migrate or upgrade to ESXi 5.x from version 4.x ESX or ESXi or version 5.0.x with the tools and methods described in “ESXi 5.5 Upgrade Options,” on page 150. To upgrade version 3.5 ESX or ESXi to ESXi 5.
Chapter 7 Upgrading and Migrating Your Hosts For components that are not listed here, you can perform the upgrade by using another upgrade method, or, for third-party components, by using the appropriate third-party tools. The following topics describe how to use Update Manager to conduct an orchestrated upgrade of your ESXi hosts.
vSphere Upgrade n If a host is a member of a Virtual SAN cluster, and any virtual machine on the host uses a VM storage policy with a setting for "Number of failures to tolerate=0", the host might experience unusual delays when entering maintenance mode. The delay occurs because Virtual SAN has to migrate the virtual machine data from one disk to another in the Virtual SAN datastore cluster. Delays might take up to hours.
Chapter 7 Upgrading and Migrating Your Hosts 6 Attach Baselines and Baseline Groups to Objects on page 174 To view compliance information and remediate objects in the inventory against specific baselines and baseline groups, you must first attach existing baselines and baseline groups to these objects. 7 Manually Initiate a Scan of ESX/ESXi Hosts on page 174 Before remediation, you should scan the vSphere objects against the attached baselines and baseline groups.
vSphere Upgrade 2 Under Maintenance Mode Settings, select an option from the VM Power state drop-down menu to determine the change of the power state of the virtual machines and appliances that are running on the host to be remediated. Option 3 Description Power Off virtual machines Powers off all virtual machines and virtual appliances before remediation. Suspend virtual machines Suspends all running virtual machines and virtual appliances before remediation.
Chapter 7 Upgrading and Migrating Your Hosts 2 3 Select the check boxes for features that you want to disable or enable. Option Description Distributed Power Management (DPM) VMware DPM monitors the resource use of the running virtual machines in the cluster. If sufficient excess capacity exists, VMware DPM recommends moving virtual machines to other hosts in the cluster and placing the original host into standby mode to conserve power.
vSphere Upgrade Prerequisites Connect the vSphere Client to a vCenter Server system with which Update Manager is registered, and on the Home page, click Update Manager under Solutions and Applications. If your vCenter Server system is part of a connected group in vCenter Linked Mode, you must specify the Update Manager instance to use, by selecting the name of the corresponding vCenter Server system in the navigation bar.
Chapter 7 Upgrading and Migrating Your Hosts 5 After the file is uploaded, click Next. 6 (Optional) Create a host upgrade baseline. 7 a Leave the Create a baseline using the ESXi image selected. b Specify a name, and optionally, a description for the host upgrade baseline. Click Finish. The ESXi image that you uploaded appears in the Imported ESXi Images pane. You can see more information about the software packages that are included in the ESXi image in the Software Packages pane.
vSphere Upgrade Attach Baselines and Baseline Groups to Objects To view compliance information and remediate objects in the inventory against specific baselines and baseline groups, you must first attach existing baselines and baseline groups to these objects. You can attach baselines and baseline groups to objects from the Update Manager Client Compliance view.
Chapter 7 Upgrading and Migrating Your Hosts 3 Select the types of updates to scan for. You can scan for either Patches and Extensions or Upgrades. 4 Click Scan. The selected inventory object and all child objects are scanned against all patches, extensions, and upgrades in the attached baselines. The larger the virtual infrastructure and the higher up in the object hierarchy that you initiate the scan, the longer the scan takes.
vSphere Upgrade To remediate a host against an upgrade baseline, attach the baseline to the host. Review any scan messages in the Upgrade Details window for potential problems with hardware, thirdparty software, and configuration issues that might prevent a successful upgrade or migration to ESXi 5.5. Procedure 1 On the Home page of the vSphere Client, select Hosts and Clusters and click the Update Manager tab. 2 Right-click the inventory object you want to remediate and select Remediate.
Chapter 7 Upgrading and Migrating Your Hosts 11 (Optional) Select Retry entering maintenance mode in case of failure, specify the number of retries, and specify the time to wait between retries. Update Manager waits for the retry delay period and retries putting the host into maintenance mode as many times as you indicate in Number of retries field. 12 (Optional) Select Disable any removable media devices connected to the virtual machine on the host.
vSphere Upgrade 16 On the Ready to Complete page, click Finish. NOTE In the Recent Tasks pane, the remediation task is displayed and will remain at about 22 percent for most of the process. The process is still running and will take approximately 15 minutes to complete. Remediate Hosts Against Baseline Groups You can remediate hosts against attached groups of upgrade, patch, and extension baselines.
Chapter 7 Upgrading and Migrating Your Hosts 9 (Optional) On the Dynamic Patches and Extensions to Exclude page, review the list of patches or extensions to be excluded and click Next. 10 On the Schedule page, specify a unique name and an optional description for the task. 11 Select Immediately to begin the process immediately after you complete the wizard, or specify a time for the remediation process to begin, and click Next.
vSphere Upgrade 17 Edit the cluster remediation options. The Cluster Remediation Options page is available only when you remediate hosts in a cluster. Option Details Disable Distributed Power Management (DPM) if it is enabled for any of the selected clusters. Update Manager does not remediate clusters with active DPM. DPM monitors the resource use of the running virtual machines in the cluster.
Chapter 7 Upgrading and Migrating Your Hosts Before upgrading, consider disconnecting your 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 ESX or ESXi installation. Do not disconnect a VMFS datastore that contains the Service Console of an existing ESX installation.
vSphere Upgrade If you are migrating a 4.x host that contains custom VIBs that are not included in the ESXi installer ISO, the option Upgrade ESXi, preserve VMFS datastore is replaced with Force Migrate ESXi, preserve VMFS datastore. CAUTION Using the Force Migrate option might cause the upgraded host to not boot properly, to exhibit system instability, or to lose functionality. If you are upgrading a 5.0.x or 5.1.x host, supported custom VIBs that are not included in the ESXi installer ISO are migrated.
Chapter 7 Upgrading and Migrating Your Hosts Procedure 1 Start the host. 2 When the ESXi installer window appears, press Shift+O to edit boot options. 3 At the runweasel command prompt, type ks=location of installation script plus boot command line options Example: Boot Option You type the following boot options: ks=http://00.00.00.00/kickstart/ks-osdc-pdp101.cfg nameserver=00.00.0.0 ip=00.00.00.000 netmask=255.255.255.0 gateway=00.00.00.
vSphere Upgrade Table 7‑5. Boot Options for ESXi Installation (Continued) Boot Option Description ks=usb Performs a scripted installation, accessing the script from an attached USB drive. Searches for a file named ks.cfg. The file must be located in the root directory of the drive. If multiple USB flash drives are attached, they are searched until the ks.cfg file is found. Only FAT16 and FAT32 file systems are supported.
Chapter 7 Upgrading and Migrating Your Hosts Installation and Upgrade Script Commands To modify the default installation or upgrade script or to create your own script, use supported commands. Use supported commands in the installation script, which you specify with a boot command when you boot the installer. To determine which disk to install or upgrade ESXi on, the installation script requires one of the following commands: install, upgrade, or installorupgrade.
vSphere Upgrade install Specifies that this is a fresh installation. Replaces the deprecated autopart command used for ESXi 4.1 scripted installations. 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 7 Upgrading and Migrating Your Hosts --overwritevmfs Required to overwrite an existing VMFS datastore on the disk before installation. --preservevmfs Preserves an existing VMFS datastore on the disk during installation. --novmfsondisk Prevents a VMFS partition from being created on this disk. Must be used with --overwritevmfs if a VMFS partition already exists on the disk.
vSphere Upgrade --overwritevmfs Install ESXi if a VMFS partition exists on the disk, but no ESX or ESXi installation exists. Unless this option is present, the installer will fail if a VMFS partition exists on the disk, but no ESX or ESXi installation exists. --forcemigrate If a version 4.x host contains customizations, such as third-party VIBS or drivers, that are not included in the installer .ISO, the installer exits with an error describing the problem.
Chapter 7 Upgrading and Migrating Your Hosts 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. Configures licensing. If not included, ESXi installs in evaluation mode. --esx= Specifies the vSphere license key to use. The format is 5 five-character groups (XXXXX-XXXXX-XXXXX-XXXXX-XXXXX).
vSphere Upgrade paranoid (optional) Causes warning messages to interrupt the installation. If you omit this command, warning messages are logged. part or partition (optional) Creates an additional VMFS datastore on the system. Only one datastore per disk can be created. Cannot be used on the same disk as the install command.
Chapter 7 Upgrading and Migrating Your Hosts n vmkLUN UID:--disk=vmkLUN_UID For accepted disk name formats, see “Disk Device Names,” on page 193. --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.
vSphere Upgrade =[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. --ignorefailure If true, the installation is considered a success even if the %post script terminated with an error. =[true|false] %firstboot Creates an init script that runs only during the first boot. The script has no effect on subsequent boots.
Chapter 7 Upgrading and Migrating Your Hosts virtualdisk Not supported in ESXi 5.x. zerombr Not supported in ESXi 5.x. %firstboot --level option not supported in ESXi 5.x. %packages Not supported in ESXi 5.x. Disk Device Names The install, upgrade, and installorupgrade installation script commands require the use of disk device names. Table 7‑6. Disk Device Names Format Examples Description VML vml.00025261 The device name as reported by the vmkernel MPX mpx.
vSphere Upgrade Table 7‑7. Commands in boot.cfg . (Continued) Command Description kernelopt=STRING Appends STRING to the kernel boot options. modules=FILEPATH1 --- FILEPATH2... --FILEPATHn Lists the modules to be loaded, separated by three hyphens (---). See “Create an Installer ISO Image with a Custom Installation or Upgrade Script,” on page 157, “PXE Boot the ESXi Installer by Using PXELINUX and a PXE Configuration File,” on page 161, “PXE Boot the ESXi Installer by Using PXELINUX and an isolinux.
Chapter 7 Upgrading and Migrating Your 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 PXE Booting the Installer ESXi 5.
Chapter 7 Upgrading and Migrating Your Hosts 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. A first boot using Auto Deploy requires that you set up your environment and add rules to the rule set. See the topic "Preparing for vSphere Auto Deploy" in the vSphere installation and Setup documentation. The following reprovisioning operations are available.
vSphere Upgrade Prerequisites n Create the image profile you want boot the host with. Use the Image Builder PowerCLI. See "Using vSphere ESXi Image Builder CLI" in the vSphere Installation and Setup documentation. n Make sure that the setup that you performed during the first boot operation is in place. Procedure 1 At the PowerShell prompt, run the Connect-VIServer PowerCLI cmdlet to connect to the vCenter Server system that Auto Deploy is registered with.
Chapter 7 Upgrading and Migrating Your Hosts Prerequisites n Install vSphere PowerCLI and all prerequisite software. n Export the host profile that you want to use. n If you encounter problems running PowerCLI cmdlets, consider changing the execution policy. See the information about using Auto Deploy Cmdlets in the vSphere Installation and Setup documentation. Procedure 1 Run the Connect-VIServer PowerCLI cmdlet to connect to the vCenter Server system that Auto Deploy is registered with.
vSphere Upgrade Procedure 1 Use 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 might 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 7 Upgrading and Migrating Your Hosts n vSphere Command-Line Interface Reference is a reference to vicfg- and related vCLI commands. NOTE If you press Ctrl+C while an esxcli command is running, the command-line interface exits to a new prompt without displaying a message. However, the command continues to run to completion. For ESXi hosts deployed with vSphere Auto Deploy, the tools VIB must be part of the base booting image used for the initial Auto Deploy installation.
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 IOVP drivers are published at this level. VMware takes support calls for VIBs with this acceptance level.
Chapter 7 Upgrading and Migrating Your 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 7 Upgrading and Migrating Your Hosts Procedure 1 Check to determine whether the host is in maintenance mode. vicfg-hostops --server=server_name --operation info 2 Run one of the following commands for each virtual machine to power off all 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 7 Upgrading and Migrating Your Hosts When you specify a target server by using --server=server_name in the procedure, the specified 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 7 Upgrading and Migrating Your 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.
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 7 Upgrading and Migrating Your 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 in the procedure, the specified server prompts you for a user name and password. Other connection options, such as a configuration file or session file, are supported.
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 7 Upgrading and Migrating Your Hosts Table 7‑9. Error and Warning Codes That Are Returned by the Installation and Upgrade Precheck Script (Continued) Error or Warning Description PARTITION_LAYOUT Upgrading or migration is possible only if there is at most one VMFS partition on the disk that 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 n On the VMware Web site, log in to your account page to access the license portal. From the license portal, upgrade your ESXi license. Use the vSphere Web Client to assign the upgraded license key to the host. n The host sdX devices might be renumbered after the upgrade. If necessary, update any scripts that reference sdX devices. n After the upgrade, convert any ESX 3.x-style /adv/Disk/MaskLUNs LUN masks to the claim rule format.
Upgrading Virtual Machines and VMware Tools 8 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 216 VMware, Inc.
Example Upgrade Scenarios 9 Upgrade scenarios for vSphere 4.1 include cases with and without clustered hosts, hosts that you upgrade on the same machine on which they are currently running (in-place upgrades), and hosts that you upgrade using different machines (migration upgrades).
vSphere Upgrade n Upgrade vCenter Server version 5.5. See Chapter 4, “Upgrading vCenter Server,” on page 61. The downtime required for this upgrade is based on the amount of data in the database. During this time, you cannot perform provisioning operations, such as cloning or creating virtual machines. n Install the version 5.5 vSphere Web Client. See “Install or Upgrade the vSphere Web Client,” on page 128. n If your environment has vSphere Update Manager, upgrade it to the latest version.
Chapter 9 Example Upgrade Scenarios n Upgrade vCenter Server to version 5.5. See Chapter 4, “Upgrading vCenter Server,” on page 61. n Install the version 5.5 vSphere Web Client. See “Install or Upgrade the vSphere Web Client,” on page 128. n If your environment has vCenter Update Manager, upgrade it to the latest version. Procedure 1 Add the ESXi 5.5 host to vCenter Server 5.5. 2 Add the ESX 4.x/ESXi 4.x hosts to vCenter Server 5.5. 3 Power off or suspend the virtual machines on the ESX 4.
vSphere Upgrade 6 Reboot the hosts, enter the BIOS, and reconfigure the hosts to boot from the network. See the information about Auto Deploy in the vSphere Installation and Setup. For ESXi 4.x hosts with compatible host profiles, the host configuration will be restored. 7 When one host is booted, complete any host configuration that was not migrated and take a host profile from the host. See the vSphere Host Profiles documentation.
Index Symbols %include command 185 %post command 185 %pre command 185 A about vSphere Upgrade 7 acceptance levels 201 accepteula command 185 Active Directory identity source 105 Active Directory LDAP Server identity source 105 additional node, vCenter Single Sign-On 86 Apply-EsxImageProfile cmdlet 197 attaching baseline 174 baseline group 174 authenticating to vCenter Server 38 Auto Deploy rebooting 197 reprovisioning hosts with 197 rule set compliance 199 scenario for migrating ESX/ESXi 4.
vSphere Upgrade E ESX, upgrading 166 ESX upgrade, preparation 143 esxcli, upgrading hosts 200 esxcli installation or upgrade, dry run 210 esxcli reboot image 211 ESXi downloading the installer 165 system requirements 13 upgrading 166 ESXi images, importing 172 ESXi installation script, about 184 ESXi ISO image, burning on a CD/DVD 154 ESXi upgrade, preparation 143 ESXi upgrade options 150 esxupdate 166 evaluation mode 214 F FCoE,installing and booting ESXi from 165 files affected by upgrade 144 firewall 2
Index J O Java Components (JRE), installing or upgrading separately 124 JDBC URL formats 55 JRE, upgrading with VIMPatch 125 JRE,installing or upgrading separately 124 JVM heap settings, recommended for vCenter Virtual Appliance 17 online Help, deploying locally 129 OpenLDAP Server identity source 105 Oracle 53 Oracle database changing the computer name 53 requirements 51 Oracle JDBC Driver 127 orchestrated host upgrades 166 orchestrated upgrade, of hosts 168 K keyboard command 185 L LDAP 135 license,
vSphere Upgrade S SAS disks 13, 15 SATA disks 13, 15 scanning, hosts 174 scenarios 32, 217 script, for installing ESXi 184 scripted installation, differences from ESXi 4.x 192 scripted upgrade of ESXi, by PXE Booting 196 scripted upgrade of ESXi, from a USB flash drive 195 scripted upgrade of ESXi,from a CD or DVD 194 SCSI 13, 15 Security Token Service 37 Service Console, removed in ESXi 5.
Index vCenter Lookup Service 37 vCenter Server downloading the installer 59 hardware requirements 17 joining a group 135 logging in 38 ports 23 postupgrade considerations 127 postupgrade tasks 138 required information for installation or upgrade 41 required information for vCenter Server installation 41 requirements for joining a group 135 setting the administrator user 37 software requirements 22 system requirements 13 upgrade prerequisites 48 upgrade using Simple Install 65 upgrading 61 upgrading separat
vSphere Upgrade VMware vCenter Server - tc Server settings in vCenter Server 137 VMware Directory Service 37 VMware Tools, upgrade procedure 220 VMware vCenter Server Appliance hardware requirements 17 software requirements 22 VMware vSphere Web Client, installing or upgrading 74, 80, 89, 95, 100, 111, 128 vSphere, upgrading components separately 220 vSphere 5.x, changes from vSphere 4.x.
