148 lines
9.9 KiB
HTML
148 lines
9.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="Determine primary and secondary cluster partitions" />
|
||
|
|
<meta name="abstract" content="In order to determine the types of cluster resource group actions that you can take within a cluster partition, you need to know whether the partition is a primary or a secondary cluster partition. When a partition is detected, each partition is designated as a primary or secondary partition for each cluster resource group defined in the cluster." />
|
||
|
|
<meta name="description" content="In order to determine the types of cluster resource group actions that you can take within a cluster partition, you need to know whether the partition is a primary or a secondary cluster partition. When a partition is detected, each partition is designated as a primary or secondary partition for each cluster resource group defined in the cluster." />
|
||
|
|
<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="rzaigtroubleshootdeterminepartitions" />
|
||
|
|
<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>Determine primary and secondary cluster partitions</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigtroubleshootdeterminepartitions"><a name="rzaigtroubleshootdeterminepartitions"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Determine primary and secondary cluster partitions</h1>
|
||
|
|
<div><p><span><img src="./delta.gif" alt="Start of change" />In order to determine the types of cluster resource
|
||
|
|
group actions that you can take within a cluster partition, you need to know
|
||
|
|
whether the partition is a primary or a secondary cluster partition. When
|
||
|
|
a partition is detected, each partition is designated as a primary or secondary
|
||
|
|
partition for each cluster resource group defined in the cluster.<img src="./deltaend.gif" alt="End of change" /></span></p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />For primary-backup model, the primary partition contains
|
||
|
|
the node that has the current node role of primary. All other partitions are
|
||
|
|
secondary. The primary partition may not be the same for all cluster resource
|
||
|
|
groups. <img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="p"><img src="./delta.gif" alt="Start of change" />A peer model has the following partition rules: <ul><li>If the recovery domain nodes are fully contained within one partition,
|
||
|
|
it will be the primary partition. </li>
|
||
|
|
<li>If the recovery domain nodes span a partition, there will be no primary
|
||
|
|
partition. Both partitions will be secondary partitions. </li>
|
||
|
|
<li>If the cluster resource group is active and there are no peer nodes in
|
||
|
|
the given partition, the cluster resource group will be ended in that partition.</li>
|
||
|
|
<li>Operational changes are allowed in a secondary partition as long as the
|
||
|
|
restrictions for the operational changes are met.</li>
|
||
|
|
<li>No configuration changes are allowed in a secondary partition. </li>
|
||
|
|
</ul>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></div>
|
||
|
|
<p>The restrictions for each Cluster Resource Group API are:</p>
|
||
|
|
|
||
|
|
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" frame="border" border="1" rules="all"><caption>Table 1. Cluster Resource Group API Partition Restrictions</caption><thead align="left"><tr><th valign="top" width="50%" id="d0e40">Cluster Resource Group API</th>
|
||
|
|
<th valign="top" width="25%" id="d0e42">Allowed in primary partition</th>
|
||
|
|
<th valign="top" width="25%" id="d0e44">Allowed in secondary partitions</th>
|
||
|
|
</tr>
|
||
|
|
</thead>
|
||
|
|
<tbody><tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Add Node to Recovery Domain</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Add CRG Device Entry</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 "> </td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Change Cluster Resource Group</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Change CRG Device Entry</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 ">X</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Create Cluster Resource Group</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 "> </td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Delete Cluster Resource Group</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 ">X</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Distribute Information</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 ">X</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">End Cluster Resource Group</span><sup>1</sup></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Initiate Switchover</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">List Cluster Resource Groups</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 ">X</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">List Cluster Resource Group Information</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 ">X</td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Remove Node from Recovery Domain</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Remove CRG Device Entry</span></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td valign="top" width="50%" headers="d0e40 "><span class="apiname">Start Cluster Resource Group</span><sup>1</sup></td>
|
||
|
|
<td valign="top" width="25%" headers="d0e42 ">X</td>
|
||
|
|
<td valign="top" width="25%" headers="d0e44 "> </td>
|
||
|
|
</tr>
|
||
|
|
<tr><td colspan="3" valign="top" headers="d0e40 d0e42 d0e44 "><div class="note"><span class="notetitle">Note:</span> <ol><li>Allowed in all partitions for peer cluster resource groups, but only affects
|
||
|
|
the partition running the API.</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</td>
|
||
|
|
</tr>
|
||
|
|
</tbody>
|
||
|
|
</table>
|
||
|
|
</div>
|
||
|
|
<p>By applying these restrictions, cluster resource groups can be synchronized
|
||
|
|
when the cluster is no longer partitioned. As nodes rejoin the cluster from
|
||
|
|
a partitioned status, the version of the cluster resource group in the primary
|
||
|
|
partition is copied to nodes from a secondary partition.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />When merging two secondary partitions for peer model, the
|
||
|
|
partition which has cluster resource group with status of Active will be declared
|
||
|
|
the winner. If both partitions have the same status for cluster resource group,
|
||
|
|
the partition which contains the first node listed in the cluster resource
|
||
|
|
group recovery domain will be declared the winner. The version of the cluster
|
||
|
|
resource group in the winning partition will be copied to nodes in another
|
||
|
|
partition.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>When a partition is detected, the <span class="apiname">Add Cluster Node Entry</span>, <span class="apiname">Adjust
|
||
|
|
Cluster Version</span>, and the <span class="apiname">Create Cluster</span> API cannot
|
||
|
|
be run in any of the partitions. The <span class="apiname">Add Device Domain Entry</span> API
|
||
|
|
can only be run if none of the nodes in the device domain are partitioned.
|
||
|
|
All of the other Cluster Control APIs may be run in any partition. However,
|
||
|
|
the action performed by the API takes affect only in the partition running
|
||
|
|
the API.</p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <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>
|