| Previous | Next |
| ERROR_CLUSTER_NETWORK_NOT_INTERNAL | ERROR_CLUSTER_NODE_ALREADY_DOWN |
ERROR_CLUSTER_NODE_ALREADY_UP
This is normally a harmless state result. It should not be treated as proof that the node is fully healthy; a node can be Up while an individual resource, group, or network interface still has a problem.
Confirm the node has stable membership, networks, and required services before declaring the incident resolved. If automation only wanted an idempotent start, handle this state as success instead of issuing additional transitions.
What to check
- Check the node state together with resource and group ownership.
- If the request came from automation, make the operation state-aware to avoid reporting an already-completed action as a failure.
- Inspect logs only if the node became Up unexpectedly or immediately changed state again.
Get-ClusterNode; Get-ClusterGroup; Get-ClusterResource
Looking for a different code? Search another status or error code.