Quantcast
Channel: High Availability (Clustering) forum
Viewing all articles
Browse latest Browse all 5654

NIC teaming seems to be confused about what NIC belongs to what team

$
0
0
I have a total of four physical servers, two of which are hypervisors and two of which are storageservers. All the servers are connected to the same switch and all servers run an up-to-date installation of Windows Server 2012 R2. The two hypervisors have two ethernet ports and both are teamed in Windows. 

The two storageservers have four ethernet ports, two of which are native and the other two belong to a PCI-NIC we added. The two native ones (the two on the motherboard) are teamed in Windows and connect to the switch. The two PCI-NIC's are connected to eachother directly with an "ad-hoc" connection (two very small cables between the four ethernet ports). The two ethernet ports on the PCI-NIC are also teamed on both storageservers.

When all the teaming is set up everything looks fine and displays active. Once we try to copy a file over the netwerk from hypervisor to hypervisor (thus using the switch) we only get a 1Gbp/s connection, this should be 2Gbp/s due to the two ethernet ports being teamed. When I try to copy a file over the ad-hoc connection between the two storageservers the copying does go by 2Gbp/s, but ever so gracefully Windows decides to use both teams on that server. So instead of using the dedicated ad-hoc team, it uses half of that connection and throws the other half over the team that is connected to the switch. I am amazed by this, because it just doesn't make any sense.

But, it gets even more strange. If I disable one of the ethernet ports of the team that is connected to the switch on the storageserver, and I then try to copy a file over the ad-hoc team.. it does use the full 2Gbp/s available.

I am completely lost.. what am I doing wrong? Am I missing something?



Viewing all articles
Browse latest Browse all 5654

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>