implementing live partition mobility

7/27/2019 Implementing Live Partition Mobility

http://slidepdf.com/reader/full/implementing-live-partition-mobility 1/32

Session Title: Implementing Live PaMobility

Speaker Name: Tyrone DeChalus

Session ID: pAI54

IBM Power Systems Technical University

featuring IBM AIX and Linux

September 8 – 12, 2008 – Chicago, IL



IBM Training

Objectives

Overview of the Live Partition Mobility Pro

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

– LUN’s must be accessible to a VIOServer on each system

Invoked by HMC command or GUI

– migrlpar



IBM Training

H Y P E R V I S O RH Y P E R V I S O RH Y P E R V I S O R

V I O Server V I O Server V I O Server

S e r v i c e

p r o c

e s s o r

L P A RL P A RL P A RL P A R

H M CH M CH M C

Server

A

hdisk0

vhost0

vscsi0 en0

en1

V L A N

en2

SEAen2

en0

V A S

I

hdisk1vtscsi0

L U N

MSP

fcs0

P r i v a t e

N e t w o r k

LV01

hdisk2

hdisk1

Your Mobile LPAR – In this Lab Ses

Go to



IBM Training

team number X

10.31.203.XXX

https://egateway1.atlanta.ibm.com

userid 46939-##

password tivoli-91

1

2

2415 614 5

2313 4

2212 3

2111 2

2010 1

3

T1,124 T1,1

T2,125 T2,

T3,127 T3,

T4,128 T4,

T5,164 T5,T6,165

HMC https://10.31.203.121

sys1 sys



IBM Training

Other Passwords:

hscroot = abc123 (for HMC)

root = ibmaix (for client LPARs)

padmin – viosrv (for Virtual I/O Server)



IBM Training

Lab Environment

sys2_v2 -

10.31.203.136

sys2_v2_T3 -10.31.203.137

sys2_v2_T4 -

10.31.203.138

sys2_v1 -

10.31.203.133

sys2_v1_T1 -10.31.203.134

sys2_v1_T2 -

10.31.203.135

r11s2fsp -

10.31.203.132

r11s2hmc -

10.31.203.131

sys1_v2 -

10.31.203.126

sys1_v2_T3 -

10.31.203.127

sys1_v2_T4 -

10.31.203.128

sys1_v1 -

10.31.203.123

sys1_v1_T1 -

10.31.203.124

sys1_v1_T2 -

10.31.203.125

r11s1fsp -

10.31.203.122

r11s1hmc -

10.31.203.121

LPARsLPARsFSPHMC



IBM Training

Components

VIO Server

Hypervisor

Partition

vSCSI

Virtual Ethernet

Virtual Disk

Virtual Ethernet

Provides the Virtual I/O

Mover Service Partition (MSP)

VASI = Virtual Asynchronous Services Interface

VASI interface to Hypervisor

Mapped through VIO Server to a LUN

Mapped through SEA in VIO Server

Support for migration

HMCConfiguration of required capabilities

Validation of configuration

Orchestrates the sequence of events

H Y P E R V I S O H Y P E R V I S O H Y P E R V I S O



hdisk0

vhost0

vscsi0 en0

V L A N

Sen2

hdisk1vtscsi0

L U N

fcs0

LV01

hdisk2

hdisk1



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 LPAR’s network and disk access

• LUN access (external hdisk with no_reserve )

• Both systems must have a shared Ethernet adapter configured to bridgnetwork

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



IBM Training

Basic Requirements (2 of 2)

Partition to be migrated must satisfy the following requ

– 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



IBM Training

Validation (1 of 5)Validation Check Options

–lslparmigr and migrlpar HMC commands

$ lslparmigr -r virtualio -m srcSystem -t dest

–-filter lpar_names=myLPAR

$ lslparmigr -r msp -m srcSystem -t destSystem"lpar_names=myLPAR“

$ migrlpar -o v -m srcSystem -t destSystem -p

-i source_msp_id=2,dest_msp_name=S2_VIOS2

–HMC GUI



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 LP

• The LPAR uses only external LUNs

– VSCSI can not be backed by LV’s 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 Re

• 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 ser

• The LPAR has a name which is NOT in use on the T

–Checks that we do not exceed the supported number of activ



IBM Training

