NIC Teaming

NIC Teaming

by Reynard Cobham -
Number of replies: 3

I'm wondering how much benefit teaming up two NICs on a server would help a Moodle install.  Anyone out there done this? smile

Also...I'm struggling to find any real info on setting this up, but since most servers now ship with multiple cards, it must be good thing, right?  The redundancy alone would be worth the effort IMHO...

Any info / links would be much appreciated :D

Rey

Average of ratings: -
In reply to Reynard Cobham

Re: NIC Teaming

by Jordan Zebor -
Make sure your switch supports LACP (802.3ad). If not then, I don't think Link Aggregation is possible. If you will be setting this up on a cisco switch you need to make sure to use the LACP, cisco's PAgP only works when interlinking cisco devices.

http://en.wikipedia.org/wiki/Link_aggregation

http://www.cisco.com/warp/public/473/126.html

In reply to Jordan Zebor

Re: NIC Teaming

by Reynard Cobham -

TY for this info, we arent using Cisco gear, but do have HP Procurve switches, I shall investigate, although from what I read this was more client end than at the switch lvl, but I know nothing on the matter, time for a readup, cheers for the links!

Rey

In reply to Reynard Cobham

Re: NIC Teaming

by Martín Langhoff -
On a single server -- unlikely to help.

Once you have the DB server separate from the webserver -- load balanced clusters, for example -- it may help, though marginally. Bonded NICs will give you more throughput (bandwidth) between webserver and DB server, where what you _really_ need is better (lower) latency.

To get better latency what I'd perhaps do is link the DB server to the webserver over a dedicated direct connection. I mean - no switch, crossover cable. Simple is fastest smile

By the same token, if bonded NICs mean higher latency (and they very likely will) they will hurt performance. I'd tune/time/benchmark the hell out of it until I'm sure the latency is as low as possible.