Managing HP Serviceguard for Linux, Sixth Edition, August 2006

Building an HA Cluster Configuration
Implementing Channel Bonding (SLES9 and SLES10)
Chapter 5 145
MTU=''
NETMASK='255.255.255.0'
NETWORK='172.16.0.0'
REMOTE_IPADDR=''
STARTMODE='onboot'
BONDING_MASTER='yes'
BONDING_MODULE_OPTS='miimon=100 mode=1'
BONDING_SLAVE0='eth0'
BONDING_SLAVE1='eth1'
The above example configures bond0 with mii monitor equal to 100 and
mode active-backup. 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 four ethernet devices you
would add:
BONDING_SLAVE2='eth2'
BONDING_SLAVE3='eth3'
NOTE Use ifconfig to find the relationship of eth IDs and the MAC address.
For more networking information on bonding, see
/usr/src/linux< kernel_version >/Documentation/networking/bonding.
txt
Restarting Networking
Restart the networking subsystem. From the console of either node in the
cluster, execute the following command on a SUSE system:
# /etc/init.d/network restart