Validation (3 of 5)•Validation Wizard example

The only thing needed

for validation



IBM Training

Validation (4 of 5)

T

w

•Validation Wizard example



IBM Training

Validation (5 of 5)

hscroot@daihmc1:~> lspartition –dlpar

<#6> Partition:<1*9117-MMA*101CD8F, p00.aixncc.uk.ibm.c

Active:<1>, OS:<AIX, 5.3, 5300-05-06-0000>, DCaps:<0

CmdCaps:<0xb, 0xb>, PinnedMem:<376><#5> Partition:<1*9117-MMA*101CD7F, p04.aixncc.uk.ibm.c

Active:<1>, OS:<AIX, 5.3, 5300-05-06-0000>, DCaps:<0

CmdCaps:<0xb, 0xb>, PinnedMem:<392>

<#7> Partition:<2*9117-MMA*101CD8F, p01.aixncc.uk.ibm.c

Active:<1>, OS:<AIX, 5.3, 5300-06-00-0000>,DCaps:<0x

CmdCaps:<0xb, 0xb>, PinnedMem:<256>

• New RMC capabilities

Enabled by new code in the VIO Server and AIX

Suggestion: always use lspartition -dlpar before trying a Migration

Partition ID#



IBM Training



S e r v i c e

p r o c e s s o r


S er v i c

e pr o c e s s or

H M CH M CH M C

Server

A

Server

B

hdisk0

vhost0

vscsi0 en0

en1H Y PH Y PH Y P

V V IV I

V L A N

en2

SEAen2

en0

E

V A S

I V A

S I

hdisk1

vtscsi0

L U N

MSP MSP

fcs0

P r i v a t e

N e t w o r k

P r i v a t e

N e t w or k

Open Network

en1

en2

SEAe

en0

V L A

RMC

R M CR M

C

