Basic storage configuration in a partition mobility environment

The mobile partition migrates from one server to another by the source server sending the logical partition state information to the destination server over a local area network (LAN). However, partition disk data cannot pass from one system to another system over a network. Thus, for partition mobility to succeed, the mobile partition must use storage resources that are managed by a storage area network (SAN). By using SAN storage, the mobile partition can access the same storage from both the source and destination servers.

The following figure shows an example of the storage configuration required for partition mobility.

An example of the storage configuration on the source and destination servers for partition mobility

The physical storage that the mobile partition uses, Physical storage 3, is connected to the SAN. At least one physical adapter that is assigned to the source Virtual I/O Server logical partition is connected to the SAN. Similarly, at least one physical adapter that is assigned to the destination Virtual I/O Server logical partition is also connected to the SAN.

If the mobile partition connects to Physical storage 3 through virtual Fibre Channel adapters, the physical adapters that are assigned to the source and destination Virtual I/O Server logical partitions must support N_Port ID Virtualization (NPIV).

The mobile partition can use virtual I/O resources that are provided by one or more Virtual I/O Server logical partitions on the source server. To ensure successful mobility, configure the same number of Virtual I/O Server logical partitions on the destination server as are configured on the source server.

The physical adapter on the source Virtual I/O Server logical partition connects to one or more virtual adapters on the source Virtual I/O Server logical partition. Similarly, the physical adapter on the destination Virtual I/O Server logical partition connects to one or more virtual adapters on the destination Virtual I/O Server logical partition. If the mobile partition connects to Physical storage 3 through virtual SCSI adapters, the virtual adapters on both the source and destination Virtual I/O Server logical partitions are assigned to access the logical unit numbers (LUNs) of Physical storage 3.

Each virtual adapter on the source Virtual I/O Server logical partition connects to at least one virtual adapter on a client logical partition. Similarly, each virtual adapter on the destination Virtual I/O Server logical partition connects to at least one virtual adapter on a client logical partition.

Each virtual Fibre Channel adapter that is created on the mobile partition (or any client logical partition) is assigned a pair of worldwide port names (WWPNs). Both WWPNs in the WWPN pair are assigned to access the LUNs of the physical storage that the mobile partition uses, or Physical storage 3. During normal operation, the mobile partition uses one WWPN to log on to the SAN and access Physical Storage 3. When you migrate the mobile partition to the destination server, there is a brief period where the mobile partition runs on both the source and destination servers. Because the mobile partition cannot log on to the SAN from both the source and destination servers at the same time using the same WWPN, the mobile partition uses the second WWPN to log on to the SAN from the destination server during the migration. The WWPNs of each virtual Fibre Channel adapter move with the mobile partition to the destination server.

When you migrate the mobile partition to the destination server, the HMC (that manages the destination server) performs the following tasks on the destination server:

Parent topic: Storage configuration in a partition mobility environment


Last updated: Tue, March 12, 2019