| Previous | Next |
| STATUS_CLUSTER_NO_SECURITY_CONTEXT | STATUS_CLUSTER_POISONED |
STATUS_CLUSTER_NETWORK_NOT_INTERNAL
The selected network is not an internal cluster network
STATUS_CLUSTER_NETWORK_NOT_INTERNAL means an operation that requires internal cluster communication was given a network not configured for that purpose. Client connectivity and internal cluster traffic have different roles; a network being reachable to clients does not make it suitable for heartbeat or node-to-node cluster work.
Verify the intended role before changing it. Reclassifying a client-facing network solely to clear this code can reduce isolation or create a new failure domain. Compare the cluster design, network inventory, and interfaces on every node before applying a role change.
What to verify
- Inspect the network role and interface membership with the FailoverClusters cmdlets.
- Confirm that all cluster nodes have the expected internal communication path.
- Use validation to check the topology after deliberate role changes.
References
- Microsoft: Get-ClusterNetwork
- Microsoft: Get-ClusterNetworkInterface
- Microsoft: Failover Clustering overview
- Microsoft: Test-Cluster
Looking for a different code? Search another status or error code.