Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase

iSCSI network binding order Expand / Collapse
Posted Wednesday, October 30, 2013 10:15 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, June 9, 2015 2:11 PM
Points: 85, Visits: 399
While this is not really SQL specific, does anyone have any information on where in the binding order the iSCSI networks should be on a Windows cluster?

I am dealing with an issue where the SQL resource group fails on a Windows cluster comprised of two VMWare virtual machines. The quorum drive and the SQL disk resources are all iSCSI using the Windows iSCSI initiator. Intermittently (usually in the early AM) the cluster will report losing connection to the storage and losing quorum. The SQL resource group will not failover or restart until it is discovered and manually restarted at the beginning of the business day. I'm concerned that the network binding order may be negatively impacting the iSCSI communication.

Thanks in advance!
Post #1509857
Posted Sunday, November 3, 2013 11:28 AM



Group: General Forum Members
Last Login: Today @ 4:10 PM
Points: 7,985, Visits: 16,022
another user encountered this previously and the recommendation from Microsoft was the following (in order from highest to lowest priority)


Personally I have always used the following


The Public network is usually always enabled for all cluster communication so based on that I set the Private to a lower priority.


"Ya can't make an omelette without breaking just a few eggs"
Post #1510913
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse