Partitioned-server upgrades
Upgrading a partitioned server is more complex than upgrading a server without partitions. When upgrading a partitioned server, consider these points.
Upgrading multiple partitions takes longer
When you upgrade a partitioned server, you actually perform one upgrade for each partition. This upgrade process includes planning, preparing for, and performing the upgrade. Planning is most involved and may require up to six weeks, depending on the complexity of your environment. Installing the i5/OS® release on a server that is not preloaded requires at least one hour. Upgrading from one server to another server requires up to three days for each partition. In addition, it is recommended that you stabilize the server after upgrading each partition, which means your total upgrade may take several weeks to complete.
Upgrading your server might change server resources
When you convert an expansion unit, two things happen. First, new buses with new bus numbers are created. You need to assign the new bus numbers to the correct partition before turning on the partition. Second, some new resource names are created. You need to reassign or rename the new resource names as appropriate. For information about converting from one expansion unit to another in a partitioned environment, see the Converting expansion units in a partitioned environment topic.
Upgrading your server might require additional resource management
If the target server has fewer processors than the source server, ensure that the target server can satisfy the minimum processor values per partition. You can redefine the partitions either before or after performing the upgrade. Either adjust the configuration on the source server to reflect the target server's processing resources or correct the configuration on the target server before starting the secondary partitions.
For example, if you are upgrading from a 4-way server to a 2-way server, define your partitions so they will work on the new 2-way server. You can do this before the upgrade, by defining the partitions so that only 2 of the 4 processors are used, or after the upgrade by defining the partitions to use only 2 instead of 4 processors.
If the target server has more processors than the current server, the configuration on the target server will indicate additional resources that must then be manually assigned to the appropriate partitions.
Similarly, ensure that target server can satisfy the minimum memory values per partition. The current memory values can be adjusted on the target server.
Running Linux in a guest partition has unique requirements
If your solution includes Linux®, be sure to use the Linux topic to help you identify the requirements for configuring Linux in an iSeries™ logical partition. If you are upgrading to a system with a POWER4™ processor and are running Linux in an iSeries logical partition, ensure that the version of Linux you are running supports the new hardware. See the Linux on the System i™ platform Web site for a list of Linux distributions that support the new hardware. If your current Linux distribution does not support the new hardware, upgrade your Linux distribution before upgrading to the new hardware.
Service representative responsibilities
In a server upgrade, the service representative upgrades all of the hardware on the partitioned server. However, the service representative does not reassign resources or upgrade software on individual partitions. IBM® offers these and other services for a fee. For more information about these services, see the IBM Migration Services Web site.
Parent topic:
iSeries upgrade conceptsRelated concepts
Upgrade planningRelated tasks
Converting expansion units for a partitioned server