File:Hardware infrastructure enabled for Live Partition Mobility.jpg

The primary requirements for the migration of a logical partition are: � Two POWER6 or POWER7 technology-based systems running PowerVM Enterprise Edition with Virtual I/O Server version 1.5 or higher and controlled by at least one HMC or each of them running the IVM are required. An optional redundant HMC configuration is supported. Remote migration between systems controlled by different HMCs running Version 7 Release 3.4 or later is supported. Live Partition Mobility is supported for partitions running AIX 5.3 Level 5300-07 or later, AIX 6.1 or later, Red Hat Enterprise Linux version 5 Update 1 or later, or SUSE Linux Enterprise Server 10 Service Pack 1 or later. � The destination system must have enough processor and memory resources to host the mobile partition (the partition profile that is running, as alternate production profiles might exist). � The operating system, applications, and data of the mobile partition must reside on virtual storage on an external storage subsystem. � No physical adapters may be used by the mobile partition during the migration. � Migration of partitions using multiple Virtual I/O Servers is supported. � At the time of publication, migration of partitions between HMC and IVM systems is not supported. � The mobile partition’s network and disk access must be virtualized by using one or more Virtual I/O Servers. – The Virtual I/O Servers on both systems must have a shared Ethernet adapter configured to bridge to the same Ethernet network used by the mobile partition. – The Virtual I/O Servers on both systems must be capable of providing virtual access to all disk resources the mobile partition is using. – The disks used by the mobile partition must be accessed through virtual SCSI, virtual Fibre Channel-based mapping, or both. Note: Virtual Fibre Channel support for migration is introduced in PowerVM Virtual I/O Server Version 2.1. Virtual Fibre Channel uses N_Port ID Virtualization (NPIV) to access SAN resources using shared Fibre Channel adapters. See Chapter 2 in PowerVM Virtualization on IBM System p: Managing and Monitoring, SG24-7590 for details about virtual Fibre Channel and NPIV configuration. 8 IBM PowerVM Live Partition Mobility Live Partition Mobility requires a specific hardware and microcode configuration that is currently available on POWER6 technology-based systems only. The procedure that performs the migration identifies the resource configuration of the mobile partition on the source system and then reconfigures both source and destination systems accordingly. Because the focal-point of hardware configuration is the HMC, it has been enhanced to coordinate the process of migrating partitions. The mobile partition’s configuration is not changed during the migration. The destination system must be able to host the mobile partition and must have enough free processor and memory resources to satisfy the partition’s requirements before migration is started. No limitation exists on the size of the mobile partition; it can even use all resources of the source system offered by the Virtual I/O Server. The operating system and application data must reside on external disks of the source system because the mobile partition’s disk data must be available after the migration to the destination system is completed. An external, shared-access storage subsystem is therefore required. The mobile partition must not own any physical adapters and must use the Virtual I/O Server for both network and external disk access. External disks may be presented to the mobile partition as virtual SCSI, or virtual Fibre resources, or both. Because the mobile partition’s external disk space must be available to the Virtual I/O Servers on the source and destination systems, you cannot use storage pools. Each Virtual I/O Server must create virtual target devices using physical disks and not logical volumes. Virtual network connectivity must be established before activating the partition migration task, while virtual disk setup is performed by the migration process. Both the source and the target system must have an appropriate shared Ethernet adapter environment to host a moving partition. All virtual networks in use by the mobile partition on the source system must be available as virtual networks on the destination system. VLANs defined by port virtual IDs (PVIDs) on the VIOS have no meaning outside of an individual server as all packets are bridged untagged. It is possible for VLAN 1 on CEC 1 to be part of the 192.168.1 network while VLAN 1 on CEC 2 is part of the 10.1.1 network. Chapter 1. Overview 9 Because two networks are possible, you cannot verify whether VLAN 1 exists on both servers. You have to check whether VLAN 1 maps to the same network on both servers. Figure 1-1 shows a basic hardware infrastructure enabled for Live Partition Mobility and that is using a single HMC. Each system is configured with a single Virtual I/O Server partition. The mobile partition has only virtual access to network and disk resources. The Virtual I/O Server on the destination system is connected to the same network and is configured to access the same disk space used by the mobile partition. For illustration purposes, the device numbers are all shown as zero, but in practice, they can vary considerably.

Source: Redbook sg24-7460-01 PowerVM Live Partition Mobility. Figure 1-1 Hardware infrastructure enabled for Live Partition Mobility