Installation guide

Page 31 of 59

HOSTNAME=node1.domain.com

4. Type: service network restart

5. Type 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 ssh is working.

8. On each node, modify the /etc/hosts file by adding the following lines (where

FQN is the fully qualified hostname and shortname is the hostname without the

domain).

127.0.0.1 localhost.localdomain localhost

<IP applications node> <FQN applications node> <shortname applications

node>

<IP infrastructure node> <FQN infrastructure node> <shortname

infrastructure node>

9. On each node, modify the /etc/resolv.conf file by adding the following lines.

nameserver <Primary DNS server address>

nameserver <Secondary DNS server address>

domain <your domain name>

10. Issue the command:

route add default gw <Gateway address>

One of the motivations for installing the Enterprise OracleAS topology is to configure

high availability, with no single points of failure. By default, a server network cable from

a server to a switch represents a single point of failure. If the switch fails, the network

cable fails, or the NIC fails, network communication will cease and applications will

become unavailable. To avoid these failure scenarios, a common practice is to

implement network bonding. Network bonding utilizes at least two network ports per

server, which are bonded together as a single logical port. The ports are connected to two

different switches, which are connected together (or “trunked”). This provides

redundancy and (optional) load balancing. If a cable is disconnected, the network bond

will fail over to the other port, and service will continue.

The following steps illustrate how to setup network bonding:

1. Log in as root.

2. Add the following line to the /etc/modprobe.conf file (or /etc/modules.conf file

for Red Hat 3.0):

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, which disables link monitoring.

Change the value to 100 milliseconds initially, and adjust it as needed to improve

performance. Type:

options bonding miimon=100 mode=1

4. In the /etc/sysconfig/network-scripts/ directory, create or edit the ifcfg-bond0

configuration file. For example, using sample network parameters, the file would

appear as follows:

DEVICE=bond0