What is NIC teaming ? Will NIC teaming will be help full? how many types of configuration are there in NIC? can we mix different teaming solutions?

NIC teaming, also known as Load Balancing/Failover (LBFO), allows multiple network adapters to be placed into a team for the purposes of

· bandwidth aggregation, and/or

· traffic failover to maintain connectivity in the event of a network component failure.

This feature has long been available from NIC vendors but until now NIC teaming has not been included with Windows Server.

The following sections address:

· NIC teaming architecture

· Bandwidth aggregation (also known as load balancing) mechanisms

· Failover algorithms

· NIC feature support – stateless task offloads and more complex NIC functionality

· A detailed walkthrough how to use the NIC Teaming management tools

NIC teaming is available in Windows Server2012 in all editions, both Server Core and Full Server versions. NIC teaming is not available in Windows8, however the NIC teaming User Interface and the NIC Teaming Windows PowerShell Cmdlets can both be run on Windows8 so that a Windows8 PC can be used to manage teaming on one or more Windows Server2012 hosts.

Existing architectures for NIC teaming

Today virtually all NIC teaming solutions on the market have an architecture similar to that shown in Figure1.

Figure1 – Standard NIC teaming solution architecture and Microsoft vocabulary

One or more physical NICs are connected into the NIC teaming solution common core, which then presents one or more virtual adapters (team NICs [tNICs] or team interfaces) to the operating system. There are a variety of algorithms that distribute outbound traffic between the NICs.

The only reason to create multiple team interfaces is to logically divide inbound traffic by virtual LAN (VLAN). This allows a host to be connected to different VLANs at the same time. When a team is connected to a Hyper-V switch all VLAN segregation should be done in the Hyper-V switch instead of in the NIC Teaming software.

Configurations for NIC Teaming

There are two basic configurations for NIC Teaming.

Switch-independent teaming. This configuration does not require the switch to participate in the teaming. Since in switch-independent mode the switch does not know that the network adapter is part of a team in the host, the adapters may be connected to different switches. Switch independent modes of operation do not require that the team members connect to different switches; they merely make it possible.

• • Active/Standby Teaming: Some administrators prefer not to take advantage of the bandwidth aggregation capabilities of NIC Teaming. These administrators choose to use one NIC for traffic (active) and one NIC to be held in reserve (standby) to come into action if the active NIC fails. To use this mode set the team in Switch-independent teaming. Active/Standby is not required to get fault tolerance; fault tolerance is always present anytime there are at least two network adapters in a team.
  • Switch-dependent teaming. This configuration that requires the switch to participate in the teaming. Switch dependent teaming requires all the members of the team to be connected to the same physical switch.

There are two modes of operation for switch-dependent teaming:

Generic or static teaming (IEEE802.3ad). This mode requires configuration on both the switch and the host to identify which links form the team. Since this is a statically configured solution there is no additional protocol to assist the switch and the host to identify incorrectly plugged cables or other errors that could cause the team to fail to perform. This mode is typically supported by server-class switches.

Dynamic teaming (IEEE802.1ax, LACP). This mode is also commonly referred to as IEEE802.3ad as it was developed in the IEEE802.3ad committee before being published as IEEE802.1ax. IEEE802.1ax works by using the Link Aggregation Control Protocol (LACP) to dynamically identify links that are connected between the host and a given switch. This enables the automatic creation of a team and, in theory but rarely in practice, the expansion and reduction of a team simply by the transmission or receipt of LACP packets from the peer entity. Typical server-class switches support IEEE802.1ax but most require the network operator to administratively enable LACP on the port.

Both of these modes allow both inbound and outbound traffic to approach the practical limits of the aggregated bandwidth because the pool of team members is seen as a single pipe.

Algorithms for traffic distribution

Outbound traffic can be distributed among the available links in many ways. One rule that guides any distribution algorithm is to try to keep all packets associated with a single flow (TCP-stream) on a single network adapter. This rule minimizes performance degradation caused by reassembling out-of-order TCP segments.

NIC teaming in Windows Server2012 supports the following traffic distribution algorithms:

 

