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 252
Cluster Node Configuration
Repeat the steps in this section for each node of the cluster.
Logon as root.
SGeSAP/LX IPF needs remote login to be enabled on all cluster hosts.
The traditional way to achieve this is via remote shell commands. If
security concerns prohibit this, it is also possible to use secure shell
access instead.
IS300 Installation Step:
Make sure that the required rpm software packages are installed on the
cluster nodes.
rpm -q serviceguard
rpm -q nfs-toolkit
rpm -q sgesap-toolkit
OS310 Optional Step:
If there are additional internal application servers on the host:
Application servers in the cluster must have an instance number which
is different from the instance number of the Central Instance. Execute
the command:
ls -d /usr/sap/<SID>/*<INSTNR>
There should be no match. Otherwise, reinstall the instance with
another instance ID.
IS320 Installation Step:
If you are planning to use the traditional remote shell access adjust the
security settings in /etc/pam.d for the following services:
In file /etc/pam.d/login comment out the following line:
auth required /lib/security/pam_securetty.so
In file /etc/pam.d/rsh change the following line:
auth required /lib/security/pam_rhosts_auth.so to
auth sufficient /lib/security/pam_rhosts_auth.so.