Subscribe to this information
POWER7 information
Firmware support matrix for partition mobility
Ensure that the firmware levels on the source and destination servers are compatible before upgrading.
In the following table, you can see that the first column
represent the firmware level you are migrating from, and the values
in the top row represent the firmware level you are migrating to.
For each combination, blocked entries are blocked by
code from migrating. Not supported entries are not blocked
from migrating, but are not supported by IBM. Mobile entries
are eligible for migration.
| Migrating from firmware level | 350_xxx, or later | 710_xxx | 720_xxx | 730_xxx | 740_xxx | 760_xxx | 763_xxx | 770_xxx | 773_xxx | 780_xxx |
|---|---|---|---|---|---|---|---|---|---|---|
| 340_039, or later | Mobile | Mobile | Mobile | Blocked | Blocked | Blocked | Blocked | Blocked | Blocked | Blocked |
| 350_xxx, or later | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 710_xxx | Mobile | Mobile | Mobile | Mobile | Mobile | Blocked | Blocked | Blocked | Blocked | Blocked |
| 720_xxx | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Blocked | Blocked | Blocked |
| 730_xxx | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 740_xxx | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 760_xxx | Mobile | Blocked | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 763_xxx | Mobile | Blocked | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 770_xxx | Mobile | Blocked | Blocked | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 773_xxx | Mobile | Blocked | Blocked | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
| 780_xxx | Mobile | Blocked | Blocked | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile | Mobile |
The following table shows the number of concurrent
migrations that are supported per system. The corresponding minimum
levels of firmware, Hardware Management Console (HMC), and Virtual I/O Server (VIOS) that are required
are also shown.
| Concurrent migrations per system | Firmware level | HMC level | VMControl | VIOS level | Maximum concurrent migrations per VIOS |
|---|---|---|---|---|---|
| 4 | All | All | All | All | 4 |
| 8 | All | Version 7 Release 7.4.0, Service Pack 1, with mandatory fix MH01302, or later | VMControl Version 1.1.2, or later | Version 2.2.0.11, Fix Pack 24, Service Pack 1, or later | 4 |
| 16 | Level 7.6, or later | Version 7 Release 7.6.0, or later | VMControl V2.4.2 | Version 2.2.2.0 | 8 |
Restrictions:
- Firmware levels 7.2 and 7.3 are restricted to eight concurrent migrations.
- Certain applications such as clustered applications, high availability solutions, and similar applications have heartbeat timers, also referred to as Dead Man Switch (DMS) for node, network, and storage subsystems. If you are migrating these types of applications, you must not use the concurrent migration option as it increases the likelihood of a timeout. This is especially true on 1 GB network connections.
- You must not perform more than four concurrent migrations on a 1 GB network connection. With VIOS Version 2.2.2.0 or later, and a network connection that supports 10 GB or higher, you can run a maximum of eight concurrent migrations.
- From VIOS Version 2.2.2.0, or later, you must have more than one pair of VIOS partitions to support more than eight concurrent mobility operations.
- Systems that are managed by the Integrated Virtualization Manager (IVM) support up to 10 concurrent migrations.
- To support the migration of up to 16 active or suspended mobile partitions from the source server to a single or multiple destination servers, the source server must have at least two VIOS partitions that are configured as mover service partitions. Each mover service partition must support up to 8 concurrent partition migration operations. If all 16 partitions are to be migrated to the same destination server, then the destination server must have at least two mover service partitions configured, and each mover service partition must support up to 8 concurrent partition migration operations.
- When the configuration of the mover service partition on the source or destination server does not support 8 concurrent migrations, any migration operation that is started by using either the graphical user interface or the command line will fail when no concurrent mover service partition migration resource is available. You must then use the migrlpar command from the command line with the -p parameter to specify a comma-separated list of logical partition names, or the --id parameter to specify a comma-separated list of logical partition IDs.
- You can migrate a group of logical partitions by using the migrlpar command from the command line. To perform the migration operations, you must use -p parameter to specify a comma-separated list of logical partition names, or the --id parameter to specify a comma-separated list of logical partition IDs.
- You can run up to four concurrent Suspend/Resume operations.
- You cannot perform Live Partition Mobility that
is both bidirectional and concurrent. For example:
- When you are moving a mobile partition from the source server to the destination server, you cannot move another mobile partition from the destination server to the source server.
- When you are moving a mobile partition from the source server to the destination server, you cannot move another mobile partition from the destination server to some other server.
