109 lines
8.0 KiB
HTML
109 lines
8.0 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="Cluster version" />
|
||
|
|
<meta name="abstract" content="A cluster version represents the level of function available on the cluster." />
|
||
|
|
<meta name="description" content="A cluster version represents the level of function available on the cluster." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptselements.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplanmixedrelease.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconfigcreatecluster.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigmanageadjustclusterversion.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigmanageadjustclusterversion.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootcommonproblems.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="rzaigplanclusterversions" />
|
||
|
|
<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>Cluster version</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigplanclusterversions"><a name="rzaigplanclusterversions"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Cluster version</h1>
|
||
|
|
<div><p>A <dfn class="term">cluster version</dfn> represents the level of function
|
||
|
|
available on the cluster.</p>
|
||
|
|
<p>Versioning is a technique that allows the cluster to contain systems at
|
||
|
|
multiple release levels and fully interoperate by determining the communications
|
||
|
|
protocol level to be used. If you are using a cluster that will contain systems
|
||
|
|
of varying release levels, see Multiple-release clusters.</p>
|
||
|
|
<p>There are actually two cluster versions:</p>
|
||
|
|
<dl><dt class="dlterm">Potential cluster version</dt>
|
||
|
|
<dd>Represents the most advanced level of cluster function available for a
|
||
|
|
given node. This is the version at which the node is capable of communicating
|
||
|
|
with the other cluster nodes.</dd>
|
||
|
|
<dt class="dlterm">Current cluster version</dt>
|
||
|
|
<dd>Represents the version currently being used for all cluster operations.
|
||
|
|
This is the version of communications between the nodes in the cluster.</dd>
|
||
|
|
</dl>
|
||
|
|
<p>The potential cluster version is incremented on every operating system
|
||
|
|
release which has significant new clustering functionality not available in
|
||
|
|
earlier cluster versions. If the current cluster version is less than the
|
||
|
|
potential cluster version, then that function cannot be used since some nodes
|
||
|
|
cannot recognize or process the request. To take advantage of such new function,
|
||
|
|
every system in the cluster needs to be at the same potential cluster version
|
||
|
|
and the current cluster version must also be set to that level.</p>
|
||
|
|
<p>When a node attempts to join a cluster, its potential cluster version is
|
||
|
|
compared against the current cluster version. If the value of the potential
|
||
|
|
cluster version is not the same as current (N) or not equal to the next version
|
||
|
|
level (N+1), then the node is not allowed to join the cluster. Note that the
|
||
|
|
current cluster version is initially set by the first node defined in the
|
||
|
|
cluster using the value specified on the create cluster API or command. </p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />For example if you want V5R3 nodes to exist with V5R4 nodes
|
||
|
|
you can do one of the following:<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<ul><li><img src="./delta.gif" alt="Start of change" />Create the cluster on a V5R3 system and add in the V5R4
|
||
|
|
node.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
<li><img src="./delta.gif" alt="Start of change" />Create the cluster on a V5R4 system specifying to allow
|
||
|
|
previous nodes to be added to the cluster, then add V5R3 systems to the cluster.<img src="./deltaend.gif" alt="End of change" /></li>
|
||
|
|
</ul>
|
||
|
|
<p>In a multiple-release cluster, cluster protocols will always be run at
|
||
|
|
the lowest node release level, the current cluster version. This is defined
|
||
|
|
when the cluster is first created. N can either be set to the potential node
|
||
|
|
version running on the node that originated the create cluster request or
|
||
|
|
one cluster version previous to the originators potential node version. Nodes
|
||
|
|
in the cluster can differ by at most one cluster version level.</p>
|
||
|
|
<p> Once all systems in the cluster have been upgraded to the next release,
|
||
|
|
the cluster version can be upgraded so that new functions are available. This
|
||
|
|
can be accomplished by adjusting the cluster version. </p>
|
||
|
|
<div class="attention"><span class="attentiontitle">Attention:</span> If the new version of the operating system is not equal
|
||
|
|
or one version higher to the current cluster version, then the cluster node
|
||
|
|
will fail when it is restarted. To recover from this situation, the node must
|
||
|
|
be deleted and recreated with the correct version. </div>
|
||
|
|
<div class="attention"><span class="attentiontitle">Attention:</span> <img src="./delta.gif" alt="Start of change" />When you are using switchable independent
|
||
|
|
disk pools in your cluster, there are restrictions in performing switchover
|
||
|
|
between releases. You need to switch a previous release independent disk pool
|
||
|
|
to a system running the current release of i5/OS™ and make it available. After it is
|
||
|
|
made available on the system running the current release of i5/OS,
|
||
|
|
its internal contents are changed and it cannot be made available to the previous
|
||
|
|
release system again. <img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<p>Read more on <a href="../apis/clust1a6.htm">cluster
|
||
|
|
versions</a> in the Cluster APIs documentation, including information about
|
||
|
|
restrictions and how cluster versions correspond to <span class="keyword">i5/OS</span> releases.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigconceptselements.htm" title="An iSeries cluster is a collection of one or more systems or partitions that work together as a single system. Use this information to understand the elements and their relationship to each other.">The elements of a cluster</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaigplanmixedrelease.htm" title="If creating a cluster that will include nodes at multiple cluster versions, then certain steps are required when you create the cluster.">Multiple-release clusters</a></div>
|
||
|
|
<div><a href="rzaigtroubleshootcommonproblems.htm" title="Lists some of the most common problems that can occur in a cluster, as well as ways to avoid and recover from them.">Common cluster problems</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="rzaigconfigcreatecluster.htm" title="To create and configure a cluster, you need to include at least one node in the cluster and you must have access to at least one of the nodes that will be in the cluster.">Create a cluster</a></div>
|
||
|
|
<div><a href="rzaigmanageadjustclusterversion.htm" title="The cluster version defines the level at which all the nodes in the cluster are actively communicating with each other.">Adjust the cluster version of a cluster</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|