sshsetup on a 7 Node RAC

In my lab environments, I setup user equivalence even for the root user as I push files such as the udev rules for storage devices, resolv.conf and nsswitch.conf files to all the RAC nodes in an automated fashion.

Here’s what the ssh setup looks like on a 7 node RAC cluster. You will be prompted to type in the password twice for each node.

[root@rh64a sshsetup]# ./sshUserSetup.sh -user root -hosts "rh64a rh64b rh64c rh64d rh64e rh64f rh64g" -noPromptPassphrase -advanced -exverify
The output of this script is also logged into /tmp/sshUserSetup_2013-08-08-06-41-46.log
Hosts are rh64a rh64b rh64c rh64d rh64e rh64f rh64g
user is root
Platform:- Linux 
Checking if the remote hosts are reachable
PING rh64a (10.0.0.40) 56(84) bytes of data.
64 bytes from rh64a (10.0.0.40): icmp_seq=1 ttl=64 time=0.029 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=2 ttl=64 time=0.029 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=3 ttl=64 time=0.029 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=4 ttl=64 time=0.030 ms
64 bytes from rh64a (10.0.0.40): icmp_seq=5 ttl=64 time=0.026 ms

--- rh64a ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.026/0.028/0.030/0.006 ms
PING rh64b (10.0.0.41) 56(84) bytes of data.
64 bytes from rh64b (10.0.0.41): icmp_seq=1 ttl=64 time=0.122 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=2 ttl=64 time=0.172 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=3 ttl=64 time=0.188 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=4 ttl=64 time=0.175 ms
64 bytes from rh64b (10.0.0.41): icmp_seq=5 ttl=64 time=0.163 ms

--- rh64b ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3999ms
rtt min/avg/max/mdev = 0.122/0.164/0.188/0.022 ms
PING rh64c (10.0.0.42) 56(84) bytes of data.
64 bytes from rh64c (10.0.0.42): icmp_seq=1 ttl=64 time=0.815 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=2 ttl=64 time=0.169 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=3 ttl=64 time=0.184 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=4 ttl=64 time=0.161 ms
64 bytes from rh64c (10.0.0.42): icmp_seq=5 ttl=64 time=0.160 ms

--- rh64c ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.160/0.297/0.815/0.259 ms
PING rh64d (10.0.0.43) 56(84) bytes of data.
64 bytes from rh64d (10.0.0.43): icmp_seq=1 ttl=64 time=0.851 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=2 ttl=64 time=0.172 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=3 ttl=64 time=0.192 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=4 ttl=64 time=0.215 ms
64 bytes from rh64d (10.0.0.43): icmp_seq=5 ttl=64 time=0.170 ms

--- rh64d ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.170/0.320/0.851/0.265 ms
PING rh64e (10.0.0.44) 56(84) bytes of data.
64 bytes from rh64e (10.0.0.44): icmp_seq=1 ttl=64 time=0.543 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=2 ttl=64 time=0.170 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=3 ttl=64 time=0.129 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=4 ttl=64 time=0.154 ms
64 bytes from rh64e (10.0.0.44): icmp_seq=5 ttl=64 time=0.166 ms

--- rh64e ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.129/0.232/0.543/0.156 ms
PING rh64f (10.0.0.45) 56(84) bytes of data.
64 bytes from rh64f (10.0.0.45): icmp_seq=1 ttl=64 time=0.792 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=2 ttl=64 time=0.160 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=3 ttl=64 time=0.190 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=4 ttl=64 time=0.164 ms
64 bytes from rh64f (10.0.0.45): icmp_seq=5 ttl=64 time=0.173 ms

--- rh64f ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.160/0.295/0.792/0.249 ms
PING rh64g (10.0.0.46) 56(84) bytes of data.
64 bytes from rh64g (10.0.0.46): icmp_seq=1 ttl=64 time=0.841 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=2 ttl=64 time=0.144 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=3 ttl=64 time=0.171 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=4 ttl=64 time=0.162 ms
64 bytes from rh64g (10.0.0.46): icmp_seq=5 ttl=64 time=0.191 ms

--- rh64g ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 0.144/0.301/0.841/0.270 ms
Remote host reachability check succeeded.
The following hosts are reachable: rh64a rh64b rh64c rh64d rh64e rh64f rh64g.
The following hosts are not reachable: .
All hosts are reachable. Proceeding further...
firsthost rh64a
numhosts 7
The script will setup SSH connectivity from the host rh64a to all
the remote hosts. After the script is executed, the user can use SSH to run
commands on the remote hosts or copy files between this host rh64a
and the remote hosts without being prompted for passwords or confirmations.

