esx to esxi technical migration guide – presentation

44
ESXi Migration Kyle Gleed Technical Marketing Manager [email protected]

Upload: ramesh2440

Post on 23-Oct-2015

43 views

Category:

Documents


7 download

DESCRIPTION

dw

TRANSCRIPT

Page 1: ESX to ESXi Technical Migration Guide – Presentation

ESXi MigrationKyle Gleed

Technical Marketing Manager

[email protected]

Page 2: ESX to ESXi Technical Migration Guide – Presentation

ESXi Convergence

ESXi Architecture

Migrating to ESXi

Pre-Migration Tasks

The Migration Process

Post-Migration Tasks

Agenda

Page 3: ESX to ESXi Technical Migration Guide – Presentation

Converging to ESXi with the next vSphere release

§ With the GA of vSphere 4.1 in July 2010 VMware officially announced that starting with the next vSphere our hypervisor architecture will converge to ESXi

§ From the release note:

VMware vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the VMware ESXi architecture.

• VMware recommends that customers start transitioning to the ESXi architecture when deploying VMware vSphere 4.1.

• VMware will continue to provide technical support for VMware ESX according to the VMware vSphere support policy on the VMware Enterprise Infrastructure Support page.

• To learn more about the ESXi architecture and how to migrate from ESX to ESXi, go to the VMware ESXi and ESX InfoCenter.

Page 4: ESX to ESXi Technical Migration Guide – Presentation

ESXi is included with all vSphere editions

§ ESXi is a high performance enterprise-ready hypervisor architecture can be used to address any of the vSphere use cases

Page 5: ESX to ESXi Technical Migration Guide – Presentation

VMware ESX Hypervisor Architecture

VMware ESXi Hypervisor Architecture

Code base disk footprint: <100 MB VMware agents ported to run directly on VMkernel Authorized 3rd party modules can also run in

VMkernel to provide hw monitoring and drivers Other capabilities necessary for integration into an

enterprise datacenter are provided nativelyNo other arbitrary code is allowed on the system

Code base disk footprint: ~ 2GB VMware agents run in Console OS Nearly all other management functionality

provided by agents running in the Console OS Users must log into Console OS in order to run

commands for configuration and diagnostics

VMware ESXi and ESX hypervisor architectures comparison

Page 6: ESX to ESXi Technical Migration Guide – Presentation

Why ESXi?

Full-featured hypervisor § Superior consolidation and scalability

§ Same performance as VMware ESX architecture

More secure and reliable§ Small code base thanks to OS-Independent, thin architecture

Streamlined deployment and configuration§ Fewer configuration items making it easier to maintain consistency

§ Automation of routine tasks through scripting environmentssuch as vCLI or PowerCLI

Simplified hypervisor Patching and Updating§ Smaller code base = fewer patches

§ The “dual-image” approach lets you revert to prior image if desired

§ VMware components and third party components can be updated independently

Next generation of VMware’s Hypervisor Architecture

Page 7: ESX to ESXi Technical Migration Guide – Presentation

The Gartner Group says…

§ “The major benefit of ESXi is the fact that it is more lightweight — under 100MB versus 2GB for VMware ESX with the service console.”

§ “Smaller means fewer patches”

§ “It also eliminates the need to manage a separate Linux console (and the Linux skills needed to manage it)…”

§ “VMware users should put a plan in place to migrate to ESXi during the next 12 to 18 months.”

Source: Gartner, August 2010

Page 8: ESX to ESXi Technical Migration Guide – Presentation

Preparing

Pre-Migration

Migration

Post Migration

ESXi Migration

Page 9: ESX to ESXi Technical Migration Guide – Presentation

Preparing

Pre-Migration

Migration

Post Migration

ESXi Migration

Page 10: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

About the ESXi Migration

Not an upgrade in the traditional sense ESX host disconnected from vCenter and shutdown

VMs stay running (vMotion/SvMotion)

Replace ESX with ESXi Assigned the same hostname and IP Address

(Re)Connect ESXi host in vCenter

Re-configure ESXi host

The ESX host specific settings are lost and need to be restored ESXi assumes the identity of the ESX host

Migrate to ESXi 4.1 directly from ESX 3.5, 4.0, or 4.1 Do not need to step through the releases (i.e. 3.5 -> 4.0 -> 4.1)

Prior to migrating you must be running vSphere 4.1

Page 11: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Important Considerations:

