How to perform LPM of AIX lpar using HMC CLI ?

In Short

Validation (v)
migrlpar -m system1 -t system2 -p partition1 --ip 9.x.x.x -o v

Migration (m)
migrlpar -m system1 -t system2 -p partition1 --ip 9.x.x.x -o m

Where system1 and system2 are source and target partition, partition1 is the AIX partition that needs to be migrated and 9.x.x.x is target hmc ip address (Optional if system2 is not connected to same HMC)

Detailed Explanation

Live Partition Mobility (LPM) is a feature of AIX Operating system where the partition can be migrated from one system to another Power System. The system where partition is currently running will be referred as source Power System and the system where partition will be migrated to will be referred as target Power System.

The admin moves the AIX partition from source to destination Power System because of reason such as maintenance activity on source system, scheduled power outage, scheduled network outage, planned software update, planned hardware update on source Power System.

Hardware requirement 
Power System - Power6 and above
HMC - Version 310 and above
AIX and VIOS version 5.3 and and later releases

LPM Setup Requirement
Storage - NPIV, vSCSI and SSP to be shared on target system, if the source and target system in not connected to same SAN switch LPM will loose disk connection. Also disk should be shared across source and target system for vSCSI and SSP.
Network - Source and Target system both should support same VLAN.
Processor and Memory - Target system should have abundant processor and memory to fit the AIX partition configuration.
MSP enabled - Source and Target system should have minimum one MSP enabled. To know more about MSP refer this page. Enable and Disable MSP
Source and Target HMC - Both source and target should have exchange ssh keys between them. To know more about Exchanging Keys refer this page. Exchange SSH Keys

Performing LPM

We need to validate the partition before the actual partition is being migrated. This step allows user to find out if storage, network, processor and memory are present on target system required for migration. If the migration fails the user/admin will require to fix it until the partition validation passes.

Command to validate the partition
migrlpar -m system1 -t system2 -p partition1 --ip 9.x.x.x -o v

Command to migrate the partition
migrlpar -m system1 -t system2 -p partition1 --ip 9.x.x.x -o m

During the migration process the Source HMC will perform another round of migration validate checks, collects the data related to storage and network, validates the data collection.

After these validation the actual partition creation starts on target system with the same capabilities as in source system, creates the profile, assign the memory and processor resource to partition and creates storage and network mappings. Then the partition is check pointed and state is resumed on target system by transferring the state, once it gets resumed the clean up of resource is done on the source system