vSphere Upgrade vSphere 5.0 Update 1 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–2012 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 5 Updated Information 7 1 About the Upgrade Process 9 2 How vSphere 5.0 Differs from vSphere 4.
vSphere Upgrade 7 Upgrading Virtual Machines 147 About VMware Tools 148 About Virtual Machines and Host Upgrades 149 Virtual Machine Hardware Versions 150 Perform an Orchestrated Upgrade of Virtual Machines with vSphere Update Manager 151 Planning Downtime for Virtual Machines 156 Downtime for Upgrading Virtual Machines 156 Manually Install or Upgrade VMware Tools in a Windows Virtual Machine 157 Manually Install or Upgrade VMware Tools in a Linux Virtual Machine 158 Manually Install or Upgrade VMware Too
About vSphere Upgrade vSphere Upgrade describes how to upgrade or migrate to vSphere 5.0 Update 1. To learn how to simplify and automate your datacenter upgrade, see the vSphere Update Manager Installation and Administration Guide. If you have legacy versions of ESX, ESXi, and vCenter Server, and you want to move to VMware vSphere™ 5.0 Update 1 by performing fresh installations of vSphere components without preserving existing configurations, see the vSphere Installation and Setup documentation.
vSphere Upgrade 6 VMware, Inc.
Updated Information This vSphere Upgrade is updated with each release of the product or when necessary. This table provides the update history of the vSphere Upgrade. Revision Description 000782-01 n n 000782-00 VMware, Inc. Updated entry for Oracle in Table: Table 4-2. Corrected step 2 of procedure “Create a USB Flash Drive to Store the ESXi Installation Script or Upgrade Script,” on page 89. Initial release.
vSphere Upgrade 8 VMware, Inc.
About the Upgrade Process 1 Upgrading is a multistage process in which procedures must be performed in a particular order. Follow theprocess outlined in this high-level overview to ensure a smooth upgrade with a minimum of system downtime. CAUTION 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 lose access to your servers. Without planning, you might incur more downtime than is necessary.
vSphere Upgrade See Chapter 6, “Upgrading and Migrating Your Hosts,” on page 77. vSphere 5.0.1 provides several ways to upgrade hosts: 7 n Use vSphere Update Manager to perform an orchestrated upgrade of your ESXi hosts. See “Using vSphere Update Manager to Perform Orchestrated Host Upgrades,” on page 99. n Upgrade a single host at a time, interactively, from an ESXi ISO installer image stored on a CD, DVD, or USB flash drive. See “Upgrade or Migrate Hosts Interactively,” on page 113.
How vSphere 5.0 Differs from vSphere 4.x 2 vSphere 5.0 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.0, see the release notes. Service Console is removed ESXi does not include a Service Console. You can perform most tasks that you performed in the Service Console by using esxcli commands in the ESXi Shell, by using vCLI commands, and by using VMware PowerCLI commands.
vSphere Upgrade Installer caching Instead of using a binary image to install the system, whatever bits were used at boot time are cached to the system. This caching reduces installation problems caused by accessing installation files across networks that are under load. NOTE Scripted installations cannot PXE boot a server and then obtain the binary image from some other form of media. Changes to partitioning of host disks All freshly installed hosts in vSphere 5.
System Requirements 3 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 2GB of physical RAM. VMware recommends 8GB of RAM to take full advantage of ESXi features and run virtual machines in typical production environments.
Chapter 3 System Requirements ESXi Booting Requirements vSphere 5.0 supports booting ESXi hosts from the Unified Extensible Firmware Interface (UEFI). With UEFI you can boot systems from hard drives, CD-ROM drives, or USB media. Network booting or provisioning with VMware Auto Deploy requires the legacy BIOS firmware and is not available with UEFI. ESXi can boot from a disk larger than 2TB provided that the system firmware and the firmware on any addin card that you are using support it.
vSphere Upgrade Table 3‑1. Recommendations for Enhanced Performance System Element Recommendation RAM ESXi hosts require more RAM than typical servers. VMware recommends 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 3 System Requirements Hosts running virtual machines with 64-bit guest operating systems have the following hardware requirements: n For AMD Opteron-based systems, the processors must be Opteron Rev E or later. n For Intel Xeon-based systems, the processors must include support for Intel Virtualization Technology (VT). Many servers that include CPUs with VT support might have VT disabled by default, so you must enable VT manually.
vSphere Upgrade Table 3‑3.
Chapter 3 System Requirements Table 3‑5.
vSphere Upgrade Processing requirements are listed in terms of hardware CPU cores. Only physical cores are counted. In hyperthreaded systems, logical CPUs do not count as separate cores. IMPORTANT The recommended disk sizes assume default log levels. If you configure more detailed log levels, more disk space is required. Table 3‑7. Medium Deployment of Up to 50 Hosts and 500 Powered-On Virtual Machines Product Cores Memory Disk vCenter Server 2 4GB 5GB vSphere Client 1 1GB 1.5GB Table 3‑8.
Chapter 3 System Requirements vCenter Server requires the Microsoft .NET 3.5 SP1 Framework. If it is not installed on your system, the vCenter Server installer installs it. The .NET 3.5 SP1 installation might require Internet connectivity to download more files. NOTE If your vCenter Server host machine uses a non-English operating system, install both the Microsoft .NET Framework 3.5 SP1 and Microsoft .NET Framework 3.5 Language Pack through Windows Update.
vSphere Upgrade Table 3‑11. Recommended Minimum Size and Rotation Configuration for hostd, vpxa, and fdm Logs.
Chapter 3 System Requirements Table 3‑12. Ports Required for Communication Between Components (Continued) Port Description 636 For vCenter Server Linked Mode, this is the SSL port of the local instance. If another service is running on this port, it might be preferable to remove it or change its port to a different port. You can run the SSL service on any port from 1025 through 65535. 902 The default port that the vCenter Server system uses to send data to managed hosts.
vSphere Upgrade Table 3‑13. Ports Required for the vCenter Server Appliance (Continued) Port Description 8443 Web Services HTTPS. Used for the VMware VirtualCenter Management Web Services. 10080 vCenter Inventory Service HTTP. 10443 vCenter Inventory Service HTTPS. 10109 vCenter Inventory Service database. 514 vSphere Syslog Collector server. 1514 vSphere Syslog Collector server (SSL). 6500 Network coredump server (UDP). 6501 Auto Deploy service. 6502 Auto Deploy management.
Chapter 3 System Requirements DNS Requirements for vSphere You install vCenter Server, like any other network server, on a machine with a fixed IP address and wellknown DNS name, so that clients can reliably access the service. Assign a static IP address and host name to the Windows server that will host the vCenter Server system. This IP address must have a valid (internal) domain name system (DNS) registration.
vSphere Upgrade Table 3‑15. Minimum Hardware Requirements Hardware Requirements Processor Intel or AMD x86 processor with two or more logical cores, each with a speed of 2GHz Network 10/100 Mbps For best performance, use a Gigabit connection between Update Manager and the ESX/ESXi hosts Memory 2GB RAM if Update Manager and vCenter Server are on different machines 4GB RAM if Update Manager and vCenter Server are on the same machine Update Manager uses a SQL Server or Oracle database.
Upgrading to vCenter Server 5.0 4 The upgrade to vCenter Server includes a database schema upgrade and an upgrade of vCenter Server 4.x. This chapter includes the following topics: n “Preparing for the Upgrade to vCenter Server,” on page 27 n “Upgrade to vCenter Server 5.0,” on page 41 n “Upgrade to vCenter Server on a Different Machine and Upgrade the Database,” on page 43 n “Upgrade the VMware vCenter Server Appliance,” on page 58 n “Update the VMware vCenter Server Appliance from a VMware.
vSphere Upgrade Table 4‑1. Upgrading vCenter Server Components 28 Product Component Description vCenter Server, vSphere Client, and vSphere Web Client VI Client 1.x Not supported. VirtualCenter Server 1.x Not supported. VirtualCenter Server 2.0 Not supported. VirtualCenter Server 2.5 Not supported. VirtualCenter Server 2.5 Update 6 Upgrade by using the data migration tool to upgrade to vCenter Server 5.0.x on a different machine.
Chapter 4 Upgrading to vCenter Server 5.0 Table 4‑1. Upgrading vCenter Server Components (Continued) Product Component Description ESX/ESXi 4.1 host Update to 4.1 Update 1 or later before upgrading vCenter Server to version 5.0 (required). Upgrade to ESXi 5.0.x (optional). ESXi 5.0 host Upgrade to ESXi 5.0.x (optional). VMFS3 volumes No change. VM3 virtual machines Upgrade (optional). VMDK3 virtual disk Not supported with vCenter Server 5.0.
vSphere Upgrade 4 Stop the VMware VirtualCenter Server service. 5 Run the vCenter Host Agent Pre-Upgrade Checker, and resolve any issues that the Pre-Upgrade Checker finds. See“Run the vCenter Host Agent Pre-Upgrade Checker,” on page 37. 6 Make sure that no processes are running that conflict with the ports that vCenter Server uses. See “Required Ports for vCenter Server,” on page 22. 7 Run the vCenter Server upgrade. 8 Configure new vSphere 5.0 licenses.
Chapter 4 Upgrading to vCenter Server 5.0 n Make sure that SSL certificate checking is enabled for all vSphere HA clusters. If certificate checking is not enabled when you upgrade, HA will fail to configure on the hosts. n In vCenter Server 4.x, select Administration > vCenter Server Settings > SSL Settings > vCenter requires verified host SSL certificates. Follow the instructions to verify each host SSL certificate and click OK. n In VirtualCenter 2.
vSphere Upgrade n Perform a complete backup of the VirtualCenter Server or vCenter Server database before you begin the upgrade. The VirtualCenter 2.5 database schema is not compatible with vCenter Server 5.0. The vCenter Server 5.0 installer upgrades your existing VirtualCenter Server database schema with extra fields, making the database unusable by VirtualCenter 2.5 Update 6. To remove the DBO role, you can migrate all objects in the DBO schema to a custom schema.
Chapter 4 Upgrading to vCenter Server 5.0 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 10g or Oracle 11g and then upgrade vCenter Server 4.x to vCenter Server 5.0. n The JDBC driver file must be included in the CLASSPATH variable.
vSphere Upgrade Table 4‑2. Configuration Notes for Databases Supported with vCenter Server Database Type Configuration Notes IBM DB2 If the database is not local to the vCenter Server system, install the IBM Data Server Runtime Client. Install the IBM DB2 native client according to the IBM instructions for your DB2 version. Ensure that the DB2 binaries directory (typically C:\Program Files\IBM\SQLLIB\BIN) is in the system path. DB2 might be installed at a different location.
Chapter 4 Upgrading to vCenter Server 5.0 Table 4‑3. vCenter Server Upgrade, Migration, or Update Scenarios for Each Database Type Database Type Supported in vCenter Server 5.0.x IBM DB2 9.5 Yes You can upgrade to vCenter Server 5.0.x from vCenter Server 4.0 Update 1, vCenter Server 4.0 Update 2, vCenter Server 4.1, and update to vCenter Server 5.0.x from vCenter Server 5.0. You cannot upgrade from vCenter Server 4.0 because vCenter Server 4.
vSphere Upgrade n Make sure that the vCenter Server computer name is updated in the domain name service (DNS). Ping the computer name to test this connection. For example, if the computer name is host-1.company.com, run the following command in the Windows command prompt: ping host-1.company.com If you can ping the computer name, the name is updated in DNS. Procedure 1 Update the data source information, as needed. 2 Verify the data source connectivity. Back Up VirtualCenter 2.
Chapter 4 Upgrading to vCenter Server 5.0 During a vCenter Server upgrade, the existing agent software is uninstalled and the updated agent software is installed in its place. If the upgrade fails, the updated agent software might not be installed and the host might become unreachable by VirtualCenter 2.5 Update 6 or later, vCenter Server 4.x, or by vCenter Server 5.0. To avoid this condition, you can run the vCenter Host Agent Pre-Upgrade Checker before you try to upgrade to vCenter Server 5.
vSphere Upgrade 2 3 Take one of the following actions to start the Pre-Upgrade Checker. n In the installation package or on the DVD, navigate to \vpx\agentupgradecheck and run the AgentUpgradeChecker.exe executable file. n Start the vCenter Server installer autorun.exe and select vCenter Host Agent Pre-Upgrade Checker from the Utility list. Select the DSN for the VirtualCenter or vCenter Server system you are upgrading from and select the login credentials that are appropriate for that DSN.
Chapter 4 Upgrading to vCenter Server 5.0 Download the vCenter Server Installer You must download the installer for vCenter Server, the vSphere Client, and associated vCenter components and support tools. Procedure 1 Download the zip file for vCenter Server from the VMware downloads page at http://www.vmware.com/support/. 2 Extract the files from the zip archive. DNS Load Balancing Solutions and vCenter Server Datastore Naming vCenter Server 5.
vSphere Upgrade Microsoft SQL Database Set to Unsupported Compatibility Mode Causes vCenter Server Installation or Upgrade to Fail vCenter Server installation with a Microsoft SQL database fails when the database is set to compatibility mode with an unsupported version. Problem The following error message appears: The DB User entered does not have the required permissions needed to install and configure vCenter Server with the selected DB.
Chapter 4 Upgrading to vCenter Server 5.0 Updating Version 3.5 Hosts in High Availability Clusters Before Upgrading vCenter Server Before you upgrade vCenter Server to version 5.0, make sure that any ESX 3.5 hosts that are in a vSphere HA cluster are updated to a patch level that supports High Availability. If a version 3.
vSphere Upgrade Prerequisites n See “Prerequisites for the vCenter Server Upgrade,” on page 30 for requirements for the vCenter Server system and for the database. n Download the vCenter Server 5.0 installer from the VMware Web site. n Back up the existing vCenter Server database. n Close all instances of the VI Client and the vSphere Client. n Make sure that you have a valid license key. n You must be logged in as Administrator on the Windows machine you are installing vCenter Server on.
Chapter 4 Upgrading to vCenter Server 5.0 9 10 Select the account for the vCenter Service to run in. Option Description SYSTEM Account Select the Use SYSTEM account checkbox, type the fully qualified domain name of the vCenter Server host, and click Next. You cannot use the SYSTEM account if you are using the bundled database or SQL Server with Windows authentication.
vSphere Upgrade n License. n Database data for a bundled SQL Server Express database only. If VMware vCenter Update Manager or vCenter Orchestrator is installed on the same machine as vCenter Server, you can use the data migration tool to migrate configuration data for these products. You can also use the tool to migrate the vCenter Update Manager database if it is a SQL Server Express database installed on the same machine as vCenter Update Manager and vCenter Server.
Chapter 4 Upgrading to vCenter Server 5.0 Back Up and Move a Local vCenter Server Database Before you upgrade vCenter Server, back up the vCenter Server database. Migrating vCenter Server with a local database to a new machine, you have several options for moving the database to the new machine. If your database is remote from VirtualCenter or vCenter Server, you do not need to move the database after you back it up.
vSphere Upgrade Procedure 1 On the source machine, stop the VirtualCenter service. a Select Start > Control Panel > Administrative Tools > Services. b Right-click VMware VirtualCenter Server and select Stop. The Status changes from Started to blank. 2 In SQL Server Management Studio, make a full back up of the source machine database. 3 Copy the backup file (.bak) to the C:\ drive on the destination machine.
Chapter 4 Upgrading to vCenter Server 5.0 2 In the SQL Server Management Studio, open the Databases directory. 3 Right-click the source database and select Tasks > Detach. 4 Select the database and click OK. 5 When the detach operation is complete, copy the data files (.mdf and .ldf) to the destination machine's database folder. By default, the database folder is C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data.
vSphere Upgrade The original database is restored onto the new machine, which you can use for the upgrade to vCenter Server 5.0. What to do next See “Back Up VirtualCenter or vCenter Server Configuration with the Data Migration Tool,” on page 50. Back Up and Restore an IBM DB2 Database Before you perform an upgrade to vCenter Server on a different machine, you might want to move the database to the new vCenter Server machine.
Chapter 4 Upgrading to vCenter Server 5.0 9 10 Enter the following backup image information. a Enter the file system media type. b Click Add and browse to the file location on the destination machine. c Click Add and browse to the backup image. d Enter the date and time of the backup image file. Click Finish. The original database is restored. What to do next See “Back Up VirtualCenter or vCenter Server Configuration with the Data Migration Tool,” on page 50.
vSphere Upgrade Table 4‑5. restore Command Variables (Continued) Variable Description TargetAlias The alias for the new database. LogsLocation The directory where log files for the new database are stored. NumBuffers The number of buffers used for the restore operation. If you do not specify the number, by default the system uses two buffers. BufferSize The size, in pages, that each buffer uses to perform the restore operation.
Chapter 4 Upgrading to vCenter Server 5.0 n If you are using a bundled database for VirtualCenter 2.5 Update 6 or later or vCenter Server 4.x, make sure that named pipes are not disabled and that the pipe name is correct. Change the default pipe name to \\.\pipe\sql\query. n If you are using a bundled database, do not change the DSN name. Use "VMware VirtualCenter' for the DSN name. If you change the DSN name, the backup operation will fail.
vSphere Upgrade 3 Test the connectivity. The system now has a DSN that is compatible with vCenter Server. When the vCenter Server installer prompts you for a DSN, select the 64-bit DSN. Restore the vCenter Server Configuration and Install vCenter Server on the Destination Machine Use the data migration tool to start the vCenter Server installer and restore the vCenter Server configuration to the destination machine.
Chapter 4 Upgrading to vCenter Server 5.0 n Ensure that the VIM_SQLEXP or SQLEXP_VIM databases do not exist on the destination machine. These databases might be left after you uninstall vCenter Server 4.0, 4.1, or 5.0. Installing vCenter Server on a machine that has either of those databases is not supported. Before running the data migration scripts, uninstall VIM_SQLEXP or SQLEXP_VIM databases, and any file system directories pertaining to previous vCenter Server installations.
vSphere Upgrade 13 Select the size of your vCenter Server inventory to allocate memory for several Java services that are used by vCenter Server. This setting determines the maximum JVM heap settings for VMware VirtualCenter Management Webservices (Tomcat), Inventory Service, and Profile-Driven Storage Service. You can adjust this setting after installation if the number of hosts in your environment changes. See the recommendations in the vCenter Server Hardware Requirements topic in System Requirements.
Chapter 4 Upgrading to vCenter Server 5.0 n Ensure that the destination vCenter Server machine has access to all other systems that it must connect to, such as the domain server, Windows Active Directory server with vCenter user accounts, database server, and license server. n Ensure that Microsoft .NET Framework 3.5 is installed on the destination machine. n Ensure that the VIM_SQLEXP or SQLEXP_VIM databases do not exist on the destination machine.
vSphere Upgrade 8 Select how to upgrade vCenter Agent. Option Description Automatic vCenter Agent is upgraded on all hosts in the vCenter Server inventory. Manual All hosts are disconnected from vCenter Server. To upgrade vCenter Agent, reconnect the host to vCenter Server. Select Manual if one of the following applies: n You need to control the timing of vCenter Agent upgrades on specific hosts.
Chapter 4 Upgrading to vCenter Server 5.0 18 If you used the data migration tool to back up VMware vCenter Update Manager configuration data, complete the steps in the Update Manager installation wizard to install vCenter Update Manager and restore the configuration. See Installing and Administering VMware vSphere Update Manager. 19 Check the \logs\restore.log file in the datamigration folder, and verify that no errors occurred during the restore process.
vSphere Upgrade 2 Copy the license files from the license folder on the source machine to the license folder on the destination machine. By default, the license folder is C:\Program Files\VMware\VMware License Server\Licenses\. 3 4 Reload the licenses. a Select Start > Programs > VMware > VMware License Server > VMware License Server Tools. b Click the Start/Stop/Reread tab. c Select the VMware License Server. d Click ReRead License File.
Chapter 4 Upgrading to vCenter Server 5.0 7 Paste the local appliance key into the Remote appliance key field of the old appliance. 8 Click Import remote key in the old appliance. 9 In the old appliance, copy the local appliance key. 10 Paste the local appliance key into the Remote appliance key field of the new appliance. 11 Click Import remote key in the new appliance. 12 In the new appliance, click Import, and click Start import.
vSphere Upgrade 2 3 On your chosen web server, create a repository directory under the document root: for example, vc_update_repo. 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. 6 Select Use Specified Repository. 7 For the Repository URL, enter the URL of the repository you created.
Chapter 4 Upgrading to vCenter Server 5.0 2 Right-click VMware VirtualCenter Server and select Manual. 3 Right-click VMware vCenter Management Webservices and select Manual. 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.
vSphere Upgrade 3 Click Download vSphere Client under Getting Started. 4 Click Save to download the vSphere Client installer. The vSphere Client installer is downloaded to the system. What to do next Install the vSphere Client. Upgrade the vSphere Client Virtual machine users and vCenter Server administrators must use the vSphere Client 5.0 to connect to vCenter Server 5.0 or to connect directly to ESX 5 hosts. You can install the VI Client 2.5, the vSphere Client 4.x, and vSphere Client 5.
Chapter 4 Upgrading to vCenter Server 5.0 If you cannot connect to the vCenter Server system, you might need to start the VMware VirtualCenter Server service manually. To start the service, in the Settings menu, select Control Panel > Administrative Tools > Services > VMware VirtualCenter Server. The machine might require several minutes to start the service. Using a License Server to Manage Version 3.5 ESX or ESXi Hosts vCenter Server 5.0 requires a license server to manage ESX/ESXi version 3.5 hosts.
vSphere Upgrade Linked Mode Considerations for vCenter Server Consider several issues before you configure a Linked Mode group. Before you configure a Linked Mode group, consider the following issues. n If you upgrade a vCenter Server that is part of a Linked Mode group, it will be removed from the group. vCenter Server does not support Linked Mode groups that contain both version 5.0 and earlier versions of vCenter Servers. After all vCenter Servers in the group are upgraded to version 5.
Chapter 4 Upgrading to vCenter Server 5.0 n The vCenter Server instances in a Linked Mode group can be in different domains if the domains have a two-way trust relationship. Each domain must trust the other domains on which vCenter Server instances are installed. n When adding a vCenter Server instance to a Linked Mode group, the installer must be run by a domain user who is an administrator on both the machine where vCenter Server is installed and the target machine of the Linked Mode group.
vSphere Upgrade 7 Click Finish. vCenter Server restarts. Depending on the size of your inventory, the change to Linked Mode might take from a few seconds to a few minutes to complete. The vCenter Server instance is now part of a Linked Mode group. It might take several seconds for the global data (such as user roles) that are changed on one machine to be visible on the other machines. The delay is usually 15 seconds or less.
Chapter 4 Upgrading to vCenter Server 5.0 n VMware Infrastructure 3 license file or a running license server when you are restoring VirtualCenter 2.5. n Database backup files. n SSL files found in: %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\SSL on the VirtualCenter or vCenter systems. n Notes from the original installation regarding the selections, settings, and information used. n vpxd.cfg files. n vCenter Server and ESX/ESXi license keys.
vSphere Upgrade Table 4‑7. Datastore and Network Permission Requirements (Continued) Object Before Upgrade Privilege After Upgrade Privilege Action Required to Enable Access Network Nonpropagating Read-only No Access Assign access privileges for networks or network folders. Propagating Read-only Assign Network None. NOTE The Read-only propagating permission on a datacenter, as well as all other permissions you have set, will continue to work as expected after the upgrade.
Chapter 4 Upgrading to vCenter Server 5.0 Update Datastore Permissions You must change Read-only nonpropagating datastore permissions to propagating datastore permissions in order for users to access the datastores. You can assign datastore permissions on datastores or folders containing datastores. Prerequisites Before performing the upgrade procedure, determine which users need access to each datastore and which privileges each user needs.
vSphere Upgrade Network Privileges In VMware vSphere 4.0 and higher, networks have their own set of access control privileges. As a result, you might need to reconfigure your permissions to grant the new network privileges. This is required if you have nonpropagating Read-only permission set on the datacenter. Table 4-9 lists the default network privileges that, when selected for a role, can be paired with a user and assigned to a network. Table 4‑9.
Chapter 4 Upgrading to vCenter Server 5.0 5 In the Assigned Role pane, do one of the following: n To assign specific network privileges defined in a role by your company, choose the custom role. NOTE The Read-only propagating permission on a datacenter, in addition to all permissions you have set, will be kept intact after the upgrade. n To migrate read-only nonpropagating datacenter permissions to propagating network permissions, choose Network Consumer (sample).
vSphere Upgrade 72 VMware, Inc.
Upgrading Update Manager 5 You can upgrade Update Manager 1.0 Update 6 and Update Manager 4.x to Update Manager 5.0. You can install Update Manager 5.0 only on a 64-bit operating system. If you are running an earlier version of Update Manager on a 32-bit platform, you must either back up and restore your database manually, or use the data migration tool to back up the existing data on the 32-bit machine, and then restore your data on the 64-bit machine on which you are installing Update Manager 5.0.
vSphere Upgrade Procedure 1 Upgrade vCenter Server to a compatible version. NOTE The vCenter Server installation wizard warns you that Update Manager is not compatible when vCenter Server is upgraded. If prompted, you must restart the machine that is running vCenter Server. Otherwise, you might not be able to upgrade Update Manager. 2 In the software installer directory, double-click the autorun.exe file at C:\installer_location, and select vSphere Update Manager. If you cannot launch the autorun.
Chapter 5 Upgrading Update Manager You upgraded the Update Manager server. What to do next Upgrade the Update Manager Client plug-in. Upgrade the Update Manager Client Plug-In The Update Manager server and the Update Manager Client plug-in must be of the same version. Prerequisites Upgrade the Update Manager server. Procedure 1 Connect the vSphere Client to a vCenter Server system with which Update Manager is registered. 2 Select Plug-ins > Manage Plug-ins.
vSphere Upgrade 76 VMware, Inc.
Upgrading and Migrating Your Hosts 6 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 to ESXi 5.0. These topics are intended for administrators who are upgrading ESX, ESXi, and virtual machines from ESX 4.x/ESXi 4.x to ESXi 5.0.
vSphere Upgrade n Make sure your system hardware complies with ESXI 5.0 requirements. See Chapter 3, “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. Server hardware for ESXi 5.0 must be 64-bit compatible. Intel VT must be enabled in the host BIOS.
Chapter 6 Upgrading and Migrating Your Hosts Migrating ESX 4.x Files and Settings to ESXi 5.0 The upgrade process preserves as much of the ESX host configuration as possible. However, because of the architectural differences between ESX 4.x and ESXi 5.0 architecture, many configuration files cannot be migrated when you select the Migrate option in the ESXi installation or upgrade wizard. Pertinent VMware files, such as /etc/vmware/esx.
vSphere Upgrade Table 6‑1. Files Migrated During Migration or Upgrade to ESXi (Continued) File Migrated Comments /etc/yp.conf Not migrated. NIS is not supported in ESXi. /etc/krb.conf Needed for Likewise to have Active Directory support. /etc/krb.realms /etc/krb5.conf /etc/krb5.acl /etc/krb5.keytab /etc/krb5.log /etc/krb5.mkey /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.
Chapter 6 Upgrading and Migrating Your Hosts Table 6‑1. Files Migrated During Migration or Upgrade to ESXi (Continued) File Migrated Comments /etc/vmware/vmauth/provider.xml /etc/hosts Migrated. /etc/resolv.conf Migrated. /usr/lib/vmware Not migrated. /etc/fstab Partially migrated. Only NFS entries will be migrated to ESXi. /etc/passwd Partially migrated. Only the root user password will be saved, if possible. /etc/shadow /etc/groups Not migrated.
vSphere Upgrade SSH Configuration Affected by Upgrading or Migrating to ESXi 5.0 The host SSH configuration is migrated only for upgrades from ESXi 4.1 to ESXi 5.0 SSH configuration is not migrated for ESX 4.x hosts or ESXi 4.0 hosts. For these hosts, SSH access is disabled during the upgrade or migration process. You can reenable SSH access in the direct console. See the information on enabling SSH access in the vSphere Installation and Setup documentation. Networking Changes in ESXi 5.0 Some ESX 4.
Chapter 6 Upgrading and Migrating Your Hosts If any of your ESX hosts require the Service Console port group to support an existing service, you can write a firstboot script to recreate the port group after the migration. See the information on the %firstboot command in “Installation and Upgrade Script Commands,” on page 117. Partitioning Changes from ESX 4.x to ESXi 5.0 The ESXi partition scheme used in ESXi 5.0 differs from that of earlier ESX and ESXi versions. ESXi 5.
vSphere Upgrade For systems in which the VMFS partition is placed on a different drive from the boot drive, the entire contents of the boot drive is overwritten during the upgrade. Any extra data on the disk is erased. ESXi 5.0.x Upgrade and Update Options VMware provides several ways to upgrade and update 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.
Chapter 6 Upgrading and Migrating Your Hosts Table 6‑2. ESXi 5.0.x Upgrade and Update Methods Upgrade or Update Method Upgrade from ESX or ESXi 4.x to ESXi 5.0.x Update or Patch from ESXi 5.0 to ESXi 5.0.x vSphere Update Manager yes yes Interactive upgrade or update from CD, DVD, or USB drive yes yes Scripted upgrade or update yes yes vSphere Auto Deploy no yes, if the ESXi 5.
vSphere Upgrade Table 6‑3. ESX/ESXi 4.0 U3 and 4.1 U1 Third-Party VIBs That Cannot Be Migrated to ESXi 5.0. 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 4.1 Upgrade 1 ESX410-201101223-UG cross_vmware-esx-driversscsi-3w-9xxx_400.2.26.08.036vm40-1OE M 4.0 Upgrade 3 ESX400-201105213-UG cross_vmware-esx-driversscsi-3w-9xxx_400.2.26.08.036vm40-1OE M Supported Upgrades and Updates to ESXi 5.0.x You can update an ESXi 5.
Chapter 6 Upgrading and Migrating Your Hosts Table 6‑4. Supported Scenarios for Upgrade or Migration to ESXi 5.0.x (Continued) Scenario for Upgrade, Migration, or Update to ESXi 5.0.x Support 4.x ESX host on a SAN or SSD Partially supported. You can upgrade the host as you would a normal ESX 4.x host, but no provisions will be made to optimize the partitions on the disk. To optimize the partition scheme on the host, perform a fresh installation. 4.x ESX host, missing Service Console .
vSphere Upgrade n PXE boot from the network. “PXE Booting the ESXi Installer,” on page 91 n Boot from a remote location using a remote management application. See “Using Remote Management Applications,” on page 99 Download and Burn the ESXi Installer ISO Image to a CD or DVD If you do not have an ESXi installation CD/DVD, you can create one. You can also create an installer ISO image that includes a custom installation script.
Chapter 6 Upgrading and Migrating Your Hosts 2 Create a partition table on the USB flash device. /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 a to set the active flag on partition 1. e Type p to print the partition table.
vSphere Upgrade The instructions in this procedure assume that the USB flash drive is detected as /dev/sdb. NOTE The ks file containing the installation or upgrade script cannot be located on the same USB flash drive that you are using to boot the installation or upgrade. Prerequisites n Linux machine n ESXi installation or upgrade script, the ks.cfg kickstart file n USB flash drive Procedure 1 Attach the USB flash drive to a Linux machine that has access to the installation or upgrade script.
Chapter 6 Upgrading and Migrating Your Hosts Create an Installer ISO Image with a Custom Installation or Upgrade Script You can customize the standard ESXi installer ISO image with your own installation or upgrade script. This enables you to perform a scripted, unattended installation or upgrade when you boot the resulting installer ISO image. See also “About Installation and Upgrade Scripts,” on page 117 and “About the boot.cfg File,” on page 125. Prerequisites n Linux machine.
vSphere Upgrade PXE booting requires some network infrastructure and a machine with a PXE-capable network adapter. Most machines that are capable of running ESXi have network adapters that are able to PXE boot. NOTE Ensure that the Auto Deploy server has an IPv4 address. PXE booting is supported only with IPv4.
Chapter 6 Upgrading and Migrating Your Hosts Figure 6‑1. Overview of PXE Boot Installation Process ESXi target host UDP DHCP server IP & TFTP server UDP TFTP server Give me an IP for the virtual network adapter Give me the network boot loader gpxelinux.0 or pxelinux.0 TCP for gPXELINUX UDP for PXELINUX Web server kernel UDP DHCP server Give me an IP for the kernel IP TCP scripts depot Give me the kernel Give me an installation script Installer starts ks.
vSphere Upgrade gPXE Example This example shows how to configure a ISC DHCP version 3.0 server to enable gPXE. allow booting; allow bootp; # gPXE options option space gpxe; option gpxe-encap-opts code 175 = encapsulate gpxe; option gpxe.bus-id code 177 = string; class "pxeclients" { match if substring(option vendor-class-identifier, 0, 9) = "PXEClient"; next-server TFTP server address; if not exists gpxe.bus-id { filename "/gpxelinux.
Chapter 6 Upgrading and Migrating Your Hosts Required Files In the PXE configuration file, you must include paths to the following files: n mboot.c32 is the boot loader. n boot.cfg is the boot loader configuration file. See “About the boot.cfg File,” on page 125 File Name for the PXE Configuration File For the file name of the PXE configuration file, select one of the following options: n 01-mac_address_of_target_ESXi_host.
vSphere Upgrade 2 On the Linux machine, install PXELINUX. PXELINUX is included in the SYSLINUX package. Extract the files, locate the pxelinux.0 file and copy it to the /tftpboot directory on your TFTP server. 3 Configure the DHCP server to send the following information to each client host: n The name or IP address of your TFTP server. n The name of your initial boot file. This is pxelinux.0. 4 Copy the contents of the ESXi installer image to the /var/lib/tftpboot directory on the TFTP server.
Chapter 6 Upgrading and Migrating Your Hosts n Server with a hardware configuration that is supported with ESXi 5.0. 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 117. n Network adapter with PXE support on the target ESXi host n IPv4 networking.
vSphere Upgrade PXE Boot the ESXi Installer Using gPXE You can PXE boot the ESXi installer using gPXE. See also “About Installation and Upgrade Scripts,” on page 117 and “About the boot.cfg File,” on page 125 Prerequisites Verify that your environment has the following components: n The ESXi installer ISO image downloaded from the VMware Web site n HTTP Web server that is accessible by your target ESXi hosts n DHCP server configured for PXE booting: /etc/dhcpd.
Chapter 6 Upgrading and Migrating Your Hosts Using Remote Management Applications Remote management applications allow you to install ESXi on servers that are in remote locations. Remote management applications supported for installation include HP Integrated Lights-Out (iLO), Dell Remote Access Card (DRAC), IBM management module (MM), and Remote Supervisor Adapter II (RSA II).
vSphere Upgrade The wizard workflows prevent erroneous upgrade sequences. For example, the wizard prevents you from upgrading virtual machine hardware before you upgrade hosts in a cluster. You can use Distributed Resource Scheduler (DRS) to prevent virtual machine downtime during the upgrade process. Update Manager monitors hosts and virtual machines for compliance against your defined upgrade baselines. Noncompliance appears in detailed reports and in the dashboard view.
Chapter 6 Upgrading and Migrating Your Hosts Within a cluster, you should select to temporarily disable HA admission control to allow vMotion to proceed, in order to prevent downtime of the machines on the hosts you remediate. After the remediation of the entire cluster, Update Manager restores HA admission control settings.
vSphere Upgrade 5 Create a Host Baseline Group on page 106 You can combine one host upgrade baseline with multiple patch or extension baselines, or combine multiple patch and extension baselines in a baseline group. 6 Attach Baselines and Baseline Groups to Objects on page 107 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.
Chapter 6 Upgrading and Migrating Your Hosts 3 (Optional) Select Retry entering maintenance mode in case of failure, specify the retry delay, and the number of retries. If a host fails to enter maintenance mode before remediation, 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.
vSphere Upgrade 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.
Chapter 6 Upgrading and Migrating Your Hosts 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.
vSphere Upgrade 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.
Chapter 6 Upgrading and Migrating Your Hosts 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.
vSphere Upgrade 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.
Chapter 6 Upgrading and Migrating Your Hosts 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.0. Procedure 1 On the Home page of the vSphere Client, select Hosts and Clusters and click the Update Manager tab.
vSphere Upgrade 12 (Optional) Select Disable any removable media devices connected to the virtual machine on the host. Update Manager does not remediate hosts on which virtual machines have connected CD, DVD, or floppy drives. In cluster environments, connected media devices might prevent vMotion if the destination host does not have an identical device or mounted ISO image, which in turn prevents the source host from entering maintenance mode.
Chapter 6 Upgrading and Migrating Your Hosts Remediate Hosts Against Baseline Groups You can remediate hosts against attached groups of upgrade, patch, and extension baselines. Baseline groups might contain multiple patch and extension baselines, or an upgrade baseline combined with multiple patch and extension baselines. You can perform an orchestrated upgrade by using a host baseline group. The upgrade baseline in the baseline group runs first, followed by patch and extension baselines.
vSphere Upgrade 12 On the Host Remediation Options page, from the Power state drop-down menu, you can select the change in the power state of the virtual machines and virtual appliances that are running on the hosts to be remediated. Option Description Power Off virtual machines Power off all virtual machines and virtual appliances before remediation. Suspend virtual machines Suspend all running virtual machines and virtual appliances before remediation.
Chapter 6 Upgrading and Migrating Your Hosts Option Details Disable Fault Tolerance (FT) if it is enabled for the VMs on the selected hosts. If FT is turned on for any of the virtual machines on a host, Update Manager does not remediate that host. For FT to be enabled, the hosts on which the Primary and Secondary virtual machines run must be of the same version and must have the same patches installed. If you apply different patches to these hosts, FT cannot be re-enabled.
vSphere Upgrade n Verify that the server hardware clock is set to UTC. This setting is in the system BIOS. n ESXi Embedded must not be on the host. ESXi Installable and ESXi Embedded cannot exist on the same host. Procedure 1 Insert the ESXi installer CD/DVD into the CD/DVD-ROM drive, or attach the Installer USB flash drive and restart the machine. 2 Set the BIOS to boot from the CD-ROM device or the USB flash drive. See your hardware vendor documentation for information on changing boot order.
Chapter 6 Upgrading and Migrating Your Hosts For a scripted installation, upgrade, or migration, you must use the supported commands to create a script. and edit the script to change settings that are unique for each host.
vSphere Upgrade 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.000 Boot Options When you perform a scripted installation, you might need to specify options at boot time to access the kickstart file. Supported Boot Options Table 6‑5.
Chapter 6 Upgrading and Migrating Your Hosts Table 6‑5. Boot Options for ESXi Installation (Continued) Boot Option Description netmask=subnet mask Specifies subnet mask for the network interface that downloads the installation script and the installation media. vlanid=vlanid Configure the network card to be on the specified VLAN. About Installation and Upgrade Scripts The installation/upgrade script is a text file, for example ks.cfg, that contains supported commands.
vSphere Upgrade Clears any existing partitions on the disk. Requires install command to be specified. --drives= Remove partitions on the specified drives. --alldrives Ignores the --drives= requirement and allows clearing of partitions on every drive. --ignoredrives= Removes partitions on all drives except those specified. Required unless the --drives= or --alldrives flag is specified. --overwritevmfs Permits overwriting of VMFS partitions on the specified drives.
Chapter 6 Upgrading and Migrating Your Hosts You can change the order of the disks by using a comma separated list appended to the argument. If you provide a filter list, the default settings are overridden. You can combine filters to specify a particular disk, including esx for the first disk with ESX installed on it, model and vendor information, or the name of the vmkernel device driver.
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 the 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 6 Upgrading and Migrating Your Hosts n Turkish n US Dvorak n Ukranian n United Kingdom network (optional) Specify a network address for the system. --bootproto=[dhcp| static] Specify whether to obtain the network settings from DHCP or set them manually. --device= Specifies either the MAC address of the network card or the device name, in the form vmnicNN, as in vmnic0. This options refers to the uplink device for the virtual switch.
vSphere Upgrade 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. Only one partition can be specified per disk and it can only be a VMFS partition datastore name Specifies where the partition is to be mounted --ondisk= or --ondrive= Specifies the disk or drive where the partition is created. --firstdisk= disk-type1, Partitions the first eligible disk found.
Chapter 6 Upgrading and Migrating Your Hosts 2 Network storage (remote) 3 USB disks (usb) You can change the order of the disks by using a comma separated list appended to the argument. If you provide a filter list, the default settings are overridden. You can combine filters to specify a particular disk, including esx for the first disk with ESX installed on it, model and vendor information, or the name of the vmkernel device driver.
vSphere Upgrade %firstboot Creates an init script that runs only during the first boot. The script has no effect on subsequent boots. If multiple %firstboot sections are specified, they run in the order that they appear in the kickstart file. NOTE You cannot check the semantics of %firstboot scripts until the system is booting for the first time. A %firstboot script might contain potentially catastrophic errors that are not exposed until after the installation is complete.
Chapter 6 Upgrading and Migrating Your Hosts Disk Device Names The install, upgrade, and installorupgrade installation script commands require the use of disk device names. Table 6‑6. Disk Device Names Format Examples Description VML vml.00025261 The device name as reported by the vmkernel MPX mpx.vmhba0:C0:T0:L0 The device name NOTE When you use a scripted upgrade to upgrade from ESX 4.x to ESXi 5.0, the MPX and VML disk names change, which might cause the upgrade to fail.
vSphere Upgrade Install, Upgrade, or Migrate ESXi from a CD or DVD Using a Script You can install, upgrade, or migrate ESXi from a CD/DVD drive using a script that specifies the installation or upgrade options. You can start the installation or upgrade script by entering a boot option when you start the host. You can also create an installer ISO image that includes the installation script.
Chapter 6 Upgrading and Migrating Your Hosts 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 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.0 provides many options for PXE booting the installer and using an installation or upgrade script.
Chapter 6 Upgrading and Migrating Your Hosts Reprovision Hosts with Simple Reboot Operations A simple reboot of a host that is provisioned with Auto Deploy requires only that all prerequisites are still met. The process uses the previously assigned image profile, host profile, and vCenter Server location. Setup includes DHCP server setup, writing rules, and making an image available to the Auto Deploy infrastructure.
vSphere Upgrade 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. Connect-VIServer myVCServer The cmdlet might return a server certificate warning. In a production environment, make sure no server certificate warnings result. In a development environment, you can ignore the warning.
Chapter 6 Upgrading and Migrating Your Hosts 3 When prompted, provide the user input. You can now direct the host to exit maintenance mode. The user input information is saved in an answer file. The next time you boot, the answer file information is applied to the host. One answer file per host is available. Assign a Host Profile to Hosts Auto Deploy can assign a host profile to one or more hosts.
vSphere Upgrade What to do next n Upgrade existing hosts to use the new host profile by performing compliance test and repair operations on those hosts. See “Test and Repair Rule Compliance,” on page 132. n Turn on unprovisioned hosts to provision them with the host profile. Test and Repair Rule Compliance When you add a rule to the Auto Deploy rule set or make changes to one or more rules, hosts are not updated automatically.
Chapter 6 Upgrading and Migrating Your Hosts Upgrading Hosts by Using esxcli Commands Using the vSphere CLI, you can patch ESXi 5.0 hosts. You cannot use esxcli commands to upgrade version 4.x ESX or ESXi hosts to ESXi 5.0. To upgrade version 4.x ESX or ESXi hosts to ESXi 5.0, use vSphere Update Manager, or perform an interactive or scripted upgrade. To use esxcli vCLI commands, you must install vSphere CLI (vCLI).
vSphere Upgrade The acceptance level of all VIBs on a host must be at least as high as the host acceptance level. For example, if the host acceptance level is VMwareAccepted, you can install VIBs with acceptance levels of VMwareCertified and VMwareAccepted, but you cannot install VIBs with acceptance levels of PartnerSupported or CommunitySupported.
Chapter 6 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. Prerequisites Install vCLI or deploy the vSphere Management Assistant (vMA) virtual machine.
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 6 Upgrading and Migrating Your Hosts 2 Run one of the following commands for each virtual machine to power off all virtual machines running on the ESXi host. Option Command To have the system try to shut down the guest operating system vmware-cmd --server=server_name path_to_vm stop soft To force the power off operation vmware-cmd --server=server_name path_to_vm stop hard Alternatively, to avoid powering off virtual machines, you can migrate them to another host.
vSphere Upgrade 3 Update the existing VIBs to include the VIBs in the depot or install new VIBs.
Chapter 6 Upgrading and Migrating Your Hosts 3 Update the existing image profile to include the VIBs or install new VIBs. IMPORTANT The software profile update command updates existing VIBS with the corresponding VIBs from the specified profile, but does not affect other VIBs installed on the target server. The software profile install command installs the VIBs present in the depot image profile, and removes any other VIBS installed on the target server.
vSphere Upgrade n Determine whether the update requires the host to be in maintenance mode or to be rebooted. If necessary, place the host in maintenance mode. See “Determine Whether an Update Requires the Host to Be in Maintenance Mode or to Be Rebooted,” on page 135. See “Place a Host in Maintenance Mode,” on page 136. 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.
Chapter 6 Upgrading and Migrating Your Hosts 5 Remove the VIB. esxcli --server=server_name software vib remove --vibname=name Specify one or more VIBs to remove in one of the following forms: n name n name:version 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.
vSphere Upgrade 2 Review the output that is returned. The output shows which VIBs will be installed or removed and whether the installation or update requires a reboot. 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.
Chapter 6 Upgrading and Migrating Your Hosts 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.
vSphere Upgrade Table 6‑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.
Chapter 6 Upgrading and Migrating Your Hosts 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 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.
vSphere Upgrade Procedure 1 From the vSphere Client, select the host in the inventory. 2 Click the Configuration tab. 3 Under Software, click Licensed Features. 4 Click Edit next to ESXi License Type. 5 Click (No License Key). 6 Click OK to save your changes. You can now access all the features of ESXi. 146 VMware, Inc.
Upgrading Virtual Machines 7 After you perform an ESX/ESXi upgrade, VMware recommends that you upgrade all the virtual machines that reside on the host. Upgrading virtual machines ensures that they remain compatible with the upgraded host software, and can take advantage of new features. The first step in upgrading virtual machines is to upgrade VMware Tools. If the virtual machines do not have VMware Tools installed, you can use the VMware Tools upgrade procedure to install VMware Tools.
vSphere Upgrade n “Perform an Automatic Upgrade of VMware Tools,” on page 162 n “Upgrade VMware Tools on Multiple Virtual Machines,” on page 163 n “Configure a Virtual Machine to Upgrade VMware Tools Automatically,” on page 164 n “Upgrade Virtual Hardware,” on page 165 n “Upgrade Virtual Hardware on Multiple Virtual Machines,” on page 166 n “Uninstall VMware Tools,” on page 166 About VMware Tools VMware Tools improves the performance and management of the virtual machine.
Chapter 7 Upgrading Virtual Machines For Windows and Linux guest operating systems, you can configure the virtual machine to automatically upgrade VMware Tools. Although the version check is performed when you power on the virtual machine, on Windows guest operating systems, the automatic upgrade occurs when you power off or restart the virtual machine. The status bar displays the message Installing VMware Tools ... when an upgrade is in progress.
vSphere Upgrade Virtual Machine Hardware Versions The hardware version of a virtual machine reflects the virtual machine's supported virtual hardware features. These features correspond to the physical hardware available on the ESXi host on which you create the virtual machine. Virtual hardware features include BIOS and EFI, available virtual PCI slots, maximum number of CPUs, maximum memory configuration, and other characteristics typical to hardware.
Chapter 7 Upgrading Virtual Machines Perform an Orchestrated Upgrade of Virtual Machines with vSphere Update Manager An orchestrated upgrade of virtual machines allows you to upgrade VMware Tools and the virtual hardware for the virtual machines in your vSphere inventory at the same time. You can perform an orchestrated upgrade of virtual machines at the folder or datacenter level. Update Manager makes the process of upgrading the virtual machines convenient by providing baseline groups.
vSphere Upgrade 3 Under Baseline Type, select VA Upgrade, and click Next. 4 On the Upgrade Options page, select Vendor and Appliance options from the respective drop-down menus. The options listed in these menus depend on the virtual appliance upgrades that are downloaded in the Update Manager repository. If no upgrades are downloaded in the repository, the available options are All Vendors and All Products, respectively. 5 Select an option from the Upgrade To drop-down menu.
Chapter 7 Upgrading Virtual Machines 2 In the New Baseline Group wizard, under Baseline Group Type, select Virtual Machines and Virtual Appliances Baseline Group. 3 Enter a name for the baseline group and click Next. 4 For each type of upgrade (virtual appliance, virtual hardware, and VMware Tools), select one of the available upgrade baselines to include in the baseline group. NOTE If you decide to remediate only virtual appliances, the upgrades for virtual machines are ignored, and the reverse.
vSphere Upgrade 5 In the Attach Baseline or Group window, select one or more baselines or baseline groups to attach to the object. If you select one or more baseline groups, all baselines in the groups are selected. You cannot deselect individual baselines in a group. 6 (Optional) Click the Create Baseline Group or Create Baseline links to create a baseline group or a baseline and complete the remaining steps in the respective wizard. 7 Click Attach.
Chapter 7 Upgrading Virtual Machines 2 Select the type of object for which you want to view compliance information. For example, Hosts and Clusters or VMs and Templates. 3 Select an object from the inventory. 4 Click the Update Manager tab to view the scan results and compliance states. Remediate Virtual Machines and Virtual Appliances You can manually remediate virtual machines and virtual appliances immediately, or can schedule a remediation at a time that is convenient for you.
vSphere Upgrade c Enter a name and optionally a description for the snapshot. d (Optional) Select the Take a snapshot of the memory for the virtual machine check box. 9 Click Next. 10 Review the Ready to Complete page, and click Finish. Planning Downtime for Virtual Machines Plan downtime for each virtual machine during the upgrade process. Typically, this downtime occurs during the virtual machine upgrade and the VMware Tools upgrade.
Chapter 7 Upgrading Virtual Machines Manually Install or Upgrade VMware Tools in a Windows Virtual Machine All supported Windows guest operating systems support VMware Tools. Install the latest version of VMware Tools to enhance the performance of the virtual machine's guest operating system and improve virtual machine management. When you power on a virtual machine, if a new version of VMware Tools is available, you see a notification in the status bar of the guest operating system.
vSphere Upgrade What to do next (Recommended) If you upgraded VMware Tools as part of a larger, system-wide upgrade, next upgrade to the newest virtual hardware version available for the virtual machine. Manually Install or Upgrade VMware Tools in a Linux Virtual Machine For Linux virtual machines, you manually install or upgrade VMware Tools by using the command line.
Chapter 7 Upgrading Virtual Machines 5 If the VMware Tools virtual CD-ROM image is not mounted, mount the CD-ROM drive. a If a mount point directory does not already exist, create it. mkdir /mnt/cdrom Some Linux distributions use different mount point names. For example, on some distributions the mount point is /media/VMware Tools rather than /mnt/cdrom. Modify the command to reflect the conventions that your distribution uses. b Mount the CD-ROM drive.
vSphere Upgrade What to do next (Recommended) If you upgraded VMware Tools as part of a larger, system-wide upgrade, next upgrade to the newest virtual hardware version available for the virtual machine. Manually Install or Upgrade VMware Tools in a Solaris Virtual Machine For Solaris virtual machines, you manually install or upgrade VMware Tools by using the command line.
Chapter 7 Upgrading Virtual Machines 9 Follow the instructions at the end of the script. Depending on the features you use, these instructions can include restarting the X session, restarting networking, logging in again, and starting the VMware User process. You can alternatively reboot the guest operating system to accomplish all these tasks. The VMware Tools label on the Summary tab changes to OK.
vSphere Upgrade What to do next (Recommended) If you upgraded VMware Tools as part of a larger, system-wide upgrade, next upgrade to the newest virtual hardware version available for the virtual machine. Operating System Specific Packages for Linux Guest Operating Systems For vSphere deployments, VMware provides operating system specific packages (OSPs) as a packaging and distribution mechanism for VMware Tools.
Chapter 7 Upgrading Virtual Machines 2 3 (Optional) In the Advanced Options field, enter advanced options for the guest operating system. Option Description Microsoft Windows Guest Operating Systems Enter /s /v "/qn" /l "Microsoft_Windows_location\filename.log" to perform a silent upgrade of VMware Tools and create a log file in the specified location on the guest operating system. Linux Guest Operating Systems n Enter --default to perform the default behavior.
vSphere Upgrade Configure a Virtual Machine to Upgrade VMware Tools Automatically You can configure a virtual machine to check for and apply VMware Tools upgrades each time you power on the virtual machine. Automatic VMware Tools upgrade is not supported for virtual machines with Solaris or NetWare guest operating systems. Prerequisites n Virtual machines must have a version of VMware Tools shipped with ESX 3.0.1 or later installed. n Virtual machines must be hosted on an ESX 3.0.
Chapter 7 Upgrading Virtual Machines Upgrade Virtual Hardware You can upgrade the hardware version of virtual machines to the latest version of ESXi. For virtual machines that are running on ESXi 5.x, VMware recommends that you upgrade the virtual hardware to version 8. Consider the following points: n When you upgrade from virtual hardware version 4 to version 8 the upgrade is reversible if you take a virtual machine backup or snapshot before performing the upgrade.
vSphere Upgrade 6 For Windows guest operating systems, reboot the guest operating system to make the changes take effect. The virtual hardware version is 8 on the VM Version label on the virtual machine Summary tab. Upgrade Virtual Hardware on Multiple Virtual Machines You can upgrade virtual hardware on multiple virtual machines in a single operation by using the Virtual Machines tab.
Chapter 7 Upgrading Virtual Machines n Log in to the guest operating system. Procedure u Use the appropriate operating-system-specific procedure to uninstall VMware Tools. Operating System Action Windows 7 Use the guest operating system's Programs > Uninstall a program item. Windows Vista and Windows Server 2008 Use the guest operating system's Programs and Features > Uninstall a program item. Windows XP and earlier Use the guest operating system's Add/Remove Programs item.
vSphere Upgrade 168 VMware, Inc.
Example Upgrade Scenarios 8 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 c Take a full backup of the vCenter Server database. See your database documentation. d Back up the vCenter Server SSL certificates. 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. After the upgrade, the hosts are automatically connected to vCenter Server 5.0 if you select that option during the upgrade process.
Chapter 8 Example Upgrade Scenarios n If your environment has vCenter Guided Consolidation, uninstall it before upgrading. 1 Run the vCenter Host Agent Pre-Upgrade Checker. See “Run the vCenter Host Agent Pre-Upgrade Checker,” on page 37. 2 If you have vCenter Server, upgrade to vCenter Server 5.0. See Chapter 4, “Upgrading to vCenter Server 5.0,” on page 27. The downtime required for this upgrade is based on the amount of data in the database.
vSphere Upgrade n If your environment has vCenter Guided Consolidation, uninstall it. n Run the vCenter Host Agent Pre-Upgrade Checker. See “Run the vCenter Host Agent Pre-Upgrade Checker,” on page 37. n Upgrade VirtualCenter 2.5 Update 6 or higher or vCenter Server 4.0 to vCenter Server 5.0. See Chapter 4, “Upgrading to vCenter Server 5.0,” on page 27. The downtime required for this upgrade is based on the amount of data in the database.
Chapter 8 Example Upgrade Scenarios n Verify that empty host storage is sufficient to hold a portion of your production virtual machines. Ideally, the storage is large enough to hold all of the migrated virtual machines. A larger capacity for virtual machines on this extra storage means fewer operations are required before all your virtual machines are migrated. n If your environment has vCenter Guided Consolidation, uninstall it before upgrading. n Run the vCenter Host Agent Pre-Upgrade Checker.
vSphere Upgrade The following process shows the upgrade path. 1 If you are not using a SQL Server Express database installed on the same machine as vCenter Server, create a backup of the database. 2 Run the backup.bat script of the data migration tool on the source machine to create a backup of the vCenter Server configuration. 3 Copy the configuration data to the destination machine.
Chapter 8 Example Upgrade Scenarios 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.
vSphere Upgrade 176 VMware, Inc.
Index Symbols %include command 117 %post command 117 %pre command 117 boot prompt 116 boot.cfg file 125 bootloader kernel options 116 C about vSphere Upgrade 5 acceptance levels 133 accepteula command 117 answer file 130 Apply-EsxImageProfile cmdlet 129 attaching baseline 107, 153 baseline group 107, 153 Auto Deploy rebooting 129 reprovisioning hosts with 128 rule set compliance 132 scenario for migrating ESX/ESXi 4.
vSphere Upgrade datastore names and vCenter Server upgrades 39 datastore permissions upgrade 69 upgrading 67 datastores, privileges 68 DB2 34 depot, software 133 DHCP, for PXE booting the ESXi installer 93 directory 65 disks local 169 VMDK 27 DNS load balancing solutions and datastores in vCenter Server 39 DNS Requirements 25 download the vCenter Server installer 39 downtime during virtual hardware upgrade 156 during VMware Tools upgrade 156 vCenter Server 38 DPM 100 DRAC 25 DRS 100 dry run for esxcli inst
Index installation script customized in ISO image 91 path to 117 supported locations 117 installing, VirtualCenter Server 64 installing ESXi, scripted 114 installing the vSphere Client 62 installing VMware Tools Linux (tar installer) 158 Microsoft Windows 157 NetWare (tar installer) 161 Solaris (tar installer) 160 installorupgrade command 117 IP addresses 87 ISO image, with custom installation script 91 J JVM heap settings, recommended for vCenter Virtual Appliance 17 K keyboard command 117 kickstart com
vSphere Upgrade postupgrade considerations 144 postupgrade considerations for vCenter Server 61 pre-upgrade checker, for vCenter Agent 37 privileges, datastores 68 process for upgrading 169 PXE, configuration files 94 PXE boot ESXi installer using PXELINUX, setup procedure 95, 96, 98 PXE booted ESXi hosts, enable remediation 104 PXELINUX boot ESXi installer using 95, 98 boot ESXi installler using 96 R reboot image 142 remediation of hosts 108, 111 of virtual appliances 155 of virtual machines 155 remote m
Index network permissions 67 stage 1 27, 38 stage 4 148 Update Manager 73 Update Manager Client 75 Update Manager server 73 vCenter Server 27 vCenter Server database 30 vCenter Server on a different machine 43 virtual machine hardware 150 vSphere Client 27 upgrading ESXi, scripted 114 upgrading hosts 77 upgrading hosts using esxcli 133 upgrading virtual hardware 166 upgrading VMware Tools Linux (tar installer) 158 Microsoft Windows 157 NetWare (tar installer) 161 process overview 148 Solaris (tar installer
vSphere Upgrade install and upgrade 147, 148 upgrade procedure 175 VMware Tools installation Linux (tar installer) 158 Microsoft Windows 157 NetWare (tar installer) 161 Solaris (tar installer) 160 VMware Tools upgrade downtime 156 Linux (tar installer) 158 Microsoft Windows 157 NetWare (tar installer) 161 process 148 Solaris (tar installer) 160 VMware Tools upgrade, automatic 162 VMware vCenter Server Appliance hardware requirements 17 software requirements 20 vpxa, See vCenter Agent vSphere, upgrading com
