iSCSI Setup in production enviroment?

[ASE001]

I’m just specify a large SQL cluster and it is using iSCSI to connect to a SAN. It will be using two 10Gbit dedicated Intel Ethernet (with iSCSI acceleration) cards to a NetApp SAN.

I’m pondering over a few design decisions around NIC settings?

Use MPIO or NIC teaming to provide network resilience?
Jumbo frames setting?
MTU setting?
Fixed or Auto speed?
Or any settings I need to consider?
Do and don’ts?

 

[ASE001]

I've been doing some research since I posted, it's seems in a Server 2008R2 clusterd enviroment both teaming and MPIO are valid. But in a Hyper-V enviroment only MPIO is supported?

I suppose what I'm after is best practice or white paper on the subject?


Cheers

 

[ASE001]

Further to my previous post I have discovered that certain Microsoft Technet articles suggest that NIC teaming is not officially supported for iSCSI, although works. NIC teaming is a function performed by the NIC vendor's driver which are not written by Microsoft therefore have limited control over. MPIO on the other hand is written by Microsoft so is supported.

Based on that, I think I will play it safe and go with MPIO.