Managing Serviceguard Extension for SAP Version B.05.10, September 2010

Example:
ENQOR_SCS_PKGNAME_C11=foobar
ENQOR_REP_PKGNAME_C11=foorep
For SAP kernel 7.x; instances SCS00 and ERS01:
ENQOR_SCS_ERS01_PKGNAME_C11=foobar
ENQOR_ERS_ERS01_PKGNAME_C11=fooers
Optional Step: OS450
For non-CFS shares, it is recommended to set AUTO_VG_ACTIVATE=0 in /etc/lvmrc.
Edit the custom_vg_activation() function if needed. Distribute the file to all cluster nodes.
Optional Step: OS460
It is recommended to set AUTOSTART_CMCLD=1 in /etc/rc.config.d/cmcluster.
Distribute the file to all cluster nodes.
Installation Step: LS470
>Define volume groups, logical volumes, IP addresses and subnets in the package control scripts
<pkg_name>.control.script.
Fill the IP[*] and SUBNET[*] array with the IP addresses and subnet addresses that the package
is attached as well.
When using the HP Serviceguard Storage Management Suite with CFS and shared access Option
3 (chapter 2 — “Planning the Storage Layout”) the definition and configuration of logical volumes
in the package control script might not be necessary for the SAP components. The CFS based file
systems are made available through the corresponding multinode packages as defined in chapter
2—”Planning the Storage Layout.” For non-CFS shares, the volume groups are directly connected
to the SAP packages. The file systems that are specified in the LV[*], FS[*] and FS_MOUNT_OPT[*]
array in this case are not identical to the file systems that are for HA NFS usage. Example:
LV[0]="/dev/vgdbC11/lvoracle"; \FS[0]="/oracle/C11"; \FS_MOUNT_OPT[0]="-o rw"
LV[1]="/dev/vgdbC11/lvsapmnt"; \FS[1]="/export/sapmnt/C11"; \FS_MOUNT_OPT[1]="-o rw"
LV[2]="/dev/vgC11/lvusrsap"; \FS[2]="/usr/sap/C11/DVEBMGS20"; \FS_MOUNT_OPT[2]="-o rw"
LV[3]="/dev/vgsapnfs/lvtrans"; \FS[3]="/export/usr/sap/trans"; \FS_MOUNT_OPT[3]="-o rw"
Installation Step: LS480
To enable the SAP specific scripts change the customer_defined_commands sections of the
package control script(s) <pkg_name>.control.script:
function customer_defined_run_cmds
{
. /etc/cmcluster/<SID>/sapwas.cntl start <SID>
test_return 51
}
function customer_defined_halt_cmds
{
. /etc/cmcluster/<SID>/sapwas.cntl stop <SID>
test_return 52
}
The SAP specific control file sapwas.cntl needs two arguments—the MODE (start/stop) and
the SAP System ID (SID). Don't omit the leading period sign in each line that calls
sapwas.cntl.
Installation Step: LS500
Distribute the package setup to all failover nodes.
For example, you have to create package directories /etc/cmcluster<SID> on all backup
nodes, copy all integration files below /etc/cmcluster/<SID> from the primary host's package
directory to the backup host's package directory using rcp(1) or cmcp(1m) and similarly copy
/etc/cmcluster/sap.functions from the primary host to the same location on the backup
hosts.
Installation Step: LS510
Legacy Package Configuration 81