On Tue, 22 Feb 2005 13:22:34 -0600, "L" <l_x2828@yahoo.com> wrote:
Quote:
"daytripper" <day_trippr@REMOVEyahoo.com> wrote in messagenews:jbvm111a20mrh160dgoc2dl8dvjcg0j4u8@4ax .com...
Quote:
On Tue, 22 Feb 2005 12:38:22 -0600, "L" <l_x2828@yahoo.com> wrote:
Quote:
> In my limited experience, both statements are true: the OS doesn't> manage> nic> teaming, fault tolerant or otherwise; and the nic vendors provide their> driver> management applet that enables teaming, etc, but only for their own> nics...I don't have much experience on line aggregation. It seems lineaggregationis specified in IEEE 802.3ad. Since this is a standard, all NIC vendorsshould follow it to implement line aggregation. If this is true, then weshould be able to use two differnet NICs from two different vendors tocreate line aggregation, right?
Ah - you're going to use logic to answer this? ;-)
I guess but I think NIC vendors really should follow IEEE802.3ad toimplement line aggregation. Otherwise, even we use two identical NICs onone server, we may still have problems. Think about another server has twoNICs from another vendor, and both servers are connected together by usinglink aggregation (using two crossover cable to connect to each other).
Quote:
My nic teaming experience is limited to Intel and they provide a nic manager that only works with their nics...
Is the "nic manager" you mentioned in Windows Control Panel? Do you knowwhich Intel NICs support line aggregation?
It's the Intel PROSet applet, sitting in the Control Panel (and the Icon Tray,
usually). The version we use covers pretty much every Intel 10/100/1000
plug-in or embedded host adapter...
"daytripper" <day_trippr@REMOVEyahoo.com> wrote in message
news:nf5n11lt8olgmnkr6pracq53b0vlenkl8j@4ax.com...
Quote:
On Tue, 22 Feb 2005 13:22:34 -0600, "L" <l_x2828@yahoo.com> wrote:
Quote:
"daytripper" <day_trippr@REMOVEyahoo.com> wrote in messagenews:jbvm111a20mrh160dgoc2dl8dvjcg0j4u8@4ax .com...
Quote:
On Tue, 22 Feb 2005 12:38:22 -0600, "L" <l_x2828@yahoo.com> wrote:>> In my limited experience, both statements are true: the OS doesn't>> manage>> nic>> teaming, fault tolerant or otherwise; and the nic vendors provide>> their>> driver>> management applet that enables teaming, etc, but only for their own>> nics...>>I don't have much experience on line aggregation. It seems line>aggregation>is specified in IEEE 802.3ad. Since this is a standard, all NIC vendors>should follow it to implement line aggregation. If this is true, then>we>should be able to use two differnet NICs from two different vendors to>create line aggregation, right? Ah - you're going to use logic to answer this? ;-)
I guess but I think NIC vendors really should follow IEEE802.3ad toimplement line aggregation. Otherwise, even we use two identical NICs onone server, we may still have problems. Think about another server hastwoNICs from another vendor, and both servers are connected together by usinglink aggregation (using two crossover cable to connect to each other).
Quote:
My nic teaming experience is limited to Intel and they provide a nic manager that only works with their nics...
Is the "nic manager" you mentioned in Windows Control Panel? Do you knowwhich Intel NICs support line aggregation?
It's the Intel PROSet applet, sitting in the Control Panel (and the Icon Tray, usually). The version we use covers pretty much every Intel 10/100/1000 plug-in or embedded host adapter...
The MyLounge.com forum is intended for informational use only and should not
be relied upon and is not a substitute for any advice. The information contained
on MyLounge.com are opinions and suggestions of members and is not a representation
of the opinions of MyLounge.com. MyLounge.com does not warrant or vouch for
the accuracy, completeness or usefulness of any postings or the qualifications
of any person responding. Please consult a expert or seek the services of an
attorney in your area for more accuracy on your specific situation. Please note
that our forums also serve as mirrors to Usenet newsgroups. Many posts you see
on our forums are made by newsgroup users who may not be members of MyLounge.com
Term of Service