NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

KeithMayer — Thu, 02 May 2013 18:40:06 GMT

Hi Edward,

The switch teaming configuration in the article above is intended for use with static switch-dependent teaming. If you're using dynamic teaming with LACP, you should modify the switch configuration above to use "active" instead of "on" as the channel-group mode by substituting the existing channel-group commands on each interface with:

channel-group 1 mode active

This will configure the switch to use LACP link negotiation across each of the interfaces in the team.

Hope this helps!

Keith

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

KeithMayer — Thu, 02 May 2013 18:19:33 GMT

Hi Shandilye,

Standby adapters are not supported by Switch-dependent NIC teaming to avoid MAC flapping issues that could otherwise occur with the network switch.

Hope this helps!

Keith

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

Edwardon — Wed, 01 May 2013 09:46:17 GMT

I enabled LACP on the switch configuration. The status says it's up.

On the windows 2012 server, create an LACP team with 4 members. I see that the status is Faulted - Reason Not found. I see traffic on the 4 members but still faulted. What could be the reason?

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

shandilye — Mon, 22 Apr 2013 09:09:04 GMT

Hi keith , can you tell me why we dont have stand-by adapter in switch dependent nic teaming?? And can it be possible that we can develop it??

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

KeithMayer — Fri, 23 Nov 2012 15:41:34 GMT

Hi Ray,

NIC Teaming can be used to increase aggregate throughput as well. Inbound traffic distribution to a server with teamed interfaces is controlled by the switch configuration, so double-check your switch documentation to make sure it's setup correctly and that it supports teaming/etherchannels and load distribution. Also check that your switch isn't throttling traffic and that your switch backplane can handle the load you are wanting.

Hope this helps!

Keith

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

KeithMayer — Fri, 23 Nov 2012 15:33:20 GMT

Hi Sig,

Yes, but if you want to extend 1 etherchannel across both switches, you'll need to stack them.

Best regards,

Keith

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

Ray — Wed, 21 Nov 2012 20:04:17 GMT

I've been trying to increase by bandwidth from the 1Gb ports to 8 ports in a Team to hopefully give me 8Gb of bandwidth. It beatufully distributes to 1Gb load amonst all 8 ports which makes my switch happy but I want to increase the bandwidth to push Tb's of data for backups from mutiple 1Gb sources. Am I crazy but I thought the team would increase throughput as well as give redundancy.

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

Sigdarkside — Wed, 21 Nov 2012 14:54:36 GMT

Glad that I have got there your second post made everything a lot clearer. I would just like to confirm the split team outline below.

Creating a channel on each switch with the same number and having 2 ports from 1 team on each is how I split them across?

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

KeithMayer — Wed, 21 Nov 2012 12:30:47 GMT

Hi Sig,

Yes - you've got it! :-) One Etherchannel on the switch per NIC team on a server.

Best regards,

Keith

re: NIC Teaming in Windows Server 2012 - Do I Need to Configure My Switch?

Sigdarkside — Wed, 21 Nov 2012 07:52:04 GMT

Thank you I think I have got this now you create separate channels per server? as on your second blog you was also using etherchannel for the server uplinks am I correct if I configured the following

Switch 1 ports 1-4 Channel 1 relate to server 1 team

Switch 2 ports 1-4 Channel 2 relate to server 2 team

Switch 1 & 2 Ports 5 - 6 channel 3 relate to server 3 team