Interactions between Configurations and Load distribution algorithms

Switch Independent configuration / Address Hash distribution

This configuration will send packets using all active team members distributing the load through the use of the selected level of address hashing (defaults to using TCP ports and IP addresses to seed the hash function).

Because a given IP address can only be associated with a single MAC address for routing purposes, this mode receives inbound traffic on only one team member (the primary member). This means that the inbound traffic cannot exceed the bandwidth of one team member no matter how much is getting sent.

This mode is best used for:

a) Native mode teaming where switch diversity is a concern;

b) Active/Standby mode teams; and

c) Teaming in a VM.

It is also good for:

d) Servers running workloads that are heavy outbound, light inbound workloads (e.g., IIS).

 

Switch Independent configuration / Hyper-V Port distribution

This configuration will send packets using all active team members distributing the load based on the Hyper-V switch port number. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port is affinitized to exactly one team member at any point in time.

Because each VM (Hyper-V port) is associated with a single team member, this mode receives inbound traffic for the VM on the same team member the VM’s outbound traffic uses. This also allows maximum use of Virtual Machine Queues (VMQs) for better performance over all.

This mode is best used for teaming under the Hyper-V switch when

a) The number of VMs well-exceeds the number of team members; and

b) A restriction of a VM to not greater than one NIC’s bandwidth is acceptable

Switch Dependent configuration / Address Hash distribution

This configuration will send packets using all active team members distributing the load through the use of the selected level of address hashing (defaults to4-tuple hash).

Like in all switch dependent configurations, the switch determines how to distribute the inbound traffic among the team members. The switch is expected to do a reasonable job of distributing the traffic across the team members but it has complete independence to determine how it does so.

Best used for:

a) Native teaming for maximum performance and switch diversity is not required; or

b) Teaming under the Hyper-V switch when an individual VM needs to be able to transmit at rates in excess of what one team member can deliver.

Switch Dependent configuration / Hyper-V Port distribution

This configuration will send packets using all active team members distributing the load based on the Hyper-V switch port number. Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port is “affinitized” to exactly one team member at any point in time.

Like in all switch dependent configurations, the switch determines how to distribute the inbound traffic among the team members. The switch is expected to do a reasonable job of distributing the traffic across the team members but it has complete independence to determine how it does so.

Best used when:

a) Hyper-V teaming when VMs on the switch well-exceed the number of team members and

b) When policy calls for switch dependent (e.g., LACP) teams and

a) When the restriction of a VM to not greater than one NIC’s bandwidth is acceptable.

NIC teaming is the process of grouping several physical NICs together into one single logical NIC, which can be used for network fault tolerance and transmit load balance.

It will help by avoid the failure of any NIC by switching the transmitting to other NIC also will help to load balance which allow to distributing traffic through the members of a NIC.

 

There are two configurations for NIC Teaming.

1-Switch-independent teaming, this configuration does not require the switch to participate in the teaming

2-Switch-dependent teaming, this configuration that requires the switch to participate in the teaming

regarding to mix different teaming solutions this is not supported in the Windows Server2012 R2 NIC Teaming solution .

NIC taming, also known as Loa Balancing/Failover (LBFO), allows multiple network adapters to b placed into a team for the purposes of .bandwidth aggregation,and/ or .Traffic failover to maintain.

Its a redundancy Solution, where you can combine two interface cards to work as a Team, it can also be used for load balancing, and Bandwidth aggregation.

This feature has been a requirement for independent hardware vendors to enter the server network adapter market, but until now NIC Teaming has not been included in Windows Server operating systems.

for high availability...it's a basic thing you should do, when you built your datacenter

 Employee empowerment, the innovative designing of hierarchical structure, and the right recruitment of talent employees are important

First, management should offer innovative working environment that encourages employees' abilities to innovate and become more open-minded. Second, organization culture should be supportive to this process of innovations. Moreover, employee empowerment, the innovative designing of hierarchical structure, and the right recruitment of talent employees are important.

Let him shar with me my innovations as we are team work and work for same goal