86 lines
6.0 KiB
HTML
86 lines
6.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 administrative domain" />
|
||
|
|
<meta name="abstract" content="A cluster administrative domain is used to manage resources that need to be maintained consistently across the nodes in a clustered environment." />
|
||
|
|
<meta name="description" content="A cluster administrative domain is used to manage resources that need to be maintained consistently across the nodes in a clustered environment." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptselements.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="rzaigconceptsclusteradmindmn" />
|
||
|
|
<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 administrative domain</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigconceptsclusteradmindmn"><a name="rzaigconceptsclusteradmindmn"><!-- --></a>
|
||
|
|
<img src="./delta.gif" alt="Start of change" /><!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Cluster administrative domain</h1>
|
||
|
|
<div><p>A <dfn class="term">cluster administrative domain</dfn> is used to manage
|
||
|
|
resources that need to be maintained consistently across the nodes in a clustered
|
||
|
|
environment. </p>
|
||
|
|
<div class="p">There can be certain operational or configuration parameters that need
|
||
|
|
to be defined on each node which is an access point for resilient data, applications,
|
||
|
|
and devices. If a change is made to one of these parameters on any node that
|
||
|
|
may be an access point for something, that change needs to propagated to all
|
||
|
|
other nodes which can be a potential access point. A cluster administrative
|
||
|
|
domain provides the capability to identify resources which need to be maintained
|
||
|
|
consistently across the nodes in a domain. It then monitors for changes to
|
||
|
|
these resources and synchronizes the changes across the active domain. A cluster
|
||
|
|
administrative domain is represented by a peer CRG. When a cluster administrative
|
||
|
|
domain is created, the peer CRG is created by the system. The name of the
|
||
|
|
cluster administrative domain becomes the name of the peer CRG. The nodes
|
||
|
|
which make up the cluster administrative domain are defined by the recovery
|
||
|
|
domain of the peer CRG. All of the nodes are peer nodes. Replicate nodes
|
||
|
|
are not allowed in a cluster administrative domain. A cluster node can only
|
||
|
|
be defined in one cluster administrative domain within the cluster. For more
|
||
|
|
information on associated cluster administrative domain tasks, see the following
|
||
|
|
topics:<ol><li><a href="rzaigplanadmindomain.htm">Plan for a cluster administrative domain</a></li>
|
||
|
|
<li><a href="rzaigadminchecklist.htm">Cluster administrative domain checklist</a></li>
|
||
|
|
<li><a href="rzaigcreateadmindomain.htm">Create a cluster administrative domain</a></li>
|
||
|
|
<li><a href="rzaigaddmonentries.htm">Add monitored resource entries</a></li>
|
||
|
|
<li><a href="rzaigstartpeercrg.htm">Start a CRG</a></li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
<p>Once the cluster administrative domain is created, normal CRG functions
|
||
|
|
are used to manage the cluster administrative domain. For example, if you
|
||
|
|
want to add a node to administrative domain, you need to add a node to the
|
||
|
|
recovery domain of the CRG with a node role of peer. To start the cluster
|
||
|
|
administrative domain, you start the peer CRG. </p>
|
||
|
|
<p>By starting and ending the CRG, the process of synchronizing changes can
|
||
|
|
be controlled. When the CRG is ended, changes made to a monitored resource
|
||
|
|
on any node in the domain are not propagated to the rest of the domain. Once
|
||
|
|
the CRG is started, changes which had been made to any monitored resource
|
||
|
|
while it was inactive will be propagated to the rest of the domain. While
|
||
|
|
the CRG is active, changes made to any monitored resource on any active node
|
||
|
|
are propagated dynamically so that the resource remains consistent across
|
||
|
|
the administrative domain. See <a href="rzaigmonitorcluadmdmn.htm">Monitor a cluster administrative domain</a> for details.</p>
|
||
|
|
<p>In order to add a node to a cluster administrative domain, you need to
|
||
|
|
add a cluster node to the recovery domain of the peer CRG. When a node is
|
||
|
|
added to the domain, all resources being managed will be created on the new
|
||
|
|
node if they do not exist and will be synchronized with the rest of the administrative
|
||
|
|
domain. </p>
|
||
|
|
<p>If the cluster administrative domain is deleted, all resources that are
|
||
|
|
defined in the cluster administrative domain are removed from every node in
|
||
|
|
the domain; however the actual resource is not removed from the system. See <a href="rzaigconceptsmre.htm">Monitored resources</a> for
|
||
|
|
details.</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>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|