Verifying that the destination shared memory pool contains an available paging space device

You can 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 by using the Hardware Management Console (HMC).

1. Identify the size requirements of the mobile partition. The paging space device for the AIX®, IBM® i, or Linux logical partition that uses shared memory (hereafter referred to as a shared memory partition) must be at least the size of the maximum logical memory of the shared memory partition. To view the maximum logical memory of the mobile partition, complete the following steps:
   1. In the navigation pane, expand Systems Management > Servers, and click the system on which the mobile partition is located.
   2. In the work pane, select the mobile partition, click the Tasks button, and click Properties. The Partition Properties window is displayed.
   3. Click the Hardware tab.

      The HMC Classic interface is not supported in Hardware Management Console (HMC) Version 8.7.0, or later. The functions that were previously available in the HMC Classic interface are now available in the HMC Enhanced+ interface.

      When the HMC is at version 8.7.0, or later, complete the following steps to 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

      1. In the navigation pane, click the Resources icon .
      2. Click All Partitions. Alternatively, click All Systems. In the work pane, click the server name that has the logical partition. Click View System Partitions. The All Partitions page is displayed.
      3. In the work pane, select the logical partition and click Actions > View Partition Properties.
   4. Click the Memory tab.
   5. Record the maximum logical memory. This is the size requirement for the paging space device for the mobile partition.
2. Identify the redundancy configuration of the mobile partition. In the Memory tab of the Partition Properties of the mobile partition, record the number of Virtual I/O Server (VIOS) logical partitions (hereafter referred to as paging VIOS partitions) that are assigned to the mobile partition:
   • If the mobile partition is assigned a primary paging VIOS partition and no secondary paging VIOS partition is assigned, then the mobile partition does not use redundant paging VIOS partitions. In this case, the mobile partition uses a paging space device that can only be accessed by one paging VIOS partition in the shared memory pool.
   • If the mobile partition is assigned a primary paging VIOS partition and a secondary paging VIOS partition, then the mobile partition uses redundant paging VIOS partitions. In this case, the mobile partition uses a paging space device that can be accessed redundantly by both paging VIOS partitions in the shared memory pool.
3. View the paging space devices that are currently assigned to the shared memory pool on the destination server:
   1. In the navigation pane, expand Systems Management and click Servers.
   2. In the work pane, select the destination server.
   3. From the Tasks menu, click Configuration > Virtual Resources > Shared Memory Pool Management. The Shared Memory Pool Management window is displayed.
      When the HMC is at version 8.7.0, or later, complete the following steps to view the paging space devices that are currently assigned to the shared memory pool on the destination server:

      1. In the navigation pane, click the Resources icon .
      2. Click All Systems. The All Systems page is displayed.
      3. In the work pane, select the system and click Actions > View System Properties. The Properties page is displayed.
      4. Click Shared Memory Pool.
   4. Click the Paging Devices tab.
   5. Take note of the available paging space devices, their size, and whether they are capable of redundancy.
   Note: Paging space devices can only be assigned to one shared memory pool at a time. You cannot assign the same paging space device to shared memory pools on two different systems at the same time.
4. Determine whether the shared memory pool on the destination server has a suitable paging space device for the mobile partition.
   1. If the mobile partition does not use redundant paging VIOS partitions, verify that there is an active paging space device that is not capable of redundancy and meets the size requirement of the mobile partition. If no such device exists, you have the following options:
      • You can add a paging space device to the shared memory pool on the destination server. For instructions, see Adding and removing paging space devices to and from the shared memory pool.
      • If the shared memory pool contains an available paging space device that satisfies the size requirements of the mobile partition, but is capable of redundancy, you can migrate the mobile partition to the destination server. In this case, when you migrate the mobile partition to the destination server (active partition mobility) or when you activate the mobile partition on the destination server (inactive partition mobility), the HMC assigns the paging space device that is capable of redundancy to the mobile partition.
   2. If the mobile partition uses redundant paging VIOS partitions, verify that an active paging space device is capable of redundancy and meets the size requirements of the mobile partition. If no such device exists, you have the following options:
      • You can add a paging space device to the shared memory pool on the destination server. For instructions, see Adding and removing paging space devices to and from the shared memory pool.
      • If the shared memory pool contains an available paging space device that satisfies the size requirements of the mobile partition, but is not capable of redundancy, you can migrate the mobile partition to the destination server. When you migrate the mobile partition to the destination server (active partition mobility) or when you activate the mobile partition on the destination server (inactive partition mobility), the HMC assigns the paging space device that is not capable of redundancy to the mobile partition. However, instead of using redundant paging VIOS partitions on the destination server, the mobile partition uses only the paging VIOS partition that has access to the paging space device that is not capable of redundancy.