D How to Complete Installation Prerequisite Tasks Manually

D.1.2.1 Create SSH Directory, and Create SSH Keys On Each Node

Complete the following steps on each node:

1. Log in as the software owner (in this example, the grid user).

2. To ensure that you are logged in as grid, and to verify that the user ID matches the expected user ID you have assigned to the grid user, enter the commands id and id grid. Ensure that Oracle user group and user and the user terminal window process you are using have group and user IDs are identical. For example:

   $ id 
   uid=502(grid) gid=501(oinstall) groups=501(oinstall),502(grid,asmadmin,asmdba)
   $ id grid
   uid=502(grid) gid=501(oinstall) groups=501(oinstall),502(grid,asmadmin,asmdba)
   

3. If necessary, create the .ssh directory in the grid user's home directory, and set permissions on it to ensure that only the oracle user has read and write permissions:

   $ mkdir ~/.ssh
   $ chmod 700 ~/.ssh
   

   Note:

   SSH configuration will fail if the permissions are not set to 700.

4. Enter the following command:

   $ /usr/bin/ssh-keygen -t dsa
   

   At the prompts, accept the default location for the key file (press Enter).

   Note:

   SSH with passphrase is not supported for Oracle Clusterware 11g release 2 and later releases.

   This command writes the DSA public key to the ~/.ssh/id_dsa.pub file and the private key to the ~/.ssh/id_dsa file.

   Never distribute the private key to anyone not authorized to perform Oracle software installations.

5. Repeat steps 1 through 4 on each node that you intend to make a member of the cluster, using the DSA key.

D.1.2.2 Add All Keys to a Common authorized_keys File

Complete the following steps:

1. On the local node, change directories to the .ssh directory in the Oracle Grid Infrastructure owner's home directory (typically, either grid or oracle).

   Then, add the DSA key to the authorized_keys file using the following commands:

   $ cat id_dsa.pub >> authorized_keys
   $ ls
   

   In the .ssh directory, you should see the id_dsa.pub keys that you have created, and the file authorized_keys.

2. On the local node, use SCP (Secure Copy) or SFTP (Secure FTP) to copy the authorized_keys file to the oracle user .ssh directory on a remote node. The following example is with SCP, on a node called node2, with the Oracle Grid Infrastructure owner grid, where the grid user path is /home/grid:

   [grid@node1 .ssh]$ scp authorized_keys node2:/home/grid/.ssh/
   

   You are prompted to accept a DSA key. Enter Yes, and you see that the node you are copying to is added to the known_hosts file.

   When prompted, provide the password for the grid user, which should be the same on all nodes in the cluster. The authorized_keys file is copied to the remote node.

   Your output should be similar to the following, where xxx represents parts of a valid IP address:

   [grid@node1 .ssh]$ scp authorized_keys node2:/home/grid/.ssh/
   The authenticity of host 'node2 (xxx.xxx.173.152) can't be established.
   DSA key fingerprint is 7e:60:60:ae:40:40:d1:a6:f7:4e:zz:me:a7:48:ae:f6:7e.
   Are you sure you want to continue connecting (yes/no)? yes
   Warning: Permanently added 'node1,xxx.xxx.173.152' (dsa) to the list
   of known hosts
   grid@node2's password:
   authorized_keys       100%             828             7.5MB/s      00:00
   

3. Using SSH, log in to the node where you copied the authorized_keys file. Then change to the .ssh directory, and using the cat command, add the DSA keys for the second node to the authorized_keys file, clicking Enter when you are prompted for a password, so that passwordless SSH is set up:

   [grid@node1 .ssh]$ ssh node2
   [grid@node2 grid]$ cd .ssh
   [grid@node2 ssh]$ cat id_dsa.pub  >> authorized_keys
   

   Repeat steps 2 and 3 from each node to each other member node in the cluster.

   When you have added keys from each cluster node member to the authorized_keys file on the last node you want to have as a cluster node member, then use scp to copy the authorized_keys file with the keys from all nodes back to each cluster node member, overwriting the existing version on the other nodes.

   To confirm that you have all nodes in the authorized_keys file, enter the command more authorized_keys, and determine if there is a DSA key for each member node. The file lists the type of key (ssh-dsa), followed by the key, and then followed by the user and server. For example:

   ssh-dsa AAAABBBB . . . = grid@node1
   

   Note:

   The grid user's /.ssh/authorized_keys file on every node must contain the contents from all of the /.ssh/id_dsa.pub files that you generated on all cluster nodes.

D.2.2.1 Modifying Kernel Settings Using KCTUNE

Use /usr/sbin/kctune to view or change kernel parameters. For example, to view kernel parameters, enter kctune with the -d flag. For example:

# /usr/sbin/kctune -d

To modify a kernel parameter, enter kctune variable=value. For example:

# /usr/sbin/kctune aio_listio_max=512

Complete this procedure on all other cluster nodes.

D.2.2.2 Modifying Kernel Settings Using SMH

The following procedure describes how to modify kernel settings using HP System Management Homepage ( SMH):

1. Optionally, set the DISPLAY environment variable to specify the display of the local system:

   • Bourne, Bash, or Korn shell:

     # DISPLAY=local_host:0.0 ; export DISPLAY
     

   • C shell:

     # setenv DISPLAY local_host:0.0
     

2. Start SMH:

   # /usr/sbin/smh
   

3. Choose the Kernel Configuration area, then choose the Configurable Parameters area.

4. Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

   If necessary, refer to the SMH online Help for more information about completing this step.

   Note:

   If you modify the value of a parameter that is not dynamic, then you must restart the system.

5. If necessary, when the system restarts, log in and switch user to root.

6. Complete this procedure on all other cluster nodes.

D.2.2.3 Modifying Kernel Settings Using KCWEB

The following procedure shows how to

1. Enter the following command to start the kcweb application:

   # /usr/sbin/kcweb -F
   

2. Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.

   If necessary, refer to the kcweb online Help for more information about completing this step.

   Note:

   If you modify the value of a parameter that is not dynamic, then you must restart the system.

3. If necessary, when the system restarts, log in and switch user to root.

4. Complete this procedure on all other cluster nodes.