Windows Server / Hyper-V & Failover Clustering
Check failover-cluster network roles during heartbeat or migration issues
A network can be available at the OS layer while cluster policy excludes it from the required traffic. Inspect managed roles.
Environment and inputs: Windows Server 2022 / 2025 baseline · Windows PowerShell with the specified role or RSAT modules; native utilities are identified in the text. Use delegated administration and elevation only where required.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
Get-ClusterNetwork | Select-Object Name, Address, Role, State, Metric, AutoMetricRead the result
The output describes cluster network configuration and reported state. It does not replace physical routing, firewall or storage-network validation.
Resolve and verify
Compare roles and metrics with the intended heartbeat, client and migration design. Correct a verified policy mismatch and confirm cluster stability.
Before changing production
Do not enable cluster communication on isolated storage networks or change several network priorities at once.