How to create a NIC Teaming on Windows Server 2012 UPDATED !

-
CLICK ON THE BELOW LINK FOR THE UPDATED POST
 How to Create/Configure a NIC Teaming on Server 2016/ 2012 Physical or VM's























How to create/ enable a NIC Teaming on Windows Server 2012 /R2










NIC Teaming Overview


NIC Teaming, also known as load balancing and failover (LBFO), allows multiple network adapters on a computer to be placed into a team for the following purposes:
  • Bandwidth aggregation
  • Traffic failover to prevent connectivity loss in the event of a network component failure 

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

More Info: Windows Server 2012 R2 





NIC Teaming Step  by Step

I've made this tutorial on a Hyper-V 2012 Virtual Machine with Server 2012 R2 with two Virtual NICs.


Go to your Server Manager Console and then click on Local Server


On Local Server Select Enable NIC Teaming  to configure the Networks


On your  NIC Teaming Console Click on TEAMS / TASKS / New Team


Now Name and Select the Adapters that you want to team




Created, now I have a Network Adapter Multiplexor of  20Gbps  bandwidth





If you go to your Network Adapter  to modify the IP you should select the Multiplexor Adapter



Thanks for watching !







Follow me on twitter  @DavidiAcevedo

Comments

Post a Comment

Popular posts from this blog

Update Rollup 3 for System Center 2012 R2 Service Manager

-
Update Rollup 3 for System Center 2012 R2 Service Manager   Issues that are fixed in this update rollup Service Manager The Microsoft Systems Center 2012 Operations Manager configuration item (CI) connector does not retrieve disk mount point information for the Service Manager database. When a service request is created from a request offering in the console and when every user prompt is of the Simple List prompt type, the console shows options from all simple lists in each user prompt. When you try to close a customized change request, you cannot close the change request, the task throws an error, and the close is not actioned. MPSync job failures that are logged to the event log do not contain enough information to allow for a quick diagnosis of the problem. All Service Manager workflows may stall when any invalid XML characters (control characters) are used in a work item property. Using the "Set Fi...
Read more