• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3167
  • Last Modified:

Link Aggregation / NIC Teaming Setup on Windows Server 2012 R2

I'am a bit new on setting up on server NIC teaming so kind bare with me.

Our company have purchased HP DL380 server with multiple NIC card. We are going to install Windows server 2012 R2 on the server. Our network switch are Cisco 2960x and already setup for Link aggregation. We would like to setup NIC Link Aggregation or Teaming. Here is my question:

1) When we setup NIC Team/Link aggregation to logical combine two Network card, how many IP address(es) do we needed/assignedfrom our network department ? Only One or Three (i.e. Two for the NIC cards itself and One for the NIC teaming IP) ?

2) What utility is required for setting up the server for NIC teaming or Link aggregation for NICs resiliency ? Shall we use the HP utilities, the Windows server 2012 R2 come with utilities or others ?

Appreciate your expert advice in advance. Let me know if further information is needed.

Thanks & Regards
Patrick T.
1 Solution
Jan KlimaCommented:
1) You will only have to set up 1 IP address for the Team.

2) You can use windows setting in Server Manager to set up NIC Teaming
patricktamAuthor Commented:
Thanks a lot for the prompt reply which will help on our network design.
Check below article to explain and setup windows built-in NIC teaming
However you can use NIC manufacturer utilities as well for NIC teaming (HP \ Intel \ Dell - Broadcom)


If you want to just aggregate available network adapter bandwidth you can create Link Aggregation Control Protocol (LACP) team
If you wanted redundency in case of switch failure, you should use switch independent mode where both NICs each should point to seperate switch.

When you create team, your actual physical network adapater will be converted to switch and new virtual network adapter wil get created to which you need to assign IP and it can talk to your corporate network

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now