bdameron_at_tscnet.net
Date: Fri May 28 2004 - 19:54:56 CEST
X-Message-Number-for-archive: 191644 Message-ID: <1085766896.40b77cf03b308@mail.tscnet.net> Date: Fri, 28 May 2004 10:54:56 -0700 Subject: [SLE] Ethernet Bonding HOW-TO!!
Well since I have not found any info regarding Ethernet bonding under SuSe 9.x
here is a quick little HOW-TO. This was done on SuSe 9.1 but should be the same
on 9.0.
SuSe has taken the efford to try to make this task much easier. But with little
to no documentation they made it much more difficult.
No more needing to load the bonding driver in the modprobe.conf. I am sure there
are some easier ways to do certain things I will list but this is how I got it
to work.
Just do the following:
First run Yast2 and configure your ethernet devices as DHCP so they create the
nice ifcfg-eth-id-<mac> files. The reason I used Yast is because it then creates
some UNIQUE id and sets the _nm_name which we are still working on what is used for.
Next modify each of your ifcfg-eth-id-<mac> files that you want to bond, they
are located in /etc/sysconfig/network, and change them from:
BOOTPROTO='dhcp'
MTU=''
REMOTE_IPADDR=''
STARTMODE='onboot'
UNIQUE='gZD2.ZqnB7JKTdX0'
_nm_name='bus-pci-0000:00:0b.0'
to:
BOOTPROTO='none'
STARTMODE='off'
UNIQUE='gZD2.ZqnB7JKTdX0'
_nm_name='bus-pci-0000:00:0b.0'
Be sure to leave the UNIQUE and the _nm_name alone. You can also leave in the
MTU and REMOTE_IPADDR as long as they are not set.
Next in /etc/sysconfig/network edit your ifcfg-bond0 file so it looks like the
following:
BOOTPROTO='static'
BROADCAST='172.16.0.255'
IPADDR='172.16.0.1'
MTU=''
NETMASK='255.255.255.0'
NETWORK='172.16.0.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='miimon=100'
BONDING_SLAVE0='eth1'
BONDING_SLAVE1='eth2'
Adjust the IP, BROADCAST, NETMASK, NETWORK accordingly for your configuration.
The new config options as you can see are BONDING_MASTER, BONDING-MODULE_OPTS,
BONDING_SLAVE. The BONDING_MODULE_OPTS is the additional options you want to
pass to the bonding module. You can not pass "max_bonds" as an option. This is
not needed as the ifup script will load the module for each bond needed.
Next is the BONDING_SLAVE. This tells ifup which ethernet devices to enslave to
bond0. So if you wanted to bond 4 ethernet devices you would add:
BONDING_SLAVE2='eth3'
BONDING_SLAVE3='eth4'
This can be a mix-match as well. As you notice I did not use eth0 in my bonding
as it is connected to a LAN and I am using eth1 and eth2 with cross-over cables
to connect to another machine. No need for an expensive gige switch.
If you want multiple bond's just create the individual ifcfg-bond files with
their specific info. Example being ifcfg-bond0, ifcfg-bond1, ifcfg-bond2. The
new ifup script searchs and loads everything needed from within the ifcfg-bond
file.
Enjoy,
Brad Dameron
SeaTab Software
www.seatab.com
-- -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
This archive was generated by hypermail 2.1.7 : Fri May 28 2004 - 19:55:24 CEST