Oracle Database Oracle Clusterware Installation Guide for HP-UX

# chmod 400 .rhosts
Configuring SSH or RCP on All Cluster Nodes
2. For each Oracle installation owner account, open the .rhosts file in that user
account home directory (in this example, crs). Add lines similar to the following,
where node1 and node2 are member nodes in the cluster, and domain is the
domain name for the cluster:
node1 crs
node1.domain crs
node2 crs
node2.domain crs
If you create the .rhosts file, then ensure that permissions for the .rhost file
are set to 400. For example:
# chmod 400 .rhosts
3. Test the RCP configuration for root and for Oracle installation owner accounts.
For example:
[root@node1] # remsh node2 11
[root@node1] # remsh node1 11
[root@node2] # remsh node1 11
[root@node2} # remsh node2 11
[crs@node1] $ remsh node2 11
[crs@node1] $ remsh node1 11
[crs@node2] $ remsh node1 11
[crs@node2} $ remsh node2 11
2.10.2 Checking Existing SSH Configuration on the System
To determine if SSH is running, enter the following command:
$ ps -ef | grep sshd
If SSH is running, then the response to this command is one or more process ID
numbers. In the home directory of the software owner that you want to use for the
installation (crs, oracle), use the command ls -al to ensure that the .ssh
directory is owned and writable only by the user.
You need either an RSA or a DSA key for the SSH protocol. RSA is used with the SSH
1.5 protocol, while DSA is the default for the SSH 2.0 protocol. With OpenSSH, you can
use either RSA or DSA. The instructions that follow are for SSH1. If you have an SSH2
installation, and you cannot use SSH1, then refer to your SSH distribution
documentation to configure SSH1 compatibility or to configure SSH2 with DSA.
2.10.3 Configuring SSH on Cluster Member Nodes
To configure SSH, you must first create RSA or DSA keys on each cluster node, and
then copy all the keys generated on all cluster node members into an authorized keys
file that is identical on each node. Note that the SSH files must be readable only by
root and by the software installation user (oracle, crs, asm), as SSH ignores a
private key file if it is accessible by others. When this is done, then start the SSH agent
to load keys into memory. In the examples that follow, the RSA key is used.
Oracle Clusterware Preinstallation Tasks 2-21