Generating an ssh key pair for the backup server, Generating an ssh key pair for the database server – HP 3PAR Application Software Suite for Oracle User Manual
Page 41
3.
If you are using HP UX, verify that the SSH daemon has strict mode disabled:
a.
Check the sshd_config file for the following line:
StrictModes no
b.
If StrictModes is set to yes, change the entry to no.
Generating an SSH Key Pair for the Backup Server
To generate an SSH key pair for the backup server:
1.
Log on to the backup server as the root or Oracle owner user.
2.
Create a key pair with no passphrase using the ssh-keygen command. If a key-pair already
exists, skip this section.
Generating public/private rsa key pair.
Enter file in which to save the key (//.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in //.ssh/id_rsa.
Your public key has been saved in //.ssh/id_rsa.pub.
The key fingerprint is:
xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx root@
NOTE:
You can create the SSH key as either dsa or rsa. The recommended key length is
1024 (the total of the public and private key lengths).
The ssh-keygen utility generates two files, id_rsa and id_rsa.pub (or id_dsa and
id_dsa.pub
). The id_rsa (or id_dsa) file contains the private key and the id_rsa.pub
(or id_dsa.pub) file contains the public key.
Generating an SSH Key Pair for the Database Server
You can either use the same SSH key pair generated for the backup server or generate a different
SSH key pair for the database server. If you choose to use the same key pair, create one HP 3PAR
CLI user, otherwise, create two different HP 3PAR CLI users to be accessed from the database
server and the backup server, respectively. If you are generating a different SSH key pair for the
database server, perform the procedure described in
“Setting Connections from the Database
Server to the HP 3PAR StoreServ Storage” (page 45)
on the database server.
NOTE:
In a Real Application Cluster (RAC) environment, all the nodes in the RAC cluster must
have the same SSH key pair to run Recovery Manager for Oracle utilities against any RAC instance
on any node.
If you choose to use the same SSH key pair, create one HP 3PAR CLI user. Then copy the SSH key
pair from the backup server to the database server as follows:
The authenticity of host 'pilot (192.168.3.130)' can't be established.
RSA key finger print is xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'pilot (192.168.3.130)' to the list of known hosts.
root@pilot's password:
Setting Up SSH Connections for Recovery Manager
41