I've just stuffed as many NICs as are available into each team and left it run that way. Like I said, I haven't ever done objective analysis of the traffic. The server is hosting a Codebase accounting software, with connections from agricultural management, payroll, a/p, a/r, inventory, websales, point of sale, and admin/reports workstations. There will be numerous other servers for other applications also hosted on this HyperV cluster.Īs far as 20 connections seeming like a low number, I agree. So no, the server NIC's are not plugged into the TOR switch. The server (will be shortly) on a HyperV cluster on 3 Server 2012r2 servers, with a HyperV switch with 4 gigabit nic's in a team (4 NIC's on each server), and the NIC's on each server will be plugged into a different UBNT switches. Just wondered what is ideal, if there is an ideal. Other switches are Netgear GS748TP switches, and we have UBNT UniFi switches here in my office, waiting to be deployed to replace the Netgears.Īs far as technical ability, I'm comfortable with any of this. TOR switch is a FOS-3124, bought for its capacity, but mostly for its dual power supplies (so yes, it's redundant, with the two power supplies fed from separate UPS's on separate circuits, which are on separate feeds from the main and the emergency generator). Why put all that traffic through only 2 fiber ports? But since each switch has 48 gigabit ports, it seems strange to not include the 4 fiber ports in each LAG. We are replacing our switches in January, and I'd kinda like to have something objective to go on as far as how many gigabit ports to include in a LAG to the TOR switch, rather than simply using 4 ports because they are available. Also, VOIP, Ruckus wifi including guest wifi for our customers, surveillance video, file sharing with lots of high-res photos on this network.Ĭurious how others use LAG's when you have 48-port gigabit switches. Each workstation has its own dedicated gigabit network drop to one of the Netgear switches. We have 20 workstations connecting to the accounting server.
Software lag switch always on software#
Software lag switch always on windows#
Just curious if there is a common practice for how many ports to include in a LAG (in Netgear terms, a Link Aggregation Group, what Windows Server calls NIC Teaming).