Re: Bonded gigabit cards
On Mon, Aug 11, 2003 at 01:49:57PM -0500, Michael Heldebrant wrote:
> Unfortunately my cluster is long gone but I had a theory to solve this
> problem. I was going to try the following:
>
> eth0 on 192.168.0.1
> eth1 on 192.168.1.1
> bond0 on 192.168.2.1
>
> Then I could set up routing for all cluster traffic over bond0 by ip
> address in the routing tables. This would also allow for dhcp and bootp
> dameons to listen and send only over eth0 (or 1) for non bonded machines
> and route through the non bonded interfaces for those machines. With a
> good DNS set up i.e. cluster1 = 192.168.2.1 and cluster1-eth0 =
> 192.168.0.1 it would be pretty transparent I would think.
>
> I've wanted to give it a shot but I don't have any hardware to test this
> theory at the moment.
You'd probably need to use the --dont-inherit option. From the
README.Debian file:
This version of ifenslave has been taken from a recent Linux kernel
tarball.
An extra option --dont-inherit/-X has been added to simulate the
behaviour of
my own version of ifenslave I once made, where the slaves continue to
work
independently.
Guus Sliepen <guus@sliepen.warande.net>, Tue, 21 May 2002 21:20:07
+0200
There's more info in the man page.
I don't have the opportunity to test this now, but maybe the next time
we have cluster downtime...
Eric
Reply to: