In another post, we introduced how to manually set up ssh user equivalence between RAC nodes, before we install GI and RAC software.
Here we introduce sshUserSetup.sh Script to create user equivalence automatically. The script is coming from GI binary media.
Pay attention to option “advanced”. Without “advanced” option, the user equivalence setting up will be racnode1–>racnode2 only. With “advanced” option, the user equivalence setting up will be racnode1<–>racnode2 .
[] grid@racnode1:/u01/app/software/grid/sshsetup$ ./sshUserSetup.sh -user grid -hosts "racnode1 racnode2" -noPromptPassphrase -advanced -exverify The output of this script is also logged into /tmp/sshUserSetup_2016-09-14-14-59-01.log Hosts are racnode1 racnode2 user is grid Platform:- Linux Checking if the remote hosts are reachable PING racnode1 (10.11.12.13) 56(84) bytes of data. 64 bytes from racnode1 (10.11.12.13): icmp_seq=1 ttl=64 time=0.017 ms 64 bytes from racnode1 (10.11.12.13): icmp_seq=2 ttl=64 time=0.015 ms 64 bytes from racnode1 (10.11.12.13): icmp_seq=3 ttl=64 time=0.015 ms 64 bytes from racnode1 (10.11.12.13): icmp_seq=4 ttl=64 time=0.009 ms 64 bytes from racnode1 (10.11.12.13): icmp_seq=5 ttl=64 time=0.008 ms --- racnode1 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4000ms rtt min/avg/max/mdev = 0.008/0.012/0.017/0.005 ms PING racnode2 (10.11.12.15) 56(84) bytes of data. 64 bytes from racnode2 (10.11.12.15): icmp_seq=1 ttl=64 time=1.71 ms 64 bytes from racnode2 (10.11.12.15): icmp_seq=2 ttl=64 time=0.081 ms 64 bytes from racnode2 (10.11.12.15): icmp_seq=3 ttl=64 time=0.094 ms 64 bytes from racnode2 (10.11.12.15): icmp_seq=4 ttl=64 time=0.084 ms 64 bytes from racnode2 (10.11.12.15): icmp_seq=5 ttl=64 time=0.077 ms --- racnode2 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4001ms rtt min/avg/max/mdev = 0.077/0.409/1.710/0.650 ms Remote host reachability check succeeded. The following hosts are reachable: racnode1 racnode2. The following hosts are not reachable: . All hosts are reachable. Proceeding further... firsthost racnode1 numhosts 2 The script will setup SSH connectivity from the host racnode1 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 racnode1 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 /home/grid/.ssh/config, it would be backed up to /home/grid/.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 /home/grid/.ssh/id_rsa. Your public key has been saved in /home/grid/.ssh/id_rsa.pub. The key fingerprint is: 77:c8:3b:d6:61:ff:21:40:f8:f0:79:d8:39:52:df:85 grid@racnode1 The key's randomart image is: +--[ RSA 1024]----+ | | | . . | | o . .E .| | .=.= o o| | S +B+= ..| | . =+o. | | + .... | | . . ...| | .| +-----------------+ Creating .ssh directory and setting permissions on remote host racnode1 THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR grid. THIS IS AN SSH REQUIREMENT. The script would create ~grid/.ssh/config file on remote host racnode1. If a config file exists already at ~grid/.ssh/config, it would be backed up to ~grid/.ssh/config.backup. The user may be prompted for a password here since the script would be running SSH on host racnode1. Warning: Permanently added 'racnode1,10.11.12.13' (RSA) to the list of known hosts. grid@racnode1's password: Done with creating .ssh directory and setting permissions on remote host racnode1. Creating .ssh directory and setting permissions on remote host racnode2 THE SCRIPT WOULD ALSO BE REVOKING WRITE PERMISSIONS FOR group AND others ON THE HOME DIRECTORY FOR grid. THIS IS AN SSH REQUIREMENT. The script would create ~grid/.ssh/config file on remote host racnode2. If a config file exists already at ~grid/.ssh/config, it would be backed up to ~grid/.ssh/config.backup. The user may be prompted for a password here since the script would be running SSH on host racnode2. Warning: Permanently added 'racnode2,10.11.12.15' (RSA) to the list of known hosts. grid@racnode2's password: Done with creating .ssh directory and setting permissions on remote host racnode2. Copying local host public key to the remote host racnode1 The user may be prompted for a password or passphrase here since the script would be using SCP for host racnode1. grid@racnode1's password: Done copying local host public key to the remote host racnode1 Copying local host public key to the remote host racnode2 The user may be prompted for a password or passphrase here since the script would be using SCP for host racnode2. grid@racnode2's password: Done copying local host public key to the remote host racnode2 Creating keys on remote host racnode1 if they do not exist already. This is required to setup SSH on host racnode1. Creating keys on remote host racnode2 if they do not exist already. This is required to setup SSH on host racnode2. 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: 8d:07:39:11:ee:f8:ac:cd:bf:00:c5:40:0a:d1:9c:ab grid@racnode2 The key's randomart image is: +--[ RSA 1024]----+ | o+ oo o. | | .+. + o | | .. B | | . + = | | . o S o | | E + . | | + | | + . | | . o.o. | +-----------------+ Updating authorized_keys file on remote host racnode1 Updating known_hosts file on remote host racnode1 Updating authorized_keys file on remote host racnode2 Updating known_hosts file on remote host racnode2 cat: /home/grid/.ssh/known_hosts.tmp: No such file or directory cat: /home/grid/.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 grid. 2. The server may have disabled public key based authentication. 3. The client public key on the server may be outdated. 4. ~grid or ~grid/.ssh on the remote host may not be owned by grid. 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. ------------------------------------------------------------------------ --racnode1:-- Running /usr/bin/ssh -x -l grid racnode1 date to verify SSH connectivity has been setup from local host to racnode1. 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. Wed Sep 14 14:59:32 AEST 2016 ------------------------------------------------------------------------ --racnode2:-- Running /usr/bin/ssh -x -l grid racnode2 date to verify SSH connectivity has been setup from local host to racnode2. 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. Wed Sep 14 14:59:33 AEST 2016 ------------------------------------------------------------------------ ------------------------------------------------------------------------ Verifying SSH connectivity has been setup from racnode1 to racnode1 ------------------------------------------------------------------------ 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. Wed Sep 14 14:59:33 AEST 2016 ------------------------------------------------------------------------ ------------------------------------------------------------------------ Verifying SSH connectivity has been setup from racnode1 to racnode2 ------------------------------------------------------------------------ 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. Wed Sep 14 14:59:33 AEST 2016 ------------------------------------------------------------------------ -Verification from racnode1 complete- ------------------------------------------------------------------------ Verifying SSH connectivity has been setup from racnode2 to racnode1 ------------------------------------------------------------------------ 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. Wed Sep 14 14:59:33 AEST 2016 ------------------------------------------------------------------------ ------------------------------------------------------------------------ Verifying SSH connectivity has been setup from racnode2 to racnode2 ------------------------------------------------------------------------ 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. Wed Sep 14 14:59:33 AEST 2016 ------------------------------------------------------------------------ -Verification from racnode2 complete- SSH verification complete.
Make DBA Life Easy 