Merge the power with VMware

© 2012 IBM Corporation

Merge the POWER (i) with VMwareJanus HertzSenior IT SpecialistIBM EMEA ETS Center of Competency for Power Systems

Common Europe Conference – Vienna | June 2012

Rev. 09-06-2012



Agenda

� iSCSI Integrated Servers overview

� Vmware Integration

–Overview

–VMware Architecture

–Release Support

–Planning and Implementation Details

–Conciderations

� Customer examples

� Installation



3

IBM i Innovative Technology

IBM i

Host

IBM Power Systems



4

IBM i Integration Benefits - Merge the POWER (i) with VMware

� Reuse existing IBM i skills

� Utilize existing Power hardware for virtual storage

–Eliminating the need to buy a dedicated seperate Storage box.

� VMware Server Management (from IBM i)

–Start / Stop of ESX hosts

� VMware Storage Management (from IBM i)

–Creation / Allocation / Shared storage

� Server Availability and reliability

� Easy Backup/Restore

� Efficient Disaster Recovery



iSCSI - internet SCSI (Small Computer System Interface), SCSI commands sent across a network in TCP/IP packets. It was developed as a storage networking standard for linking data storage facilities

What is iSCSI?

Initiator

Initiator - system making the iSCSI requests for data

Target

Target - system receiving the iSCSI requests for data

Power System



6

IBM i Integration with BladeCenter and System x

iSCSI connection between IBM i and BladeCenter System x using

iSCSI HBAs (Host Bus Adapters) or standard ethernet ports.

Standard ethernet cables and switches (gigabit).

� IBM i 6.1 enables iSCSI Software Initiators

� IBM i 7.1 enables iSCSI Software Targets

IBM i

IBM i



Software Target Support

In an IBM i 6.1 (and previous releases) Integrated Server Environment the customer

is limited to an environment containing physical iSCSI Target HBAs with 1GB

connectivity.

In IBM i 7.1, we have implemented the new software target solution you can use

dedicated 1GB or 10GB Ethernet ports for iSCSI connectivity.

IBM i



Software Target Details

Target Side• No Target iSCSI HBA required• Use dedicated Ethernet adapters/ports

• can be either 1 Gb or 10 Gb• NWSH points to virtual device• Can mix hardware and software Targets

Initiator Side• No Initiator iSCSI HBA required*• Use dedicated Ethernet adapters/ports

• can be either 1 Gb or 10 Gb• Can mix hardware and software initiators

Dedicated 1Gb or 10Gb connections

Advantages• Enable support in POWER7 (no iSCSI HBA support)• Can get to 10 Gb infrastructure• Reduce cost of solution• No specialized hardware required

* Supported on certain models, see supported hardware list



Software Initiator Configuration Considerations

� Microsoft iSCSI Initiator Service is required for every server that requires more

than one session

– Initiator code must be downloaded from Microsoft for Windows Server 2003

� Ensure the latest BIOS/Firmware is installed for both the server and network

adapters (NIC)

� Enable software initiator as the boot device in the BIOS/UEFI setup menu

� Software Initiator must be used with VMware ESXi5 servers



VMware on BladeCenter and System x Integrated with IBM i

�VMware ESX is a leading

virtualization solution for x86

servers– Virtualization supports multiple

Windows, Linux, and Netware

environments on a single server

– Enables the reduction of the number of

physical servers

� IBM i integration with BladeCenter

and System x via iSCSI supports

VMware ESX– IBM i provides virtual storage support

for VMware ESX servers

– Extends the value of advanced IBM i

storage management

IBM System i

http://www-03.ibm.com/systems/i/bladecenter/

Power System



VMware VMotion Enabled by Shared Storage

Running onBlade1ESX1

Running on

Blade2

• Enabled by share links to storage spaces between NWSDs (ESX1 and ESX2)

• Enables VMware VMotion, HA and DRS functions

•Available on IBM i 6.1 and later

ESX2

VM1 VM2 VM3 VM4

ESX1ESX2VM1

VM2VM3VM4



12

VMware ESX Architecture – “Classic”

� Virtual machines run on VMkernel

� Management agents run in Service Console

VM VMVM

DistributedVM File System

Device Drivers

Storage Stack

Virtual NIC &Switch

Network Stack

VM

VMM VMMVMM VMM

VMX VMX VMX

