IBM System p · IBM Power Systems AIX Virtualization Continuum LPAR / Micropartitions AIX V5.3 on...

Francis COUGARD IBM Products and Solutions Support Center – Montpell ier

®

IBM System p

© Copyright IBM Corporation 2009

Application and Partition Mobility

IBM pssc - Montpellier IBM

2© Copyright IBM Corporation 2007

Index

Application and Partition Mobility Presentation

Videocharger and DB2 VPS Partition MobilityDemonstration


®

IBM System p


Application Mobility Presentation

An AIX Version 6 Feature



AIX Workload Partitions

�Software partitioned system capacity –Each Workload Partition obtains a regulated share of system resources

–Each Workload Partition can have unique network, filesystems and security

�Two types of Workload Partitions–System Partitions–Application Partitions

�Separate administrative control–Each System Workload partition is a separate administrative and security domain

�Shared system resourcesOperating System, I/O, Processor, Memory

WorkloadPartition

ApplicationServer

WorkloadPartition

WebServer

WorkloadPartitionBilling

WorkloadPartition

Test

WorkloadPartition

BI

Separate regions of application space within a sing le AIX image

� Improved administrative efficiency by reducing the number of AIX images to maintain

AIX

WorkloadPartition

Test



� AIX Workload Partitions complement Logical Partitions

Workload Isolation

Res

ou

rce

Fle

xib

ility

IBM Power Systems AIX Virtualization Continuum

LPAR /MicropartitionsAIX V5.3 on POWER5 or later

WorkloadPartitions

AIX 6 on POWER4 or later

AIX WorkloadManager

AIXV4.3.36 on POWER3™ or later



Two WPAR AIX Offerings…

�AIX 6– Workload Partitions (WPAR) included in AIX 6– Element (single system) WPAR Management

�Workload Partitions Manager™– Enablement for Live Application Mobility– Cross System Management for Workload Partitions– Automated, Policy-based Application Mobility– Part of IBM System Director Family

WPAR Manager



WorkloadPartition

QA

WorkloadPartition

Data Mining

AIX Live Application Mobility

WorkloadPartition

App Server

WorkloadPartition

WebWorkloadPartition

Dev

Move a running Workload Partition from one server to anotherfor outage avoidance and multi-system workload balancing

Workload Partitione-mail

Works on any hardware supported by AIX 6, including POWER5 and POWER4

WorkloadPartitionsManager

PolicyWorkloadPartitionBilling

AIX

AIX



Bibliography

SG24-7431


®

IBM System p


Partition Mobility Presentation

A Power 6 Feature



�Rebalance processing power across servers when

and where you need it

�Reduce planned downtime by moving workloads to another server

during system maintenance

Movement to a

different server

with no loss of

service

Virtualized SAN and Network InfrastructureVirtualized SAN and Network Infrastructure

Live Partition Mobility requires the purchase of the optional PowerVM Enterprise Edition

�Move a running partition from one POWER6 processor-based server to another with no application downtime

PowerVM Enhancements – Live Partition Mobility



Partition Mobility: Active and Inactive LPARs

Active Partition Mobility� Active Partition Migration is the actual movement of a running LPAR from one

physical machine to another without disrupting* the operation of the OS and applications running in that LPAR.

� Applicability� Workload consolidation (e.g. many to one)� Workload balancing (e.g. move to larger system)� Planned CEC outages for maintenance/upgrades� Impending CEC outages (e.g. hardware warning received)

Active Partition Mobility� Active Partition Migration is the actual movement of a running LPAR from one

physical machine to another without disrupting* the operation of the OS and applications running in that LPAR.

� Applicability� Workload consolidation (e.g. many to one)� Workload balancing (e.g. move to larger system)� Planned CEC outages for maintenance/upgrades� Impending CEC outages (e.g. hardware warning received)

Inactive Partition Mobility� Inactive Partition Migration transfers a partition that is logically ‘powered off’ (not

running) from one system to another.

Inactive Partition Mobility� Inactive Partition Migration transfers a partition that is logically ‘powered off’ (not

running) from one system to another.

Partition Mobility supported on POWER6AIX 5.3, AIX 6.1 and Linux



Hardware / software requirements

� Minimum of two POWER6-based systems– Advanced Power virtualization (APV) = PowerVM Enterprise Edition required

� Storage Area Network (SAN)– Supported by Virtual I/O Server (VIOS)

� Virtualization Manager – Hardware Management Console (HMC) – Integrated Virtualization Manager

� LAN (Gbit Minimum) between both Virtual I/O Servers

� eFW 3.2

� Operating System Minimum Level– AIX Version 5.3 Technology Level 7– AIX6.1– Linux RHEL V5 update 1– Linux SLES 10 Service pack 1



Partition Mobility –virtualized components and required level

� Partition– Virtual Disk

• Mapped through VIO Server to a LUN– Virtual Ethernet

• Mapped through SEA in VIO Server

� Hypervisor– vSCSI– Virtual Ethernet– Support for migration

� VIO Server– Provides the Virtual I/O– VASI interface to Hypervisor– Mover Service Partition (MSP)– Must be at release level 1.5 or later