Upgrading vCenter Sever vCenter must be upgraded first

Hardware Compatibility Verify your hardware is supported

Storage Considerations Boot disk vs. Local disks

Shared Storage

Operational Changes Any changes needed when the COS goes away?

Identifying your Migration Path Upgrade or replace hardware?

vC DB local or remote?

Proper planning is crucial to a successful ESXi migration

Page 12: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Upgrading vCenter Server vCenter must be running at or above the ESXi version

i.e. migrating to ESXi 4.1, need vCenter 4.1 or higher Should you upgrade or replace your VirtualCenter/vCenter Server?

Server meet the hardware and OS Requirements?

New vC DB or convert an existing vC DB?

vC DB database supported?

vC DB run local or remote? What vCenter Plug-ins are used/enabled?

Will you need to convert any VI3 licenses?

Consider your timeframe to complete the migration?

Will you migrate all hosts at once, or gradually over time?

Recommend you convert/migrate your existing vC DB when possible and keep the vC DB on a separate host to accommodate growth

Page 13: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Hardware compatibility considerations Using the same hardware or replacing with new servers?

Is the ESX server running on 64bit hardware?

Is the ESX server and related components on the ESXi HCL? http://www.vmware.com/resources/compatibility/search.php

Any hardware changes to coincide with the ESXi migration?

Add/Replace CPU or Memory?

Add/Replace NICs or HBAs?

Firmware updates?

Other?

Recommend you complete and validate any hardware changes before migrating to eliminate risk of hardware problems hampering your migration

Page 14: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Storage Considerations Running SAN, NAS, iSCSI?

FC “re-discovered” on boot

NAS/iSCSI manually re-configured

Save NAS/iSCSI configs

Use the ESXi Migration Host Configuration Worksheet

<link to worksheet> Any storage changes to coincide with the migration?

Add/Remove/Replace Disks?

Add/Remove LUNs?

Add/Remove replication?

Recommend you complete and validate any storage changes before migrating to eliminate risk of storge problems hampering your migration

Page 15: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Storage Considerations (cont.)

Boot Disk Boot from local disk, SAN, SD, USB?

Overwriting an existing ESX installation?

Any VMs or templates stored on the boot disk?

Unused storage on the boot disk is automatically formatted as VMFS

When ESXi is installed, boot disk is automatically re-partitioned Any VMs and templates residing on the boot disk will be lost

Local Disk(s) Local disk = non-boot disks only accessible to the ESX host

VMs/templates on local disks are not affected by the migration

VMs and templates on local disks need to be manually re-registered following the migration

Recommend you use SvMotion to migrate VMs/templates off the boot disk prior to migrating. Record location of VMs/Templates on local disk.

Page 16: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Operational Considerations Running anything in the COS?

Agents/Tools/Scripts? Will you still need the agent/tool/script functionality following the migration ?

Do you need to move agents/tools inside VMs

Do you need to convert scripts to PowerCLI or vCLI Will you use vCLI or PowerCLI for remote management?

Assign a Windows Management VM for PowerCLI

Deploy the vMA for vCLI Identify local procedures that you will need to adapt:

Host monitoring (SNMP, CIM)

Host backups

Automated deployment and provisioning tools

Recommend you assign a management VM for remote management.

Page 17: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Choosing a Migration Path VMware recommends always upgrading to latest version of vSphere, i.e. 4.1

Common migration paths (assumes vSphere 4.1 is target release):

VI3.5 -> vSphere 4.1 Running VirtualCenter 2.5 / ESX 3.5 and moving to vCenter 4.1 / ESXi 4.1

vSphere 4.0 -> vSphere 4.1i Running vSphere 4.0 and moving to vCenter 4.1 / ESXi 4.1

vSphere 4.1 -> vSphere 4.1i Running vSphere 4.0 and moving to vCenter 4.1 / ESXi 4.1

You can go directly to vSphere 4.1, it is not necessary to step through the different releases (i.e. 3.5 -> 4.0 -> 4.1)

Requirement: always upgrade vCenter first!

Note that you cannot manage ESX 2.x hosts in vCenter 4.1. Remove ESX 2.x hosts before migrating.

Page 18: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

Key Questions vCenter Upgrade Path

Verify vCenter Hardware

vC DBlocation

Verify vC DBArchitecture

Choose Upgrade Path

Verify vCenter Version

Page 19: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Migrate

ESX to ESXi 4.1 Migration Path

