Implementing Live Partition Mobility

IBM Power Systems Technical University featuring IBM AIX and Linux
September 8 12, 2008 Chicago, IL
Session Title: Implementing Live Partition Mobility Session ID: pAI54

Speaker Name: Tyrone DeChalus
2008 IBM Corporation
IBM Training
Trademarks
The following are trademarks of the International Business Machines Corporation in the United States, other countries, or both.
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.
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
The following are trademarks or registered trademarks of other companies.

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.
* 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.
IBM Training
Objectives
Overview of the Live Partition Mobility Process Implement Live Partition Mobility
IBM Training
Overview of Process
Move running partitions from one system to another POWER6 Systems Partition with only virtual devices Virtual disk(s) must be LUNs on external SAN storage LUNs must be accessible to a VIOServer on each system Invoked by HMC command or GUI migrlpar
IBM Training
Your Mobile LPAR In this Lab Session

LP PA AR R L L P A R
hdisk0 hdisk1
Server A
vscsi0
en0
H HY YP PE ER RV V II S SO OR R
vhost0 vtscsi0 LV01 hdisk2 fcs0 en2 hdisk1 en0 en1 en2 SEA
Service processor
VLAN
VASI
Private Network
MSP
V V II O O Server Server
Go to the lab exercise to resolve
H HM MC C
LUN
IBM Training
https://egateway1.atlanta.ibm.com userid 46939-## password tivoli-91
2
sys2
HMC https://10.31.203.121
sys1
team number X 10.31.203.XXX
10
20 7
T1,124
11 2
T1,134
21 8
T2,125
12 3
T2,135
22 9
T3,127
13 4
T3,137
23 10
T4,128
14 5 15 6
T4,138
24 11 25 12
T5,164
T6,165
T5,167
T6,168
IBM Training
Other Passwords:
hscroot = abc123 (for HMC) root = ibmaix (for client LPARs) padmin viosrv (for Virtual I/O Server)
IBM Training
Lab Environment
HMC r11s1hmc 10.31.203.121 FSP r11s1fsp 10.31.203.122 LPARs sys1_v1 10.31.203.123 sys1_v1_T1 10.31.203.124 sys1_v1_T2 10.31.203.125 sys2_v1 10.31.203.133 sys2_v1_T1 10.31.203.134 sys2_v1_T2 10.31.203.135 LPARs sys1_v2 10.31.203.126 sys1_v2_T3 10.31.203.127 sys1_v2_T4 10.31.203.128 sys2_v2 10.31.203.136 sys2_v2_T3 10.31.203.137 sys2_v2_T4 10.31.203.138 LPARs sys1_v3 10.31.203.163 sys1_v3_T5 10.31.203.164 sys1_v3_T6 10.31.203.165 sys2_v3 10.31.203.166 sys2_v3_T5 10.31.203.167 sys2_v3_T6 10.31.203.168
r11s2hmc 10.31.203.131
r11s2fsp 10.31.203.132
IBM Training
Components
Partition
Virtual Disk
Mapped through VIO Server to a LUN Mapped through SEA in VIO Server
hdisk0 hdisk1
Server A
Virtual Ethernet
vscsi0
en0
vhost0 vtscsi0 LV01 hdisk2 fcs0 en2 hdisk1 en0 en1 en2 SEA
VASI
VIO Server
Provides the Virtual I/O VASI interface to Hypervisor Mover Service Partition (MSP)
MSP
HMC
Configuration of required capabilities Validation of configuration Orchestrates the sequence of events
LUN
H HM MC C
VASI = Virtual Asynchronous Services Interface

2008 IBM Corporation 9
Private Network
vSCSI Virtual Ethernet Support for migration
Service processor
Hypervisor
VLAN
IBM Training
Basic Requirements (1 of 2)
Two POWER6 Systems managed by the same HMC
Advanced Power Virtualization Enterprise (APV-E) feature activated
Compatible CODE levels (with Partition Mobility enabled)

