Adding node in windows cluster freezes at “waiting for notification that node ‘‘ is a fully functional member of the cluster”
When you try to add a node to cluster in windows2008 or windows2008 R2 or windows 2012 it may get stuck in the below screen With message “waiting for notification that node is a fully functional member of the cluster”
After some time you will notice “operation is taking longer time than expected” and eventually after the time out add node wizard will fail with error “Unable to successfully cleanup”.
You may notice “the operation is taking longer than expected in some time”
If you look at cluster diagnostic log you may find
[RHS] RhsCall::Perform_NativeEH: ERROR_NOT_READY(21)’ because of ‘Startup routine for ResType MSMQTriggers returned 21.’
Failed to write SPNs to node’s computer object – status 5
1. To resolve the exclude UDP port 3343 from fire wall.
2. If the issue persists after opening the UDP port 3343. Check failover clustering diagnostic event for error “Failed to write SPNs to node’s computer object – status 5”. If you find above error make sure http://support.microsoft.com/kb/976424 is applied in Domain controller.
3. If you find event ID 1289 “The Cluster Service was unable to access network adapter ‘Microsoft Failover Cluster Virtual Miniport’. Verify that other network adapters are functioning properly and check the device manager for errors associated with adapter ‘Microsoft Failover Cluster Virtual Miniport’. If the configuration for adapter ‘Microsoft Failover Cluster Virtual Miniport’ has been changed, it may become necessary to reinstall the failover clustering feature on this computer” follow the steps in http://support.microsoft.com/kb/973838
4. Make sure IPv6 is enabled on all NIC’s
5. Enabled Cluster communication and client access on the Public network http://technet.microsoft.com/en-us/library/cc728293%28v=ws.10%29.aspx
6. Make sure Symantec Endpoint Protection is uninstalled/disabled when you add the node.
7. Make sure there is no duplicate name computer objects for nodes in AD .follow http://blogs.technet.com/b/askcore/archive/2011/05/31/cluster-installation-time-out-issues.aspx
Number 6. Every so often you just need someone to slap you in the face to remind you of the dumb things that can go wrong. We were setting up our first 2012 cluster and couldn’t get the nodes to talk to each other. We were convinced it was something to do with the Microsoft NIC teaming. Turns out we used an unmanaged Symantec package to install AV on both servers. We were so used to installing our managed packages that we completely forgot Network Threat Protection is part of the original package. FML! The good news is that the cluster build went quite smoothly after that.