Oracle rac ssh equivalence Configuration

Oracle rac ssh equivalence configuration (I). To facilitate communications between nodes in the RAC environment, you must configure the SSH equivalence statement: when a user or program is connected from one machine to another without a password, the background of this application is: the Installation Process of Clusterware and Database is first installed on a node, and then the installer automatically copies the locally installed content to the same remote directory. This is a background copy process, the installer has no chance to enter a password for authentication. Therefore, you must configure user equivalence. In the Hadoop cluster configuration process, you also need to configure SSH equivalence. During Hadoop running, you need to manage the remote Hadoop daemon, after Hadoop is started, NameNode uses SSH to start and stop various Daemon Processes on each DataNode. Therefore, the SSH equivalent configurations of the two are the same. (ii) install and start the SSH protocol first. installation or not: # rpm-qa | grep openssh # rpm-qa | grep rsync as shown in Figure If no, run the following command: # yum install ssh # yum install rsync to start SSH: # service sshd start (3) SSH equivalence principle. Suppose there are two machines on the network: A & B, and A must implement password-free public key authentication, then: ① generate A key pair on A first, including A public key and A private key ② and then copy the public key to B ③ When A connects to B through SSH, B will generate A random number and encrypt the random number with the public key of, sent to A ④ A and decrypted with the private key after receiving the encrypted number, return the decryption count to B ⑤ B to confirm that the decryption count is correct, and then allow A to connect. (4) ensure that the UID of the Oracle user on each node is the same as the GID of the DBA group. For example: [plain] Node 1: [root @ odd ~] # Id oracle uid = 500 (oracle) gid = 500 (oinstall) groups = 500 (oinstall) node 2: [root @ even ~] # Id oracle uid = 500 (oracle) gid = 500 (oinstall) groups = 500 (oinstall), 501 (dba) (v) configuration step ① set the network to write all IP addresses and hostnames into the hosts file, and keep the/etc/hosts file of each node the same [plain] [root @ even ~] # Cat/etc/hosts 127.0.0.1 localhost. localdomain localhost 192.168.1.115 even.example.com even 192.168.1.116 odd.example.com odd [mysql @ odd ~] $ Cat/etc/hosts 127.0.0.1 localhost. localdomain localhost 192.168.1.115 even.example.com even 192.168.1.116 odd.example.com odd ② run the following commands on ODD and EVEN respectively: # cd $ HOME # mkdir. ssh # chmod 700. ssh # cd. ssh # ssh-keygen-t rsa # ssh-keygen-t dsa # cat *. pub> authorized_keys ③ migrate authorized_keys in ODD: # scp authorized_keys even.example.com:/root /. ssh/keys_odd in EVEN: # cat keys_odd> authorized_keys # Scp authorized_keys odd.example.com:/root/. ssh/(6) test in ODD: [root @ odd ~] # Ssh even.example.com Last login: Mon May 6 12:58:12 2013 from odd.example.com [root @ even ~] # In EVEN: [root @ even ~] # Ssh odd.example.com Last login: Mon May 6 11:57:49 2013 [root @ odd ~] #