HMC, System Firmware, AIX, VIO Server
The same LMB (Logical Memory Block) size on each System Source and target systems Virtual I/O Server:
VASI / MSP LUN access ( external hdisk with no_reserve ) provide mobile LPARs network and disk access
LUN access (external hdisk with no_reserve ) Both systems must have a shared Ethernet adapter configured to bridge to the same Ethernet network
Target System :
No partition with the same name as the one that is to be Migrated Must have sufficient resources (e.g. CPU & Memory) available
10
IBM Training
Basic Requirements (2 of 2)
Partition to be migrated must satisfy the following requirements: Allocated only Virtual devices 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
11
IBM Training
Validation (1 of 5)
Validation Check Options lslparmigr and migrlpar HMC commands

$ lslparmigr -r virtualio -m srcSystem -t destSystem \ -filter lpar_names=myLPAR $ lslparmigr -r msp -m srcSystem -t destSystem -filter \ "lpar_names=myLPAR $ migrlpar -o v -m srcSystem -t destSystem -p myLPAR \ -i source_msp_id=2,dest_msp_name=S2_VIOS2
HMC GUI
12
IBM Training
Validation (2 of 5)
Validation process checks the following: RMC connections to both VIO Servers RMC connection to the partition to be Migrated LMB sizes on Both Systems Checks the Partition to be Migrated (Partition Readiness) : No physical adapters defined as required in the LPAR The LPAR uses only external LUNs
VSCSI can not be backed by LVs in VIOS

The LPAR supports active migration ( OS support ) The LPAR type is aixlinux The LPAR is NOT a Mover Service Partition The LPAR is NOT using Barrier Synchronisation Registers The LPAR is NOT using Huge Pages The LPAR state is active/running The LPAR is NOT in a Partition workload Group The LPAR MAC address is unique ( across both servers ) The LPAR has a name which is NOT in use on the Target System Checks that we do not exceed the supported number of active migrations
IBM Training
Validation (3 of 5)
Validation Wizard example
The only thing needed for validation
IBM Training
Validation (4 of 5)
Validation Wizard example
Target VIO Server with the LUN available Select Migrate when Validation is successful
IBM Training
Validation (5 of 5)
New RMC capabilities
Enabled by new code in the VIO Server and AIX Partitions
hscroot@daihmc1:~> lspartition dlpar
Partition ID#
<#6> Partition:<1*9117-MMA*101CD8F, p00.aixncc.uk.ibm.com, 9.137.62.240> Active:<1>, OS:<AIX, 5.3, 5300-05-06-0000>, DCaps:<0x19f>, CmdCaps:<0xb, 0xb>, PinnedMem:<376> <#5> Partition:<1*9117-MMA*101CD7F, p04.aixncc.uk.ibm.com, 9.137.62.244> Active:<1>, OS:<AIX, 5.3, 5300-05-06-0000>, DCaps:<0x19f>, CmdCaps:<0xb, 0xb>, PinnedMem:<392> <#7> Partition:<2*9117-MMA*101CD8F, p01.aixncc.uk.ibm.com,9.137.62.241> Active:<1>, OS:<AIX, 5.3, 5300-06-00-0000>,DCaps:<0x5f>, CmdCaps:<0xb, 0xb>, PinnedMem:<256>
Suggestion: always use lspartition -dlpar before trying a Migration

16
IBM Training
Partition Mobility Process (1 of 4)

hdisk0
Server A
Server B
vscsi0
en0
RMC
Service processor
VLAN VLAN
Service processor
VASI
VASI
vhost0 vtscsi0 hdisk1 fcs0 en2 en1 en2 SEA
en1 en2 en2 SEA hdisk1 en0
MSP
RM C
Private Network
MSP
C RM
Private Network
en0
fcs0
H HM MC C
Open Network
Ethernet Network
LUN
Storage Area Network

IBM Training

hdisk0
Server A
Server B
hdisk0
vscsi0
en0
RMC
Service processor
VLAN
RMC
VLAN
en0
Service processor
VASI
VASI
en1 en2 en2 SEA hdisk1 en0 vhost0 vtscsi0 fcs0
MSP
RM C
Private Network
MSP
C RM
Private Network
en0
H HM MC C
Open Network
Ethernet Network
LUN

IBM Training
Migrating the LPAR (3 of 4)