VMkernel

User mode API (POSIX subset)

ResourceScheduling

Service

Console

hostd

3rd party

agents

vpxa

VMX



13

VMware ESX Architecture – “Classic”

VMkernel

– Resource scheduling and I/O stacks

VMkernel native applications

– Virtual machines (VMM & VMX)

– Authentication daemon

Service Console

– Bootstrap

– VMware and 3rd party agents

– 3rd party software

– Direct administration



14

VMware ESXi Architecture

� Hostd & vpxa run on VMkernel

� 3rd party agents run as plug-ins in a CIM framework

� Direct Console User Interface (DCUI) for simple direct administration

runs on VMkernel

VM VMVM

DistributedVM File System

Device Drivers

Storage Stack

Virtual NIC &Switch

Network Stack

VM

VMM VMMVMM VMM

VMX VMX VMX

VMkernel

User mode API (fuller POSIX subset)

ResourceScheduling

hostd

vpxa

VMX

SFCB

CIM broker

3rd party

CIM plugins

DCUI



15

VMware ESXi Architecture

� VMkernel

– Resource scheduling and I/O stacks

– Bootstrap

� VMkernel native applications

– Virtual machines (VMM & VMX)

– Authentication daemon

–Direct Console User Interface (DCUI), can be locked

down

– VMware agents

– 3rd party agents as CIM providers inside CIM

framework



16

Main Differences – ESX / ESXi

VMware ESXi VMware ESX

On-disk Footprint ESXi 3.5 = 32 MB

ESXi 4.x = ~ 70 MB

ESXi 5.0 = 144 MB

ESX 3.5 = 2GB

ESX 4.x = biggerL

Bootstrap Direct from bootloader Service Console driven

Direct Management

Interaction

DCUI Service Console shell session

OEMs Agents CIM plug-in modules Full stacks in Service Console

Other Agents Implemented via VI SDK only Full stacks in Service Console

Scripts, automation and

troubleshooting

DCUI, Remote CLI, and VI

SDK

Shell and VI SDK

Other software Moved to outside environment Resident in Service Console



IBM i 7.1 Enhancements – VMware Support Changes

Support for VMware vSphere in IBM i 7.1

• VMware ESXi server management

The IBM i Integrated Server Support software does not run directly on the VMware ESX server.Instead, an iSCSI attached integrated Windows server serves as a management server for the VMware ESX server.An integrated Windows server can serve as the management server for any number of integrated VMware ESX servers within the same IBM i logical partition.At least one integrated Windows server is required in each IBM i logical partition that hosts integrated VMware ESX servers.

For details please see: http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/index.jsp?topic=/rzahq/managingintegratedesxservers.htm



VMware vSphere 5 Support

VMware vSphere 5 offers two versions of ESXi 5 server versions:

• ESXi 5 Installable:• This version is installed on disk.• It contains a VMware Kernel which is the hypervisor that

hosts guest operating systems.• It does not contain a Console OS (COS).

• ESXi 5 Embedded:• This version is embedded on USB flash.• It contains a VMware Kernel which is the hypervisor that

hosts guest operating systems.• It does not contain a COS.

VMware GA – August 2011IBM i Support – August 2011!Requires IBM i Group PTF SF99369 Level 8



VMware vSphere 4 Support

VMware vSphere 4 offers three versions of ESX 4 server versions:

• ESX 4:• This version is installed on disk.• It contains a Console Operating System (COS) based on Red Hat

Enterprise and a VMware Kernel which is the hypervisor that hosts guest operating systems.

• ESXi 4 Installable:• This version is installed on disk.• It contains a VMware Kernel which is the hypervisor that hosts

guest operating systems.• It does not contain a COS.

• ESXi 4 Embedded:• This version is embedded on USB flash.• It contains a VMware Kernel which is the hypervisor that hosts

guest operating systems.• It does not contain a COS.



IBM i 6.1 & 7.1 VMware vSphere 4 and 5 Support

HWI

System x

HWI

Blades

SWI

System x

SWI

Blades

ESX 4 Yes Yes No No

ESXi4.x Yes Yes Yes Yes

ESXi5 No No Yes Yes

HWI - Hardware Initiator

SWI - Software Initiator

Notes:• HWI - not all versions of HWI supported, see:

http://www-03.ibm.com/systems/i/advantages/integratedserver/iscsi/solution_guide.html• SWI - only supported on certain System x and Blades models see:

http://www-03.ibm.com/systems/i/advantages/integratedserver/iscsi/solution_guide.html

ESX Server Management server is always required on 7.1



Service Console infrastructure

IBM i onIBM i

Startup and shutdown commands sent from IBM i to VMware Console of iSCSI attached ESX server

iSCSI

VMware ESXServer

COS

VMware ESXServer

COS

Dynamic linking of storage is allowed but requires manual intervention in order for ESX server to recognize new storage.

ESX 3.x and 4.x servers on i 5.4 and i 6.1



Management Server infrastructure

VMware ESXiServerInstallable

IBM i onIBM i

ManagementServer(Windows)

Virtual EthernetPoint to Point

iSCSI

Startup, shutdown, and dynamic linking commands are sent from IBM i to iSCSI attached Management Server

iSCSI

ESX4 and ESXi4 and later servers on i 6.1 and i 7.1

Dynamic linking of storage automatically recognized by ESXi server

VMware ESXiServerEmbedded

Memory Stick



Management Server infrastructure with platform manager

VMware ESXiServerInstallable

IBM i onIBM i

ManagementServer(Windows)

Virtual EthernetPoint to Point

iSCSI

Startup, shutdown, and dynamic storage linking commands are sent from IBM i to iSCSI attached Management Server to ESX Platform Manager (such as VMware vCenter Server)

iSCSI

ESX PlatformManager

Phys Eth

iSCSI (Optional)

Dynamic linking of storage automatically recognized by ESXi server

VMware ESXiServerEmbedded

Memory Stick

ESX4 and ESXi4.x servers on i 6.1 and i 7.1ESXi5 servers on i 7.1

Can be one server



Save while active support for VMware Storage Space

24 © Copyright IBM Corporation 2011

• IBM i Integrated Server Support is enhanced to provide save while active (SWA) support for integrated VMware ESX servers.

• Storage spaces for VMware ESX servers can be saved from IBM i while the ESX server is active. This allows a concurrent save of ESX data without requiring the ESX server to be shut down or applications ended.

• See the IBM i iSCSI Solution Guide, section 7.8.4 for additional information.

• The following IBM i group PTFs are used to deliver this enhancement:

• IBM I 7.1 Group PTF: SF99369 Level 6 (June 2011)



First Place to Start for iSCSI on IBM i Solution

http://www-03.ibm.com/systems/i/advantages/integratedserver/iscsi/solution_guide.html



Implementation steps and considerations

� Planning, planning and planning!!

– Use the IBM i iSCSI solution guide!

– And the IBM i iSCSI solution work sheets

� Verify hardware support

– From an intergrated server (IBM i) point of view (Solution Guide):• www-03.ibm.com/systems/i/advantages/integratedserver/iscsi/solution_guide.html

– From a Vmware point of view. Use Vmware Compatebility Guide: • www.vmware.com/resources/compatibility/search.php?deviceCategory=server

� Verify software support

– IBM i iSCSI solution guide

– Verify/Install required license programs & group PTF

� Concider iSCSI Multipathing, dual switches.

– Remember to set Vmware multipath appropriatly.• Default is ”fixed path”. All vmware datastores will typically default to same path, even if

two paths are present. Change to ”Round-Robin” or manually assign alternating paths

for Datastores..

� Concider iSCSI virtual storage I/O memory pool

26



Implementation steps and considerations – cont.

� Migration of Vmware environment needed when moving from IBM 5.4 to 6.1

and 6.1 to 7.1

– See IBM i iSCSI solution guide

� Migration also needed if moving from ESX to ESXi

– See IBM i iSCSI solution guide

� Consult the ”Performance Capability Reference Guide”

– Chapter 17 ”Integrated BladeCenter and System x Performance”

27



Performance Capabilities Reference Guide

http://www-03.ibm.com/systems/i/advantages/perfmgmt/resource.html




PTFs

� Before installing an integrated server, load all of the following required PTFs:

� Note: Use the IBM i WRKPTFGRP command to verify that you have the latest level of the group PTF

installed.

� Action required: The group PTF for your IBM i release contains a service pack PTF for the IBM i Integrated

Server Support code that runs on the integrated Windows or VMware ESX server.

After installing the group PTF, you need to install the service pack from IBM i to each Windows or VMware

