Hi,
Since there are many articles and questions about these 2 designs when implement Hyper-v 2012 Failover Cluster:
Design 1:
Use NIC Teaming to connect to ISCSI, and Later convert the disk to CSV (Test it and working)
Design 2:
Use MPIO of WS2012 to connect to ISCSI, and later convert it to CSV (Not tested with 2012 Hyper-V Cluster)
Refering to this article:
"The Microsoft’s Windows Server 2012 NIC Teaming (LBFO) solution is also supported for iSCSI targets (such as Microsoft’s iSCSI target) anytime, not just in the shared NIC scenario..."
But also,
“For iSCSI, network adapter teaming (also called load balancing and failover, or LBFO) is not supported. You can consider using MPIO software instead.”
So to Resume, i didn't get this points:
The Technet statement that basically quotes “iSCSI + NIC Teaming not supported” is still true for all teaming solutions, with the EXCEPTION of the Windows Server 2012inbox NIC Teaming solution we provide.
· If iSCSI Initiator is used with dedicated NICs such as in a stand-alone and/or Failover Clustering environment, then NIC Teaming should not be used (because it adds no benefit over MPIO for dedicated NICs).
· If iSCSI Initiator is used in a shared NIC scenario such as in a Hyper-V 2012 environment, then iSCSI Initiator used over the Hyper-V switch (and over NIC Teaming) is supported.
My Questions are about WS2012 Hyper-v FO Cluster with ISCSI :
- NIC Teaming is supported ?? its is Best Practice ?
- MPIO Is supported ?? its is Best Practice ?
- Converting MPIO to CSV does have any known issues ?
.
I would like to Clarify it once for All ! Thank you
Systems Engineer & Solutions Architect
Please remember to click “Mark as Answer” on the post that answer your thread question. Also you can "Vote as Helpful" for the posts that helps you. This can be beneficial to other community members reading the thread.