60 lines
4.5 KiB
HTML
60 lines
4.5 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="Avoid a cluster partition" />
|
||
|
|
<meta name="abstract" content="The typical network-related cluster partition can best be avoided by configuring redundant communications paths between all nodes in the cluster." />
|
||
|
|
<meta name="description" content="The typical network-related cluster partition can best be avoided by configuring redundant communications paths between all nodes in the cluster." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigplandesignnetwork.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptpartition.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconfigcommtips.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootpartitionerrors.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigtroubleshootpartitionerrors.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="rzaigplanavoidclusterpartition" />
|
||
|
|
<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>Avoid a cluster partition</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigplanavoidclusterpartition"><a name="rzaigplanavoidclusterpartition"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Avoid a cluster partition</h1>
|
||
|
|
<div><p>The typical network-related cluster partition can best be avoided
|
||
|
|
by configuring redundant communications paths between all nodes in the cluster.</p>
|
||
|
|
<p> A <dfn class="term">redundant communications path</dfn> means that you have two lines
|
||
|
|
configured between two nodes in a cluster. If a failure on the first communication
|
||
|
|
path should occur, the second communication path can take over to keep communications
|
||
|
|
running between the nodes, thereby minimizing conditions that can put one
|
||
|
|
or more nodes of the cluster into a cluster partition. One thing to consider
|
||
|
|
when configuring these paths is that if both of your communications lines
|
||
|
|
go into the same adapter on the system, these lines are still at risk if this
|
||
|
|
single adapter fails.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />However, it should be noted that a cluster partition is
|
||
|
|
not always avoidable. If your system experiences a power loss or if
|
||
|
|
a hardware failure occures, the cluster may become partitioned. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigplandesignnetwork.htm" title="Before you configure your networks for clustering, you need to plan carefully and do some initial pre-cluster configuration involving TCP/IP.">Design your network for clusters</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaigconceptpartition.htm" title="A cluster partition is a subset of the active cluster nodes that results from a communications failure. Members of a partition maintain connectivity with each other.">Cluster partition</a></div>
|
||
|
|
<div><a href="rzaigconfigcommtips.htm" title="Consider these tips when you set up your communications paths.">Tips: Cluster communications</a></div>
|
||
|
|
<div><a href="rzaigtroubleshootpartitionerrors.htm" title="Certain cluster conditions are easily corrected. If a cluster partition has occurred, you can learn how to recover. This topic also tells you how to avoid a cluster partition and gives you an example of how to merge partitions back together.">Partition errors</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|