Managing Serviceguard Extension for SAP on Integrity Linux, December 2005

Step by Step Installation of SGeSAP on Integrity Linux for SAP WAS Central Instances
Cluster Configuration
Chapter 2 73
IS760 Installation Step:
Edit the renamed toolkit.sh file in the package directory. Change the
default name to the hanfs.sh file to reflect the changed filename. The
following is an example for two package concept:
In dbtoolkit.sh replace the line HA_SCRIPT=${0%/*}/hanfs.sh with
the line HA_SCRIPT=${0%/*}/dbhanfs.sh
IS770 Installation Step:
Edit the renamed hanfs.sh file in the package directory to configure the
HA NFS service. Add all cross-mounted directories that have been
identified in section “Planning the LVM layout for Clustered SAP
Environments” to the XFS[*] array of the NFS EXPORT DIRECTORY
section.
Example entries for a dbhanfs.sh or dbcihanfs.sh file with Oracle
database:
XFS[0]=”-o rw *:/export/usr/sap/trans”
XFS[1]=”-o rw *:/export/sapmnt/LUX”
A SAPDB example would also have the following entries added:
XFS[2]=”-o rw *:/export/sapdb/programs”
XFS[3]=”-o rw *:/export/sapdb/data”
XFS[4]=”-o rw *:/export/var/spool/sql/ini
IS780 Installation Step:
A Serviceguard service monitor for the HA NFS can be configured in
section NFS MONITOR. The naming convention for the service should
be <pkgtype><SID>NFS. Example for SAP System C11:
NFS_SERVICE_NAME[0]=”dbciC11nfs”
NFS_SERVICE_CMD[0]=”${SGCONF}/C11/nfs.mon”
NFS_SERVICE_RESTART[0]=”-r 0”