POWER7 information

Preparing the source and destination Virtual I/O Server logical partitions for partition mobility

You must verify that the source and destination Virtual I/O Server (VIOS) logical partitions 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 verification includes tasks such as verifying the version of the VIOS partitions and enabling the mover service partitions.

To prepare the source and destination VIOS partitions for active or inactive partition mobility, complete the following tasks.

Table 1. Preparation tasks for the source and destination VIOS partitions
VIOS planning tasks Active mobility task Inactive mobility task Information resources
1. Ensure that at least one VIOS partition is installed and activated on both the source and destination servers.

If the mobile partition receives virtual storage resources from redundant VIOS partitions on the source server, install the same number of VIOS partitions on the destination server, if possible.

Remember: In some situations, you can select the option to override virtual storage errors if possible and move a logical partition to a destination system with less redundancy.
 X X Installing the Virtual I/O Server and client logical partitions
2. Ensure that the source and destination VIOS partitions are at the following versions:
  • To move AIX® or Linux logical partitions, ensure that the source and destination VIOS partitions are at Version 2.1.2.0, Service Pack 1, or later.
  • To move IBM® i logical partitions, ensure that the source and destination VIOS partitions are at Version 2.2.1.3, Fix Pack 25, Service Pack 1, or later.
Notes:
  • From VIOS Version 2.2.0.11, Fix Pack 24, Service Pack 1 to VIOS Version 2.2.1.0, Live Partition Mobility for a client partition that uses storage that is provisioned from a shared storage pool is not supported.
  • From VIOS Version 2.2.0.11, Fix Pack 24, Service Pack 1 to VIOS Version 2.2.2.2, the Suspend/Resume feature for an AIX, IBM i, or Linux logical partition, which uses storage that is exported from a VIOS partition that is backed up by a shared storage pool is not supported.
  • From VIOS Version 2.2.3.0, or later, you can import one or more physical volumes into a shared storage pool.
    • You must not move an active or inactive partition that can access the physical volume while the import operation is in progress.
    • You must deactivate the paging space device for a partition that supports the Suspend/Resume features by disabling the features in the partition profile. After the import operation completes, you can enable these features again before the partition profile is activated.
 X X
3. Ensure that the mover service partition is enabled on one or more source and destination VIOS partitions.
Note: From VIOS Version 2.2.0.11, Fix Pack 24, Service Pack 1 to VIOS Version 2.2.1.0, you cannot use a VIOS logical partition that uses a shared storage pool as a mover service partition.
 X   Enabling the source and destination mover service partitions
4. If the mobile partition uses shared memory, verify that at least one VIOS partition is assigned to the shared memory pool on the destination server (subsequently referred to as a paging VIOS partition) and that it is at release level 2.1.1, or later.

If the mobile partition accesses its paging space device redundantly through two paging VIOS partitions and you want to maintain this redundancy on the destination server, verify that two paging VIOS partitions are assigned to the shared memory pool on the destination server.

Notes:
  • From VIOS Version 2.2.0.11, Fix Pack 24, Service Pack 1 to VIOS Version 2.2.1.0, you cannot use a VIOS logical partition that uses a shared storage pool as a paging space partition.
  • In VIOS Version 2.2.0.11, Fix Pack 24, Service Pack 1, or later, you cannot use logical units in shared storage pools as paging devices.
 X X
5. If the mobile partition uses shared memory, verify that the shared memory pool on the destination server contains a paging space device that satisfies the size requirements and redundancy configuration of the mobile partition. X X Verifying that the destination shared memory pool contains an available paging space device
6. Optional: Synchronize the time-of-day clocks for the source and destination VIOS partitions. X   Synchronizing the time-of-day clocks of the source and destination Virtual I/O Server logical partitions
Parent topic: Preparing for partition mobility
Related concepts:
Source and destination Virtual I/O Server logical partitions in a partition mobility environment

Send feedback Rate this page

Last updated: Sat, March 17, 2018