112 lines
7.4 KiB
HTML
112 lines
7.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="Monitored resources" />
|
||
|
|
<meta name="abstract" content="Monitored resources are types of system resources that can be managed by a cluster administrative domain. These resources are represented in the cluster administrative domain as monitored resource entries (MREs)." />
|
||
|
|
<meta name="description" content="Monitored resources are types of system resources that can be managed by a cluster administrative domain. These resources are represented in the cluster administrative domain as monitored resource entries (MREs)." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptselements.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaigconceptsclusteradmindmn.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="rzaigconceptsmre" />
|
||
|
|
<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>Monitored resources</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaigconceptsmre"><a name="rzaigconceptsmre"><!-- --></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">Monitored resources</h1>
|
||
|
|
<div><p><dfn class="term">Monitored resources</dfn> are types of system resources
|
||
|
|
that can be managed by a cluster administrative domain. These resources are
|
||
|
|
represented in the cluster administrative domain as <dfn class="term">monitored resource
|
||
|
|
entries (MREs)</dfn>.</p>
|
||
|
|
<div class="p">Resources which are synchronized by the cluster administrative domain are
|
||
|
|
represented by monitored resource entries (MRE). Once an MRE is added to the
|
||
|
|
cluster administrative domain, changes made to the resource on any node in
|
||
|
|
the cluster administrative domain will be propagated to all nodes in the active
|
||
|
|
domain. You can use three Integrated Operating Environments APIs to manage
|
||
|
|
MREs in a cluster administrative domain: <ul><li><a href="../apis/qfpaadde.htm">Add Monitored
|
||
|
|
Resource Entry (QfpadAddMonitoredResourceEntry) API</a></li>
|
||
|
|
<li><a href="../apis/qfparmve.htm">Remove Monitored
|
||
|
|
Resource Entry (QfpadRmvMonitoredResourceEntry) API</a></li>
|
||
|
|
<li><a href="../apis/qfpartve.htm">Retrieve
|
||
|
|
Monitored Resource Information (QfpadRtvMonitoredResourceInfo) API</a></li>
|
||
|
|
</ul>
|
||
|
|
</div>
|
||
|
|
<p>A monitored resource entry can be added to the cluster administrative domain
|
||
|
|
for the following types of resources: </p>
|
||
|
|
<ul><li>System values</li>
|
||
|
|
<li>User profiles </li>
|
||
|
|
<li>Job descriptions</li>
|
||
|
|
<li>Class </li>
|
||
|
|
<li>Independent disk pools device description </li>
|
||
|
|
<li>Network attributes</li>
|
||
|
|
<li>System environment variables </li>
|
||
|
|
<li>TCP/IP attributes </li>
|
||
|
|
</ul>
|
||
|
|
<p>An MRE can only be added to the cluster administrative domain if all nodes
|
||
|
|
in the domain are active and participating in the group. An MRE cannot be
|
||
|
|
added if the cluster administrative domain is partitioned. Once the MRE is
|
||
|
|
added, changes to the resource represented by the MRE are propagated to all
|
||
|
|
active nodes in the domain when the peer CRG is started. If the CRG is ended,
|
||
|
|
pending changes will be propagated to the active domain when the CRG is started
|
||
|
|
again. </p>
|
||
|
|
<p>There is a global status associated with an MRE. When the resource represented
|
||
|
|
by an MRE has the same values for all of the attributes that are being monitored
|
||
|
|
on all nodes in the active domain, the global status for that resource is
|
||
|
|
consistent. If the cluster administrative domain attempts to update a resource
|
||
|
|
on one or more nodes, and the update fails, the global status of the resource
|
||
|
|
is inconsistent. When the global status is inconsistent, the administrator
|
||
|
|
must determine the cause of the failure and correct it. The cluster administrative
|
||
|
|
domain will attempt to resynchronize the resource the next time it is updated,
|
||
|
|
probably when the administrator changes the resource as a result of fixing
|
||
|
|
the problem which caused an update to fail, or when the CRG is restarted.</p>
|
||
|
|
<p>When the cluster administrative domain CRG is ended, the global status
|
||
|
|
for all MREs is set to inconsistent. This is because while the CRG is ended,
|
||
|
|
changes can be made to monitored resources on different nodes and they therefore
|
||
|
|
become inconsistent. </p>
|
||
|
|
<p>If the resource represented by an MRE is a system object, it should not
|
||
|
|
be deleted, renamed or moved to a different library without removing the MRE
|
||
|
|
first. If a resource is deleted, renamed or moved to a different library,
|
||
|
|
the global status for the MRE will be inconsistent and any changes made to
|
||
|
|
the resource on any node after that will not be propagated to the cluster
|
||
|
|
administrative domain.</p>
|
||
|
|
<p>When a node is added to the cluster administrative domain, all of the MREs
|
||
|
|
from the active domain will be copied to the new node. Any resources represented
|
||
|
|
by an MRE which do not exist on the new node will be created and the values
|
||
|
|
of the attributes will be set to the same values as the active cluster administrative.
|
||
|
|
</p>
|
||
|
|
<p>If there are nodes in the cluster administrative that are not active, any
|
||
|
|
resource changes that are made in the active domain will be propagated to
|
||
|
|
the inactive nodes once they rejoin the active domain. If a cluster administrative
|
||
|
|
domain is partitioned, changes will continue to be synchronized among the
|
||
|
|
active nodes in each partition. When the nodes are merged back together again,
|
||
|
|
the cluster administrative domain will propagate all changes made in every
|
||
|
|
partition so that the resources are consistent within the active domain.
|
||
|
|
If multiple changes were made in different partitions to the same resource,
|
||
|
|
each change will be processed by the cluster administrative domain after the
|
||
|
|
partitions are merged, although the sequence is indeterminate.</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 class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="rzaigconceptsclusteradmindmn.htm" title="A cluster administrative domain is used to manage resources that need to be maintained consistently across the nodes in a clustered environment.">Cluster administrative domain</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<img src="./deltaend.gif" alt="End of change" /></body>
|
||
|
|
</html>
|