Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Linux Configuration
Chapter 3 125
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 Serviceguard Extension for SAP on Linux
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.
Ensure that $HOME/.ssh/authorized_keys2 is not writable by group
and others. The same is valid for the complete path.
Permissions on ~<user> should be 755. Permissions on
~<user>/.ssh/authorized_keys2 must be 600 or 644.
Allowing group/other write access to .ssh or authorized_keys2 will
disable automatic authentication.
IS275 Installation Step:
Make sure that the required rpm software packages are installed on the
cluster nodes. Check the status of the rpm kits with:
rpm -q serviceguard
rpm -q nfs-toolkit
rpm -q sgesap-toolkit
rpm –q sgcmon
rpm –q pidentd
If the rpm packages are missing install them with the following
command
rpm -Uhv \
serviceguard-<version>.product.<linux-os>.<platform>.rpm