Managing HP Serviceguard for Linux Ninth Edition, April 2009

BONDING_SLAVE0='eth0'
BONDING_SLAVE1='eth1'
The above example configures bond0 with mii monitor equal to 100 and
active-backup mode. Adjust the IP, BROADCAST, NETMASK, and NETWORK
parameters to correspond to your configuration.
As you can see, you are adding the configuration options BONDING_MASTER,
BONDING-MODULE_OPTS, and BONDING_SLAVE. BONDING-MODULE_OPTS are
the additional options you want to pass to the bonding module. You cannot pass
max_bonds as an option, and you do not need to because the ifup script will load
the module for each bond needed.
BONDING_SLAVE 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 between eth IDs and the MAC
addresses.
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 any node in the cluster, execute
the following command on a SUSE system:
/etc/init.d/network restart
NOTE: It is better not to restart the network from outside the cluster subnet, as there
is a chance the network could go down before the command can complete.
If there is an error in any of the bonding configuration files, the network may not
function properly. If this occurs, check each configuration file for errors, then try to
start the network again.
Setting up a Lock LUN
The lock LUN requires a partition of one cylinder of at least 100K defined (via the
fdisk command) as type Linux (83). You will need the pathnames for the lock LUN
as it is seen on each cluster node. On one node, use the fdisk command to define a
partition of 1 cylinder, type 83, on this LUN. Here is an example:
Respond to the prompts as shown in the following table to set up the lock LUN partition:
fdisk <Lock LUN Device File>
Preparing Your Systems 157