Preparing the HMC for partition mobility

You need to verify that the Hardware Management Console (HMC) that manage the source and destination servers are configured correctly so that you can migrate the mobile partition from the source server to the destination server.

To prepare the HMC or HMCs for active or inactive partition mobility, complete the following tasks.

Table 1. Preparation tasks for the HMC
HMC planning tasks Active mobility task Inactive mobility task Information resources
1. Ensure that the HMC that manages the source server and the HMC that manages the destination server meet the following version requirements:
  • If the source server, the destination server, or both servers are POWER8® processor-based servers, ensure that the HMC or HMCs that manage the servers are at Version 8 Release 8.1, or later.
  • If the source server, the destination server, or both servers are POWER7® processor-based servers, ensure that the HMC or HMCs that manage the servers are at Version 7 Release 7.1, or later.
  • If the source server or the destination server is a POWER6® processor-based server, ensure that the HMC that manages that server is at Version 7 Release 3.5, or later.
  • If the HMC at the source server is at version 7.7.8 or later, the HMC at the destination server must be at version 7.7.8 or later. If the HMC at the destination server is at an earlier version, select the Override partition UUID check box.
X X
2. If the source server is managed by one HMC and the destination server is managed by a different HMC, verify that the secure shell (SSH) authentication keys are set up correctly between the HMC that manages the source server and the HMC that manages the destination server. X X Verifying SSH authentication between the source and destination HMC
3. If the mobile partition on the source server uses Active Memory™ Expansion, ensure that the HMC that manages the destination server is at Version 7 Release 7.1, or later. X X Verifying the destination server for Active Memory Expansion
4. If the mobile partition on the source server is capable of suspension, ensure that the HMC that manages the destination server is at Version 7 Release 7.2, or later. The Suspend/Resume feature for logical partitions is supported on POWER8 processor-based servers when the firmware is at level 8.4.0, or later. X X
5. If the mobile partition on the source server is capable of the Trusted Boot capability, ensure that the HMC that manages the destination server is at Version 7 Release 7.4.0, or later. X X
6. If you are moving an IBM i mobile partition, ensure that the HMC that manages the destination server is at Version 7 Release 7.5.0, or later. X X
7. If the mobile partition on the source server is capable of remote restart, ensure that the HMC that manages the destination server is at Version 7 Release 7.6.0, or later. You must add the reserved storage device that is mapped to the partition that is on the source server to the reserved storage pool in the destination server.

When the HMC at the source and destination servers are at Version 8.2.0, or later, and when the servers support the simplified version of the remote restart feature, you can migrate partitions that are capable of the simplified version of the remote restart feature.

X X
If the mobile partition on the source server is configured with less than 0.1 and greater than or equal to 0.05 processing units, ensure that the destination server supports the same configuration. The HMC must be at Version 7 Release 7.6.0, or later. X X Verifying the processor-level hardware capabilities of the destination server
If the mobile partition on the source server uses the virtual server network (VSN), verify that the destination server also uses VSN. The HMC must be at Version 7 Release 7.7.0, or later. X X Verifying that the destination server supports the virtual server network



Last updated: Tue, March 12, 2019