Verify ESX Version

Verify Storage

Migrate or Shutdown VMs

Upgrade to ESXi 4.1

vCenter Upgrade

Verify Hardware

Page 20: ESX to ESXi Technical Migration Guide – Presentation

Preparing to Upgrade

Summary

Important to understand the ESXi architecture Impact on deployment

Impact on operations

Be aware of key requirements and limitations Upgrade vCenter first

64-bit Hardware required (vCenter, VCDB, ESX)

VMs/Templates on the ESX boot disk that cannot be migrated will be lost

VMs/Templates on local disk that cannot be migrated will need to be re-registered

Take advantage of the vSphere Enterprise + 60 day evaluation license Use vMotion/svMotion to migrate VMs

Use HA/DRS to maintain uptime

Page 21: ESX to ESXi Technical Migration Guide – Presentation

Preparing

Pre-Migration

Migration

Post Migration

ESXi Migration

Page 22: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Pre-migration Overview Step 1: Migrate VMS off ESX host

Step 2: Put Host into Maintenance Mode and remove from HA/DRS cluster

Page 23: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Rolling upgrades allowed In a rolling upgrade:

ESXi migration is performed over multiple maintenance windows

During each window only one or two hosts are migrated at a time Running a mix of ESX 3.5, ESX 4.0, ESX 4.1 and ESXi 4.1 hosts in the same cluster is allowed

While running with mixed versions avoid deploying new VMs or upgrading VM hardware versions or vmtools Deploying a new VM on an ESXi 4.1 host with hardware version 7 could cause

problems if the host fails and the VM is re-started on an ESX 3.5 host for example Managing 3.5 hosts with vCenter 4.1 beyond the 60 day evaluation periods will require installing a 3.5 license server to

manage the 3.5 license keys

Minimize the time spent running a cluster with mixed versions of ESX

Page 24: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Step 1: Migrate VMs/Templates off the Host Evacuate all VMs and templates off the host

Use vMotion/svMotion to migrate VMs

Any VMs you are unable to migrate will need to be shutdown Note: VMs/Templates on the boot disk will be lost during the migration

Take advantage of the vCenter 60 day Enterprise + evaluation license

Page 25: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Step 2: Place the host into maintenance mode From vCenter right-click on the host -> maintenance mode

Remove the host from the HA/DRS cluster

HA automatically disabled when host is put into maintenance mode

Caution, putting the ESX host into maintenance mode could affect admission control. Do NOT remove the host from the vCenter inventory!

Page 26: ESX to ESXi Technical Migration Guide – Presentation

Preparing

Pre-Migration

Migration

Post Migration

ESXi Migration

Page 27: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Migration Overview Step 1: Install ESXi

Step 2: Logon to ESXi & (re)configure the host

Step 3: Reconnect the ESXi host to vCenter & (re)configure

Step 4: Re-register any VMs/Templates on local storage

Page 28: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Step 1: Install ESXi Boot host off install media

Follow prompts to install ESXi

Note that the ESXi installation will overwrite the boot disk

Page 29: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Step 2: Logon to the Direct Console User Interface (DCUI) and configure host settings

From the DCUI configure:

Set the root password

Configure NICs for the management network

Configure the hostname and DNS

Set the IP address, gateway, and default route

Page 30: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Step 3: Reconnect the ESXi host in vCenter and (re)configure Right click the host in vCenter and choose “Connect”

When prompted provide the ESXi server user and password Using the Host Configuration Worksheet reconfigure the ESXi host

Add/Configure NTP, vSwiches and PortGroups, NFS Datastores, iSCSI Move the server back into the HA cluster

Page 31: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Step 4: Re-register VMs and Templates on local storage In vCenter go to Inventory -> Datastores

For each local datastore

Right click -> Browse

Expand the VM folder

Right click -> Add to Inventory

Page 32: ESX to ESXi Technical Migration Guide – Presentation

Migration to ESXi

Migration Highlights: You can migrate to ESXi with no VM downtime

Requires vMotion/svMotion

Use the vSphere 60 day Enterprise + evaluation license! Rolling upgrades are possible

Mixed clusters with ESX 3.5/4.0/4.1 and ESXi 4.1 are supported

Minimize the time running clusters with mixed ESX versions ESXi retains the ESX host’s identity in vCenter

Disconnect, but do not remove ESX host from vCenter

Removing host from vCenter removes all historical and performance data related to the host from the VCDB

