«If you have an existing VI3 environment, at some point you’ll probably want to upgrade it to vSphere. Before jumping right into the upgrade process, ...»
4. To begin the upgrade, click the Upgrade Host button and the Upgrade Wizard will launch.
5. At the Image Location screen, select the ISO or ZIP file of the ESX/ESXi 4.0 image that you wish to use to upgrade the host to, and click Next to continue.
6. The ISO will be validated. At the EULA screen, accept the licensing agreement and click Next to continue.
7. At the Host Credentials screen, enter the host user credentials (root) and click Next. If you have not placed the host in maintenance mode yet, you will be warned that you need to before proceeding. At the Host Compatibility Check screen, the host will be checked and any problems will be noted; if there are no problems, it will automatically go to the next screen.
8. At the Console OS Settings screen, select a datastore and size for the Service Console virtual disk file. You must choose either a local or a storage area network (SAN) datastore, as neither software iSCSI nor NFS datastores are
supported for this. If you are using a SAN datastore, it cannot be shared with other hosts and it must be zoned to only that host. The minimum size for the virtual disk is 7.82GB; however, if you want to create additional partitions inside the Service Console per the recommendations in Chapter 11, you should increase this to at least 18GB. Once you select a datastore and size, click Next to continue.
9. At the Post-Upgrade Options screen, choose whether a rollback will be attempted in case the upgrade fails. In addition, you can choose to run a post-upgrade script and also select to roll back the upgrade if the script fails. Click Next to continue.
10. At the Ready to Complete screen, click Finish to begin the upgrade. The upgrade will proceed and the status will be displayed. First the ISO image will be copied to the host, and then the host will be shut down and restarted and the upgrade will begin. The new Service Console VM will be created and partitioned, and the packages will be installed inside it; then it will reboot again once it is complete.
When the host restarts you will get a message that the upgrade has succeeded. If the upgrade failed for whatever reason, you should restart the Host Update utility before trying again. You can also view the log located on the host in the /var/log/vmware/vua.log file. If the host shows Disconnected in vCenter Server afterward, right-click on it and select Connect. Finally, exit maintenance mode, and the upgrade will be complete and your host will be ready to use.
USING UPDATE MANAGERUpdate Manager uses baselines that are created and then used to determine if a host is compliant with the specification of the baseline. If it is not, the host is remediated to bring it into compliance with the baseline. To upgrade hosts to vSphere with Update Manager, you need to first create a new upgrade baseline for vSphere 4.0. Once you create the baseline, you attach it to the host and then the upgrade begins. To create a new baseline, follow these steps.
1. Launch Update Manager from the vSphere Client, select the Baseline and Groups tab, and then select the Upgrade Baselines tab below it.
2. Click the Create link to create an Upgrade Baseline.
3. At the Baseline Name & Type screen, enter a name for the baseline and choose the Host Upgrade baseline type; click Next to continue.
304 CHAPTER 12 UPGRADING TO VSPHERE
4. At the Upgrade Version screen, select an upgrade ISO file to use for ESX hosts and an upgrade ZIP file to use for ESXi hosts. These files are available on the vSphere download page on VMware’s website. Once you click Next, the files will be uploaded to the Update Manager server and imported.
5. At the COS VMDK Location screen, choose to automatically use a datastore which will use a local datastore, or manually choose a datastore instead.
Click Next to continue.
6. At the Post-upgrade Options screen, choose whether a rollback will be attempted in case the upgrade fails. In addition, you can choose to run a post-upgrade script and select to roll back the upgrade if the script fails.
Click Next to continue.
7. At the Ready to Complete screen, click Finish to create the baseline.
Now that you have a baseline created, you can attach it to your VI3 hosts to bring them into compliance with the baseline. When you attach the baseline to your hosts, your hosts will be evaluated, and if they are not in compliance with the baseline, they will be upgraded to bring them into compliance. Follow these steps to attach the baseline to a host.
1. In the Hosts and Clusters tab, select the VI3 host that you want to upgrade to vSphere, and in the right pane select the Update Manager tab.
2. Click the link to Attach the vSphere upgrade baseline to the host.
3. Once the baseline is attached, click the Remediate button to begin the process of upgrading the host to make it compliant.
4. The Remediation Wizard will launch; at the Remediation Selection screen, select the Upgrade baseline and click Next to continue.
5. At the EULA screen, accept the licensing agreement and click Next to continue.
6. At the ESX 4.0 Upgrade screen, you have the option to change the COS VMDK Location, Rollback on Failure, and Post-upgrade Script settings.
These settings will display even if you are upgrading an ESXi host, in which case you can ignore them. Click Next to continue.
7. At the Host Remediation Options screen, choose to have the remediation occur immediately, or scheduled for a later time. In addition, you can specify failure options for when the host is placed in maintenance mode.
If VMs cannot be powered off or VMotioned to other hosts, you can specify to retry, fail the task, power them off, or suspend them. Click Next to continue.
PHASE 2: UPGRADING ESX AND ESXI 305
8. At the Ready to Complete screen, click Finish to begin the remediation. The host will automatically enter maintenance mode and restart, and the upgrade will begin.
Once the remediation completes, the host will show as compliant and will automatically exit maintenance mode. If the upgrade fails, you can check the logs to try to find out why. On ESXi hosts, you can use the vSphere Client to export the logs, which are located in /esx3–installation/esx4–upgrade/ and /var/log/vmware/. For ESX hosts, the logs are located in /esx4–upgrade/ and /var/log/vmware/ on the host server.
POST-UPGRADE CONSIDERATIONSOnce you upgrade your hosts, there are some steps you may need to perform afterward to clean them up.
If vCenter Server manages the host, you must reconnect the host to vCenter G Server by right-clicking the host in the vCenter Server inventory and selecting Connect.
When the upgrade is complete, ESX/ESXi is in evaluation mode. Evaluation G mode lasts for 60 days. You must assign an upgraded license to your product within 60 days of the upgrade.
After the ESX/ESXi upgrade, third-party agents are disabled but remain on G the disk. To reenable them, you must reinstall them. You can use the vihostupdate vSphere CLI command to install third-party extensions.
For ESX hosts only, the web access service is disabled by default in vSphere G as a security measure. If you want to enable it, follow these steps.
1. Log in to the ESX Service Console.
2. Type service vmware–webAccess status to check the status of the service.
3. Type service vmware–webAccess start to start the service. The service will run only until the host is restarted.
4. To have the service start each time the host boots, type chkconfig ––level 345 vmware–webAccess on.
Once you have determined the upgrade is stable, you can remove the ESX3 G instance from the bootloader menu that displays when the host starts up.
This removes the ability to roll back to ESX3 and deletes the ESX3 files from the /boot directory, deletes the ESX3 references from the /etc/fstab 306 CHAPTER 12 UPGRADING TO VSPHERE
the VMware License Server application from the vCenter Server.
PHASE 3: UPGRADING VIRTUAL MACHINESAfter you upgrade your hosts to vSphere, you need to upgrade your VMs as well. This includes upgrading the virtual hardware from version 4 that is used in VI3 to version 7 that is used in vSphere, and also upgrading VMware Tools to the latest version. However, if there is a possibility that the VMs will be migrated to a VI3 host due to a VMotion, HA, or DRS event, you should wait as the version 7 VM hardware is not supported on VI3 hosts. There are two ways you can upgrade both the virtual hardware and VMware Tools. You can use the vSphere Client and upgrade VMs one by one, or you can use Update Manager and update many VMs at once. You must first power off the VMs to upgrade their virtual hardware. VMware Tools upgrades can be done while the VM is powered on, but Windows VMs must be restarted afterward. The process for upgrading Windows VMs is as follows.
1. Make sure the VMs are powered on, open the console for the VM, and log in to the guest OS.
2. Select the VM in the vSphere Client, right-click on it, and select Guest and then Install/Upgrade VMware Tools.
3. Choose either an Interactive or Automatic upgrade. The Interactive option allows you to select which components to install. The Automatic option will install VMware Tools without prompts and automatically restart the VM afterward.
To upgrade VMware Tools on multiple VMs at once, follow these steps.
1. Select a host in the left pane, and then select the Virtual Machine tab.
2. Hold the Ctrl key while clicking on multiple powered-on VMs.
3. Once you have selected them all, right-click and select Guest→Install/Upgrade VMware Tools.
To configure VMs to automatically upgrade VMware Tools when they boot, follow these steps.
1. Power off the VM.
2. Edit the settings of the VM.
3. On the Options tab, select VMware Tools in the left pane, and in the right pane under Advanced, put a checkmark by the “Check and upgrade Tools before each power-on” field.
The next time the VM is powered on it will install or upgrade VMware Tools automatically and restart if necessary.
UPGRADING VIRTUAL MACHINE HARDWAREUpgrading virtual hardware from version 4 to version 7 is reversible if you take a VM backup or snapshot before performing the upgrade. If you do not take a snapshot before upgrading, you must use vCenter Converter to create a new VM with version 4 hardware. VMs must be powered off when their virtual hardware is upgraded. Also make sure you upgrade VMware Tools before upgrading virtual hardware. To upgrade the virtual hardware of a VM, follow these steps.
1. Power off the VM.
2. Select the VM in the vSphere Client, right-click on it, and select Upgrade Virtual Hardware.
308 CHAPTER 12 UPGRADING TO VSPHERE
3. Choose Yes at the confirmation message and the upgrade will proceed.
4. Power on the VM.
5. Log in to Windows. Restart once the new devices are detected.
To upgrade virtual hardware on multiple VMs at once, follow these steps.
1. Select a host in the left pane, and then select the Virtual Machine tab.
2. Hold the Ctrl key while clicking on multiple powered-off VMs.
3. Once you have selected them all, right-click and select Upgrade Virtual Hardware.
USING UPDATE MANAGER TO UPGRADE VMWARE TOOLS AND
VIRTUAL HARDWAREYou can also use Update Manager to upgrade VMware Tools on VMs. Baselines have already been created for VMs to upgrade their VMware Tools and virtual hardware version to match the host, as shown in Figure 12.2.
Figure 12.2 Upgrading virtual hardware and VMware Tools using baselines To upgrade VMs using Update Manager, just attach those baselines to the VMs and remediate them, and they will automatically be upgraded.
SUMMARY Upgrading your virtual environment to vSphere is exciting, as you can finally start using the many new features that are available in vSphere. It is best to get some experience using vSphere before upgrading so that you are better prepared to use it. Read through the documentation, set up a test lab if you can, and look through the Upgrade Center web page (www.vmware.com/products/vsphere/upgrade-center/) on VMware’s website.
There are many great guides, tools, and videos that can help prepare you for