v6 - Windows Server 2012 Nic Teaming and network design

Public beta (bugs, reports, suggestions, features and requests)

Moderators: anton (staff), art (staff), Max (staff), Anatoly (staff)

Post Reply
peter.auchincloss
Posts: 16
Joined: Thu Jun 17, 2010 3:10 pm

Tue Aug 21, 2012 4:49 pm

ANy general recommendations for usage of Server 2012 Teaming vs. stand alone multiple nics for data, hearbeat or replication channels?
originally teaming was recommended (several years ago) more recently non teamed - any change or recommended best practices for server 2012 and pending new starwind release?

from figure on Beta site - Also looks like 3 node cfg has iscsiA,icsiB data channels from each node + 3 replication net. channels. Is this recommended cfg?

P
User avatar
anton (staff)
Site Admin
Posts: 4008
Joined: Fri Jun 18, 2004 12:03 am
Location: British Virgin Islands
Contact:

Wed Aug 22, 2012 6:30 am

NIC teaming sucks for SAN traffic. Don't do it. Use MPIO @ initiator and StarWind takes care itself of multiple channels in the best way.

With 3-way replication there are too many ways to go - you don't really need to triple network paths, doubling is an option as well.
peter.auchincloss wrote:ANy general recommendations for usage of Server 2012 Teaming vs. stand alone multiple nics for data, hearbeat or replication channels?
originally teaming was recommended (several years ago) more recently non teamed - any change or recommended best practices for server 2012 and pending new starwind release?

from figure on Beta site - Also looks like 3 node cfg has iscsiA,icsiB data channels from each node + 3 replication net. channels. Is this recommended cfg?

P
Regards,
Anton Kolomyeytsev

Chief Technology Officer & Chief Architect, StarWind Software

Image
Post Reply