Subscribe to this information
POWER7 information
HMC-managed systems: Preparing the source and destination servers for partition mobility
You need to verify that the source and destination servers are configured correctly so that you can successfully move the mobile partition from the source server to the destination server by using the Hardware Management Console (HMC). This includes tasks such as verifying the logical memory block size of the source and destination servers, and verifying the available memory and processor resources of the destination server.
To prepare the source and destination servers for active or inactive partition mobility, complete the following tasks.
| Server planning tasks | Active mobility task | Inactive mobility task | Information resources |
|---|---|---|---|
| 1. Ensure that the PowerVM® Enterprise Edition hardware feature is activated. | X | X | |
| 2. If you do not have the PowerVM Enterprise Edition hardware feature, you can evaluate Live Partition Mobility at no cost by using Trial Live Partition Mobility. Ensure that you enter the activation code for Trial Live Partition Mobility. | X | X | |
3. Ensure that the source
and destination servers are one of the following POWER7® models:
Notes:
|
X | X | |
| 4. Ensure that the firmware levels on the source and destination servers are compatible. | X | X | Firmware support matrix for partition mobility |
5. Ensure that the source and destination servers
are managed by an HMC in
one of the following ways:
|
X | X | |
| 6. Ensure that the logical memory block size is the same on the source and destination servers. | X | X | Changing the logical memory block size |
| 7. Ensure that the destination server is not running on battery power. If the destination server is running on battery power, return the server to its regular power source before moving a logical partition. | X | X | |
| 8. If the mobile partition uses shared memory, ensure that the shared memory pool is created on the destination server. | X | X | Configuring the shared memory pool |
| 9. Ensure that the destination server has enough available memory to support the mobile partition. | X |
|
|
| 10. Ensure that the destination server has enough available processors to support the mobile partition. | X | Determining available processors on the destination server | |
| 11. Verify that the source and destination mover service partitions can communicate with each other. | X | ||
| 12. Optional: Define the partition profile policy for inactive partition mobility. | X | Defining the partition profile policy for inactive partition mobility | |
| 13. If the mobile partition on the source server uses Active Memory™ Expansion, verify that the destination server is capable of Active Memory Expansion. | X | X | Verifying the destination server for Active Memory Expansion |
| 14. If
the mobile partition on the source server is suspend-capable, verify
that the destination server also supports suspend-capable partitions.
You must also verify that there is a minimum of one reserved storage
device with a size that can be determined by running the lsrsdevsize command
from the HMC command
line. Before you can use a disk from the reserved storage pool, you might need to clear the first 4096 bytes of the disk when you see a message that indicates that the disk cannot be used. The disk might have stale data indicating that it is already in use by another partition on the managed system, or might actively be used by another managed system. You must verify with your system administrator whether the disk is currently being used. You must initialize the first 4096 bytes of the disk only after you have ensured that the disk is no longer in use and that you have corrected all of the configuration issues associated with using the disk. |
X | X |
|
| 15. If the mobile partition on the source server is capable of the Trusted Boot feature, verify that the destination server supports the Trusted Boot feature and has the same trusted key as the source server. Also, verify that the destination server has an adequate number of available Virtual Trusted Platform Modules (VTPMs) for the mobile partitions to use. | X | X |
|
| 16. If you are moving an IBM i mobile partition, verify that the destination server supports the migration of IBM i mobile partitions and the restricted I/O mode. Also, verify that the IBM i mobile partition is in the restricted I/O mode. | X | X |
|
| If the mobile partition on the source server is a shared processor partition, and configured with processing units to virtual processor ratio of less than 0.1 and greater than or equal to 0.05, verify whether the destination server supports the processor minimum entitlement of 0.05 processor per virtual processor. The source and destination servers must be POWER7 processor-based servers. | X | X | You can verify that the destination server supports the same configuration as the source server by checking the processor level hardware capabilities of the destination server. To check the processor level hardware capabilities, see Verifying the processor-level hardware capabilities of the destination server. |
| If the mobile partition has Single Root IO Virtualization (SR-IOV) logical ports, then that partition cannot be migrated to the destination server. | X | X | |
| If the mobile partition is using a virtual Ethernet adapter which is using a virtual switch that is in the VEPA mode, or the mobile partition is using a virtual Ethernet adapter with a VSI profile, then verify that the destination server also supports virtual server network (VSN). | X | X |
|
