Owner's Manual

Deployment Guide 13
Configuring the Public and Private Networks
This section presents steps to configure the public and private cluster networks.
NOTE: Each node requires a unique public and private IP address and an additional public IP address to serve
as the virtual IP address for the client connections and connection failover. The virtual IP address must belong
to the same subnet as the public IP. All public IP addresses, including the virtual IP address, should be registered
with DNS.
Depending on the number of NIC ports available, configure the interfaces as shown in Table 1-5.
NOTE: The Oracle installer requires that the public interface name and the bond name for the private interface be
the same on all the cluster nodes. If the public interfaces are different, a workaround is to use bonding to abstract
the network interfaces and use this for Oracle installation.
Configuring the Public Network
If you have not already configured your public network, configure it by performing the following steps
on each node:
1
Log in as root .
2 Edit the network device file /etc/sysconfig/network-scripts/ifcfg-eth# , where # is the number
of the network device, and configure the file as follows:
DEVICE=eth0
ONBOOT=yes
IPADDR=<Public IP Address>
NETMASK=<Subnet mask>
BOOTPROTO=static
HWADDR=<MAC Address>
SLAVE=no
3
Edit the /etc/sysconfig/network file, and, if necessary, replace localhost.localdomain
with the fully qualified public node name.
For example, the line for node 1 would be as follows:
HOSTNAME=node1.domain.com
Table 1-5. NIC Port Assignments
NIC Port Three Ports Available Four Ports available
1 Public IP and virtual IP Public IP
2 Private IP (bonded) Private IP (bonded)
3 Private IP (bonded) Private IP (bonded)
4 NA Virtual IP