NOTE 1:
As part of the setup procedure, this script will use ssh and scp to copy
files between the local host and the remote hosts. Since the script does not
store passwords, you may be prompted for the passwords during the execution of
the script whenever ssh or scp is invoked.

NOTE 2:
AS PER SSH REQUIREMENTS, THIS SCRIPT WILL SECURE THE USER HOME DIRECTORY
AND THE .ssh DIRECTORY BY REVOKING GROUP AND WORLD WRITE PRIVILEDGES TO THESE
directories.

Do you want to continue and let the script make the above mentioned changes (yes/no)?
yes

The user chose yes
User chose to skip passphrase related questions.
Creating .ssh directory on local host, if not present already
Creating authorized_keys file on local host
Changing permissions on authorized_keys to 644 on local host
Creating known_hosts file on local host
Changing permissions on known_hosts to 644 on local host
Creating config file on local host
If a config file exists already at /root/.ssh/config, it would be backed up to /root/.ssh/config.backup.
Removing old private/public keys on local host
Running SSH keygen on local host with empty passphrase
Generating public/private rsa key pair.
Your identification has been saved in /root/.ssh/id_rsa.
Your public key has been saved in /root/.ssh/id_rsa.pub.
The key fingerprint is:
f1:fb:5e:da:7e:04:5b:c1:27:5e:26:1c:4f:a0:e7:ed root@rh64a
The key's randomart image is:
+--[ RSA 1024]----+
|             .+o.|
|             .+=+|
|        .   ...=+|
|         o   oo..|
|        S .   .+.|
|           .  ...|
|          .   ..E|
|           . +  .|
|           .+.o. |
+-----------------+
Creating .ssh directory and setting permissions on remote host rh64a
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64a. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64a.
Warning: Permanently added 'rh64a,10.0.0.40' (RSA) to the list of known hosts.
root@rh64a's password: 
Done with creating .ssh directory and setting permissions on remote host rh64a.
Creating .ssh directory and setting permissions on remote host rh64b
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64b. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64b.
Warning: Permanently added 'rh64b,10.0.0.41' (RSA) to the list of known hosts.
root@rh64b's password: 
Done with creating .ssh directory and setting permissions on remote host rh64b.
Creating .ssh directory and setting permissions on remote host rh64c
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64c. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64c.
Warning: Permanently added 'rh64c,10.0.0.42' (RSA) to the list of known hosts.
root@rh64c's password: 
Done with creating .ssh directory and setting permissions on remote host rh64c.
Creating .ssh directory and setting permissions on remote host rh64d
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64d. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64d.
Warning: Permanently added 'rh64d,10.0.0.43' (RSA) to the list of known hosts.
root@rh64d's password: 
Done with creating .ssh directory and setting permissions on remote host rh64d.
Creating .ssh directory and setting permissions on remote host rh64e
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64e. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64e.
Warning: Permanently added 'rh64e,10.0.0.44' (RSA) to the list of known hosts.
root@rh64e's password: 
Done with creating .ssh directory and setting permissions on remote host rh64e.
Creating .ssh directory and setting permissions on remote host rh64f
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64f. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64f.
Warning: Permanently added 'rh64f,10.0.0.45' (RSA) to the list of known hosts.
root@rh64f's password: 
Done with creating .ssh directory and setting permissions on remote host rh64f.
Creating .ssh directory and setting permissions on remote host rh64g
THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR root. THIS IS AN SSH REQUIREMENT.
The script would create ~root/.ssh/config file on remote host rh64g. If a config file exists already at ~root/.ssh/config, it would be backed up to ~root/.ssh/config.backup.
The user may be prompted for a password here since the script would be running SSH on host rh64g.
Warning: Permanently added 'rh64g,10.0.0.46' (RSA) to the list of known hosts.
root@rh64g's password: 
Done with creating .ssh directory and setting permissions on remote host rh64g.
Copying local host public key to the remote host rh64a
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64a.
root@rh64a's password: 
Done copying local host public key to the remote host rh64a
Copying local host public key to the remote host rh64b
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64b.
root@rh64b's password: 
Done copying local host public key to the remote host rh64b
Copying local host public key to the remote host rh64c
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64c.
root@rh64c's password: 
Done copying local host public key to the remote host rh64c
Copying local host public key to the remote host rh64d
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64d.
root@rh64d's password: 
Done copying local host public key to the remote host rh64d
Copying local host public key to the remote host rh64e
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64e.
root@rh64e's password: 
Done copying local host public key to the remote host rh64e
Copying local host public key to the remote host rh64f
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64f.
root@rh64f's password: 
Done copying local host public key to the remote host rh64f
Copying local host public key to the remote host rh64g
The user may be prompted for a password or passphrase here since the script would be using SCP for host rh64g.
root@rh64g's password: 
Done copying local host public key to the remote host rh64g
Creating keys on remote host rh64a if they do not exist already. This is required to setup SSH on host rh64a.

