A Cluster node represents a group of hosts collaborating to form a cluster. The Cluster node represents the group rather than a single physical entity. They are also used represent mainframe sysplexes. Cluster nodes are under the full control of patterns.
Cluster node lifecycle
The following section describes the scenarios in which a Cluster node is created, updated, or removed.
The creation of a Cluster node is under the full control of patterns. Clusters are created when they are detected on a host by a pattern which is searching for them. The pattern contains the conditions which enable it to detect a cluster. Once found, the pattern creates the Cluster that it needs. A relationship link is automatically created to the Host node and the Cluster will have a key generated.
The generated key for a Cluster node is entirely dependent on the kind of Cluster.
The update procedure for a Cluster node is also under full control of patterns. When the pattern has identified a cluster, it calculates a key. If a Cluster node with that key already exists, it is updated accordingly.
A Cluster node can be destroyed either manually or automatically. Cluster nodes are automatically removed when the last remaining Host node or MFPart is unlinked. In some cases, particular patterns might not create a cluster until hosts are detected. In these cases, the pattern will remove the Cluster node when there is only one host linked to it. For vCenter cluster nodes, cluster nodes are removed when a VMware cluster no longer exists.
To manually remove a Cluster node, find the necessary Cluster, select it in the list and pick Destroy from the Actions list. Aging of Clusters node are controlled by a Software Instance node. For more information about cluster aging, see Software Instance node.
This is a Cascade Removal type, see Cascade Removal.
Cluster node attributes
The attributes on a Cluster node as described in the following table:
Type of cluster.
Internal Identifier of cluster.
Internal Name of cluster
Globally unique key.
The primary name that the cluster is known by.
Description of the cluster. Legacy attribute not currently used. Can be used by patterns if desired
URL for information about the cluster. Legacy attribute not currently used. Can be used by patterns if desired
Business Continuity Critical
If true, the cluster is critical to operation of the business. Legacy attribute not currently used. Can be used by patterns if desired
Supported by 3rd Party
If true, the cluster is supported by a third party. Legacy attribute not currently used. Can be used by patterns if desired.
Other names by which this cluster is known. Legacy attribute not currently used. Can be used by patterns if desired.
|Whether the cluster supports failover between members.|
Cluster node relationships
The relationships on a Cluster node are as described in the following table:
Logical hosts that are part of this logical cluster.
MFParts that are part of this Sysplex.
Member Coupling Facilities
Coupling Facilities that are part of this Sysplex.
Software instances that provide this logical cluster.
Software instances that depend upon this logical cluster.
Pattern that is maintaining this cluster.
Software instances that is managing this cluster.
|Software Instances running on this cluster|
|Members of this cluster|
|Services managed by this cluster|
Not displayed in UI
A file attached to this element.
The lifecycle status of this element.
The recovery time specified for this element.
Family of this element.
The Organizational Unit that this element belongs to.
Location of this element.
The person responsible for the support of this element.
The person responsible for this element from a business perspective.
The person responsible for this element from an IT perspective.
Software Instances running on this cluster.
Members of this cluster.
Services managed by this cluster.
Service Software Cluster
Software Clusters that provide this logical cluster.
Dependant Software Clusters
Software Clusters that depend upon this logical cluster.