Move My i

Today is a major announcement day for IBM i with Technology Refresh 4 (TR4). Steve's “You and i” blog reviews the content of this announcement.

Last year, IBM provided support to suspend an i partition, which I previously wrote about in “Suspend my i”. 

The most significant function in IBM i TR4 is Live Partition Mobility. With Live Partition Mobility, you can take an active, running IBM i partition and move it from one frame to another frame, without disruption to your applications. I'm not going to discuss more about what mobility is and why you might want to use it, as Steve covered that in his blog. What I do want to write about is a little more detail on just what you need to accomplish this.

There are both hardware and software prerequisites:

• POWER7 tower/rack system for both the source and destination systems
  • Firmware service pack 730_xx, 740_xx, or later
  • IBM Hardware Management Console V7R7.5.0M0, or later
• All I/O must be virtual and supported by VIOS; it can be Virtual SCSI (VSCSI), Virtual Fibre Channel (NPIV) or Virtual Ethernet
• The configuration must use only external storage and that storage must be accessible to both the source and destination systems
• Both source and destination systems must be on the same Ethernet network
• IBM i 7.1 TR4 PTF group – SF99707 level 4
• PowerVM Enterprise Edition on both the source and target system
• VIOS 2.2.1.5 (FP25 SP3) on both the source and target system [[CORRECTION: It's VIOS 2.2.1.4]]

There are a few restrictions that are too detailed to review in this blog; the Live Partition Mobility documentation in the IBM i developerWorks site reviews the complete set of prerequisites, requirements and restrictions.

The actual move of a partition is initiated from the HMC. IBM Systems Director VMControl has relocation, which you can imagine will ultimately support IBM i as well.

In general, applications and the operating system are unaware that the partition is moved from one system to another. There are some exceptions to this, such as Collection Services; when the partition is starting to run on the target system, the Collection Services collector job will cycle the collection so correct hardware information is recorded on the target system.

There are two new work management exit points that are part of the IBM i suspend and mobility support. These exit points allow to you run a program before and after a partition is suspended or moved. (These exit points are the same, regardless of whether you are suspending a partition or moving a partition). 

            Work with Registration Information

 

 Type options, press Enter.

  5=Display exit point  8=Work with exit programs

 

              Exit

   Exit         Point

 Opt Point         Format  Registered Text

 _  QIBM_QWC_RESUME    RSMS0100   *YES   Resume system

 _  QIBM_QWC_SUSPEND   SSPS0100   *YES   Suspend system  

The suspend exit is called before the partition is suspended or moved and is called two twice. The first time it is called to check to see if the operation is allowed. The second call is to prepare for the move or suspend operation.

The resume exit is called after the move is complete or after the system has been restarted from a suspended state. Applications can use these exit points to monitor and accept or refuse move or suspend requests. Running an exit program after a move or suspend also allows an application to refresh any copies of any system-specific information, log information about mobility requests for licensing or other purposes, adjust heart beat rates or whatever actions an application may require.

For more information on these exit points, refer to the “What's New”for APIs in the IBM i 7.1 Information Center.

The following messages may be logged to the QSYSOPR message queue as part of the suspend or move request:

• CPI09A5 - Partition suspend request in progress.
• CPI09A6 - Partition not ready for suspend request.
• CPI09A7 - Partition suspend request canceled.
• CPI09A8 - Partition resumed after migration.
• CPI09A9 - Partition resumed from hibernation.

The system serial number will change when a partition has been moved. The model and processor feature may also change.

The documentation on enhancements added to IBM i via Technology Refreshes can be found on the IBM developerWorks web site.

Other sources for documentation on Live Partition Mobility for IBM i include:

• Partition mobility overview for HMC
  
• IBM PowerVM Live Partition Mobility
  
• API Guide (For registering system exits)
• Licensing information
• Software Knowledge Base

          Search for “Live Partition Mobility” to find any usage notes.

 

Comments

[Dawn May]

There are some upcoming PowerVM Technical Webinars, one of which is on Live Partition Mobility with IBM i.

IBM i Live Partition Mobility
June 13th 2012, 10:00 - 11:00 BST (UK time)

See this web page for details -
http://tinyurl.com/UK-PowerVM-VUG

Dawn

[Dawn May]

The replay is available for the PowerVM technical webinar: IBM i Live Partition Mobility

If you listen to this reply, please register first.

Speaker: Jeffrey Blight
Register first --> http://tinyurl.com/UK-PowerVM-VUG
Replay --> available from same page

Dawn

[Jared Draper]

Dawn,

Thanks for the article I just had one quick question.

You mention that the VIOS level has to be VIOS 2.2.1.5 (FP25 SP3) but I don't see that as available for download yet from Fix Central or from Entitled software.

Also developer works says that you need VIOS 2.2.1.4, or later, on both source and target system here:

https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/IBM%20i%20Technology%20Updates/page/Live%20Partition%20Mobility

Can you confirm what level of VIOS is required? Thanks.

[Dawn May]

Hi Jared,

The developerWorks articles is correct - VIOS 2.2.1.4 is the level required. I'll see if we can update the blog to reflect the correct level.

Thanks for pointing this out.

Dawn