You can learn about the tasks that the Integrated Virtualization Manager (IVM) performs to validate your system configuration for active and inactive Partition Mobility.
Before you attempt to migrate an active logical partition, you need to validate your environment. You can use the validation function on the IVM to validate your system configuration. If the IVM detects a configuration or connection problem, it displays an error message with information to help you resolve the problem.
The following tables list validation tasks that the IVM performs to verify that the source and destination systems are ready for active or inactive Partition Mobility.
| Validation task | Active mobility task | Inactive mobility task |
|---|---|---|
| Checks that the resource monitoring and control (RMC) connections are established. | Checks the RMC connections to the mobile partition, the source and destination Virtual I/O Server (VIOS) management partitions, and the connection between the source and destination mover service partitions. | Checks the RMC connections to the source and destination VIOS management partitions. |
| Checks mobility capability and compatibility. | Checks the source and destination servers, POWER6® hypervisor, VIOS management partitions, and mover service partitions. | Checks the VIOS management partitions and the POWER6 hypervisor. |
| Checks the number of current migrations against the number of supported migrations. | Checks the number of current active migrations against the number of supported active migrations. | Checks the number of current inactive migrations against the number of supported inactive migrations. |
| Validation task | Active mobility task | Inactive mobility task |
|---|---|---|
| Checks that the necessary processing resources are available to create a shell logical partition on the destination system. | X | X |
| Checks that the necessary memory resources are available to create a shell logical partition on the destination system. |
|
For a mobile partition that uses dedicated memory, checks that enough physical memory is available on the destination system. |
| Checks that the
necessary I/O adapter resources are available to create a shell logical
partition on the destination system. During validation, the IVM extracts the device description for each virtual adapter on the VIOS management partition on the source server. The IVM uses the extracted information to determine whether the VIOS management partition on the destination server can provide the mobile partition with the same virtual SCSI, virtual Ethernet, and virtual fibre channel configuration that exists on the source server. This includes verifying that the VIOS management partition on the destination server has enough available slots to accommodate the virtual adapter configuration of the mobile partition. |
X | X |
| Checks that the logical memory block size is the same on the source and destination servers. | X |
| Validation task | Active mobility task | Inactive mobility task |
|---|---|---|
| Checks that all required I/O devices are connected to the mobile partition through the VIOS management partition. That is, no physical adapters are assigned to the mobile partition and no virtual serial adapters are in virtual slots higher than 1. | X | X |
| Checks that no virtual SCSI disks are backed by logical volumes and that no virtual SCSI disks are attached to internal disks (not on the SAN). | X | X |
| Checks that the virtual SCSI disks assigned to the logical partition are accessible by the VIOS management partition on the destination server. | X | |
| Checks that the reservation policies of the physical volumes are the same for the source and destination VIOS partitions. | X | X |
| Checks that the required virtual LAN IDs are available on the destination VIOS management partition. | X | X |
| Checks that the user-defined names of the virtual target devices on the source VIOS partition can be maintained on the destination VIOS partition. | X | X |
| Checks that the user-defined adapter IDs of the virtual server adapters on the source VIOS partition can be maintained on the destination VIOS partition. | X | X |
For a mobile partition that uses shared memory,
the IVM checks
for an available paging space device in one of the following ways:
|
X |
| Validation task | Active mobility task | Inactive mobility task |
|---|---|---|
| Checks that the operating system on the mobile partition is the AIX® or Linux® operating system. | X | X |
| Checks the mobile partition,
its operating system, and its applications for migration capability. The AIX operating system passes the check migration request to those applications and kernel extensions that have registered to be notified of dynamic reconfiguration events. The operating system either accepts or rejects the migration. |
X | |
| Checks that the mobile partition is not the redundant error path reporting logical partition. | X | X |
| Checks that the mobile partition is not in a partition workload group. | X | X |
| Checks the uniqueness of the virtual MAC addresses or the mobile partition. | X | X |
| Checks the state of the mobile partition. | Checks that the mobile partition state is Active or Running. | Checks that the mobile partition state is Not Activated. |
| Checks that the name of the mobile partition is not already in use on the destination server. | X | X |
| Checks that the mobile partition is not configured with barrier synchronization register (BSR) arrays. | X | |
| Checks that the mobile partition is not configured with huge pages. | X | |
| Checks that the mobile partition does not have a Host Ethernet Adapter (or Integrated Virtual Ethernet). | X |
Subscribe to this information