Owner's Manual

Configuring Storage, Oracle User Equivalence, and Networking for Oracle RAC 47
Configuring the Private Network Using Bonding
Before you deploy the cluster, configure the private cluster network to allow
the nodes to communicate with each other. This involves configuring network
bonding and assigning a private IP address and hostname to each node in
the cluster.
To set up network bonding for Broadcom
®
or Intel
®
NICs, and to configure the
private network, perform the following steps on
each node :
1 Log in as root .
2 Add the following line to the /etc/modprobe.conf file:
alias bond0 bonding
3
For high availability, edit the /etc/modprobe.conf file and set the option
for
link monitoring .
The default value for
miimon is 0. The default value disables link
monitoring. Change the value to 100 milliseconds initially. Adjust it as
needed to improve performance. For example, type:
options bonding miimon=100 mode=6 max_bonds=2
4
In the /etc/sysconfig/network-scripts/ directory, create or edit the
ifcfg-bond0 configuration file.
For example, using sample network parameters, the file appears as:
DEVICE=bond0
IPADDR=192.168.0.1
NETMASK=255.255.255.0
NETWORK=192.168.0.0
BROADCAST=192.168.0.255
ONBOOT=yes
BOOTPROTO=none
USERCTL=no
The entries for NETMASK, NETWORK, and BROADCAST are optional.
DEVICE=
bondn is the required name for the bond, where n specifies the
bond number. IPADDR is the private IP address.
To use
bond0 as a virtual device, you must specify the devices that are
bonded as slaves.