Creating keys on remote host rh64b if they do not exist already. This is required to setup SSH on host rh64b.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
84:07:79:b1:07:35:cd:b0:44:d7:a0:bf:0d:2e:e1:af root@rh64b
The key's randomart image is:
+--[ RSA 1024]----+
|      ..o+*+oo   |
|      .o.+ =o .  |
|      ..+ +      |
|       o . .     |
|        S . o    |
|         . o +   |
|          o o .  |
|           o     |
|          E..    |
+-----------------+
Creating keys on remote host rh64c if they do not exist already. This is required to setup SSH on host rh64c.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
3e:7f:3c:b7:f5:c7:fa:78:7e:c5:6a:b9:fc:2f:47:92 root@rh64c
The key's randomart image is:
+--[ RSA 1024]----+
|                 |
|                 |
|                 |
|                 |
|        S      o |
|       .      E +|
|        o  .   *o|
|         o  +.*oB|
|          .. +*@X|
+-----------------+
Creating keys on remote host rh64d if they do not exist already. This is required to setup SSH on host rh64d.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
e9:d7:f8:f0:46:c5:7c:5e:c1:25:ec:a1:50:72:b1:8a root@rh64d
The key's randomart image is:
+--[ RSA 1024]----+
|          ..+oo o|
|          .o .o+ |
|           ..= ..|
|         o .. = o|
|        E .  . o.|
|       .   o.   .|
|        . +..    |
|         . +.    |
|           .o    |
+-----------------+
Creating keys on remote host rh64e if they do not exist already. This is required to setup SSH on host rh64e.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
cc:b2:0c:6d:4b:99:20:70:61:41:27:f5:6e:c8:33:8f root@rh64e
The key's randomart image is:
+--[ RSA 1024]----+
|..B+o            |
| + o .           |
|  . . .          |
|   o = =         |
|    * X S        |
|     @ +         |
|    E =          |
|                 |
|                 |
+-----------------+
Creating keys on remote host rh64f if they do not exist already. This is required to setup SSH on host rh64f.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
41:60:7e:f4:21:87:77:97:23:c3:c1:e8:2b:96:9f:c7 root@rh64f
The key's randomart image is:
+--[ RSA 1024]----+
|      o.+.o+.. . |
|     o o.+o.* +  |
|      . oo.. + . |
|       . ..      |
|        S. .     |
|        + .      |
|       . o o     |
|          o E    |
|           .     |
+-----------------+
Creating keys on remote host rh64g if they do not exist already. This is required to setup SSH on host rh64g.
Generating public/private rsa key pair.
Your identification has been saved in .ssh/id_rsa.
Your public key has been saved in .ssh/id_rsa.pub.
The key fingerprint is:
93:aa:49:22:6f:cb:ae:87:0a:ff:38:e0:ea:a0:fb:b1 root@rh64a
The key's randomart image is:
+--[ RSA 1024]----+
|                 |
|                 |
|                 |
|         .       |
|        S        |
|.      . .       |
|=oo . .          |
|=*+* o           |
|XOE++            |
+-----------------+
Updating authorized_keys file on remote host rh64a
Updating known_hosts file on remote host rh64a
Updating authorized_keys file on remote host rh64b
Updating known_hosts file on remote host rh64b
Updating authorized_keys file on remote host rh64c
Updating known_hosts file on remote host rh64c
Updating authorized_keys file on remote host rh64d
Updating known_hosts file on remote host rh64d
Updating authorized_keys file on remote host rh64e
Updating known_hosts file on remote host rh64e
Updating authorized_keys file on remote host rh64f
Updating known_hosts file on remote host rh64f
Updating authorized_keys file on remote host rh64g
Updating known_hosts file on remote host rh64g
cat: /root/.ssh/known_hosts.tmp: No such file or directory
cat: /root/.ssh/authorized_keys.tmp: No such file or directory
SSH setup is complete.

