Symantec logo

Creating $DB2InstHome/.rhosts

On each system, create a file named $DB2InstHome/.rhosts, and place a "+" character within it. This file permits a system to access the database without being prompted for a password.

If security is a concern, put the hostname and userid inside the .rhosts file, as shown in the following examples:

dbmach01 db2inst1

dbmach02 db2inst1

dbmach03 db2inst1

dbmach04 db2inst1

Or

+ db2inst1

Using the command, rsh system_name,test that you can remotely log in with the DB2 instance (for example, db2inst1) account from one system in the cluster to another without being prompted for a password. Test this from each system in the cluster to all other systems.

Configuring ssh on Suse

 To configure ssh on Suse

  1. Log on to the system from which you want to install VCS.
  2. Generate a DSA key pair on this system by running the following command:

    # ssh-keygen -t dsa

  3. Accept the default location: ~/.ssh/id_dsa
  4. When prompted, enter a passphrase and confirm it.
  5. Change the permissions of the .ssh directory, type:

    # chmod 755 ~/.ssh

  6. The file ~/.ssh/id_dsa.pub contains a line beginning with ssh_dss and ending with the name of the system on which it was created. Copy this line to the /root/.ssh/authorized_keys2 file on all systems where VCS is to be installed.

      Note   If the local system is part of the cluster, make sure to edit the authorized_keys2 file on that system.


  7. Run the following commands on the system from which the installation is taking place:

    # exec /usr/bin/ssh-agent $SHELL

    # ssh-add


      Note   This step is shell-specific and is valid for the duration the shell is alive.


  8. When prompted, enter your DSA passphrase.

    You are ready to install VCS on several systems by running the installvcs script on any one of them or on an independent machine outside the cluster.

    To avoid running the ssh-agent on each shell, run the X-Window system and configure it so that you will not be prompted for the passphrase. Refer to the Red Hat documentation for more information.