Understanding the required options for HMC CLI 'migrlpar' command for LPM validation or migration

Steps

This document helps capturing the output of the HMC migrlpar command for an LPM migration or validation  as well as explaining how to fill in the required options of the  command, which can be later used for debugging purpose by support.

$ oem_setup_env (gain root access )

# script /tmp/<case number>.HMC.txt

# ssh -l hscroot <HMC IP address>

a)  To get the version of the HMC:

$ lshmc -v

b) To get [managed_system] name of this frame

$ lssyscfg -r sys -F name

c) To get the VIO server names and the mobile LPAR name as known by HMC

$ lssyscfg -r lpar -m <managed system name> -F --header

d) Provided below is one long command line for validation. Please check step 7. of this tech note for help with filling in the options for the command.

$migrlpar -o v

-m managed system

-t managed system -p partition name

-i "source_msp_id=<ID>,source_msp_ipaddr=<ip_addr>,dest_msp_id=<ID>,dest_msp_ipaddr=<IPaddr>"

-d 5 -v

The "v" following the -o indicates that this command is for LPM validation. If we were to migrate an LPAR, then we would replace "v" with "m" with the "-o" in the above

command line.

$ exit <— this will exit from the HMC

# exit <— this will end writing to the /tmp/<case number>.HMC.txt

The output of the command run in 3. b) helps identify all the systems the HMC manages.

A)Firstly, we need to identify the system where the mobile LPAR ( the VM that we need to LPM) resides on. This is the source system. That is our managed system that goes with-m option.

Then identify the system where we need this LPAR to migrate to. This is the destination system or the target system. This is the managed system that goes with the -t option.

.

B)The attribute partition name is the mobile LPAR that we need to migrate.

.

C)The next step is to figure out which VIO servers are enabled as the Mover Service Partitions ( MSPs) on both the source and destination systems. We need one from the source system and the another one from the destination system.

The following link has documentation that explains how to enable the MSP using HMC.

https://www.ibm.com/support/knowledgecenter/en/POWER5/iphc3_p5/iphc3planviosmsp.htm

.

D) Once we have identified or enabled MSP on both the source and destination managed systems, then we need to note the partition IDs for these two VIO servers

source_msp_id=<ID><--- ID is the partition ID of the MSP on the source system.

dest_msp_id=<ID><--- ID is the partition ID of the MSP on the destination system.

.

E) The next step is to identify the IP address that we are going to use on these MSPs for the migration.

a) Login to the source MSP as padmin user:

# oem_setup_env

$ ifconfig -a

If there is one IP configured, then you use that for the source_msp_ipaddr=<ip_addr>

If there are more than one, then pick the IP address that is configured on a dedicated adapter interface.

.

b) Login to the destination MSP as padmin user:

# oem_setup_env

$ ifconfig -a

If there is one IP configured, then you use that for the dest_msp_ipaddr=<IPaddr>

If there are more than one, then pick the dedicated adapter.