Oracle Database Oracle Clusterware Installation Guide for HP-UX

Checking the Network Requirements
the system hosts file, /etc/hosts. Select an address for your VIP that meets the
following requirements:
– The IP address and host name are currently unused (it can be registered in a
DNS, but should not be accessible by a ping command)
– The VIP is on the same subnet as your public interface
■ A private IP address with a host name for each private interface
Oracle recommends that you use private network IP addresses for these interfaces
(for example: 10.*.*.* or 192.168.*.*). You can use DNS servers, or the /etc/hosts
file, or both to register the private IP address. Note that if you use DNS servers
alone, and the public network becomes unreachable due to NIC or cable failure,
then the private IP addresses can fail to resolve.
For the private interconnects, because of Cache Fusion and other traffic between
nodes, Oracle strongly recommends using a physically separate, private network.
You should ensure that the private IP addresses are reachable only by the cluster
member nodes.
During installation, you are asked to identify the planned use for each network
interface that OUI detects on your cluster node. You must identify each interface
as a public or private interface, and you must use the same private interfaces for
both Oracle Clusterware and Oracle RAC.
You can bond separate interfaces to a common interface to provide redundancy, in
case of a NIC failure, but Oracle recommends that you do not create separate
interfaces for Oracle Clusterware and Oracle RAC. If you use more than one NIC
for the private interconnect, then Oracle recommends that you use NIC bonding.
Note that multiple private interfaces provide load balancing but not failover,
unless bonded.
For example, if you intend to use the interfaces eth2 and eth3 as interconnects,
then before installation, you must configure eth2 and eth3 with the private
interconnect addresses. If the private interconnect addresses are 10.10.1.1 for eth2
and 10.10.2.1 for eth3, then bond eth2 and eth3 to an interface, such as bond0,
using a separate subnet such as 10.10.222.0. During installation, define the Oracle
Clusterware private node names on 10.10.222.0, and then define 10.10.222.0 (and
only that one) as a private interconnect. This ensures that Oracle Clusterware and
Oracle RAC are using the same network.
After installation, if you modify interconnects on Oracle RAC with the CLUSTER_
INTERCONNECTS initialization parameter, then you must change it to a private IP
address, on a subnet that is not used with a public IP address, nor marked as a
public subnet by oifcfg. Oracle does not support changing the interconnect to an
interface using a subnet that you have designated as a public subnet.
See Also: Oracle Clusterware Administration and Deployment Guide for
further information about setting up and using bonded multiple
interfaces
You should not use a firewall on the network with the private network IP
addresses, as this can block interconnect traffic.
Before installation, check that the default gateway can be accessed by a ping
command. To find the default gateway, use the route command, as described in your
operating system's help utility. After installation, configure clients to use either the VIP
address, or the host name associated with the VIP. If a node fails, then the node's
virtual IP address fails over to another node.
Oracle Clusterware Preinstallation Tasks 2-11