67 lines
4.4 KiB
HTML
67 lines
4.4 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="Example: A cluster administrative domain to manage peer resources" />
|
||
|
|
<meta name="abstract" content="Provides an example configuration of a cluster administrative domain used to monitor resources within a cluster." />
|
||
|
|
<meta name="description" content="Provides an example configuration of a cluster administrative domain used to monitor resources within a cluster." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigscenarios.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="rzaigscenarioclusteradmindmn" />
|
||
|
|
<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>Example: A cluster administrative domain to manage peer resources</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigscenarioclusteradmindmn"><a name="rzaigscenarioclusteradmindmn"><!-- --></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">Example: A cluster administrative domain to manage peer resources</h1>
|
||
|
|
<div><p>Provides an example configuration of a cluster administrative domain
|
||
|
|
used to monitor resources within a cluster.</p>
|
||
|
|
<div class="p">This example configuration provides the following:<ul><li>Two-node cluster</li>
|
||
|
|
<li>A cluster administrative domain with the two nodes in its domain node
|
||
|
|
list</li>
|
||
|
|
<li>A Monitored Resource Entry (MRE) for a user profile which is to be synchronized
|
||
|
|
within the domain.</li>
|
||
|
|
</ul>
|
||
|
|
<br /><img src="rzaig507.gif" alt="A two-node cluster featuring an application CRG and a data CRG." /><br /></div>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />In this example, the administrator wants to ensure the user
|
||
|
|
profile remains consistent throughout the cluster so a cluster administrative
|
||
|
|
domain was created to monitor and synchronize changes to the user profile.
|
||
|
|
The cluster administrative domain is represented by a peer CRG that contains
|
||
|
|
Node L and Node R. A monitored resource entry is added to the cluster administrative
|
||
|
|
domain for the user profile. In this example, all of the attributes of the
|
||
|
|
user profile were specified when the MRE was added. Therefore when any attribute
|
||
|
|
of the user profile is changed on either node L or node R, the change is automatically
|
||
|
|
propagated to the active nodes in the domain, once the CRG is started.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<div class="p">The following steps describe what the administrator completed to set up
|
||
|
|
this example:<ol><li>Create a cluster with Nodes L and R.</li>
|
||
|
|
<li>Create a cluster administrative domain on Nodes L and R</li>
|
||
|
|
<li>Add an MRE to represent the user profile</li>
|
||
|
|
<li>Start the Peer CRG that represents the cluster administrative domain </li>
|
||
|
|
<li>Change the user profile on either node L or on node R. The user profile
|
||
|
|
on the other node will be changed automatically by the cluster administrative
|
||
|
|
domain. The global status for the monitored resource will be consistent if
|
||
|
|
the change is successful. </li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigscenarios.htm" title="Use these examples of typical cluster implementations to understand when, why, and how using clusters can be beneficial.">Examples: Cluster configurations</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|