lkml.org 
[lkml]   [2004]   [Nov]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subjectethernet channel bonding (bonding.o) on 2.6.x
Date
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I'm trying to migrate a couple of server from a 2.4 kernel to 2.6 (Mandrake
9.1 -> 10.0)
All servers have 4 nics (a mix of e1000 and bcm5700) arranged in two logical
interfaces.

Note: Mandrakes ifconfig/ifup scripts have the necessary logic to ifenslave
ethX interfaces to a bondX interface automatically (through options in the
ifcfg-ethX and ifcfg-bondX config files).

On 2.4 I used the following in /etc/modules.conf, which worked perfectly:

- --
alias bond0 bonding
alias bond1 bonding

options bond0 miimon=100 mode=1
options bond1 -o bonding1 miimon=100 mode=1
- --

When I come to use these settings with /etc/modprobe.conf, only bond0 comes
up. The system complains that there 'doesnt seem to be a device for bond1'
and doesn't bring it up.

Using 'generate-modprobe.conf' It thinks I should be using:

- --
alias bond0 bonding
alias bond1 bonding
options bond0 miimon=100 mode=1
options bond1 miimon=100
install bond1 /sbin/modprobe -o bonding1 --ignore-install bonding
- --

This doesn't work - I get the same error.

If I manually do:

# modprobe bonding -o bonding1
# ifconfig bond1 up

Then I can bring up bond1 by hand.

I'm guessing the 'install' line is supposed to load a second instance of the
bonding driver (which I didn't think I needed with 2.6's module loading
needed - I can load e1000 twice without doing anything special) but it isn't.


Does anyone have a system with more than one bonded interface that actually
works?

Cheers,

Mark.

- --
Mark Watts
Senior Systems Engineer
QinetiQ Trusted Information Management
Trusted Solutions and Services group
GPG Public Key ID: 455420ED

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBhgf0Bn4EFUVUIO0RAuAHAKCDS5DtJMzRJjJGnGXly6b0GjRL/wCg8h/A
PXmz2ltABkxPQWXfVY4XVBQ=
=Wsch
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:07    [W:0.033 / U:0.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site