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

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3 143
For testing it can help to create a file called ${SGCONF}/<SID>/debug on
all nodes in the cluster. This enables you to start the Serviceguard
packages without running the Serviceguard Extension for SAP on Linux
specific steps of starting or stopping an SAP instance. Do not forget to
remove all debug files after the tests.
Serviceguard NFS Toolkit Configuration
The cross-mounted file systems need to be added to a package that
provides Highly Available NFS services. This is usually the (dbci), the
(db), or the standalone (sapnfs) package. The most flexibility is provided
with the standalone Serviceguard NFS (sapnfs) package.
Logon as root to the primary host to perform the following tasks.
IS520 Installation Step:
If it is intended to use a standalone Serviceguard NFS package, create a
directory for the sapnfs Serviceguard package. To be somewhat
consistent with the Serviceguard SAP SID package names, the
uppercase name SAPNFS was chosen.
mkdir –p ${SGCONF}/SAPNFS
cp ${SGROOT}/nfstoolkit/hanfs.sh ${SGCONF}/SAPNFS/hanfs.sh
cp ${SGROOT}/nfstoolkit/toolkit.sh \
${SGCONF}/SAPNFS/toolkit.sh
cp ${SGROOT}/nfstoolkit/hanfs.conf \
${SGCONF}/SAPNFS/hanfs.conf
cp ${SGROOT}/nfstoolkit/nfs.mon ${SGCONF}/SAPNFS/nfs.mon
IS540 Installation Step:
In this step the NFS Server directories that will be NFS exported are
configured.
Edit the hanfs.sh file in the ${SGCONF}}/SAPNFS package directory to
configure the Serviceguard NFS service. Add all cross-mounted
directories that have been identified in section “Planning the LVM layout
for Clustered SAP Environments” to be of type “SHARED NFS”.
Example entries are:
XFS[0]=”-o rw *:/export/usr/sap/trans”
XFS[1]=”-o rw *:/export/sapmnt/<SID>”