Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Linux Configuration
Chapter 2 53
Create an .rhosts file in the home directories of the Linux users root,
<sid>adm. Allow login for root as root from all nodes including the node
you are logged into. Allow login for root and <sid>adm as <sid>adm from
all nodes including the node you are logged into. Be careful with this
step, many problems result from an incorrect setup of remote access.
Check the setup with remsh commands. If you have to provide a
password, the .rhosts does not work.
IS330 Installation Step:
Use the followoing steps, if you are planning to use the secure shell
mechanism:
1. First make sure that the openssh rpm-package is installed.
rpm -qa | grep ssh
2. Create a private and public key for the root user:
ssh -keygen -t dsa
Executing this command creates a .ssh directory in the root user's
home directory including the following files:
id_dsa
id_dsa.pub
The file id_dsa.pub contains the security information (public key) for
the user@host pair e.g. root@<local>. This information needs to be
added to the file $HOME/.ssh/authorized_keys2 of the root and
<sid>adm user.
Create these files if they are not already there. This will allow the root
user on <local> to remotely execute commands via ssh under his own
identity and under the identity of <sid>adm on all other relevant nodes.
On each cluster node where a SGeSAP/LX IPF package can run, test the
remote access to all relevant systems as user root with the following
commands:
ssh <hostN> date
ssh -l <sid>adm <hostN> date
Do these tests twice since the first ssh command between two user/host
pairs usually requires a keyboard response to acknowledge the exchange
of system level id keys.