Owner's Manual

16 Deployment Guide
Configuring the Public Network
NOTE: Ensure that your public IP address is a valid, routable IP address.
If you have not already configured the public network, do so 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
4
Ty p e :
service network restart
5
Ty p e ifconfig to verify that the IP addresses are set correctly.
6 To check your network configuration, ping each public IP address from a client on the LAN outside
the cluster.
7 Connect to each node to verify that the public network is functioning and type ssh <public IP>
to verify that the secure shell ( ssh) command is working.
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 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