© 2011 VMware Inc. All rights reserved Introducing VMware vSphere 5.0 Module 2

© 2011 VMware Inc. All rights reserved

Introducing VMware vSphere 5.0

Module 2

2-2


VMware vSphere: What’s New – Revision A

You Are Here

VMware vSphere:What’s New

Course Introduction

Introducing vSphere 5.0

Virtual Machine Management

Network Management

Storage Management

Scalability

High Availability

New Alternatives for Deploying vSphere

2-3



Importance

To implement and effectively use VMware vSphere® 5.0, you must understand its new components, new features, and key enhancements.

2-4



Learner Objectives

After this module, you should be able to do the following:

Discuss key enhancements to the vSphere components:

• VMware ESXi™

• VMware vCenter Server™

• VMware vSphere® Update Manager

Discuss the enhancements made to:

• ESXi interactive installation

• ESXi scripted installation

Upgrade vCenter Server to version 5.0.

Upgrade Update Manager to version 5.0.

Install VMware vSphere® Client™ 5.0.

Upgrade VMware ESX® 4.1 to ESXi 5.0.

2-5



What’s New in vSphere 5.0?

vSphere 5.0 is the first release to offer only the ESXi hypervisor architecture.

vSphere 5.0 does not include ESX.

• The service console no longer exists.

• VMware vSphere® Command-Line Interface and VMware vSphere® PowerCLI are available for command-line administration.

vCenter Server 5.0 can still manage ESX hosts (3.5 and 4.x).

The upgrade process upgrades ESX/ESXi 4.x to ESXi 5.0.

vCenter Server 5.0

2-6



New ESXi Hardware Maximums

New for ESXi 5.0:

2TB host memory

Up to 160 logical CPUs

512 virtual machines per host

2,048 virtual CPUs per host

2TB160 LCPUs

2048 vCPUs512 VMs

2-7



New ESXi Requirements

A new requirement for installing or upgrading to ESXi 5.0:

For RAM, a minimum of 2098MB is required.

New installation and boot device options:

USB devices

Disks larger than 2TB

See the VMware Compatibility Guide at http://www.vmware.com/resources/compatibility.

2-8



Changes to the ESXi Interactive Installation Process

vSphere 5.0 introduces the following changes to the ESXi interactive installation process:

A graphical installer is no longer available.

The installer can be used for new installations or upgrades.

New installations use the GUID Partition Table instead of the Master Boot Record partition format.

New installations create a 4GB scratch partition.

2-9



Enhancements to the ESXi Scripted Installation Process

vSphere 5.0 introduces the following enhancements to the ESXi scripted installation:

Adding the location of the installation media in the installation script is no longer required.

The installation image is loaded directly into the host RAM when the host boots.

The table describes command changes to scripted installations.

Command changes

Commands

Commands that have been deprecated

autopart, esxlocation, serialnum, vmserialnum

Commands no longer supported

auth/authconfig, bootloader, firewall, firewallport, timezone, virtualdisk, zerombr, %packages

2-10



Performing an ESXi Scripted Installation

When the ESXi installer screen appears, press Shift+O to edit boot options.

Type ks=<location_of_installation_script> <boot_command-line_options>.

• Example:

ks=nfs://192.168.0.101/FS2/isos/esxi-B.cfg nameserver=192.168.0.57 ip=192.168.0.3 netmask=255.255.255.0 gateway=192.168.0.254

2-11



New vCenter Server Requirements

Component Requirement vCenter Server 5.0

HardwareMemory 4GB minimum

Disk storage 4GB minimum

Software

Default database Microsoft SQL Server 2008 R2 Express

Operating systems Windows Server 2003 and 2003 R2; Windows Server 2008 and 2008 R2

Database operator (DBO) rights

No longer required for installation or upgrade

The requirements are specific to a vCenter Server system.

vSphere 5.0 introduces an alternative to the vCenter Server system: VMware vCenter Server Appliance.

The vCenter Server Appliance has its own set of requirements.

