| Previous | Next |
| STATUS_CLUSTER_NODE_ALREADY_UP | STATUS_CLUSTER_NETWORK_ALREADY_ONLINE |
STATUS_CLUSTER_NODE_ALREADY_DOWN
The node is already in the requested Down state
STATUS_CLUSTER_NODE_ALREADY_DOWN means a caller requested a transition to Down for a node that the cluster already considers down. It is distinct from removing the node from cluster membership: the object can remain part of the cluster database while its runtime state is Down.
This result should lead to a state check rather than another stop command. Determine whether the node was deliberately stopped, lost cluster communication, or never completed startup. Those cases have different recovery paths even though the requested transition is equally redundant.
What to verify
- List node state and membership before attempting any rejoin or removal.
- Collect cluster logs around the last state change rather than relying only on a service-control result.
- Confirm quorum and workload placement before taking additional nodes offline.
References
Looking for a different code? Search another status or error code.