ESX Server. See the Installing IBM i integration service packs section of the IBM i iSCSI Solution Guide

for service pack installation instructions.

� Reference:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Waededb4f351a_47fd_b2dc_61f672cfcc7f/page/IBM

%20i%20PTFs

29



30

New Shared Memory Pool for iSCSI I/O

• Replaces private pool QFPHIS used in V5R4• Can use any of the Shared xx pools• Specify the Shared xx in NWSD for i5/OS to use shared pool for that NWSD



Vmware patching

� Remember to update your Vmware software to latest patch level as well (within the

same ESX(i) version, ie.4.0, 4.1 or 5.0)

� Recommend using Vmware update manager.

� Surgest updating your Vmware patchlevel with same frequence as with PTFs.

� http://www.vmware.com/patchmgr/download.portal

31



IBM i 7.1 Enhancements – INSINTSVR Command • New install command for Windows Server 2008, ESX4, and ESXi v4 / v5 servers L less parameters!• Replacement for the old INSWNTSVR command from previous releases• Automatically creates some objects if not on the system

• Connection Security object



Create Server Install Wizard

Systems Director Navigator for i



Installing and Configuring the Management Server

� Management Server is a Windows service on Windows Server 2003 or 2008

� Install service using ibmvmins command in C:\Windows\as400wsv\ESX

� Configure using ibmvmcon from the same directory– Specify NWSD name

– Specify IP address of the VMware host (server)

– Specify IP address of the VMware Platform Manager if it exists

� Run commands from user QVMWINT (need administrator privileges)



Network Server Status

� Status will be Active on WRKNWSSTS if IBM i is communicating with Management Server

� Status with be CNNPND if Admin Server job is running on IBM i but it’s not communicating with the Management Server



VMware Power Down Configuration Tip

� Default Shutdown Delay for VMs is 2 minutes meaning a vary off will cause the

VMware server to wait for 2 minutes before powering down VMs

� Recommend changing to 0 seconds



Debug Logs

� Several logs available on the Integrated Server drive on the Management

Server (usually the D: drive)

–ibmvmadm – admin monitor job log

–ibmvmcon – configuration task log

–ibmvmins – server install log

–ibmvmtsk – server task log



38

HT Bendix A/S, Denmark

First integrated VMware ESX 4 installation in Nordic on IBM i 7.1!

• 1 IBM i 7.1 host LPAR – running various applications

• 2 iSCSI attached System x 3650 M3 running VMware ESX 4, for consolidation of a number of older physical Windows Servers and an existing standalone VMware ESX 3.5 server.• 1 iSCSI attached System x 3550 M3 running Windows Server 2008 R2, and acting as administration server for the VMware server.

iSCSI integrated ServersPower Virtualization

www.htbendix.dkIBM System i520

2 * IBM System x3550

IBM System x3650



39

Haribo Lakrids A/S, Denmarkwww.haribo.com

• Candy manufacture

• 1 System i 525 (2 way Power6)• 1 System x 3850 (ESX4)• 2 System x 3850 M2 (ESX4)• 1 System x3550 M2 (vCenter)

• 1 IBM i 6.1 host LPAR – running RPG applications• 3 iSCSI attached System x 3850 (M2) running VMware ESX 4

• More than 30 virtual machines• Approx. 3 TB VMs• Including 2 old IXS Windows Servers migrated with VMware Converter from old i810. • VMotion, HA, MPIO

iSCSI integrated ServersPower Virtualization



Backup slides




41

Service Processor Manager (SPM)

In IBM i 7.1 Service Processor Manager (SPM) is a build in function of IBM i.

The SPM functionality has been PTF’ed into IBM i 6.1

Before IBM i 7.1

– In previous releases the customer had the option to either use Service

Processor Manager or IBM Director (5722-DR1) for integrated server

management connections and power control.

Enhancement

– IBM Director (5722-DR1) is no longer used for server management

connections or power control. This reduces the software requirement for the

Integrated Server solution by no longer requiring 5722-DR1 to be installed

on the IBM i.

� NOTE: The newer System x server models require SPM because they use a newer service

processor called an imbedded management module (IMM).



42

IBM Systems Director Navigator for IBM i

• Moving iNav functions to the new web console

• Point browser to URL: http://systemname:2001/

• All GUI function that was in iNav is there



Web GUI Updates - Create Server

� Creating a server in an IBM i Integrated Server IBM i Integration with BladeCenter and System x

environment has never been easier. Use IBM Systems Director Navigator for i Web GUI to walk

you through a server installation.

� In release IBM i 7.1, supported Operating Systems include:

– Windows Server 2008 and Windows Server 2003 Server editions.

– VMware ESX 4.x

– VMware ESXi 4.x & 5.0



Web GUI Updates - Delete Server

When a server is not active or starting, an

option to delete the server is now available.



IBM i 7.1 Enhancements – DLTINTSVR Command

New delete server command for integrated servers #



Cloning Windows Servers

Assuming you have a working Integrated Windows Server:

1. Start the base Windows server and run the sysprep tool

2. Shut down the server

3. From Systems Director Navigator for i, run the cloning wizard to clone the server

• Select Integrated Server Administration -> Create Server and select “Base on existing object” then specify NWSD of server to be cloned and the new server name

• Select the Virtual Storage and Remote System that the server clone will use

4. Change Virtual Ethernet point to point connection if you don’t like default used by cloning wizard

5. Start the server clone and handle licensing requirements, etc.

6. Adjust host name / IP address on Windows if necessary

See Chapter 5 of iSCSI Solution Guide for details

See “i Can” blog at

http://ibmsystemsmag.blogs.com/i_can/2011/06/clone-an-integrated-windows-server.html



10Gb Connectivity

Target Side• Dedicated 10Gb Ethernet adapters required

Initiator Side• Dedicated 10Gb Ethernet adapters required.

Dedicated 10Gb connections

Advantages• 4-6 times faster than 1 Gb• standard 10Gb adapters



NWSCFGRMTSYSThe Initiator

System x or BladesiSCSI HBA Port Configuration

IBM iSystem x or Blade

IBM i Integrated Server – Object Model (Physical Target HBA)

NWSHThe Target Device

NWSCFGSRVPRCRemote powercontrol management

iSCSI HBA

ServiceProcessor

iSCSI HBA /Ethernet NIC

I5/OS

Hardware

Storage Path

Remote System

Server

NWSSTGStorage Space(Virtual Disk)

NWSDThe Storage-Server Link

NWSCFGCNNSECThe Link Security

Switch

Ethernet



NWSCFGRMTSYSThe Initiator

System x or BladesiSCSI HBA Port Configuration

IBM iSystem x or Blade

IBM i Integrated Server – Object Model (Software Target)

VirtualNWSH+ LINDThe Target Device

NWSCFGSRVPRCRemote powercontrol management

Ethernet NIC

ServiceProcessor

iSCSI HBA /Ethernet NIC

I5/OS

Hardware

Storage Path

Remote System

Server

NWSSTGStorage Space(Virtual Disk)

NWSDThe Storage-Server Link

NWSCFGCNNSECThe Link Security

Switch

Ethernet



50

Trademarks

The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.

The following are trademarks or registered trademarks of other companies.

* All other products may be trademarks or registered trademarks of their respective companies.

Notes:

Performance is in Internal Throughput Rate (ITR) ratio based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput improvements equivalent to the performance ratios stated here.

IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.

All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will vary depending on individual customer configurations and conditions.

This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for information on the product or services available in your area.

All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.

Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has not tested those products and cannot confirm the performance, compatibility, or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

Prices subject to change without notice. Contact your IBM representative or Business Partner for the most current pricing in your geography.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office.IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency, which is now part of the Office of Government Commerce.

For a complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml:

*, AS/400®, e business(logo)®, DBE, ESCO, eServer, FICON, IBM®, IBM (logo)®, iSeries®, MVS, OS/390®, pSeries®, RS/6000®, S/30, VM/ESA®, VSE/ESA, WebSphere®, xSeries®, z/OS®, zSeries®, z/VM®, System i, System i5, System p, System p5, System x, System z, System z9®, BladeCenter®

Not all common law marks used by IBM are listed on this page. Failure of a mark to appear does not mean that IBM does not use the mark nor does it mean that the product is not actively marketed or is not significant within its relevant market.Those trademarks followed by ® are registered trademarks of IBM in the United States; all others are trademarks or common law marks of IBM in the United States.

Merge the power with VMware

Technology

Transcript of Merge the power with VMware