Help - Line Aggregation

[L]

Hi,

Could some one please tell me how to configure/setup line aggregation on
Windows platforms. Is line aggregation supported by Windows or by the NIC
drivers?

Suppose I install two one-port NICs on Windows 2003, how can I group these
two NICs together to use line aggregation?

Thanks,

T.
--

[Guest]

It would be supported by the NIC drivers. Such as HP, Dell, Etc.

[L]

<bryce.yates@gmail.com> wrote in message
news:1109093442.001574.169240@z14g2000cwz.googlegroups.com... It would be supported by the NIC drivers. Such as HP, Dell, Etc.

So Windows OS does not have any contribution to line aggregation?

Suppose we have two different NICs from two different vendors and they both
support line aggregation, can we install them on the same server to
use/create line aggregation? Or do we have to use both NICs from the same
vendor if we need line aggregation?

Thanks,

T.
--

[Guest]

That would be correct. You can also configure this at the switch level
with Cisco Switches. My experience has been to use 2 of the same nics
and use the software they provide for NIC teaming.

[L]

<bryce.yates@gmail.com> wrote in message
news:1109095537.907744.163100@z14g2000cwz.googlegroups.com... That would be correct.

Which one did you mean? OS doesn't have any contribution to line
aggregation, or I have to use the same NICs from the same vendor on a
server?
You can also configure this at the switch level with Cisco Switches. My experience has been to use 2 of the same nics and use the software they provide for NIC teaming.

[daytripper]

On Tue, 22 Feb 2005 12:22:53 -0600, "L" <l_x2828@yahoo.com> wrote:
<bryce.yates@gmail.com> wrote in messagenews:1109095537.907744.163100@z14g2000cwz.googlegroups.com... That would be correct.
You can also configure this at the switch level with Cisco Switches. My experience has been to use 2 of the same nics and use the software they provide for NIC teaming.Which one did you mean? OS doesn't have any contribution to lineaggregation, or I have to use the same NICs from the same vendor on aserver?

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...

/daytripper

[L]

> 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?

Thanks,


T.
--

[daytripper]

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 aggregationis 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? ;-)

My nic teaming experience is limited to Intel and they provide a nic manager
that only works with their nics...

/daytripper

[L]

"daytripper" <day_trippr@REMOVEyahoo.com> wrote in message
news:jbvm111a20mrh160dgoc2dl8dvjcg0j4u8@4ax.com... 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 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 to
implement line aggregation. Otherwise, even we use two identical NICs on
one server, we may still have problems. Think about another server has two
NICs from another vendor, and both servers are connected together by using
link aggregation (using two crossover cable to connect to each other).
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 know
which Intel NICs support line aggregation?

Thanks,

T.
--

[Bob Willard]

L wrote: "daytripper" <day_trippr@REMOVEyahoo.com> wrote in message news:jbvm111a20mrh160dgoc2dl8dvjcg0j4u8@4ax.com...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 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 to implement line aggregation. Otherwise, even we use two identical NICs on one server, we may still have problems. Think about another server has two NICs from another vendor, and both servers are connected together by using link aggregation (using two crossover cable to connect to each other).

Uh, in general, the intent of standards is not to force vendors to do
something, but to coerce vendors to do it in this standard way
*if they do it at all*.

Specifically, for line aggregation, I would not expect it to work on
a multiple-vendor lash-up until I'd reviewed the results of a few rounds
of plug-fests; even then, I'd carefully read the vendor's disclaimers
rather carefully.
--
Cheers, Bob

[daytripper]

On Tue, 22 Feb 2005 13:22:34 -0600, "L" <l_x2828@yahoo.com> wrote:
"daytripper" <day_trippr@REMOVEyahoo.com> wrote in messagenews:jbvm111a20mrh160dgoc2dl8dvjcg0j4u8@4ax.com... 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 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). 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

[L]

"daytripper" <day_trippr@REMOVEyahoo.com> wrote in message
news:nf5n11lt8olgmnkr6pracq53b0vlenkl8j@4ax.com... On Tue, 22 Feb 2005 13:22:34 -0600, "L" <l_x2828@yahoo.com> wrote:"daytripper" <day_trippr@REMOVEyahoo.com> wrote in messagenews:jbvm111a20mrh160dgoc2dl8dvjcg0j4u8@4ax.com... 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). 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...

Thanks for the info.

T.
--

[UdiviDruzei]

buy viagra (http://hometown.aol.com/tinakandelaki/viagra.html) buy cheap viagra (http://hometown.aol.com/tinakandelaki/viagra.html) buy cheapest viagra (http://hometown.aol.com/tinakandelaki/viagra.html) buy viagra online (http://hometown.aol.com/tinakandelaki/viagra.html) order viagra (http://hometown.aol.com/tinakandelaki/viagra.html) buy viagra alternative (http://hometown.aol.com/tinakandelaki/viagra.html) buy viagra internet (http://hometown.aol.com/tinakandelaki/viagra.html) buy generic viagra online (http://hometown.aol.com/tinakandelaki/viagra.html) buy viagra canada (http://hometown.aol.com/tinakandelaki/viagra.html) buy viagra online cheap (http://hometown.aol.com/tinakandelaki/viagra.html) cheapest place buy viagra online (http://hometown.aol.com/tinakandelaki/viagra.html) where to buy viagra online (http://hometown.aol.com/tinakandelaki/viagra.html) buy cheapest online viagra (http://hometown.aol.com/tinakandelaki/viagra.html) discount viagra online (http://hometown.aol.com/tinakandelaki/viagra.html) cheap oem discount software (http://cheap-oem-software.lavaeasy.info)