NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Steve — Thu, 16 May 2013 15:34:01 GMT

Thanks

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Don Stanwyck — Tue, 16 Apr 2013 05:04:54 GMT

The NIC Teaming Deployment guide is published with answers to most questions. Please take a few minutes and download the guide from www.microsoft.com/.../details.aspx and read it. If you have questions or suggestions that we should incorporate into the next version of the guide please let me know.

Yoda - your question is answered in the guide. We do support teaming under the Hyper-V switch.

Topokin - please see the answer I posted above in response to Pavol.

--don stanwyck

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Jeffrey Tippet [MSFT] — Tue, 16 Apr 2013 01:11:37 GMT

@strange error

The NIC Teaming GUI will show an adapter as not "teamable" if the adapter meets any of these criteria:

- The NIC is already in a team or a Hyper-V switch

- The NIC is used for kernel debugging

- The NIC is not Ethernet (the driver's INF has *PhysicalMediaType set to something other than 0 or 14)

- The NIC cannot bind to TCPIP or TCPIPv6 (it's ok if the binding isn't currently enabled; the NIC is only blocked if the checkbox doesn't show up at all)

Additionally, if the "Hide adapters that cannot be added to a team" setting in the GUI is checked, then the GUI will also hide a NIC if it meets any of these criteria:

- The NIC is not currently bound to TCPIP or TCPIPv6

- The NIC is marked as "hidden" by the NIC driver (the driver's INF has Characteristics with bit 8 set for NCF_HIDDEN)

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

topokin — Sat, 23 Mar 2013 15:24:22 GMT

I have Windows Server 2012 Full installation on HP DL 360p G8. Teaming is configured with 2 nic through the "Server Manager" console, however I observed that the MAC-Address of the "Teamed-NIC" often alternates itself between MAC-Address of both physical NICs.

Is this a normal behaviour or there is something still missing. The teaming is configured in LACP mode.

Since this system is to serve as a License-Server and some licenses configuration are MAC-Address dependency, how can I overcome this random chages

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

strange error — Mon, 18 Feb 2013 22:20:11 GMT

I have a Windows 2012 Data Center Edition installation where all 4 NIC's are showing as "can not be added to a team" but there are no teams configured. We're trying to create a team but since we can not added any interfaces it's impossible. Anyone else run across this?

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Yoda — Fri, 15 Feb 2013 11:20:28 GMT

Hi there,

what´s about NIC-teaming with Hyper-V Hosts für the virtual Switch? Is this a supported scenario?

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Thomas W Shinder - MSFT — Tue, 27 Nov 2012 12:50:22 GMT

In Windows Server 2012 NIC Teaming is a feature of the operating system. In the past, you had to depend on NIC vendor driver support for NIC Teaming, and then you would only team that vendor's NICs. In Windows Server 2012, you can team any NICs from any vendor. Also, regarding the question of the differences between the vendor driven and operating system NIC teaming- with the Windows Server 2012 NIC Teaming there's now a standard set of built-in features, while in the past, each vendor teaming implemented a different set of capabilities.

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

MMF — Mon, 26 Nov 2012 10:19:48 GMT

What exactly is the difference to using a network team provided in Server 2003 - 2008 R2?

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Don Stanwyck — Wed, 10 Oct 2012 14:03:22 GMT

Pavol - the MAC address of the team is the MAC address of the first NIC in the team that we see after a reboot. If you want a static IP address for the team you can assign it directly to the team. If you want a static MAC address for the team you can also set that on the advanced properties of the primary team interface.

--don

re: NIC Teaming in Windows Server 2012 Brings Simple, Affordable Traffic Reliability and Load Balancing to your Cloud Workloads

Neel — Mon, 08 Oct 2012 15:31:28 GMT

Good One!!!