------------------------------------------------------------------------
Verifying SSH setup
===================
The script will now run the date command on the remote nodes using ssh
to verify if ssh is setup correctly. IF THE SETUP IS CORRECTLY SETUP,
THERE SHOULD BE NO OUTPUT OTHER THAN THE DATE AND SSH SHOULD NOT ASK FOR
PASSWORDS. If you see any output other than date or are prompted for the
password, ssh is not setup correctly and you will need to resolve the
issue and set up ssh again.
The possible causes for failure could be:
1. The server settings in /etc/ssh/sshd_config file do not allow ssh
for user root.
2. The server may have disabled public key based authentication.
3. The client public key on the server may be outdated.
4. ~root or ~root/.ssh on the remote host may not be owned by root.
5. User may not have passed -shared option for shared remote users or
may be passing the -shared option for non-shared remote users.
6. If there is output in addition to the date, but no password is asked,
it may be a security alert shown as part of company policy. Append the
additional text to the <OMS HOME>/sysman/prov/resources/ignoreMessages.txt file.
------------------------------------------------------------------------
--rh64a:--
Running /usr/bin/ssh -x -l root rh64a date to verify SSH connectivity has been setup from local host to rh64a.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64b:--
Running /usr/bin/ssh -x -l root rh64b date to verify SSH connectivity has been setup from local host to rh64b.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64c:--
Running /usr/bin/ssh -x -l root rh64c date to verify SSH connectivity has been setup from local host to rh64c.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64d:--
Running /usr/bin/ssh -x -l root rh64d date to verify SSH connectivity has been setup from local host to rh64d.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:55 CDT 2013
------------------------------------------------------------------------
--rh64e:--
Running /usr/bin/ssh -x -l root rh64e date to verify SSH connectivity has been setup from local host to rh64e.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
--rh64f:--
Running /usr/bin/ssh -x -l root rh64f date to verify SSH connectivity has been setup from local host to rh64f.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
--rh64g:--
Running /usr/bin/ssh -x -l root rh64g date to verify SSH connectivity has been setup from local host to rh64g.
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL. Please note that being prompted for a passphrase may be OK but being prompted for a password is ERROR.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:56 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64a to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
-Verification from rh64a complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:57 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64b to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
-Verification from rh64b complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:58 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64c to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
-Verification from rh64c complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:42:59 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64d to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
-Verification from rh64d complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:00 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64e to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
-Verification from rh64e complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:01 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64f to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
-Verification from rh64f complete-
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64a
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:02 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64b
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64c
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64d
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64e
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64f
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
------------------------------------------------------------------------
Verifying SSH connectivity has been setup from rh64g to rh64g
------------------------------------------------------------------------
IF YOU SEE ANY OTHER OUTPUT BESIDES THE OUTPUT OF THE DATE COMMAND OR IF YOU ARE PROMPTED FOR A PASSWORD HERE, IT MEANS SSH SETUP HAS NOT BEEN SUCCESSFUL.
Thu Aug  8 06:43:03 CDT 2013
------------------------------------------------------------------------
-Verification from rh64g complete-
SSH verification complete.

I also run a simple test to confirm that I can login to all the RAC nodes without being prompted for a password by executing hostname and date commands together:

[root@rh64a ~]# cat ssh_setup_test.ksh
ssh rh64a "hostname; date"
ssh rh64b "hostname; date"
ssh rh64c "hostname; date"
ssh rh64d "hostname; date"
ssh rh64e "hostname; date"
ssh rh64f "hostname; date"
ssh rh64g "hostname; date"

[root@rh64a ~]# ./ssh_setup_test.ksh 
rh64a
Thu Aug  8 06:48:35 CDT 2013
rh64b
Thu Aug  8 06:48:35 CDT 2013
rh64c
Thu Aug  8 06:48:35 CDT 2013
rh64d
Thu Aug  8 06:48:35 CDT 2013
rh64e
Thu Aug  8 06:48:36 CDT 2013
rh64f
Thu Aug  8 06:48:35 CDT 2013
rh64a
Thu Aug  8 06:48:36 CDT 2013