The vCenter Server Appliance is discussed in module 8, “New Alternatives for Deploying VMware vSphere.”

2-12



New vCenter Installer

2-13



Overview of the Upgrade Process

To upgrade vCenter Server, vSphere Client, Update Manager, and ESX/ESXi hosts:

1. Verify requirements.

2. Back up.

3. Upgrade to vCenter Server 5.0.

4. Upgrade to Update Manager 5.0.

5. Install vSphere Client 5.0 and install the Update Manager plug-in.

6. Use Update Manager to upgrade to ESXi 5.0.

7. Upgrade VMFS-3 datastores.(Discussed in module 5, “Storage Management”)

8. Upgrade virtual machine hardware and VMware Tools.(Discussed in module 3, “Virtual Machine Management”)

2-14



Performing a vCenter Server In-Place Upgrade

To upgrade a 64-bit system, perform an in-place upgrade.

An in-place upgrade:

Requires downtime of vCenter Server

Does not require that you power off hosts or virtual machines

vCenter Server 4.1While the upgrade

is in progress,VMware vSphere®

Distributed Resource

Scheduler stops working but

VMware vSphere® High Availability

continues to work.

2-15



Upgrading to vCenter Server on a Different Machine

To upgrade a 32-bit system to vCenter Server 5.0 (64-bit), migrate the vCenter Server database and configuration to a 64-bit machine (physical or virtual).

Back up the vCenter Server database.

Move the database to the new machine, if the database is local.

Back up vCenter Server configuration settings.

• Use the data migration tool.

Create a 64-bit data source name (DSN) that points to the database (for nonbundled databases.)

On the new 64-bit machine, install vCenter Server, and restore the vCenter Server database and configuration settings.

2-16



Using the Data Migration Tool

The data migration tool is used to back up the following:

vCenter Server configuration settings:

• Lightweight Directory Access Protocol (LDAP) data

• Port settings (for example, HTTP, HTTPS, Web services)

• SSL certificates

• Licenses

vCenter Server database, local SQL Server Express database only

The data migration tool can also be used to install vCenter Server and restore data.

The data migration tool is on the vCenter installation media.

2-17



Upgrading Update Manager

Update Manager 5.0 has the following enhancements:

Remediation of multiple servers simultaneously

Scheduling of reboot after a VMware® Tools/virtual hardware upgrade

ESX to ESXi migration

Guest operating system patching is no longer available.

To upgrade Update Manager, use the vCenter Installer.

After upgrading Update Manager:

Install vSphere Client 5.0.

Install the Update Manager plug-in.

2-18



Migrating ESX and Upgrading ESXi

Two main scenarios:

Migrate an ESX host to ESXi 5.0.

Upgrade an ESXi host to ESXi 5.0.

Most standard configurations are preserved, but not all, such as:

Information that is not applicable to ESXi:

• /etc/sysconfig/mouse or /etc/sudoers

Custom configuration files:

• Scripts added to /etc/rc.d

Most third-party software is not preserved:

Supported components are Cisco Nexus 1000v and EMC PowerPath.

All other components must be replaced after the host is upgraded.

2-19



Configuration Files Preserved During the Migration/Upgrade

Configuration files Action/etc/vmware/esx.conf Migrated

/etc/ntp.conf, ntp.drift, ntp.keys Migrated

/etc/krb.*, /etc/krb5.* Migrated

/etc/hosts, /etc/resolv.conf Migrated

