I've spent an entire day chasing down one article after another that claims it might have a resolution for this problem and absolutely nothing is panning out. This is more or less a hail mary in case someone can explain to me where in the cluster.log things go wrong, because I just can't see it.... it's possible I just have been at the computer too long.
Anyway, this exact condition happens when I try to create the cluster with both nodes at the same time, or when I try to add one node to the other I already have set up successfully - so it's got something to do with node-to-node communication, but I'll be damned if I can figure out what.
- Windows 2008 R2 SP1 Enterprise, god so many updates.
- Ran all operations as Domain Administrator
- Windows firewall turned off on both nodes for all zones.
- No Antivirus is installed
- Ipv6 and IPv4 are enabled. Problem also exists if IPv4 is only enabled.
- No issues with domain or network participation, this is a fresh install in known-good infrastructure.
The Wizard goes all the way through to where it is trying to finalize the cluster and it spits up "Unable to cleanup" followed by the Report's explanation
"An error occurred while creating the cluster.
An error occurred creating cluster 'ISOHADR1wsfc'.
This operation returned because the timeout period expired"
I've built more Microsfot clusters over the years than I care to count and I'm still impressed with Microsoft's ability to obfuscate fault evidence. Can anyone make sense of this cluster.log for me? or any of it? I need a drink.
Here's a pastebin of the log: http://pastebin.com/8LE31htH
Thanks very much in advance for your time and consideration, hopefully this is just something silly I missed.