Partition State Information
Transferred from the Source System Hypervisor Source System MSP collects this through the VASI Source MSP Transfers the State Information to the Target MSP Target MSP transfers the data to Hypervisor Hypervisor transfers state to the new partition Includes the following :
Current Processor configuration - dedicated/shared, processor count, and processor entitlement (minimum/maximum/desired) Memory configuration - (minimum/maximum/desired), Virtual Adapter configuration ( vSCSI and VLAN ) partitions memory content, hardware page table (HPT), processor state, virtual adapter state, non-volatile RAM (NVRAM), time of day (ToD), partition configuration, state of each resource
Note : The State Information represents the LPARs current characteristics ( it is NOT based on any of the LPAR profiles )
IBM Training

hdisk0
Server A
Server B
hdisk0
vscsi0
en0
RMC
Service processor
VLAN
RMC
VLAN
en0
Service processor
VASI
VASI
MSP
RM C
Private Network
Logical Memory Copy
MSP
C RM
Private Network
en0
H HM MC C
Memory Copy over network
Open Network
Ethernet Network
LUN

IBM Training

Server A Server B LP PA AR R L L P A R
hdisk0 en0 vscsi0
RMC
Service processor
VLAN VLAN
Service processor
VASI
VASI
en2 hdisk1 fcs0 en1 en2 SEA
MSP
RM C
Private Network
MSP
C RM
Private Network
en0
H HM MC C
Open Network
Ethernet Network
LUN

IBM Training
Summary
Overview of the Live Partition Mobility Process Implement Live Partition Mobility
V4.1
Student Exercises with hints
EXempty
Implementing Live Partition Mobility

Conference Lab Session
(with hints)
What this exercise is about

This exercise covers the steps required to perform the Live Partition Mobility procedure.
What you should be able to do

At the end of this exercise, you should be able to: Configure the environment to support a Live Partition Mobility process Migrate an LPAR between two POWER6 systems
Introduction
In this exercise, you configure the assigned lab environment to support a Live Partition Mobility process. You configure the Virtual I/O Servers as Mover Service Partitions, and start and monitor the migration process.
Requirements
Each student must have access to two POWER6 systems and the associated HMCs. The systems must have the PowerVM Enterprise PVMe (APVe) feature enabled in the system firmware.
Copyright IBM Corp. 2007

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
1-1
Lab Environment
HMC r11s1hmc 10.31.203.121 FSP r11s1fsp 10.31.203.122 LPARs sys1_v1 10.31.203.123 sys1_v1_T1 10.31.203.124 sys1_v1_T2 10.31.203.125 sys2_v1 10.31.203.133 sys2_v1_T1 10.31.203.134 sys2_v1_T2 10.31.203.135 LPARs sys1_v2 10.31.203.126 sys1_v2_T3 10.31.203.127 sys1_v2_T4 10.31.203.128 sys2_v2 10.31.203.136 sys2_v2_T3 10.31.203.137 sys2_v2_T4 10.31.203.138 LPARs sys1_v3 10.31.203.163 sys1_v3_T5 10.31.203.164 sys1_v3_T6 10.31.203.165 sys2_v3 10.31.203.166 sys2_v3_T5 10.31.203.167 sys2_v3_T6 10.31.203.168
r11s2hmc 10.31.203.131
r11s2fsp 10.31.203.132
1-2
POWER6
V4.1
EXempty
Exercise instructions (with hints)

