| Previous | Next |
| ERROR_CLUSTER_INVALID_NETWORK | ERROR_CLUSTER_IPADDR_IN_USE |
ERROR_CLUSTER_NODE_UP
This is commonly an idempotency or state-transition status rather than a fault. For example, an operation designed for an offline node can return this code after another administrator or automation job has already brought the node online.
Read the current node state before applying operations that require Down or joining state. For idempotent tooling, treat an already-Up node explicitly rather than using repeated state changes as a health check.
What to check
- Confirm the current node state before retrying the command.
- Check for concurrent maintenance or automation actions that changed the node state.
- If the node unexpectedly returned to Up, inspect the cluster log for the preceding membership transition.
Get-ClusterNodeLooking for a different code? Search another status or error code.