Link to home
Start Free TrialLog in
Avatar of tcampbell_nc
tcampbell_nc

asked on

Proper Method to configure NIC Teaming to agregate bandwidth

Server OS - Windows 2012 R2 Standard
Switch - HP Procurve 1910-24G

I have read a lot of posts (most of them old) regarding this issue.  I am coming late to the game.  I presently have a Dell PE-T620 server running Windows 2012 R2 Standard.  It has two dual-port NICs.  One is the onboard Intel Gigabit 2P I350t.  The other is a Broadcom NetXtreme Gigabit Ethernet dual port.  I have all 4 NICs bound in a Single NIC Team and have performed no configuration on the switch.

I am reading older posts that say it is absolutely a bad idea to have different manufacturer's NICs in the same team.  I have also read where no switch configuration is needed, and also where the LACP should be configured on the switch.  There seems to be so many different directions and opinions.

This particular server has been running solid with this configuration for almost 2 years.  The only reason I am exploring this is that users are starting to see some performance issues.  The server runs a document management system (Worldox) for a law firm.  When a user selects a document to open, there is a 4-8 second delay before the document is retrieved.  I am beginning to wonder if this is due to a bad NIC teaming configuration on the server.

Thanks in advance for your advice.
ASKER CERTIFIED SOLUTION
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tcampbell_nc
tcampbell_nc

ASKER

Very well said.  There are so many paths to NIC Teaming as the technology evolved, that googling for information can leave a person confused.  I am using the Microsoft NIC Teaming (not a third party).  The HP switch does support LACP, but I do not have it configured.  I have observed good traffic flow on each of the team member NICs with no errors on any.  I suspect that we are overloading the DB manager (not SQL - Worldox uses CTree).  But before I started down that rabbit hole, I wanted to be sure that there was nothing else I needed to do for the NIC Teaming.  Thanks