"assume makes an ass out of u and me"
Joao Carneiro - DLS wrote:
Ups, seems like I'm sleeping or something... I recall a quote
"assumption is the mother of all fuckups"
cheers
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Klaus-Peter Niedermann
Sent: quarta-feira, 15 de Junho de 2005 13:15
To: [email protected]
Subject: Re: [Ltsp-discuss] LTSP and bonding
Joao Carneiro - DLS schrieb:
I mantain my previous statement.
I too.
I said in the first email:
"our LTSP (with LTSP Version 4.1.1) clients have two ethernet cards
each."
...
"For High-Availability reasons, we want to use bonding with this clients
now."
...
"Who has experience with LTSP and bonding on client side and can give us
some
hints?"
I said in my second email:
"No, i need bonding on the (thin) client side for redundancy reasons."
What i said third email, you can see below.
And again:
Your CLIENTS have two NICs each. We need bonding on the client side for
increased network availability.
You do not need any ltsp kernel with bonding support. Only the
SERVER(the machine that serves clients) kernel must provide bonding
support.
So your question is not about ltsp but about configuring bonding on a
`standard`(if there is such a creature...) linux server.
For configuration look in
usr/src/linux/Documentation/networking/bonding.txt (if you have the
sources for the kernel on the default location) or get it at google.
Unless of coarse ... if you wish that the thin clients have multiple
bonding NIC's for increased network availability... I seriously doubt
it...
Believe me, i know it ;-)
>Shawn Austin wrote:
>
>> Channel bonding does not provide a redundant connection. What it
>> provides is twice the bandwidth by using one card for outbound
traffic,
>> and one for inbound traffic.
>>
>> Shawn
>
>And where did you get this information? The bonding module has four
different
>modes. This is taken from the kernel documentation file
"bonding.txt":
>
>
>
>mode
> Specifies one of four bonding policies. The default is
round-robin.
> Possible values are:
>
> 0 Round-robin policy: Transmit in a sequential order
from the
> first available slave through the last. This mode
provides
> load balancing and fault tolerance.
>
> 1 Active-backup policy: Only one slave in the bond is
active. A
> different slave becomes active if, and only if, the
active >slave
> fails. The bond's MAC address is externally visible
on only
> one port (network adapter) to avoid confusing the
switch.
> This mode provides fault tolerance.
Exactly, and that (mode 1) is what we need for the thin clients. Our
servers
already running with this mode.
So, have anyone experience with compiling the bonding module into the
LTSP kernel ?
Do i have to checkout LBE (the LTSP-4_1_0 tag) and change the kernel
config
(adding bonding) ? Is this the right way ?
Greetings
KP
Thanxs,
KP
--
David Morris
DMS AePONA (England) Ltd
E-mail: [EMAIL PROTECTED] Web: http://www.aepona.co.uk/
Phone: +44 (0)79 5174 0388
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.freenode.net
