Windows Server R2 NIC Teaming

To improve the adaptability and performance of virtualized environments, Windows Server 2012/R2 built-in support for network adapter hardware with Nic bundling. Although NIC bundling technology in Windows Server 2012/R2 is not a feature of Hyper-V, it is essential for critical hyper-V environments because it provides greater adaptability and performance to virtual machines. Nic bundling is also known as "adapter bundling" and "Load Balancing Failover" (LBFO). Allows multiple network adapters on one computer to be placed in the NIC group for the following purposes: bandwidth aggregation, communication failover, to prevent loss of connectivity in the event of a network component failure.

In the current IT environment, all NIC bundling solutions on the market use a similar architecture, as shown in

650) this.width=650; "height=" 273 "title=" image "style=" Border:0px;padding-top:0px;padding-right:0px;padding-left : 0px;background-image:none; "alt=" image "src=" http://s3.51cto.com/wyfs02/M01/58/DA/ Wkiom1s-u86jfxigaab-l80fzz8426.jpg "border=" 0 "/>

Two or more physical network adapters connect to the multiplexing unit of the NIC bundle solution, which can then be rendered as one or more virtual adapters (also called bundled network adapters) for the operating system. There are several algorithms for allocating incoming and outgoing traffic between physical network adapters. Currently in a non-Microsoft NIC bundle solution, bundled network adapters distribute traffic on a virtual LAN (VLAN), so applications can connect to different VLANs at the same time. From a technical point of view, this division of communications is not a function of Nic bundling, but because other commercially available NIC bundling solutions have this capability, Windows Server 2012/R2 also includes this functionality.

In Windows Server 2012/R2, the NIC bundle mainly uses two sets of basic algorithms:

1. The algorithm that requires the switch to participate in the bundle is also called Switch dependency mode. These algorithms typically require that all network adapters that are bundled are connected to the same switch.

2. There is no need for the switch to participate in the bundled algorithm, also known as switch standalone mode. Because the switch does not know that the network adapter participates in the bundle, the bundled network adapters can be connected to different switches. Switch-independent mode does not have to require members of the bundle to connect to different switches, but this is a viable practice.

NIC teaming is compatible with all network features in Windows Server 2012/R2, but the following three features are exceptions: SR-Iov, Remote direct access (RDMA), TCP chimney offload.

NIC teaming requires an Ethernet network adapter that can be used to detach traffic that uses VLANs. All modes that provide fault protection through failover require a minimum of two Ethernet network adapters. The Windows Server 2012 implementation supports up to 32 NICs in a single combination.

1. Open Server Manager and click on local server to view current server network information. The system is disabled by default and requires the technology to be manually enabled.

650) this.width=650; "height=" 480 "title=" clip_image004 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image004 "src=" http://s3.51cto.com/wyfs02/ M02/58/da/wkiom1s-u8_srlbfaaf2b-ivtyc444.jpg "border=" 0 "/>

2. Click "Disabled" to open the NIC teaming configuration page, and any NIC groups currently configured, so "group" is "0" and all available network adapter information can be added to the group

650) this.width=650; "height=" 486 "title=" clip_image006 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image006 "src=" http://s3.51cto.com/wyfs02/ M00/58/da/wkiom1s-u8-ccackaafnn71tjcy918.jpg "border=" 0 "/>

3. Click the task in groups to select New Group

650) this.width=650; "height=" 475 "title=" clip_image008 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image008 "src=" http://s3.51cto.com/wyfs02/ M01/58/da/wkiom1s-u8-zyacbaadkrzxn2ha157.jpg "border=" 0 "/>

4. Create a new group page, type the name of the NIC group, and select which network adapters you want to add to the group

650) this.width=650; "height=" 499 "title=" clip_image010 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image010 "src=" http://s3.51cto.com/wyfs02/ M02/58/da/wkiom1s-u8_xrulyaafcsz-1b1k113.jpg "border=" 0 "/>

5. Expand additional properties to see teaming mode, load Balancing mode, standby adapter, and primary group Interface (VLAN) for the NIC Group

650) this.width=650; "height=" 253 "title=" clip_image012 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image012 "src=" http://s3.51cto.com/wyfs02/ M00/58/d7/wkiol1s-vksw81dtaadfxzprtnw810.jpg "border=" 0 "/>

There are two main options for NIC bundling in switch dependent mode:

1. Universal or static bundling (IEEE 802.3ad Draft v1): This mode requires that the switch and the configuration on the computer identify which links are bundled. Because this is a statically configured solution, there is no other protocol to assist in the exchange, and the computer may fail the bundle if it detects a faulty connection to the cable or other error. This mode is typically supported by server-level switches.

2. Dynamic bundling (IEEE 802.1ax, LACP): IEEE 802.1ax uses Link Aggregation Control Protocol (LACP) to dynamically identify the link between a computer and a specific switch. This automatically creates the bundle and theoretically only needs to transmit or deny LACP from the peer network adapter to scale up or down the bundle. Typical server-level switches typically support IEEE 802.1ax, but most switches require manual management of operations to enable the LACP capabilities of the ports.

Both of these modes can cause incoming and outgoing traffic to reach the aggregated bandwidth limit, because the link pool in the bundle can be used as a single pipeline.

3. Switch Standalone mode: system default, this mode does not require the switch to participate in the combination configuration, because the switch in standalone mode does not recognize that the NIC is part of the virtual machine host.

650) this.width=650; "height=" 249 "title=" clip_image014 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image014 "src=" http://s3.51cto.com/wyfs02/ M01/58/d7/wkiol1s-vkscetkgaac08hit_zc298.jpg "border=" 0 "/>

The NIC bundle in Windows Server R2 supports the following distribution methods to support load balancing:

1. Hyper-V switch port. If the virtual machine uses a separate media access control (MAC) address, the virtual machine MAC address can provide basic communication partitioning. This is an advantage of using the architecture in a virtualized environment. Because a neighboring switch can determine that a particular source MAC address is located on a connected network adapter, the switch balances the egress load (traffic from the switch to the computer) across multiple links based on the MAC address of the target virtual machine. This approach is ideal for use with virtual machine queues. However, this mode may not achieve a sufficient average allocation and limits the available bandwidth for a single network adapter to be used by a virtual machine. (Note: Windows Server R2 uses the Hyper-V switch Port as an identifier instead of the source MAC address, because in some cases the virtual machine may need to use multiple MAC addresses on one switch port.) )

2. Hash. The algorithm creates a hash based on the packet component and assigns the packet to an available network adapter based on the hash value. This ensures that all packets from the same TCP stream will use the same network adapter. The hashing algorithm itself is typically balanced across all available network adapters. Some commercially available network card bundling solutions monitor the distribution of traffic and allocate a specific hash value to different network adapters to better balance the traffic. This dynamic redistribution is also known as Intelligent load Balancing or adaptive load balancing.

In a hash operation, a component that can be used as an input party includes:

1) Source and destination MAC address

2) Source and destination IP address, can be considered or regardless of MAC address (double hash)

3) Source and destination TCP port, typically used with IP address (quad hash)

The quad hash enables more granular distribution of traffic flows, which in turn can move smaller data streams in a separate way between network adapters. However, this technique cannot be used for communication with non-TCP or UDP protocols, nor for traffic that is hidden by TCP and UDP ports in the stack, such as traffic protected by Internet Protocol security (IPSEC). In this case, the hashing technique used is rolled back to a double hash. If the communication is not an IP traffic, the Hashishen generator uses the MAC address of the source and destination addresses.

3. Dynamic NIC bundle. Windows Server R2 uses the concept of Flowlet to implement dynamic LBFO. Flowlet is a set of TCP/IP packets that exist in most network traffic flows, inheriting the feature of TCP communication "burst". The advantage of using Flowlet to balance load is that the Flowlet is smaller in volume than stream, sending more frequently, and can be more accurately and quickly re-balancing network communication among different members. Windows Server 2012 cannot detect Flowlet, so it cannot be rebalanced. Flowlet always uses the same path as the previous Flowlet in the traffic flow. In Windows Server R2, each Flowlet can be routed independently to the last used NIC in the bundle. Each packet in the Flowlet then uses the same bundle member. With MAC address rewriting, nearby switches will not detect the movement of the stream.

650) this.width=650; "height=" 244 "title=" clip_image016 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image016 "src=" http://s3.51cto.com/wyfs02/ M02/58/d7/wkiol1s-vktji_wqaacoh-h54ga098.jpg "border=" 0 "/>

The NIC bundle in Windows Server R2 can also be used for virtual machines. This allows a virtual machine to connect to multiple hyper-V switches through a virtual network adapter, even if one of the network adapters under the switch is disconnected. This feature is particularly important when using features such as single-root I/O virtualization (SR-Iov), because SR-Iov communication is not transmitted over the Hyper-V switch and therefore cannot be protected by a NIC bundle in the Hyper-V switch. By bundling the virtual machine itself, an administrator can set up to two hyper-V switches, each connected to a dedicated network adapter that supports SR-Iov. This can be achieved by:

1. Each virtual machine installs virtual function through one or more network adapters that support SR-Iov, and then, once a network adapter is disconnected, the virtual machine can still fail over from the primary virtual function to the backing virtual function.

2. Or a virtual machine can obtain a virtual function from a network adapter and connect to other switches through a non-virtual function network adapter. If the network adapter associated with the virtual Function is disconnected, the communication can be switched on and off directly to the other switch.

Under the standby adapter, the default is "None (all network adapters are active, that is, active-active)"

650) this.width=650; "height=" 267 "title=" clip_image018 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image018 "src=" http://s3.51cto.com/wyfs02/ M00/58/d7/wkiol1s-vksyjs97aadvoxn1bqc168.jpg "border=" 0 "/>

If the administrator wants the network interface to have VLAN capabilities, tap default VLAN to open the VLAN dialog box to select the appropriate VLAN ID

650) this.width=650; "height=" 499 "title=" clip_image020 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image020 "src=" http://s3.51cto.com/wyfs02/ M01/58/d7/wkiol1s-vkxtfzjbaaeep2xjshu220.jpg "border=" 0 "/>

6. Click OK to create the NIC group to support high availability of the NIC

650) this.width=650; "height=" 483 "title=" clip_image022 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image022 "src=" http://s3.51cto.com/wyfs02/ M00/58/d7/wkiol1s-vkaidd-aaagrrs94ugc349.jpg "border=" 0 "/>

7. Open the Network Sharing Center and view the network properties at this time to create a specially identified network card, i.e. Vmnic

650) this.width=650; "height=" 279 "title=" clip_image024 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image024 "src=" http://s3.51cto.com/wyfs02/ M00/58/da/wkiom1s-u9kh5runaafv4hmbebi697.jpg "border=" 0 "/>

8. Legacy network adapter properties, no Tcp/ipv4 information, but one more Microsoft network adapter multipath Transporter protocol for network adapter load balancing and failover

650) this.width=650; "height=" 499 "title=" clip_image026 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image026 "src=" http://s3.51cto.com/wyfs02/ M02/58/da/wkiom1s-u9lhp2f0aagsu_8p8aa008.jpg "border=" 0 "/>

The following shows how to create a NIC using Windows PowerShell Teaming

1. Open Windows PowerShell as an administrator

2. Use "Get-netadapter" to query the current host all network card information

650) this.width=650; "height=" 219 "title=" clip_image028 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image028 "src=" http://s3.51cto.com/wyfs02/ M00/58/da/wkiom1s-u9ow9-azaaf0j5h7xqo480.jpg "border=" 0 "/>

3. Use the "New-netlbfoteam" command to add NIC1 and NIC2 to the NIC group "Appnic"

650) this.width=650; "height=" 255 "title=" clip_image030 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image030 "src=" http://s3.51cto.com/wyfs02/ M01/58/d7/wkiol1s-vkjacdmtaafyapjug1g562.jpg "border=" 0 "/>

4. Use "Get-netlbfoteam" to view NIC teaming information

650) this.width=650; "height=" "title=" clip_image032 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image032 "src=" http://s3.51cto.com/wyfs02/ M02/58/d7/wkiol1s-vkidedfnaagkxh3dxwm880.jpg "border=" 0 "/>

5. Use "Set-netlbfoteam" to modify NIC teaming teaming mode

650) this.width=650; "height=" "title=" clip_image034 "style=" margin:0px;border:0px;padding-top:0px;padding-right : 0px;padding-left:0px;background-image:none; "alt=" clip_image034 "src=" http://s3.51cto.com/wyfs02/M00/58/D7/ Wkiol1s-vkjsdgbhaace6l0qh1o621.jpg "border=" 0 "/>

6. Use "Set-netlbfoteam" to modify the NIC teaming load Balancing mode

650) this.width=650; "height=" 206 "title=" clip_image036 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image036 "src=" http://s3.51cto.com/wyfs02/ M01/58/d7/wkiol1s-vkizv8wqaaecolfbms4214.jpg "border=" 0 "/>

7. Use the command to set the NIC teaming mode to switch standalone mode, load Balancing mode is transporports (address hash)

650) this.width=650; "height=" 187 "title=" clip_image038 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image038 "src=" http://s3.51cto.com/wyfs02/ M02/58/d7/wkiol1s-vkmcrcvhaad3pipnrky917.jpg "border=" 0 "/>

8. Use "Get-netlbfoteammember" to view the NIC teaming network adapter status, currently displayed active-active

650) this.width=650; "height=" 395 "title=" clip_image040 "style=" margin:0px;border:0px;padding-top:0px; Padding-right:0px;padding-left:0px;background-image:none, "alt=" clip_image040 "src=" http://s3.51cto.com/wyfs02/ M00/58/d7/wkiol1s-vknxthxiaaitluuzjno657.jpg "border=" 0 "/>

9. Use "Set-netlbfoteammember" to modify the NIC to standby mode

650) this.width=650; "height=" "title=" clip_image042 "style=" border:0px;padding-top:0px;padding-right:0px; Padding-left:0px;background-image:none, "alt=" clip_image042 "src=" http://s3.51cto.com/wyfs02/M00/58/DA/ Wkiom1s-u9wjxqlaaag25elzcvk841.jpg "border=" 0 "/>

This article is from "Xu Ting Blog-Microsoft technology Sharing" blog, please be sure to keep this source http://ericxuting.blog.51cto.com/8995534/1606383

Windows Server R2 NIC Teaming