SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Ownership of cluster disk 'Cluster Disk xxx has been unexpectedly lost by this node.


Ownership of cluster disk 'Cluster Disk xxx has been unexpectedly lost by this node.

Author
Message
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4521 Visits: 1930
Perry Whittle (5/3/2013)
sql-lover (5/2/2013)
-Change the network binding order. Put HeartBeat second and SAN last (SAN was 2nd and heartbeat the last one)

I can sort of see why but I don't see this is to relevant, the cluster communication can still take place over the public network (the default setting)


sql-lover (5/2/2013)
-Assign fix IP values on the iSCSI initiator properties

Now this is relevant, your heartbeat and iscsi adapters should be set to not register themselves in DNS. Always provide fixed IP details to the initiator disk device connection to ensure the correct adapters are bound. My article linked above details this.


Agree.

So I would give a try to the 2nd one (1st is done) which was initially configured by our IT resource, by the way.
Ramasankar Molleti
Ramasankar Molleti
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 203
Is your problem got resolved?
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4521 Visits: 1930
sankar276 (5/3/2013)
Is your problem got resolved?


No.

My cluster has been stable past 7 days or so, but I have not changed the iSCSI setting yet.
Ramasankar Molleti
Ramasankar Molleti
SSC Veteran
SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)SSC Veteran (264 reputation)

Group: General Forum Members
Points: 264 Visits: 203
Seems to me it is an OS issue.

http://support.microsoft.com/kb/972797

Better test before changing.
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4521 Visits: 1930
sankar276 (5/3/2013)
Seems to me it is an OS issue.

http://support.microsoft.com/kb/972797

Better test before changing.


Interesting.

We applied a hotfix already, but did nothing, it happened again. Now, not sure if it was the same or not.

I'll take notice though, thanks for reply.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53934 Visits: 17679
sql-lover (5/6/2013)
it happened again. Now, not sure if it was the same or not.

I'll take notice though, thanks for reply.

Have you made the changes in the iscsi initiator?

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4521 Visits: 1930
Perry Whittle (5/7/2013)
sql-lover (5/6/2013)
it happened again. Now, not sure if it was the same or not.

I'll take notice though, thanks for reply.

Have you made the changes in the iscsi initiator?


Today ... :-)

But tested the process on my VMware lab already.
ginolard
ginolard
SSC-Enthusiastic
SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)SSC-Enthusiastic (119 reputation)

Group: General Forum Members
Points: 119 Visits: 19
Sorry to hijack but we are experiencing a similar issue on our 3-node cluster. Two of the disks attached to an HP MSA SAN reguarly "lose ownership".

The iSCSI initiator properties for ALL targets are set to

Local Adapater: Default
Initiator IP: Default
Target Portal IP: Default

Are you saying these values should be changed to this?

Local Adapater: Microsoft iSCSI Initiator
Initiator IP: x.x.x.x
Target Portal IP: x.x.x.x

I also notice that the binding order is DIFFERENT on each node, God knows what idiot set that up but I guess they should be exactly the same?
sql-lover
sql-lover
SSCarpal Tunnel
SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)SSCarpal Tunnel (4.5K reputation)

Group: General Forum Members
Points: 4521 Visits: 1930
ginolard (5/7/2013)
Sorry to hijack but we are experiencing a similar issue on our 3-node cluster. Two of the disks attached to an HP MSA SAN reguarly "lose ownership".

The iSCSI initiator properties for ALL targets are set to

Local Adapater: Default
Initiator IP: Default
Target Portal IP: Default

Are you saying these values should be changed to this?

Local Adapater: Microsoft iSCSI Initiator
Initiator IP: x.x.x.x
Target Portal IP: x.x.x.x

I also notice that the binding order is DIFFERENT on each node, God knows what idiot set that up but I guess they should be exactly the same?


Two things ...

Each case is different, so I suggest open a new thread and post your issue, so any other user or Perry can step in and help. Not that I mind you for hijack my thread though :-) ... but you may get better attention.

2nd thing is ... the MS engineer advice was to change the binding order and put the fixed IP on iSCSI initiatior, yes, that is correct. But I do differ on the 1st advice though. This is how I usually configure my Clusters (binding order(

-Public
-Heartbeat
-SAN

This is why MS is recommending

-Public
-SAN
-Heartbeat

And binding order should BE THE SAME ON ALL NODES!

I do agree that the iSCSI initiator should use actual IPs though, and that's what I will change today with the help of my IT resource.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)SSC Guru (53K reputation)

Group: General Forum Members
Points: 53934 Visits: 17679
ginolard (5/7/2013)
The iSCSI initiator properties for ALL targets are set to

Local Adapater: Default
Initiator IP: Default
Target Portal IP: Default

Are you saying these values should be changed to this?

Local Adapater: Microsoft iSCSI Initiator
Initiator IP: x.x.x.x
Target Portal IP: x.x.x.x

Yes, see my article at this link


ginolard (5/7/2013)
TI also notice that the binding order is DIFFERENT on each node, God knows what idiot set that up but I guess they should be exactly the same?

The binding order must be the same on all nodes

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" ;-)
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search