Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««1234»»»

Ownership of cluster disk 'Cluster Disk xxx has been unexpectedly lost by this node. Expand / Collapse
Author
Message
Posted Friday, May 3, 2013 7:27 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
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.
Post #1449191
Posted Friday, May 3, 2013 9:56 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 3, 2014 1:44 AM
Points: 103, Visits: 111
Is your problem got resolved?
Post #1449387
Posted Friday, May 3, 2013 10:04 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
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.
Post #1449388
Posted Friday, May 3, 2013 10:14 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Monday, November 3, 2014 1:44 AM
Points: 103, Visits: 111
Seems to me it is an OS issue.

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

Better test before changing.
Post #1449389
Posted Monday, May 6, 2013 2:46 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
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.
Post #1449888
Posted Tuesday, May 7, 2013 2:36 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 6,752, Visits: 14,400
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"
Post #1450027
Posted Tuesday, May 7, 2013 7:17 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
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.
Post #1450125
Posted Tuesday, May 7, 2013 8:41 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 12:40 AM
Points: 7, 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?
Post #1450194
Posted Tuesday, May 7, 2013 9:12 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, December 17, 2014 8:01 AM
Points: 416, Visits: 1,345
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.
Post #1450209
Posted Tuesday, May 7, 2013 12:17 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 6:20 AM
Points: 6,752, Visits: 14,400
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"
Post #1450290
« Prev Topic | Next Topic »

Add to briefcase ««1234»»»

Permissions Expand / Collapse