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.
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.
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.
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.
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.
Using iSeries™ Navigator
To monitor a cluster administrative domain, follow these steps:Using CL commands and APIs
You can use the following commands and APIs to monitor a cluster administrative domain:
