IMPORTANT ANNOUNCEMENT FOR OUR READERS!
AskPFEPlat is in the process of a transformation to the new Core Infrastructure and Security TechCommunity, and will be moving by the end of March 2019 to our new home at https://aka.ms/CISTechComm (hosted at https://techcommunity.microsoft.com). Please bear with us while we are still under construction!
We will continue bringing you the same great content, from the same great contributors, on our new platform. Until then, you can access our new content on either https://aka.ms/askpfeplat as you do today, or at our new site https://aka.ms/CISTechComm. Please feel free to update your bookmarks accordingly!
Why are we doing this? Simple really; we are looking to expand our team internally in order to provide you even more great content, as well as take on a more proactive role in the future with our readers (more to come on that later)! Since our team encompasses many more roles than Premier Field Engineers these days, we felt it was also time we reflected that initial expansion.
If you have never visited the TechCommunity site, it can be found at https://techcommunity.microsoft.com. On the TechCommunity site, you will find numerous technical communities across many topics, which include discussion areas, along with blog content.
NOTE: In addition to the AskPFEPlat-to-Core Infrastructure and Security transformation, Premier Field Engineers from all technology areas will be working together to expand the TechCommunity site even further, joining together in the technology agnostic Premier Field Engineering TechCommunity (along with Core Infrastructure and Security), which can be found at https://aka.ms/PFETechComm!
As always, thank you for continuing to read the Core Infrastructure and Security (AskPFEPlat) blog, and we look forward to providing you more great content well into the future!
Whether ’tis nobler in the mind to suffer not knowing the answer to this question or educate thy self…
Enough of Shakespeare… Where’s my PFE, when I need him?
Well in previous releases of the operating system, customers always depended on vendors to provide a support solution for NIC Teaming software. Even then in those days, neither the vendors nor Microsoft supported teaming iSCSI Initiator and recommended using the vendor’s MPIO (multi-path I/O) solution and/or DSM (device-specific modules).
So here’s where the confusion comes in and a lot of customers have been asking us…
Is NIC Teaming supported for iSCSI, or not supported for iSCSI?
Because when customers read this TechNet article Failover Clustering Hardware Requirements and Storage Options, it states “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 demystify the question that inspired me to write this blog, I consulted with Don Stanwyck (Sr. Program Manager / Windows Core Networking) who is the authority on this subject and here is the essence of the message he conveyed:
· 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 2012 inbox 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 (see figure below) such as in a Hyper-V 2012 environment, then iSCSI Initiator used over the Hyper-V switch (and over NIC Teaming) is supported.
· In a native environment where the NICs are shared between iSCSI Initiator and other uses, the following configuration is also supported.
· Just to make one point clear, 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. So even if the iSCSI initiators aren’t using Microsoft’s NIC Teaming (LBFO) solution (and perhaps not MPIO/DSM either), the iSCSI targets can use teamed NICs however you like.
KEY IMPORTANT TAKE AWAY
When iSCSI is used with dedicated NICs, then using any teaming solution is not recommended and MPIO/DSM should be used. But when iSCSI is used with shared NICs, those shared NICs can be teamed and will be supported as long as it’s being used with Microsoft’s Windows Server 2012 NIC Teaming (LBFO) solution.
In addition, we will always recommend you consult with your iSCSI storage vendor to confirm the support of iSCSI solutions with their storage. When in doubt, you can always search the status of any hardware testing completed on the Windows Server Catalog – Certified for Windows Server 2012.
NIC Teaming Overview.
Hope you find this blog enlightening and clears up any doubts you might have heard regarding the ability to use NIC Teaming software with iSCSI.
Off I go to travel the world and see cities where no PFE has gone before…
Mike Rosado (About me…)
As my lawyer would say… “This posting is provided “AS IS” with no warranties, and confers no rights