Tuesday, February 26, 2013

Live Partition Mobility

PowerVM LPM allows for the movement of an active or inactive partition from one system to another with no application downtime.

  1.  Power6 or newer       
  2. PowerVM enterprise edition.
  3. If both Source and destination systems managed with same HMC . In this case HMC must be at version 7 release 3.2 or later.
  4. If both source and destination systems connected to separate HMC
  5. Both HMC’s connected to same network.
  6. Both HMC’s must be at version 7, release 3.4
  7.  A SSH connection must be set correctly between the 2 HMCs
  8.  Systems have a VIO installed with version or later
  9.  Power6 based systems must have a firmware level of 01Ex320 or later.
  10.  The systems must have the same logical memory block size. This can be checked through ASMI.
  11.  At least one of the source and one of the destination VIO servers are set as Mover service partition.
  12. Both VIO servers should have their clocks synchronized.
  13.  The amount of memory available on the destination system is greater than or equal to the amount of memory used by the mobile partition of the source system.
  14. If mobile partition uses dedicated processors, the destination system must have at least this number of available processors.
  15. If the mobile partition is assigned to a shared processor pool, the destination system must have enough spare entitlement to allocate it to the mobile partition in the destination shared processor pool.
  16. The destination system must have at least one vio server that has access to all the network and storage resources used by the migrating partition.
  17. The destination system must have a virtual switch configured with same name as the source system.
  18.  IO resources must be virtual. Virtual SCSI devices must be backed by SAN volumes.
  19. Systems using IVE cannot be migrated. The migration partition can use only virtual Ethernet
  20.  The partition is not designated as a redundant error path reporting partition.
  21.  The partition is not part of an LPAR workload group
  22.  The partition has a unique name.
  23.  The additional virtual adapter slots for this partition do not appear as required in the partition profile.
  24. The OS must be at AIX 5.3 TL 7 or later
  25.  The partition doesn’t use Barrier synchronization register. Partition does not use huge pages.
  26. If source system configured with dual VIO then you need 2 or more VIO’s on the destination system
LPM Validation process:-

  1. Active partition migration capability and compatibility check
  2.  RMC Check
  3.  Partition Readiness
  4. System resource availability
  5. Virtual adapter mapping
  6.  OS and application readiness check

Use high speed Ethernet link between systems. A minimum of 1 GBPS link is preferable.

Migration Validation: - This process verifies that the migration of a given partition on one server to another specified server meets all the compatibility requirements. Select Partition àoperations àMobilityà Validate à Fill remote HMC, user, destination server and click validate. Once successful validation select Migrate.

Through Command line:- migrlpar –o m –m “ Source” –t “Destination” –id “partition id” –redundantvios 1 –mpio 1

No comments:

Post a Comment