ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzamd_5.4.0.1/rzamdconsiderlpar.htm

116 lines
7.9 KiB
HTML

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html lang="en-us" xml:lang="en-us">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="security" content="public" />
<meta name="Robots" content="index,follow" />
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
<meta name="DC.Type" content="concept" />
<meta name="DC.Title" content="Partitioned server upgrades" />
<meta name="abstract" content="Find information unique to upgrading a partitioned server." />
<meta name="description" content="Find information unique to upgrading a partitioned server." />
<meta name="DC.Relation" scheme="URI" content="rzamdupgradeconcepts.htm" />
<meta name="DC.Relation" scheme="URI" content="rzamdexpanupgradelpar.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzalm/rzalmlinuxkickoff.htm" />
<meta name="DC.Relation" scheme="URI" content="http://www-1.ibm.com/servers/eserver/iseries/linux/" />
<meta name="DC.Relation" scheme="URI" content="http://www-1.ibm.com/services/its/us/inteapps.htm" />
<meta name="DC.Relation" scheme="URI" content="../rzait/rzaiticlpar.htm" />
<meta name="DC.Relation" scheme="URI" content="rzamdplanupgrade.htm" />
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1998, 2006" />
<meta name="DC.Format" content="XHTML" />
<meta name="DC.Identifier" content="rzamdconsiderlpar" />
<meta name="DC.Language" content="en-us" />
<!-- All rights reserved. Licensed Materials Property of IBM -->
<!-- US Government Users Restricted Rights -->
<!-- Use, duplication or disclosure restricted by -->
<!-- GSA ADP Schedule Contract with IBM Corp. -->
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
<link rel="stylesheet" type="text/css" href="./ic.css" />
<title>Partitioned server upgrades</title>
</head>
<body id="rzamdconsiderlpar"><a name="rzamdconsiderlpar"><!-- --></a>
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
<h1 class="topictitle1">Partitioned server upgrades</h1>
<div><p>Find information unique to upgrading a partitioned server.</p>
<p>Upgrading a partitioned server is more complex than upgrading a server
without partitions. When upgrading a partitioned server, be aware of the following.</p>
<div class="section"><h4 class="sectiontitle">Upgrading multiple partitions takes longer</h4><p>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 <span class="keyword">i5/OS™</span> 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.</p>
</div>
<div class="section"><h4 class="sectiontitle">Upgrading your server may change server resources</h4><p>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 Convert expansion units in a partitioned environment
topic.</p>
</div>
<div class="section"><h4 class="sectiontitle">Upgrading your server may require additional resource management</h4><p>If
the target server has <var class="varname">fewer</var> processors than the source
server, you must 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.</p>
<p>For example,
if you are upgrading from a 4-way server to a 2-way server, you must 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.</p>
<p>If the target server has <var class="varname">more</var> 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.</p>
<p>Similarly, you must ensure that target server can satisfy
the minimum memory values per partition. The current memory values can be
adjusted on the target server.</p>
</div>
<div class="section"><h4 class="sectiontitle">Running Linux<sup>®</sup> in a guest partition has unique requirements</h4><p>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, you must ensure that the version of Linux you are running supports the new
hardware. See the Linux for IBM<sup>®</sup> Web site for a list of Linux distributions
that support the new hardware. If your current Linux distribution does not support the
new hardware, you must upgrade your Linux distribution before upgrading to
the new hardware.</p>
</div>
<div class="section"><h4 class="sectiontitle">Service representative responsibilities</h4><p>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, select <span class="uicontrol">Migration</span> on
the Integrated Applications Services Web site.</p>
<p>For additional information
about logical partitions, see the Logical partitions topic.</p>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzamdupgradeconcepts.htm" title="Review both the process for upgrading your server and some considerations for upgrading a partitioned server. Find information about which servers you can upgrade to the new iSeries servers. Learn the terminology that is used in this topic.">Upgrade concepts</a></div>
</div>
<div class="relconcepts"><strong>Related concepts</strong><br />
<div><a href="../rzalm/rzalmlinuxkickoff.htm">Linux</a></div>
<div><a href="http://www-1.ibm.com/servers/eserver/iseries/linux/" target="_blank">Linux for IBM</a></div>
<div><a href="http://www-1.ibm.com/services/its/us/inteapps.htm">Integrated Applications Services</a></div>
<div><a href="../rzait/rzaiticlpar.htm">Logical partitions</a></div>
<div><a href="rzamdplanupgrade.htm" title="Find out how planning can help you minimize your downtime and make your upgrade as easy as possible.">Plan the upgrade</a></div>
</div>
<div class="reltasks"><strong>Related tasks</strong><br />
<div><a href="rzamdexpanupgradelpar.htm" title="When performing any of the following expansion unit conversions in a partitioned environment, it is essential that detailed planning is performed before starting the expansion unit conversion.">Convert expansion units for a partitioned server</a></div>
</div>
</div>
</body>
</html>