Partition Mobility Process (1 of 4



IBM Training



S e r v i c e

p r o c e s s o r


S er v i c

e pr o c e s s or

H M CH M CH M C

Server

A

Server

B

hdisk0

vhost0

vscsi0 en0

en1H Y PH Y PH Y P

V V IV I

V L A N

en2

SEAen2

en0

E

V A S

I V A

S I

hdisk1

vtscsi0

L U N

MSP MSP

fcs0

P r i v a t e

N e t w o r k

P r i v a t e

N e t w or k

Open Network

en1

en2

SEAe

en0

V L A

RMC RMC

R M CR M

C

vhost0




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 Targ

• Target MSP transfers the data to Hypervisor

• Hypervisor transfers state to the new partition

Note : The State Information represents the LPAR’s curren

( it is NOT based on any of the LPAR profiles )

• Includes the following :Current Processor configuration - dedicated/shared, pro

processor entitlement (minimum/maximum/desired)

Memory configuration - (minimum/maximum/desired), V

configuration ( vSCSI and VLAN )

partition’s memory content, hardware page table (HPT),

adapter state, non-volatile RAM (NVRAM), time of d

configuration, state of each resource



IBM Training



S e r v i c e

p r o c e s s o r


S er v i c

e pr o c e s s or

H M CH M CH M C

Server

A

Server

B

hdisk0

vhost0

vscsi0 en0

en1H Y PH Y PH Y P

V V IV I

V L A N

en2

SEAen2

en0

E

V A S

I V A

S I

hdisk1

vtscsi0

L U N

MSP MSP

fcs0

P r i v a t e

N e t w o r k

P r i v a t e

N e t w or k

Open Network

en1

en2

SEAe

en0

V L A

RMC RMC

R M CR M

C

vhost0


Memory Copy over network

Logical Memory Copy



IBM Training

V V IV I



S e r v i c e

p r o c e s s o r

S er v i c

e pr o c e s s or

H M CH M CH M C

Server

A

Server

B

en1H Y PH Y PH Y P

V L A N

en2

SEAen2

en0

E

V A S

I V A

S I

hdisk1

L U N

MSP MSP

fcs0

P r i v a t e

N e t w o r k

P r i v a t e

N e t w or k

Open Network

en1

en2

SEAe

en0

V L A

RMC

R M CR M

C




IBM Training

Summary

Overview of the Live Partition Mobility Pro

Implement Live Partition Mobility



Student Exercises with hints

Course materials may not be reproduced in whole or in part

without the prior written permission of IBM.

© Copyright IBM Corp. 2007 Implementing Live Partition Mobility 1-1

V4.1

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.






1-2 POWER6 © Copyright IBM Corp. 2007

Lab Environment

sys2_v3 -

10.31.203.166

sys2_v3_T5 -

10.31.203.167

sys2_v3_T6 -

10.31.203.168

sys2_v2 -

10.31.203.136

sys2_v2_T3 -

10.31.203.137

sys2_v2_T4 -

10.31.203.138

sys2_v1 -

10.31.203.133

sys2_v1_T1 -

10.31.203.134

sys2_v1_T2 -

10.31.203.135

r11s2fsp -

10.31.203.132

r11s2hmc -

10.31.203.131

sys1_v3 -

10.31.203.163

sys1_v3_T5 -

10.31.203.164

sys1_v3_T6 -10.31.203.165

sys1_v2 -

10.31.203.126

sys1_v2_T3 -

10.31.203.127

sys1_v2_T4 -10.31.203.128

sys1_v1 -

10.31.203.123

sys1_v1_T1 -

10.31.203.124

sys1_v1_T2 -10.31.203.125

r11s1fsp -

10.31.203.122

r11s1hmc -

10.31.203.121

LPARsLPARsLPARsFSPHMC

sys2_v3 -

10.31.203.166

sys2_v3_T5 -

10.31.203.167

sys2_v3_T6 -

10.31.203.168

sys2_v2 -

10.31.203.136

sys2_v2_T3 -

10.31.203.137

sys2_v2_T4 -

10.31.203.138

sys2_v1 -

10.31.203.133

sys2_v1_T1 -

10.31.203.134

sys2_v1_T2 -

10.31.203.135

r11s2fsp -

10.31.203.132

r11s2hmc -

10.31.203.131

sys1_v3 -

10.31.203.163

sys1_v3_T5 -

10.31.203.164

sys1_v3_T6 -10.31.203.165

sys1_v2 -

10.31.203.126

sys1_v2_T3 -

10.31.203.127

sys1_v2_T4 -10.31.203.128

sys1_v1 -

10.31.203.123

sys1_v1_T1 -

10.31.203.124

sys1_v1_T2 -10.31.203.125

r11s1fsp -

10.31.203.122

r11s1hmc -

10.31.203.121

LPARsLPARsLPARsFSPHMC







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:

Table 1: Backing devices: Logical volume disks

Team

number

Virtual I/O Server LPAR Name VIO adapter information

for logical volume disks

Team 1 sys1_ v1 sys1 _v1_T1 vhost0 T1_rootvgTeam 2 sys1 _v1 sys1 _v1_T2 vhost1 T2_rootvg

Team 3 sys1 _v2 sys1 _v2_T3 vhost0 T3_rootvg

Team 4 sys1 _v2 sys1_ v2_T4 vhost1 T4_rootvg



Team 7 sys2_ v1 sys2 _v1_T1 vhost0 T1_rootvg



Team 10 sys2 _v2 sys2_ v2_T4 vhost1 T4_rootvg

Team 11 sys2 _v3 sys2 _v3_T5 vhost0 T5_rootvgTeam 12 sys2 _v3 sys2 _v3_T6 vhost1 T6_rootvg

Team

number

Virtual I/O Server LPAR Name VIO adapter information

for shared disks

Team 1 sys1_ v1 sys1 _v1_T1 vhost0 shared disk

Team 2 sys1 _v1 sys1 _v1_T2 vhost1 shared disk


Team 4 sys1 _v2 sys1_ v2_T4 vhost1 shared disk



Team 7 sys2_ v1 sys2 _v1_T1 vhost0 shared disk









Table 2: Backing devices: Shared disks

__ 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 shouldlast 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.

Team 10 sys2 _v2 sys2_ v2_T4 vhost1 shared disk









V4.1

EXempty







__ 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 foryou 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 LPAR’s original rootvg.

» $ rmdev -dev T<#>_rootvg (see table 1above for value of #)







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 formost 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 don’t 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 managedsystem'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







__ 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







V4.1

EXempty Exercise review and wrap-up

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

feature.

implementing live partition mobility

Documents