Preface
You must work with a partner for this exercise You move your team's LPAR on your PRIMARY managed system to your Secondary managed system - Teams 1 thru 6: Primary is sys1 (secondary is sys2) - Teams 7 thru 12: Primary is sys2 (secondary is sys1) All hints are marked by a sign. Partition mobility preparation steps: Put logical partition rootvg on external storage LUN. The lab environment has the following virtual SCSI backing devices:
Team number Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9 Team 10 Team 11 Team 12
Virtual I/O Server LPAR Name sys1_v1 sys1_v1 sys1_v2 sys1_v2 sys1_v3 sys1_v3 sys2_v1 sys2_v1 sys2_v2 sys2_v2 sys2_v3 sys2_v3 sys1_v1_T1 sys1_v1_T2 sys1_v2_T3 sys1_v2_T4 sys1_v3_T5 sys1_v3_T6 sys2_v1_T1 sys2_v1_T2 sys2_v2_T3 sys2_v2_T4 sys2_v3_T5 sys2_v3_T6
VIO adapter information for logical volume disks vhost0 T1_rootvg vhost1 T2_rootvg vhost0 T3_rootvg vhost1 T4_rootvg vhost0 T5_rootvg vhost1 T6_rootvg vhost0 T1_rootvg vhost1 T2_rootvg vhost0 T3_rootvg vhost1 T4_rootvg vhost0 T5_rootvg vhost1 T6_rootvg
Table 1: Backing devices: Logical volume disks
Team number Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9
Virtual I/O Server LPAR Name sys1_v1 sys1_v1 sys1_v2 sys1_v2 sys1_v3 sys1_v3 sys2_v1 sys2_v1 sys2_v2 sys1_v1_T1 sys1_v1_T2 sys1_v2_T3 sys1_v2_T4 sys1_v3_T5 sys1_v3_T6 sys2_v1_T1 sys2_v1_T2 sys2_v2_T3
VIO adapter information for shared disks vhost0 shared disk vhost1 shared disk vhost0 shared disk vhost1 shared disk vhost0 shared disk vhost1 shared disk vhost0 shared disk vhost1 shared disk vhost0 shared disk
Implementing Live Partition Mobility 1-3
Team 10 sys2_v2 sys2_v2_T4 Team 11 sys2_v3 sys2_v3_T5 Team 12 sys2_v3 sys2_v3_T6 Table 2: Backing devices: Shared disks
vhost1 shared disk vhost0 shared disk vhost1 shared disk
__ 1. On your team LPAR session on your primary system, make sure you see only hdisk0 and hdisk1 and then execute the command alt_disk_copy -d hdisk1 to clone the rootvg volume group to hdisk1. The alternate disk installation should last several minutes. When done, check to make sure the bootlist contains hdisk1. Then reboot the partition and check that rootvg is now active on hdisk1. # bootlist -o -m normal # lspv hdisk0 00c4b88e3d8adc74 rootvg hdisk1 00c4b88e844fced5 altinst_rootvg # shutdown -Fr # lspv hdisk0 00c4b88e3d8adc74 old_rootvg hdisk1 00c4b88e844fced5 rootvg
Partition Mobility steps: __ 2. Access your primary system HMC using a browser session and view the system Properties' to verify that your system has the capability: Active Partition Mobility Capable Select Systems Management --> Servers. Select your server/POWER6 system by selecting the box in the Select' column, then Properties' from the context or task menus. __ 3. Your HMC controls each phase of the migration process; phases on source and destination systems. In order to accomplish this, it must be configured to manage the source and destination systems. At this time, if your HMC browser session does not list two managed systems then ask your instructor for help. __ 4. On your HMC browser session, display your vio LPAR Properties menu. Look at the General tab and verify the Mover Service Partition' attribute is set.
1-4
POWER6
V4.1
EXempty

