68 lines
4.6 KiB
HTML
68 lines
4.6 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="Shorten hardware maintenance and upgrade windows" />
|
||
|
|
<meta name="abstract" content="By effectively planning hardware maintenance and upgrades, you can greatly reduce and even eliminate the impact of these activities to availability of your server." />
|
||
|
|
<meta name="description" content="By effectively planning hardware maintenance and upgrades, you can greatly reduce and even eliminate the impact of these activities to availability of your server." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzalwshorten_planned.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="rzalwhw_upgrade" />
|
||
|
|
<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>Shorten hardware maintenance and upgrade windows</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzalwhw_upgrade"><a name="rzalwhw_upgrade"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Shorten hardware maintenance and upgrade windows</h1>
|
||
|
|
<div><p>By effectively planning hardware maintenance and upgrades, you
|
||
|
|
can greatly reduce and even eliminate the impact of these activities to availability
|
||
|
|
of your server.</p>
|
||
|
|
<p>There are times when you need to perform routine maintenance on your hardware
|
||
|
|
or increase the capacity of your hardware. These operations can be disruptive
|
||
|
|
to your business. </p>
|
||
|
|
<p>If you are performing a system upgrade, be sure that you do careful planning
|
||
|
|
before you begin. The more carefully you plan for your new server, the faster
|
||
|
|
the upgrade will go. For more details on the planning process, see <a href="../rzamd/rzamd1.htm">Upgrades</a>.</p>
|
||
|
|
<div class="section"><img src="./delta.gif" alt="Start of change" /><h4 class="sectiontitle">Concurrent maintenance</h4><p>Many hardware components on the iSeries system can be replaced, added, or
|
||
|
|
removed concurrently while the system is operating. For example, the ability
|
||
|
|
to "hot plug" is supported for PCI card slots, disk slots, and redundant fans
|
||
|
|
and power supplies. Concurent maintenance improves the availability of the
|
||
|
|
system and allows you to perform certain upgrades, maintenance,
|
||
|
|
or repairs without impacting the users of the system.</p>
|
||
|
|
<p>For details on
|
||
|
|
concurrent maintenance, see <a href="../rzaly/rzalycmaintdef.htm">Concurrent maintenance</a>.</p>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Capacity on Demand</h4><p>With IBM<sup>®</sup> eServer™ Capacity on Demand, you can activate
|
||
|
|
additional processors and pay only for the new processing power as your needs
|
||
|
|
grow. You can increase your processing capacity without disrupting any of
|
||
|
|
your current operations.</p>
|
||
|
|
<p>Capacity on Demand is a feature that offers
|
||
|
|
the capability to nondisruptively activate one or more central processors
|
||
|
|
of your server. Capacity on Demand adds capacity in increments of one processor,
|
||
|
|
up to the maximum number of stand-by processors built into your model. Capacity
|
||
|
|
on Demand has significant value for installations where you want to upgrade
|
||
|
|
without disruption.</p>
|
||
|
|
<p>For more information on this feature, see <a href="../rzatq/rzatqcodparent.htm">Capacity on Demand</a>.</p>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzalwshorten_planned.htm" title="Planned outages are necessary and are expected; however, because they are planned does not mean they are nondisruptive. Planned outages are often related to system maintenance.">Shorten planned outages</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|