Troubleshooting the resource monitoring and control (RMC) subsystem

The RMC subsystem runs as a daemon process on individual machines. You can use it to manage and monitor the resources of a single machine, or you can use it to manage and monitor the resources of a cluster's peer domain or management domain. In a peer domain or management domain, the RMC daemons on the various nodes work together to enable you to manage and monitor the domain's resources.

The term peer domain is defined as a set of nodes which have a consistent knowledge of the existence of each other and of the resources shared among them. On each node within the peer domain, RMC depends on a set of core cluster services, which include Topology Services, Group Services and Cluster Security Services.

The term management domain is defined as a set of nodes whose resources can be managed and monitored from one of the nodes, which is designated as the Management Control Point (MCP). All other nodes are considered to be Managed Nodes. Topology Services and Group Services are not used in a management domain.

When troubleshooting the RMC subsystem, it is important to note that, because of the dependencies of this subsystem on the core cluster services, problems that occur in the core cluster services may manifest in RMC. Because this is so, you should perform the diagnostic procedures for the core cluster services once you complete the initial verification tests for RMC. The most common problems caused by problems in the core cluster services are sundered or partitioned domains due to underlying network interface problems, and authentication or authorization errors due to incorrect security configuration.