97 lines
6.2 KiB
HTML
97 lines
6.2 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="task" />
|
||
|
|
<meta name="DC.Title" content="Monitor a cluster administrative domain" />
|
||
|
|
<meta name="abstract" content="Once a cluster administrative domain is created and the appropriate monitored resource entries are added, the cluster administrator should monitor the activity within the administrative domain to insure that the monitored resources remain consistent." />
|
||
|
|
<meta name="description" content="Once a cluster administrative domain is created and the appropriate monitored resource entries are added, the cluster administrator should monitor the activity within the administrative domain to insure that the monitored resources remain consistent." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigmanage.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="rzaigmonitorcluadmdmn" />
|
||
|
|
<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>Monitor a cluster administrative domain</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigmonitorcluadmdmn"><a name="rzaigmonitorcluadmdmn"><!-- --></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">Monitor a cluster administrative domain</h1>
|
||
|
|
<div><p>Once a cluster administrative domain is created and the appropriate
|
||
|
|
monitored resource entries are added, the cluster administrator should monitor
|
||
|
|
the activity within the administrative domain to insure that the monitored
|
||
|
|
resources remain consistent.</p>
|
||
|
|
<div class="section"><p>If the global status of status of a monitored resource is inconsistent,
|
||
|
|
the administrator should take the necessary steps to determine why the resource
|
||
|
|
is inconsistent, correct the problem and resynchronize the resource.</p>
|
||
|
|
<p>If
|
||
|
|
the resource is inconsistent because an update failed on one or more nodes,
|
||
|
|
there is information kept for the MRE that will help you determine the cause
|
||
|
|
of the failure. On the node where the failure occurred, a message is logged
|
||
|
|
with the MRE which is the cause of the failed update. On the other nodes,
|
||
|
|
there will be a message logged which tells you there was a failure, along
|
||
|
|
with the list of nodes where the update failed.</p>
|
||
|
|
<p>Once the cause of the
|
||
|
|
inconsistency is determined, the resource can be resynchronized, either as
|
||
|
|
a result of an update operation on the node where the failure occurred, or
|
||
|
|
by ending and restarting the administrative domain.</p>
|
||
|
|
<p>The global status
|
||
|
|
for a monitored resource is always set to inconsistent if the resource is
|
||
|
|
deleted, renamed or moved on any node in the domain. If this is the case,
|
||
|
|
the MRE should be removed because the resource will no longer be synchronized
|
||
|
|
by the cluster administrative domain.</p>
|
||
|
|
<p><strong>Using iSeries™ Navigator</strong></p>
|
||
|
|
To monitor a
|
||
|
|
cluster administrative domain, follow these steps:</div>
|
||
|
|
<ol><li class="stepexpand"><span>In iSeries Navigator,
|
||
|
|
expand <span class="menucascade"><span class="uicontrol">Management Central </span> > <span class="uicontrol">Clusters</span></span>. </span></li>
|
||
|
|
<li class="stepexpand"><span>Expand the cluster for which the cluster administrative domain
|
||
|
|
is associated. </span></li>
|
||
|
|
<li class="stepexpand"><span>Expand <span class="uicontrol">Peer Resources</span>, and right-click <span class="uicontrol">New
|
||
|
|
Administrative Domain</span> and select <span class="uicontrol">Properties</span>. </span> The possible values for the status of the resource across the active
|
||
|
|
cluster administrative domain are:<dl><dt class="dlterm">Consistent</dt>
|
||
|
|
<dd> The values for all the resource's attributes monitored by the system
|
||
|
|
are the same on all active nodes within the cluster administrative domain.</dd>
|
||
|
|
<dt class="dlterm"> Inconsistent</dt>
|
||
|
|
<dd>The values for all the resource's attributes monitored by the system are
|
||
|
|
not the same on all active nodes within the cluster administrative domain,
|
||
|
|
or the cluster administrative domain is not active. </dd>
|
||
|
|
<dt class="dlterm">Pending</dt>
|
||
|
|
<dd>The values of the monitored attributes are in the process of being synchronized
|
||
|
|
across the cluster administrative domain. </dd>
|
||
|
|
<dt class="dlterm">Added</dt>
|
||
|
|
<dd>The monitored resource entry has been added to the monitored resource
|
||
|
|
directory in the cluster administrative domain but has not yet been synchronized. </dd>
|
||
|
|
</dl>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
<div class="section"><p><strong>Using CL commands and APIs</strong></p>
|
||
|
|
<p>You can use the following
|
||
|
|
commands and APIs to monitor a cluster administrative domain:</p>
|
||
|
|
<ul><li>There is no supported CL command equivalent for this function. The source
|
||
|
|
for a non-supported command and call processing program (CPP) has been provided
|
||
|
|
in the QUSRTOOL library. To learn about this command source and CPP, look
|
||
|
|
at the member QFPADINFO in file QATTINFO.</li>
|
||
|
|
<li><a href="../apis/qfpartve.htm">Retrieve
|
||
|
|
Monitored Resource Information (QfpadRtvMonitoredResourceInfo) API</a> </li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaigmanage.htm" title="This topic contains information that covers some of the tasks that involve managing your clusters.">Manage clusters</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|