Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
HP-UX Configuration
Chapter 3132
Cluster Node Configuration
Repeat the steps in this section for each node of the cluster.
Logon as root.
SGeSAP 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.
IS240 Installation Step:
Make sure that the required software packages are installed on all
cluster nodes:
• Serviceguard Extension for SAP, B7885BA (HP 9000 Servers) or
T2803BA (Integrity Servers)
The swlist command may be utilized to list available software on a
cluster node
If a software component is missing install the required product depot
files using the swinstall tool.
IS250 Installation Step:
Check that /etc/logingroup is a link to /etc/group.
IS260 Installation Step:
You need to allow remote access between cluster hosts. This can be done
by using remote shell remsh(1) or secure shell ssh(1) mechanisms.
If you allow remote access using the remote shell mechanism:
Create an .rhosts file in the home directories of the HP-UX users root,
<sid>adm and (if applicable) informix. 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.