<div>
<div class="content wysiwyg-content">
Hello<br />
I have an Intel I350T4 Nic with 4 ports. &nbsp;I would like to set this up for performance and fault tolerance in a Hyper-V environment. &nbsp;<br />
<br />
I would like to have one of the ports for the Host server and the other 3 for traffic on the VMs that will reside there.<br />
<br />
Is this a case where I should setup different teams? &nbsp;Do I assign IP addresses for each of the NIC ports? &nbsp;Should I use the Intel Teaming application or the native Server application?<br />
<br />
Thanks in advance!
</div>
</div>


Hello
I have an Intel I350T4 Nic with 4 ports.  I would like to set this up for performance and fault tolerance in a Hyper-V environment.  

I would like to have one of the ports for the Host server and the other 3 for traffic on the VMs that will reside there.

Is this a case where I should setup different teams?  Do I assign IP addresses for each of the NIC ports?  Should I use the Intel Teaming application or the native Server application?

Thanks in advance!

How do I use a multiport Nic for performance and fault tolerance in server 2012 r2 hyper-v environment

Servers are computing devices that are similar to desktop computers in that they have the same basic components, but are significantly different in size, configuration and purpose. Servers are usually accessed over a network, and many run unattended, without a computer monitor, input device, audio hardware or USB interfaces. Many servers do not have a graphical user interface (GUI), and are configured and managed remotely. Servers typically include hardware redundancy such as dual power supplies, RAID disk systems, and ECC memory, along with extensive pre-boot memory testing and verification. Critical components might be hot swappable, and to guard against overheating, servers might have more powerful fans or use water cooling.

Server Hardware

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Hyper-V is a native hypervisor; it can create virtual machines on x86-64 systems and supersedes Windows Virtual PC as the hardware virtualization component of the client editions of Windows NT. A server computer running Hyper-V can be configured to expose individual virtual machines to one or more networks. Hyper-V Server supports remote access via Remote Desktop Connection. Administration and configuration of the host OS and the guest virtual machines is generally done over the network.