Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

<nfsreloc>:/export/usr/sap/trans
It is important that the nosymlink option is specified. The nosymlink option does not create symbolic
links to local directories if the NFS server file system is local. Instead it always mounts from the virtual
IP address <nfsreloc>. Therefore a cluster node can be an NFS server and client at the same time
and the NFS server file systems can be dynamically relocated to the other cluster nodes.
5. After completing the automounter changes restart the automounter with /etc/rc.d/autofs
restart
Cluster Configuration
This section describes the cluster software configuration with the following topics:
• Serviceguard Configuration
• Serviceguard NFS Toolkit Configuration
• Serviceguard Extension for SAP on Linux Configuration
Configuring SGeSAP/LX on Linux
The following sections contain information on configuring SGeSAP/LX (Serviceguard Extension for SAP). It
is assumed that a basic Serviceguard cluster is up and running.
As mentioned in an earlier section of this document, references to variable ${SGCONF} can be replaced
by the definition of the variable that is found in this file /etc/cmcluster.config. The default values are:
• For SUSE Linux - SGCONF=/opt/cmcluster/conf
• For Redhat Linux - SGCONF=/usr/local/cmcluster/conf
The Serviceguard NFS toolkit also uses a installation directory. This directory is different for SUSE Linux and
Redhat Linux so any references to variable ${SGROOT} can be replaced by the following definition:
• For SUSE Linux - SGROOT=/opt/cmcluster
• For Redhat Linux - SGROOT=/usr/local/cmcluster
SGeSAP/LX uses a staging directory during the installation. As the staging directory is different for SUSE
Linux and Redhat Linux references to variable ${SAPSTAGE} can be replaced by the following definition:
• For SUSE Linux - SAPSTAGE=/opt/cmcluster/sap
• For Redhat Linux - SAPSTAGE=/usr/local/cmcluster/sap
Export the variables so they are available to the user environment:
export SGCONF
export SGROOT
export SAPSTAGE
Variables ${SGCONF} and ${SGROOT} can also be set with the following command:
. /etc/cmcluster.conf
Installation Step: IS400
Create a SGeSAP/LX package directory.
Logon as root on the primary host.
This directory will be used by all packages that belong to the SAP System with a specific SAP System ID
<SID>.
mkdir -p ${SGCONF}/<SID>
Installation Step: IS410
In a previous installation step, the command:
rpm -Uhv sgesap-toolkit-<version>.product.<linux-os>.<platform>.rpm
has copied all relevant SGeSAP/LX files in the ${SAPSTAGE}staging area.
The following files need to be copied from the ${SAPSTAGE} staging to the SGeSAP/LX package directory:
74 Step-by-Step Cluster Conversion