| Previous | Next |
| STATUS_CLUSTER_INVALID_NODE | STATUS_CLUSTER_JOIN_IN_PROGRESS |
STATUS_CLUSTER_NODE_EXISTS
The cluster already contains that node entry
STATUS_CLUSTER_NODE_EXISTS reports a duplicate-node condition in cluster configuration. It commonly appears when a management operation tries to create or register a node record whose identity is already present, even if that member is currently unavailable.
Resolve the identity collision before changing membership. Removing or re-adding a node just to clear this status can disrupt quorum, ownership, or workload placement. First determine whether the existing record is the same server, a stale record from a rebuild, or the wrong target cluster.
What to verify
- Enumerate node names and IDs before attempting another add.
- Check whether the server was rebuilt, renamed, or restored from an image.
- Use validation and documented membership procedures instead of editing configuration state indirectly.
References
Looking for a different code? Search another status or error code.