Where allowed to run: All environments (*ALL) Threadsafe: No |
Parameters Examples Error messages |
The Change Cluster Node Entry (CHGCLUNODE) command is used to change cluster membership information for a cluster node entry. The information that can be changed is the cluster interface addresses defined for the node and status of the node. The node entry which is being changed may or may not have Cluster Resource Services started.
You can add, remove, or replace an interface address for the cluster node. The cluster interface address is an IP address that is used by Cluster Resource Services to communicate with other nodes in the cluster. The address is in dotted decimal format.
You can also change the the status of a node to Failed. Using this command to change the status of a node to Failed provides a way to tell Cluster Resource Services that a node has really failed. There are certain failure conditions that Cluster Resource Services cannot detect as a node failure. Rather, the problem appears to be a communication problem and the cluster looks like it has become partitioned. By telling Cluster Resource Services that a node has failed, it makes recovery from the partition state simpler for primary-backup model cluster resource groups since a backup node from the remaining active cluster nodes can then be assigned as the primary node.
For primary-backup model cluster resource groups:
If a problem is detected and the command does not complete successfully, the command can be run again once the problem is corrected. Any cluster resource group that had already had the status of a node changed from Partition to Failed and the recovery domain order changed will not be affected by running this command again.
Warning: Changing the node status to failed when, in fact, the node is still active and a true partition has occurred should not be done. Doing so for primary-backup model cluster resource groups, allows a node in each partition to become the primary node for a cluster resource group. When two nodes think they are the primary node, data such as files or data bases could become corrupted if two different nodes are each making independent changes to copies of their files. In addition, the two partitions cannot be merged back together when a node in each partition has been assigned the primary role.
Restrictions:
Top |
Keyword | Description | Choices | Notes |
---|---|---|---|
CLUSTER | Cluster | Name | Required, Positional 1 |
NODE | Node identifier | Name | Required, Positional 2 |
OPTION | Option | *ADDIFC, *RMVIFC, *CHGIFC, *CHGSTS | Required, Positional 3 |
OLDINTNETA | Old IP address | Character value | Optional, Positional 4 |
NEWINTNETA | New IP address | Character value | Optional, Positional 5 |
Top |
Specifies the cluster that contains the node being changed.
This is a required parameter.
Top |
Specifies the node being changed.
This is a required parameter.
Top |
Indicates what is being changed.
This is a required parameter.
Top |
Specifies the cluster interface address which is being replaced or removed. The address is in dotted decimal format.
This is a required parameter.
Top |
Specifies the cluster interface address which is being added to the node information or replacing an old cluster interface address. The address is in dotted decimal format.
This is a required parameter.
Top |
CHGCLUNODE CLUSTER(MYCLUSTER) NODE(NODE01) OPTION(*CHGSTS)
This command changes the status of node NODE01 in cluster MYCLUSTER to Failed.
Top |
Top |