NIC Teaming and iSCSI

hi,

from following article: https://blogs.technet.microsoft.com/askpfeplat/2013/03/18/is-nic-teaming-in-windows-server-2012-supported-for-iscsi-or-not-supported-for-iscsi-that-is-the-question/ we know can use iscsi on lbfo , has advantages on mpio in cases. , iscsi on lbfo supported targets.

now, have storages have 2 nic, have 3, others 4. on other side, hyper-v servers have 4,5,6,8 nics. have 2 solutions implementation.

if use mpio, need create virtual adapters on storage server to create paths on alternate vlans 6 vlans (as hyper-v server have 6 nics iscsi traffic) or need create teams on hyper-v servers access storage (over 2 vlans) , run mpio on top of teams.

in other case, team on both sides , run iscsi traffic on teams (initiator , target). 1 seems involve way less moving parts other (straight teaming instead of teaming + vlan + mpio). , feel simpler better.

so work while still offering performances ? iscsi traffic able use bandwidth of aggregated nics properly?

thanks comments

never run mpio on top of nic teaming.  use 1 or other.

traffic conform lowest common denominator, otherwise known skinniest pipe in communication link.  if iscsi target has 2 nics, theoretical max ever hope out of throughput of slowest of 2 nics times two.

have performed benchmarks have proven storage bottleneck in environment?  because increase available bandwidth storage not mean applications can benefit it.

are looking @ solution because have several 1 ge links?  better solution go 2 10 ge connections instead of trying work things out multiple 1 ge links.

and, though iscsi supported on teamed nics, still recommended use mpio.

---

. : | : . : | : . tim

Windows Server  >  Hyper-V