In the Cluster Name field, provide a cluster name. The default value for cluster name is based on the node name. If you change this name, note that the cluster name that you use must be globally unique throughout your enterprise. Cluster names must be at least one character long, and can be up to 15 characters in length. Example: myclstr
The OUI displays only the local node information. Click Add, and provide the following information for the other nodes in the cluster:
An IP address with an associated host name (or network name) registered in the DNS for the public interface. If you do not have an available DNS, then the host name and IP address should be recorded in the system hosts file, /etc/hosts.
One virtual IP (VIP) address with an associated host name registered in a DNS. If you do not have an available DNS, then the host name and VIP address should be recorded in 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 not reachable outside of the cluster member nodes.
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.
For example, with a two node cluster where each node has one public and one private interface, you might have the configuration shown in the following table for your network interfaces, where the hosts file is /etc/hosts:
| Node | Host Name | Type | IP Address | Registered In |
|---|---|---|---|---|
| rac1 | rac1 | Public | 143.46.43.100 | DNS (if available, else the hosts file) |
| rac1 | rac1-vip | Virtual | 143.46.43.104 | DNS (if available, else the hosts file) |
| rac1 | rac1-priv | Private | 10.0.0.1 | Hosts file |
| rac2 | rac2 | Public | 143.46.43.101 | DNS (if available, else the hosts file) |
| rac2 | rac2-vip | Virtual | 143.46.43.105 | DNS (if available, else the hosts file) |
| rac2 | rac2-priv | Private | 10.0.0.2 | Hosts file |
To enable VIP failover, the configuration shown in the preceding table defines the public and VIP addresses of both nodes on the same subnet, 143.46.43. When a node or interconnect fails, then the associated VIP is relocated to the surviving node, enabling fast notification of the failure to the clients connecting through that VIP. If the application and client are configured with transparent application failover options, then the client is reconnected to the surviving node.
You can install Oracle Clusterware using a cluster configuration file. If you use a cluster configuration file, then review the instructions in the cluster configuration template to ensure that you provide all required information for Oracle Clusterware configuration. You can find the cluster configuration template at the root directory of the Oracle Clusterware installation media. Click Use Cluster Configuration File, and provide the path to the completed cluster configuration file.
If you need to remove a node from an existing cluster, then select the node, and click Remove.