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

Cisco Bandwidth Aggregation

I am having an issue getting bandwidth aggregation to work properly between a Windows Server 2008, Cisco SG500-52, and Windows Server 2012 R2.

On the 2008 server I have two 1Gb ports configured with BACS4 with a Team Type of 802.3 ad.  For these two ports the switch has them configured as trunk ports.  The ports are also in one LAG, LACP is Enabled, the link is up, and it has these two ports as active members.

On the 2012 R2 server I have two 1Gb ports configured through Windows NIC Teaming.  The Teaming mode is LACP and the load balancing mode is Dynamic.  The status says that it is Online and it shows both ports as being Active.  For these two ports the switch has them configured as trunk ports.  The ports are also in one LAG, LACP is Enabled, the link is up, and it has these two ports as active members.

This configuration still limits my bandwidth to 1Gb.  On both servers I have used Performance Monitor and looked at each individual NIC for Bytes Total/sec and it looks like it is still only using one NIC.

What am I missing?

Thanks.
0
ollybuba
Asked:
ollybuba
  • 3
  • 2
2 Solutions
 
rgormanCommented:
I am not 100% sure but I think with teaming on the NIC's it will only use a single interface for a single session to another host.  If there were another server in the mix then you would see a transmit on each NIC, one to each of the servers receiving.  The reverse of that is true too.

I could be wrong though...
0
 
Axis52401Security AnalystCommented:
I have this setup in my environment and my TEAM status shows 2Gpbs so it is possible. However on the windows side of things I have my type set as SLA, Static Link Aggregation. I feel that you may be missing that. It still provides fault tolerance in case one link goes down but check your settings on the windows side first.

Right click the team --> properties --> configure --> settings --> modify team --> type --> set to SLA

Thats what I had to do anyway. I know that there are different options available but if you want 2Gpbs of throughput that should work for you.
0
 
Axis52401Security AnalystCommented:
*meant to say, 'windows side of things I have my team set to as SLA'
0
Live Q & A: Securing Your Wi-Fi for Summer Travel

Traveling this summer? Join us on June 18, 2018 for a live stream to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
ollybubaAuthor Commented:
If I change my teaming mode to static teaming vs LACP do o need to enable LACP on the switch? How about configuring an LAG?
0
 
Axis52401Security AnalystCommented:
At one time I had an slm2014 which is similar to the switch you are using and at that time I had configured a LAG for the SLA. So I can't speak directly to whether or not use LACP or LAG on the switch side but I am confident a LAG will work for you on the switch side with SLA on the server side.
0
 
ollybubaAuthor Commented:
What I have found is that when you have LACP as the teaming mode in Windows Server 2012 R2, you also have to have LACP enabled on the LAG with Cisco.  Makes sense.  When you use the static teaming mode, you still have to setup a LAG but you don't enable LACP.  You also can use NIC teaming between two servers.  The catch with NIC teaming is that each interface acts in what I would consider half-duplex mode.  At least with two interfaces, one port sends and one receives.  Having traffic moving in both directions is the only way to achieve full bandwidth utilization of the team from what I've seen.  I'm guessing that changes when you start adding even more interfaces.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

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