aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/networking/bonding.txt
diff options
context:
space:
mode:
authorAlexandra N. Kossovsky <Alexandra.Kossovsky@oktetlabs.ru>2007-04-26 04:40:13 -0400
committerDavid S. Miller <davem@davemloft.net>2007-04-26 04:40:13 -0400
commit9198d2220d29b87ac3a05a3b791c50bb8a014d63 (patch)
tree72202a496f77e4143ce68ad16d7d6004c2172d5a /Documentation/networking/bonding.txt
parent4ef8d0aeafda8388dd51f2671b7059192b1e5a5f (diff)
[NET]: bonding documentation fix for multiple bonding interfaces
Fix bonding driver documentation for the case of multiple bonding interfaces. Signed-off-by: "Alexandra N. Kossovsky" <Alexandra.Kossovsky@oktetlabs.ru> Acked-by: Jay Vosburgh <fubar@us.ibm.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/networking/bonding.txt')
-rw-r--r--Documentation/networking/bonding.txt35
1 files changed, 2 insertions, 33 deletions
diff --git a/Documentation/networking/bonding.txt b/Documentation/networking/bonding.txt
index de809e58092f..1da566630831 100644
--- a/Documentation/networking/bonding.txt
+++ b/Documentation/networking/bonding.txt
@@ -920,40 +920,9 @@ options, you may wish to use the "max_bonds" module parameter,
920documented above. 920documented above.
921 921
922 To create multiple bonding devices with differing options, it 922 To create multiple bonding devices with differing options, it
923is necessary to load the bonding driver multiple times. Note that 923is necessary to use bonding parameters exported by sysfs, documented
924current versions of the sysconfig network initialization scripts 924in the section below.
925handle this automatically; if your distro uses these scripts, no
926special action is needed. See the section Configuring Bonding
927Devices, above, if you're not sure about your network initialization
928scripts.
929
930 To load multiple instances of the module, it is necessary to
931specify a different name for each instance (the module loading system
932requires that every loaded module, even multiple instances of the same
933module, have a unique name). This is accomplished by supplying
934multiple sets of bonding options in /etc/modprobe.conf, for example:
935
936alias bond0 bonding
937options bond0 -o bond0 mode=balance-rr miimon=100
938
939alias bond1 bonding
940options bond1 -o bond1 mode=balance-alb miimon=50
941
942 will load the bonding module two times. The first instance is
943named "bond0" and creates the bond0 device in balance-rr mode with an
944miimon of 100. The second instance is named "bond1" and creates the
945bond1 device in balance-alb mode with an miimon of 50.
946
947 In some circumstances (typically with older distributions),
948the above does not work, and the second bonding instance never sees
949its options. In that case, the second options line can be substituted
950as follows:
951
952install bond1 /sbin/modprobe --ignore-install bonding -o bond1 \
953 mode=balance-alb miimon=50
954 925
955 This may be repeated any number of times, specifying a new and
956unique name in place of bond1 for each subsequent instance.
957 926
9583.4 Configuring Bonding Manually via Sysfs 9273.4 Configuring Bonding Manually via Sysfs
959------------------------------------------ 928------------------------------------------