Resource classes defined by the configuration resource manager
In general, you do not need to manipulate resources of these classes directly. Instead, use the configuration resource manager commands.
Table 1 describes the resource classes
defined by the configuration resource manager. In general, you do
not need to manipulate resources of these classes directly. Instead,
use the configuration resource manager commands. However, you might
need to:
- Modify attributes of the RSCTParameters class.
- Modify the CritRsrcProtMethod attribute of the IBM.PeerNode class or a resource instance of the IBM.PeerNode class.
- Modify the OpQuorumOverride attribute of the IBM.PeerNode class.
- Modify the OpQuorumTieBreaker attribute of the IBM.PeerNode class.
- Modify the IsPreferredGSGL attribute of the IBM.PeerNode class.
| Resource class | Description |
|---|---|
| IBM.CommunicationGroup | Each resource of this class represents a communication resource upon which liveness checks (Topology Services heartbeat) is performed. |
| IBM.HeartbeatInterface | Each resource of this class represents a heartbeat interface that exists in the peer domain. |
| IBM.NetworkInterface | Each resource of this class represents an IP network interface that exists in the peer domain. |
| IBM.PeerDomain | Each resource of this class represents an RSCT
peer domain in which a particular node is defined. Each node has its
own IBM.PeerDomain
resource class, with each instance of the resource class, representing
an RSCT peer domain in which the node is defined. The number of instances
of this resource class, therefore, indicates the number of peer domains
in which the node is defined. For the DomainType resource
persistent attribute, |
| IBM.PeerNode | Each resource of this class represents a node defined in the peer domain. A node is here defined as an instance of an operating system, and is not necessarily tied to hardware boundaries. |
| IBM.RSCTParameters | Represents operational characteristics of RSCT subsystems. |
| IBM.TieBreaker | Each resource of this class represents a tiebreaker. A tiebreaker is used, when domain partitioning results in two subdomains, each containing exactly one-half of the nodes, to determine which subdomain has an operational quorum. In QuorumLess mode, a tiebreaker is always used to determine the subdomain that has an operational quorum. |