� HMC– Configuration of required capabilities– Validation of configuration– Orchestrates the sequence of events– version and release must be at V7R320 or later

� VASI = Virtual Asynchronous Services Interface

HYPV

hdisk0

en0

EthernetNetwork

HMC

Service processor

Private network

vhost0 vfscsi0

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

Lpar 1

System A

VIO

LUN

Storage Area Network



Partition Mobility – Preparation task

� The same LMB (Logical Memory Block) size on each System� Must have sufficient resources (e.g. CPU & Memory) available� No partition with the same name as the one which is to be Migrated

System A System BHYPV

Service processor

Private network

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

HYPV

hdisk0

en0

HMC

Service processor

Private network

vhost0vfscsi0

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

LPAR mig1

Ethernet network

LUN


PUblicnetwork



Partition Mobility – Basic requirements

� The partition to be Migrated :– Not set for Redundant error path reporting– No additional Virtual Serial ports– Not part of a Workload group– Not using Barrier Synchronization Register– Not using Huge Pages– Not using physical I/O

� Disk Setup– All systems in a migration domain must be connected on a Storage Area Network

(SAN) to shared physical disks - No internal or VIOS-based disks– SAN disks must be configured to be visible from both systems– Both redundant, that is, Multi-Path I/O (MPIO), and non-redundant Virtual SCSI

configurations supported

* Important Planning Note: All user-defined virtual devices must have a Virtual Slot number higher than 10. This will be enforced by the HMC code.



Migration Flow

� User identifies migrating partition and systems invo lved in migration

� Verification test is performed target system equivale ncy

� Migration is initiated on source system

� Data is transferred from source to target system

� When a percentage of data has been transferred– Partition is suspended on source system– Partition resumes execution on target system

� When all data has been transferred– Migration completes– Partition resources on source system are freed

� If an error is detected at any point, migration is abo rted



Partition Mobility – Initial steps

HYPV

Service processor

Private network

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

HYPV

hdisk0

en0

Ethernet network

HMC

Service processor

Private network

vhost0vfscsi0

hdiskX

fsc0

VASI MSP

LUN

ent1virt

ent0

en2 if

ent2SEA

hdiskX

System A System B

LPAR mig1

vhost0 vfscsi0

PUblicnetwork




Partition Mobility – Partition recreated on server B

HYPV

hdisk0

en0

Service processor

Private network

vhost0 vfscsi0

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

HYPV

hdisk0

en0

HMC

Service processor

Private network

vhost0vfscsi0

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

Server A Server B

Logical Memory Copy

LUN


Ethernet network Memory Copy over network

PUblicnetwork



Partition Mobility – Migration completion

– The source Virtual I/O Servers unlock, unconfigure, or undefine virtual resources on the source servers. – The HMC removes the hosting virtual adapter slots from the source Virtual I/O Server logical partition

profiles as required.� Finally, the source LPAR is removed.

System B

System A

HYPV

Service processor

Private network

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

HYPV

hdisk0

en0

Service processor

Private network

vhost0 vfscsi0

hdiskX

fsc0

VASI MSP

ent1virt

ent0

en2 if

ent2SEA

hdiskX

Lpar mig1

PUblicnetwork

HMC

Ethernet network


LUN



Target Partition Is Different From Source Partition

� Partition number is different

� Server serial number is different

� Maximum number of potential (hot-pluggable) and installed physical processors may be different

� The model class may be different (high-end vs. low-end system)

� Same partition name

� Same logical partition configuration– min, online, and max logical CPUs– min, online, and max logical memory– min, actual, and max entitled capacity

� Same logical device configuration– Same IP addresses– Same vSCSI setup to access disk



Partition Mobility – Dual VIO

� Dual VIO Server – Dual Virtual I/O Server and client mirroring may be used if you have two

independent storage subsystems providing disk space

� Dual Virtual I/O Server and multipath I/O– only if the destination system is configured with two Virtual I/O Servers that can

provide the same multipath setup

* Important Planning Note: All user-defined virtual devices must have a Virtual Slot number higher than 10. This will be enforced by the HMC code.



Dynamic Heterogeneous Multi-Path I/O

� Delivers flexibility for Live Partition Mobility environments � Provides efficient path redundancy to SAN resources

– Supported between virtual NPIV and physical Fibre Channel Adapters – AIX 5.3 and 6.1 partitions – POWER6 processor-based servers

Power Hypervisor

VIOS

FC AdapterVirtual FC AdapterFC Adapter

Power Hypervisor

VIOS

FC AdapterVirtual FC AdapterFC Adapter

1) Real adapter

2) Virtual adapter to prepare for mobility

3) Partition moves via virtual adapter

4) Real adapter

NPIV NPIV



Bibliography

SG24-7460

IBM System p · IBM Power Systems AIX Virtualization Continuum LPAR / Micropartitions AIX V5.3 on...

Documents

Transcript of IBM System p · IBM Power Systems AIX Virtualization Continuum LPAR / Micropartitions AIX V5.3 on...