| Previous | Next |
| STATUS_CLUSTER_NODE_UP | STATUS_CLUSTER_NODE_NOT_PAUSED |
STATUS_CLUSTER_NODE_PAUSED
The node is paused rather than active
STATUS_CLUSTER_NODE_PAUSED means the target is a cluster member in a paused state. Pausing is commonly used for planned maintenance; with drain, clustered roles are moved away before the node is paused. It is therefore not interchangeable with a node crash or membership removal.
Determine whether the pause was intentional and whether workloads were drained. Resuming a node merely because a request failed can undo a maintenance boundary or trigger unwanted failback, so first verify the maintenance plan and current role placement.
What to verify
- Inspect the node state and the owner of each affected clustered role.
- Use
Suspend-ClusterNode -Drainonly as a planned maintenance action. - Use
Resume-ClusterNodeafter confirming that returning workloads is intended.
References
Looking for a different code? Search another status or error code.