Cluster Node Information

If you do not use Grid Naming Service, then you must provide the public and virtual host name for each node you intend to make a member of the cluster. In addition, you must have SSH configured on all nodes for the installation owner user on all nodes that you plan to have as a cluster member. To check the SSH configuration, or to configure SSH if it is not set up, click SSH.

Provide fully qualified domain name public and virtual host names for the cluster. For example:

node1.example.com node1-vip.example.com
node2.example.com node2-vip.example.com

Click Add, Edit or Remove to add to or modify a list of nodes for configuration, or click Use Cluster Configuration File to provide the path to a configuration file with node information that you have prepared.


Note:

If you have another vendor's clusterware installed, then you cannot use a cluster configuration file.

The cluster configuration file should have the following syntax, where node is the name of the public hostname for a node in the cluster, and vip is the name of a virtual IP address for that node:

node vip
node vip

For example, with nodes node1 and node2, and VIP hostnames node1-vip and node2, the cluster configuration file contains the following entries:

node1 node1-vip
node2 node2-vip

When you have completed configuration tasks on this screen, click Next.

Review the following for additional information:

Public Hostname

Provide the public hostnames of the servers that you want to have configured as cluster members. For example:

node1.example.com
node2.example.com

Virtual Hostname

A virtual hostname is the hostname associated with a virtual IP address. If you choose to configure virtual IP addresses manually instead of enabling automatic configuration, then provide the virtual hostname of the cluster members. For example:

node1-vip.example.com
node2-vip.example.com

Provide a virtual IP (VIP) 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:

Before installation, confirm 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 the SCAN for the cluster.

SSH Connectivity

Click the SSH Connectivity button to configure SSH.

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 completed the required task of setting up identical groups, users and passwords on all nodes for the installation owner account, then the Installer can configure passwordless SSH access.

The installation owner (the user account running the installation) is listed by default as the Operating System Username. Provide the password for that user in the Operating System Password field. You can also set up SSH for other user accounts if they are configured identically on all prospective cluster members.

Click Test if you think SSH connectivity has been set up, so that you can confirm that it is operating.

Click Setup to start the SSH configuration process.

If you are using a shared location as the home for the installation owner account, then click User home is shared by the selected nodes.

If you have existing SSH keys set up in the installation owner account, and you want to enable the existing SSH keys by reloading them into memory, instead of generating new keys, then click Reuse private and public keys existing in the user home.

If you have locked operating system accounts, then you must create the SSH configuration manually. Refer to operating system documentation, or to the Oracle software installation guide for manual SSH configuration instructions.