/etc/pam.d/* Migrated

/etc/vmware/vmkiscsid/* Migrated

/etc/passwd, /etc/shadow Partially migrated; root and vpxuser accounts

/etc/yp.conf Not migrated; NIS not supported in ESXi

/etc/syslog.conf Migrated for ESXi, not migrated for ESX

Partial list of configuration files and whether they are migrated during the upgrade

See vSphere Upgrade Guide for the complete list.

2-20



Configuration Settings Affected by the Migration/Upgrade

Firewall configuration:

Rule set files and customized firewall rules are not preserved.

Resource pool settings:

Settings might be insufficient to start all virtual machines.

Networking changes:

If migrating ESX:

• Service console network interface cards (NICs) are converted to VMkernel NICs.

• The service console port group is removed.

Partitioning changes:

The ESXi 5.0 partition scheme differs from ESX and earlier ESXi versions.

For more details, see

vSphere 5.0 Upgrade Guide.

2-21



Migration/Upgrade Methods

Migration/upgrade method

ESX 3.5*ESX/

ESXi 4.xUse case

Use Update Manager. XFor sites that already use vCenter Server and Update Manager

Interactively use the ESXi installer. X For a small number of

hosts

Perform a scripted migration/upgrade. X For an efficient way to

deploy multiple hosts

Perform a new installation. X XFor upgrading ESX 3.5 hosts or for use in your own custom upgrade plan

* ESX/ESXi 3.5 hosts can be upgraded to version 4.x first and then upgraded to ESXi 5.0.

After you upgrade or migrate to ESXi 5.0,you cannot roll it back to the previous version.

2-22



Using Update Manager to Migrate/Upgrade to ESXi 5.0

With Update Manager 5.0, you can migrate an ESX host to ESXi 5.0.

An ESX limitation:

The /boot partition must be greater than 350MB. If it is not, use an interactive or scripted upgrade, instead.

To use Update Manager to upgrade an ESX/ESXi host to ESXi 5.0:

1. Import the ESXi 5.0 image.

2. Create the ESXi 5.0 upgrade baseline.

3. Attach the baseline to the host.

4. Remediate the host.

Use Image Builder to create a custom ESXi 5.0 ISO image, containing third-party agents and device drivers.

Image Builder is discussed in module 8, “New Alternatives for Deploying VMware vSphere.”

2-23



Interactive and Scripted Migration/Upgrade

Use the interactive ESXi installer to migrate ESX or upgrade ESXi.

The following changes have been made to the interactive ESXi installer:

No graphical installer

Single installer wizard for newinstallations and upgrades

The scripted upgrade is similar to performing a scripted installation in ESX and ESXi.

The default upgrade script is ks.cfg.

2-24



Managing ESXi Through the DCUI and esxcli Commands

With ESXi 5.0, the following changes have been made to the direct console user interface (DCUI) and the esxcli commands.

The DCUI can be accessed remotely, using an SSH session.

The esxcli command set has been revised and expanded.

The local and remote versions of esxcli are now identical.

2-25



Lab 1

In this lab, you will upgrade vSphere 4.1 components to vSphere 5.0.

1. View vCenter Server, ESX host, and virtual machine versions in the inventory.

2. Upgrade vCenter Server 4.1 to version 5.0.

3. Upgrade Update Manager 4.1 to version 5.0.

4. Install vSphere Client 5.0 and the Update Manager plug-in.

5. Import an ESXi 5.0 image to Update Manager.

6. Create an upgrade baseline for ESXi 5.0.

7. Upgrade an ESX 4.1 host to ESXi 5.0.

2-26



Review of Learner Objectives

You should be able to do the following:

Discuss key enhancements to the vSphere components:

• ESXi

• vCenter Server

• Update Manager

Discuss the enhancements made to:

• ESXi interactive installation

• ESXi scripted installation

Upgrade vCenter Server to version 5.0.

Upgrade Update Manager to version 5.0.

Install vSphere Client 5.0.

Upgrade ESX 4.1 to ESXi 5.0.

2-27



Key Points

vSphere 5.0 is the first release to offer only the ESXi hypervisor architecture.

When migrating from ESX/ESXi 4.x to ESXi 5.0, the upgrade process preserves as much of the host’s configuration as possible.

VMware recommends that you use Update Manager to upgrade your ESX/ESXi hosts.

Questions?

Documents

© 2011 VMware Inc. All rights reserved Introducing VMware vSphere 5.0 Module 2