October 30, 2013 at 10:15 am
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!
November 3, 2013 at 11:28 am
another user encountered this previously and the recommendation from Microsoft was the following (in order from highest to lowest priority)
Public
Private
iSCSI
Personally I have always used the following
Public
iSCSI
Private
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" 😉
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply