Shulou(Shulou.com)05/31 Report--

Today, I will talk to you about how to use NIC teaming components in Windows Server 2012. Many people may not know much about it. In order to let you know more, Xiaobian summarizes the following contents for you. I hope you can gain something according to this article.

High availability is the most important thing in IT today. Security, compliance and common business requirements keep IT merchants running. Going back decades, I remember how scary and expensive high availability was to compete with Windows and other competing operating systems. Many Windows administrators are still experiencing pain, high fees to pay for high availability in their environment. Microsoft is counting on NIC teaming in Windows Server 2012 to fix this problem.

For cloud scenarios or simple indoor settings, Windows Server 2012 provides many features in the NIC teaming applet. Accurate to build and extremely simple to configure.

NIC teaming, or load balancing and failover, allows multiple network cards to combine for port aggregation and failover in case network hardware fails. In Windows Server 2012, we are tied to NIC vendors to provide these features. Without a direct OS collection, Microsoft does not officially support NIC teaming. In Windows Server 2012, NIC teaming was dequeued and integrated into the OS.

Some out-of-the-box NIC teaming features include:

Virtual NIC support inside Hyper-V

Switch-dependent, switch-independent modes do not all require that each NIC be connected to the same Ethernet switch

VLAN offloading, applications can simultaneously session different VLANs

Support up to 32 NIC per group

Technologies that do not support NIC teaming in Windows Server 2012 include PCI I/O Virtualization, Remote Direct Memory Access, and TCP Chimney.

Configuring NIC teaming is a simple process: boot up, add groups to the server, and configure each group with a specific NIC.

You can do this using PowerShell, Server Manager GUI, and RSAT tools in Windows 8. PowerShell has NIC teaming-specific commands, as follows:

NetLbfoTeam (retrieve, create, delete, rename, set)

NetLbfoTeamMember (add, retrieve, delete, set)

NetlbfoTeamNic (retrieve, create, delete, set)

Simply type Get-Command-Module NetLbfo to get all available commands.

Configuring NIC groups in GUI is important:

1. Select Local Server/Properties/Remote Desktop/ NIC Combination Management.

2. Select the server name and select New Team under Teams/Tasks.

3. Enter the group name and select the dedicated network card you want.

More information on NIC teaming can be found in Microsoft's document Windows Server 2012 NIC Teaming (LBFO) Deployment and Management.

One of the things I've seen over the years is that network administrators don't take full advantage of the IT management and security technologies available to them. As a former webmaster, I think this is largely due to a general lack of time and attention. NIC teaming isn't sexy anymore, but it can give you a lot of server recovery. Customers, internal auditors and even administrators will never know you're using it, but that's what keeps businesses running smoothly anyway and makes things seem simple. Microsoft gave us NIC teaming, and I can't think of any reason not to use it in Windows Server 2012.

After reading the above, do you have any further understanding of how to use NIC teaming components in Windows Server 2012? If you still want to know more knowledge or related content, please pay attention to the industry information channel, thank you for your support.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.