Some concepts of the Windows Server R2 NIC teaming

650) this.width=650; "Src=" Http://s4.51cto.com/wyfs02/M00/8A/AC/wKioL1g3mtTibOs_AADIxONYogk874.png-wh_500x0-wm_3 -wmp_4-s_1122865668.png "title=" Nic1.png "alt=" Wkiol1g3mttibos_aadixonyogk874.png-wh_50 "/>

Group mode

1. Static Group:

also called a switch dependency group because of this NIC The combination requires the switch to participate in the combination, so NIC all adapters in a group must be connected to the same switch, not on multiple different switches. The switch is required to support the IEEE802.3AD standard.

2. Switch Independence:

the NIC The combination does not require a switch to participate in the combination, so each adapter can be connected to a different switch and also provides basic fault tolerance at the switch level.

3.LACP:

the Link Aggregation Control Protocol (link Aggregation controls PROTOCOL,LACP), which can automatically combine multiple NIC a network adapter that is combined into a single logical (virtual) unit. The switch is required to support LACPandis set to active.

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/8A/B0/wKiom1g3mtSy4TZfAAC12UZObUg051.png-wh_500x0-wm_3 -wmp_4-s_3524316574.png "title=" Nic2.png "alt=" Wkiom1g3mtsy4tzfaac12uzobug051.png-wh_50 "/>

Load Balancing Mode

2. Address hash:

   NIC after a group receives a packet, it is first checked and then the information for the destination address (for example, IP address, port, etc.) through a hashing algorithm, based on the results NIC The group decides to pass the packet through the NIC issued. Because of the hashing algorithm, the traffic direction cannot be controlled, and the large amount of data flows to the same network card.
   

4. hyper-v Port:

     If your server is running multiple hyper-v nic
   

6. Dynamic:

   traffic can be passed through a call flowlets concept to achieve dynamic LBFO , the concept is actually to split a large packet into smaller packets, through different NIC sent out.
   

   
   

650) this.width=650; "Src=" Http://s2.51cto.com/wyfs02/M01/8A/AC/wKioL1g3mtWyDu9HAACxzjnhVF8717.png-wh_500x0-wm_3 -wmp_4-s_3922857686.png "title=" Nic3.png "alt=" Wkiol1g3mtwydu9haacxzjnhvf8717.png-wh_50 "/>

Alternate adapter: Configurable as needed

Precautions:

1 , on the physical server, Windows Server R2 only supported at most + a NIC Teaming ;

2 , in virtual machine ( hyper-v "in group mode only supports" switch independent ", load Balancing mode only supports" address hash "

3 , these types of network adapters are not supported: wlan bluetooth , Span style= "FONT-FAMILY:CALIBRI;" lang= "en-us" xml:lang= "en-US" >wwan infiniband

4 , only in NIC build groups above, cannot create groups on the basis of groups;

5 , in the virtual machine, only support two network cards, but in the experimental test, can contain more network cards

Thanks to the blog support of the Snow orchid great God, http://yupeizhi.blog.51cto.com/

This article is from the "Record Bit Technology" blog, please make sure to keep this source http://seawind.blog.51cto.com/6845370/1876474

Some concepts of the Windows Server R2 NIC teaming