December 17, 2014 at 3:18 am
Can any one tell me why there is an error for Disk while doing
Windows clustering for Sql 2012 failover clustering setup.
I configured SAN with iscsi target software and configured target and initiator for doing two node clustering while doing windows clustering.I did configure public and private nwetwork address for clustering requirements
I validated my Clustering Report I did not show any warnings at all.
But still when I created cluster on Node1 it immediately failed back to another node and in cluster events different critical events generated.
mainly I got ownership of Clustering Disk was lost by this node(node1) error.Check network connection and valiadate report.
There in the Disk management I saw Disk0(Quorum disk) and disk1(Foe Sql) were set to offline status and Node2 showed it as ONline.I am getting all disk related warnings in my cluster valiadtion test.Though my Quorum Setting is Node and Disk Majority.
What could have gone wrong here????
December 17, 2014 at 4:14 am
attaching new LUns to a Windows server 2008 on will automatically offline the disks as part of the Diskpart offline policy. This is mainly to avoid the situation where more than one node connects to the disks and corrupts it.
Are you using the Microsoft iSCSI initiator?
Check your iSCSI network configurations?
Can you post any errors from the Windows app and sys event logs?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 17, 2014 at 5:14 am
yes I am using ISCSI Initatiator and I have one NIC for public network and another NIC heartbeat on both nodes participating in clustering.
My DC is ISCSI Target
Network configuration is
192.168.1.10
255.255.255.0
prefered DNS is 192.168.1.10
NODE1
public IP is 192.168.1.20
subnet mask:255.255.255.0
Defaultgetway:192.168.1.1
private Network is :192.168.10.201
subnetmask:255.255.255.0
I have disabled netbios and also dns registration is off
NODE2
public IP is 192.168.1.30
subnet mask:255.255.255.0
Defaultgetway:192.168.1.1
private Network is :192.168.10.202
subnetmask:255.255.255.0
I have disabled netbios and also dns registration is off
what further configuration is needed.
validation did not show any warnings.
I create Target1 on DC with ISCSI with VirtualDISK0 for Quorum size 2gb and VirtualDisk1 for SQL size 20 gb.I have configured one target for both the nodes.I used IP address for specifying IQN.
I went to each node and in initiator wizard I set my DC as Target and added virtual disks.
Then in NODE1 I configured virtualDisk0 and VirtualDisk1 for NTFS partition and gave volume as E and F respectively....
I am rather confused why Cluster Disk warning is generated.
What steps I am Missing while doing storage configuration.....??
They are online on Node1 and offline on node2 and are visible on both the nodes.
Then when I create cluster it failsover and gives error for "ownership on clustered Disk is lost by Node1 "
December 17, 2014 at 5:55 am
you've setup a heartbeat network which you don't actually require, but where is your iSCSI NIC to segregate the iSCSI network traffic?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
December 17, 2014 at 10:48 am
I did the configuration from googling it and what steps I found I just followed it.I do not know how to configure ISCSI NIC and what network address is needed.
sorry to ask you so many queries as I am new to networking
and clustering is not known to me.
Could u pls tell me how to do it.
I am on vmware7.0 for doing basically SQL understanding.
December 18, 2014 at 5:03 am
December 19, 2014 at 12:15 am
Thank you,I appreciate ur prompt reply.
December 19, 2014 at 3:12 am
I did go through articles you suggested but still how to configure ISCSI network is not clear .How cluster or AD will recognize NIC is for ISCSI.
I configured my wfc with having two NIC on both the nodes
public and private with proper configuration and still I see in validation that it is a single point of failure...Can not understand..So pls any help further....
December 19, 2014 at 4:51 am
sej2008 (12/19/2014)
How cluster or AD will recognize NIC is for ISCSI.
By disabling Netbios resolution, disabling DNS registration and not stting a default gateway the cluster service should automatically discover the network as not suitable for any cluster communication.
My articles are fairly comprehensive, i would suggest you work through them a few times from scratch until you're comfortable
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply