| Previous | Next |
| STATUS_CLUSTER_NETWORK_ALREADY_OFFLINE | STATUS_COULD_NOT_RESIZE_LOG |
STATUS_CLUSTER_NODE_ALREADY_MEMBER
The join target is already a cluster member
STATUS_CLUSTER_NODE_ALREADY_MEMBER indicates that the requested add or join operation targets a server that is already represented as a member of this failover cluster. Repeating the join does not repair an unavailable node, a paused node, or a node with a different runtime problem.
The useful next question is whether the existing member is Up, Down, Paused, or stuck during another operation. Keep membership identity separate from reachability and cluster service state; otherwise automation can incorrectly treat an existing record as proof of a usable node.
What to verify
- Enumerate members and verify that the target belongs to the intended cluster, not a similarly named environment.
- Inspect node state before retrying an add operation.
- Run validation before changing membership when the target has recently been rebuilt or reconfigured.
References
Looking for a different code? Search another status or error code.