Originally posted by: Blazer7
I was under the impression that this thread had run its course. AFAICR it was never the point of this thread to promote teaming and I can't remember anyone here trying to do so. The point of this thread was to make clear of what teaming requires in order to function and that has already been done.
There are a couple of common misconceptions about link aggregation that cause people to have unrealistic expectations of resultant performance.
Originally posted by: Madwand1
No, this thread has made clear claims about performance benefits given specific configurations, and these claims are false, and based on misunderstandings.
Originally posted by: TheBeagle
Good Morning Mr. MadWand1 & Everyone.
Mr. MadWand1: The object of my lengthy endeavor was to get the Teaming function to become operational.
Originally posted by: TheBeagle
Good Morning Mr. MadAd & Everyone.
In reality, I was just damn glad to find out HOW to get Teaming to function, let alone start some additional comparative testing routine.
Originally posted by: Madwand1
Besides, if there are no implied or hoped for performance benefits in this setup, then why bother? Why be interested in teaming? Why spend money on managed switches? Why tell people this is what you need to do if you want this work? For what end? For no good reason, just because you can and have money to spend, or because you think it will give you a performance benefit?
Originally posted by: Blazer7
the topic is not just about networking but also about the mobo manufacturers policy on not disclosing all info related to this feature to their customers.
Shedding some light on this may turn out to be quite beneficial for some ppl here in Motherboards. Understanding how a specific feature works along with its requirements and overall functionality may change how ppl look at teaming and how this specific feature affects their final decision when purchasing a mobo.
Originally posted by: Blazer7
We are not talking about server hardware here so why would anyone need teaming ?
Teaming is not the only issue here. Another one is the fact that mobo makers do not provide their customers with all the needed info on this specific feature while they do advertise their products as being capable of teaming. Letting ppl know of what teaming requires, what it's real use is and what they can expect from it makes it much easier to evaluate the need of that feature.
Originally posted by: SolMiester
I think the best function of your teamed motherboard NIC's, will be fault-tolerance, especially if you have mapped drives back to the server.
Originally posted by: Blazer7
I believe that it was already mentioned that performance wise there is little to gain from teaming so I really do not understand your obsession with this.
Originally posted by: Madwand1
If you agree with my point, that there's typically nothing to be gained from teaming in home environments, that this is a fruitless expenditure of time and money, then we're done.
If however you like the OP posted advice about getting teaming to work and what additional acquisitions you'd need to make for that, then I think the question would be -- why bother if it doesn't provide any performance benefits in the end? Or if it does, then what are the benefits? How can these be seen / shown?
Originally posted by: Blazer7
Like the OP I too believe that people need to know of what teaming requires in order to function properly. Since teaming is advertised by mobo makers it is only fair that the public should learn of the cost, requirements and benefits of teaming in order to evaluate the need of that feature or not.
Originally posted by: Madwand1
As it happens though, much of the material in this thread is misleading and incorrect.
It isn't even true that you must use a switch with teaming support in order to team NICs, although this varies with different implementations, and using the standard technique with a managed switch is preferred for standardization.