Estimated migration time per host = 30 minutes

ESXi Installation = 10 minutes

Configure TCP/IP and reconnect to vCenter = 5 minutes

Re-configure host in vCenter = 15 minutes

Page 33: ESX to ESXi Technical Migration Guide – Presentation

Preparing

Pre-Migration

Migration

Post Migration

ESXi Migration

Page 34: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

ESXi Direct Console User Interface (DCUI)

DCUI, Lockdown Mode, and Troubleshooting Options can be enabled/disabled from the vSphere Client

Page 35: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

ESXi Lockdown Mode

When in Lockdown Mode all configuration changes go through vCenter Server

Page 36: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

ESXi Troubleshooting Services Local Tech Support Mode (TSM)

Enable/Disable local shell access to the host

Remote Tech Support Mode Service (SSH) Enable/Disable remote SSH access

to the host

Modify Tech Support timeout Timeout when Tech Support Mode

logins are automatically disabled

Restart Management Agents Restart agents that allow remote

management

Do not enable troubleshooting services until they are required. When troubleshooting services are enabled, anyone who is logged in has complete control of the host

Page 37: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

Configure the ESXi Scratch Partition 4GB (default) partition mounted as /scratch

Used to store output from vm-support as well as upgrade files

Created automatically during install if disk > 5GB

Can be (re)configured on boot disk or other local or SAN datastore

Page 38: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

Configure the ESXi Scratch Partition (cont.) Creating a Scratch Partition

Tech Support Mode / Scripted Install: vim-cmd hostsvc/advopt/update ScratchConfig.ConfiguredScratchLocation string

/vmfs/volumes/storage1/<unique-name>

vCLI: vicfg-advcfg.pl --server <hostname> --username root -s

/vmfs/volumes/storage1/<unique-name> ScratchConfig.ConfiguredScratchLocation

PowerCLI: Set-VMHostAdvancedConfiguration -VMHost (Get-VMHost <fqdn-hostname>)

-Name "ScratchConfig.ConfiguredScratchLocation" -Value "/vmfs/volumes/storage1/<unique-name>"

Page 39: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

Active Directory Join ESXi host to Active Directory using the vSphere

Client

Select the host and choose Configuration -> Authentication Services -> Properties

Domain name format:

Name.tld (i.e. vmware.com)

Name.tld/container/path (i.e. vmware.com/OU1/OU2)

See the ESXi Configuration Guide, Chapter 13

Page 40: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

Setup Syslog ESXi system logs are stored in memory and do

not persist reboots unless redirected to a log host

Use the vSphere Client to setup log host:

Select the host and choose Configuration -> Advanced Settings -> Syslog

Enter the remote logging host for Syslog.Remote.Hostname

See ESXi Installable and vCenter Server Setup Guide, Chapter 6

Page 41: ESX to ESXi Technical Migration Guide – Presentation

Post Migration Tasks

Other Post Migration Tasks

ESXi host configuration backup vicfg-cfgbackup

Setup SNMP vicfg-snmp

Configure Host Profiles vSphere Client

Patching/Updating with vSphere Update Manager (VUM)

Setup/Configure the vSphere CLI Virtual Appliance (vMA)

Install/Configure PowerCLI

Upgrade VM Tools

Upgrade VM Hardware Version

Upgrade VMFS Version

Page 42: ESX to ESXi Technical Migration Guide – Presentation

Call to action for VMware partners

§ Learn about ESXi and become an expert

§ Make sure your customers know about ESXi convergence in the next release of vSphere

§ Help your customers plan and complete their ESX to ESXi migrations with their upgrade to vSphere 4.1

§ When working on new vSphere 4.1 deployments advise your customers to deploy ESXi directly

Page 43: ESX to ESXi Technical Migration Guide – Presentation

Help Your Customers Plan Their Migration to ESXi Today

For more information:• Visit the ESXi page on Partner Central:

https://na6.salesforce.com/apex/page?name=products.esxi

• Visit the ESXi and ESX Info Center: www.vmware.com/go/ESXiInfoCenter

• Read “VMware ESXi: Planning, Implementation, and Security” by Dave Mischenko (Release Date: October 2010, list price $49.99)

• Register for VMware training “Transitioning to ESXi”: www.vmware.com/go/esxi/education

Future proof VMware deployments by migrating to ESXi

VMware ESXi architecture will be the only hypervisor in future vSphere releases after vSphere 4.1