The cmm_membership_remove() function removes the
node from which this function is called from the cluster. The node is still
configured to be in the cluster, but its role has changed. The CMM API is
always accessible for an CMM_OUT_OF_CLUSTER node.
When the nhcmmd daemon detects that a node is no longer part of the cluster, it informs other applications
or services that are registered to receive notification. See the Netra High Availability Suite Foundation Services 2.1 6/03 CMM Programming Guide for information
on the notifications returned in different scenarios.
To reintegrate a node into the cluster after the cmm_membership_remove() function has been called on the node, restart the node's nhcmmd daemon by rebooting the node.
Note that after the cmm_membership_remove() call,
a node is still to be configured to be in the cluster, but it has the CMM_OUT_OF_CLUSTER role. Because it is still configured to be in
the cluster, it can access cluster information:
This is different from a node not being configured for any cluster. If the node is not configured for any
cluster, the CMM_ENOCLUSTER value is returned.
Any program running on the node can call cmm_membership_remove(). There is no authentication carried out of the program making
the call. Calling this function from the master leads to a failover (or CMM_ECANCELED if no vice-master can take the mastership role).