Microsoft issued a hotfix over the holidays to deal with an issue where:
- You configure a failover cluster that has some computers that are running Windows Server 2008 R2.
- One cluster node is offline or is removed from the cluster.
- You try to rejoin the cluster node to the cluster after a while.
In this scenario, the cluster node cannot rejoin the cluster.
According to Microsoft, the cause is that:
When a cluster node tries to rejoin a cluster after it is restarted or removed from the cluster, the virtual IP address of the cluster node may be changed. However, other cluster nodes still use old route records in their route database. Therefore, the cluster node cannot rejoin the cluster.
A supported hotfix is available from Microsoft.
This blog post is the property of Aidan Finn (@joe_elway / http://www.aidanfinn.com) and may not be reused in any manner without prior consent of Aidan Finn. You may quote one paragraph from this blog post if you link to the original blog post.
- KB2727972–W2008 R2 Cluster Node Crashes When You Restart A Node
- KB2575625 – W2008 R2 Cluster Starts Failover After 80 Seconds When You Shutdown Active Node
- KB2710487 – Error 1359 & Cluster Service Stops In W2008 or W2008 R2 Failover Cluster
- KB2769588 – An Update That Adds 4-Node Failover Cluster Deployment Support In OEM WS2012 OOBE
- KB2738482 – W2008 R2 Cluster Validation Indicates Unsigned ACOIPMI Driver