1-5
__ 5. Start an HMC command line session to your primary system (use ssh/putty) and execute the lslparmigr command to list the source and destination system's mover service partitions (managed system names are displayed in the HMC browser session). hscroot@<hmc_hostname> $ lslparmigr r msp m <source managed system name> \ -t <destination managed system name> \ --filter lpar_names=<mobile partition name> __ 6. Using the HMC browser session, start the Validation' process. Select System Management -> Servers' and select your managed system's name. In the Contents pane, select your mobile LPAR by selecting the selection box on the same row as your LPAR. Then from the LPAR's context menu, select Operations -> Mobility -> Validate. Make sure menu is filled in for destination= your secondary managed system and profile=default (shared processor pool may be left empty). Note: Make sure the MSP values are for your source and destination MSPs. The GUI usually defaults to the first MSP found. This may not be correct for you team! Use the MSP Pairing button to resolve. __ 7. Wait. You should get an error (HSCLA27C) regarding a virtual disk backed by LVM. Continue to the next step. If you get any other error you need to fix that first.
__ 8. On your AIX LPAR, perform an ODM clean up, then remove the hdisk0 disk device. # alt_rootvg_op -X old_rootvg # rmdev -dl hdisk0 __ 9. On your assigned Virtual I/O Server, delete the logical volume virtual scsi device that was mapped to the logical volume used for your AIX LPARs original rootvg. $ rmdev -dev T<#>_rootvg (see table 1above for value of #)
1-6 POWER6
V4.1
EXempty
__ 10. Validate again. You must successfully validate before proceeding to the next step. The following message(s) shows a successful outcome (these are warnings (not errors)): HSCLA295 As part of the migration process, the HMC creates a new migration profile containing the partition's current state. The default is to use the current profile, which replaces the existing definition of this profile. While this works for most scenarios, other options are possible. You may specify a different existing profile, which would be replaced with the current partition definition, or you may specify a new profile to save the current partition state. HSCLA291 The selected partition may have an open virtual terminal session. The HMC forces termination of the partition's open virtual terminal session when the migration has completed. HSCLA248 The host adapter for virtual SCSI adapter 12 on the virtual I/O server (VIOS) partition 65535 allows for any remote partition to connect, not just the migrating partition. For this reason, when you migrate the partition off of this managed system, the hosting virtual SCSI adapter remains with the VIOS and you may not be able to migrate the partition back.
__ 11. Establish two login sessions -- one to each of your vio LPARs. In these sessions, start topas to monitor the CPU and network resource utilization during the migration process. __ 12. In a separate telnet session, log on to your mobile LPAR. Execute the wormc binary, if it is available in the root directory. This allows you to have a visual indicator that your mobile LPAR is running. It also shows that the LPAR has started to run on the target system by changing color. If you dont have this executable, simply run topas or ping command (ping your HMC). __ 13. Use the HMC browser session or the migrlpar HMC command to perform the migration. To use the browser session, if the Validation' session window is still opened, select the Migrate' button. Make sure the MSP values are for your source and destination MSPs. The GUI usually defaults to the first MSP found. This may not be correct for you team! Use the MSP Pairing button to resolve. Otherwise, select System Management -> Servers' and select your managed system's name. In the Contents pane, select your mobile LPAR by selecting the selection box on the same row as your LPAR. Then from the LPAR's context menu, select Operations -> Mobility -> Migrate. Or to use the HMC command line interface execute the following command: $ migrlpar -o m -m <source_managed_system> -t <dest._Managed_sys.> -p \ <mobile lpar> -n < partition_profile_name_to_create> -d 5 v
Copyright IBM Corp. 2007 Implementing Live Partition Mobility
1-7
__ 14. Look at the topas command outputs and notice the kernel, CPU, and network activity. Using the lspartition HMC command, identify the LPAR's new partition ID and managed system. $ lspartition -dlpar
End of exercise
1-8
POWER6
V4.1
EXempty
Exercise review and wrap-up

This exercise provided hands on exposure to the POWER6 Logical Partition Mobility feature.

1-9
1-10 POWER6

Implementing Live Partition Mobility

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Implementing Live Partition Mobility

Încărcat de

Drepturi de autor:

Formate disponibile

IBM Power Systems Technical University featuring IBM AIX and Linux

September 8 12, 2008 Chicago, IL

Session Title: Implementing Live Partition Mobility Session ID: pAI54

2008 IBM Corporation

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

The following are trademarks or registered trademarks of other companies.

2008 IBM Corporation

2008 IBM Corporation

2008 IBM Corporation

Your Mobile LPAR In this Lab Session

Go to the lab exercise to resolve

2008 IBM Corporation

https://egateway1.atlanta.ibm.com userid 46939-## password tivoli-91

team number X 10.31.203.XXX

2008 IBM Corporation

2008 IBM Corporation

VASI = Virtual Asynchronous Services Interface

vSCSI Virtual Ethernet Support for migration

Compatible CODE levels (with Partition Mobility enabled)

2008 IBM Corporation

2008 IBM Corporation

Validation Check Options lslparmigr and migrlpar HMC commands

2008 IBM Corporation

VSCSI can not be backed by LVs in VIOS

Validation Wizard example

The only thing needed for validation

2008 IBM Corporation

Validation Wizard example

Suggestion: always use lspartition -dlpar before trying a Migration

Partition Mobility Process (1 of 4)

Storage Area Network

Partition Mobility Process (2 of 4)

Storage Area Network

Migrating the LPAR (3 of 4)

Partition Mobility Process (2 of 4)

Logical Memory Copy

Storage Area Network

Partition Mobility Process (4 of 4)

Storage Area Network

2008 IBM Corporation