Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 6672

Help in creating first Windows Failover Cluster

$
0
0

This is my first attempt in creating a failover cluster. I've followed the instructions on "Failover Cluster Step-by-Step Guide: Configuring Accounts in Active Directory" along with the required ports.

https://technet.microsoft.com/en-us/library/cc731002(v=ws.10).aspx#BKMK_steps_precreating
http://cybergav.in/2013/07/28/windows-server-failover-cluster-port-requirements-for-intra-node-connectivity/

Added the Failover Cluster Featurs via Manager on both server-dev01 & server-dev02. I ran the validation and all seems to check out.  I then create the cluster, "server-cdev", via "Create Cluster Wizard".  That didn't go well.

I pulled the logs via PowerShell command "Get-ClusterLog" and tried looking at the logs but can't really make heads or tails with it.

There's some things I don't get and I'm hoping you can help me out.
 - Why there are random IPv4 and IPv6 (IPv6 not enabled) on the logs that I know nothing off and not on our DNS records in the logs?
 - Both 137 & 3343 ports are open on our firewall but can't telnet to server-dev01 <- either -> server-dev2 on port 3343 / 137. Does this need to be fixed before running the cluster wizard?
 - I see these two but have no idea what they mean (I did see a similar post but no answer to the question - https://social.technet.microsoft.com/Forums/windowsserver/en-US/9d25c123-a763-405f-8c20-61da2d4b4390/cluster-creation-error?forum=winserver8gen)
[DCM] DiskControlManager bitlocker load status 126
[API] DmQueryString failed to retrieve the security   descriptor status 2, default security descriptor will be used for authorizing client connections

I tried posting the logs here but got an error message about the "Body must be 4 - 60000 characters long"

Your help is greatly appreciated..


Viewing all articles
Browse latest Browse all 6672

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>