Provide information to configure the cluster. The following configuration steps are completed on this screen:
Provide the name of your cluster. This name is used as the single client access name (SCAN).
The SCAN is a hostname used to provide service access for clients to the cluster. Because the SCAN is associated with the cluster as a whole, rather than to a particular node, the SCAN makes it possible to add or remove nodes from the cluster without needing to reconfigure clients. It also adds location independence for the databases, so that client configuration does not have to depend on which nodes are running a particular database. Clients can continue to access the cluster in the same way as with previous releases, but Oracle recommends that clients accessing the cluster use the SCAN.
By default, the cluster name is identified with the hostname of the server on which you are installing (the "local node"), removing digits in the hostname. For example, if the server hostname is test1, then the default cluster name is test-cluster.
Provide the public hostnames of the servers that you want to have configured as cluster members. For example:
node1.example.com node2.example.com
Use the Add, Edit and Remove buttons to enter cluster member hostnames for configuration.
The public IP address is defined in a DNS or in a hosts file. It uses the public interface (the interface with access available to clients).
The virtual IP hostnames are automatically assigned, based on the public hostnames. For example, with the hostnames node1.example.com and node2.example.com, the VIP names by default are node1-vip.example.com and node2-vip. You should have them configured in a DNS or in a hosts file in the form hostname-vip. However, they should not be in use (they should not be pingable) before installation.
Click the SSH Connectivity button to configure SSH.
The installation requires SSH connectivity to be configured between nodes in the cluster, so that the Installer can open secure remote shell sessions as the installation owner account on each cluster member.
If you have set up identical groups, users and passwords on all nodes for the installation owner account, then the Installer can configure passwordless SSH access automatically.
If you have locked operating system accounts, then you must create the SSH configuration manually. Refer to operating system documentation, or to the installation guide for your product for manual SSH configuration instructions.
Click the Use Cluster Configuration File button to select a cluster configuration file that you have created to provide the node addresses for the cluster. You can find instructions for how to create a cluster configuration file in the Oracle Grid Infrastructure Installation Guide document for your platform.
In the table, review the list of network interfaces (NICs) that OUI found on the nodes. Accept the defaults, or click the interface type list and select which NICs to use for public and private interconnects. If you have more than two NICs, then indicate which NICs Oracle Clusterware should not use. For example, you may have additional NICs for network storage or other purposes that you do not want Oracle Clusterware to use.