2

This may be a dumb question, but is there any benefit of using LAG on only one managed switch with 2 VLAN's? By default my switch, Netgear GS724T, assigns 8 LAG's to the default VLAN. I am using VLAN1 and a created VLAN20 that I am running a different subnet on each of these VLANs. Should I just disable the LAG's altogether? By the way all ports are untagged. Purpose here is to use one switch with two seperate subnets (192.168.1.x and 192.168.20.x).

3

Assuming you are talking about Link Aggregation Groups (please specify, because "LAG" can have many meanings), they only make sense when connecting two switches together, or two network ports on the same server, or in any other situation when you want to treat two physical links as a single logical one (this is known as "Etherchannel" in Cisco land).

This is useful for link aggregation, load balancing and failover; but it really doesn't make any sense if you only have one switch and you are only connecting single-NIC servers to it.

4
  • Yes, I was referring to Link Aggregation Groups. I figured with only one switch, there was no need for LAG. I will turn it off. Thanks – dcol Jul 2 '16 at 20:06
  • I was just thinking this over. If I use two NIC ports from the same server for the purpose of failover. How does this get setup on the server side? I cannot have two NICs with the same IP. – dcol Jul 2 '16 at 20:10
  • 1
    Think I figured this out. Use teaming on the Windows OS side. Easy since I am running Server 2012. Then my guess is I just setup the two ports on the switch on the same LAG. – dcol Jul 2 '16 at 20:16
  • Exactly. You can setup a link aggregation on the server, and a LAG on the switch. – Massimo Jul 3 '16 at 13:04

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.