Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3140
Specify subnets to be monitored in the SUBNET section.
OS435 Installation Step:
When using the HP Serviceguard Storage Management Suite with CFS
and storage layout option 3 of chapter 2 the package(s) dependencies to
the corresponding mount point packages holding the required file
systems need to be defined. This ensures a successful package start only
if the required CFS file system(s) are available.
DEPENDENCY_NAME SG-CFS-MP-1
DEPENDENCY_CONDITION SG-CFS-MP-1=UP
DEPENDENCY_LOCATION SAME_NODE
DEPENDENCY_NAME SG-CFS-MP-2
DEPENDENCY_CONDITION SG-CFS-MP-2=UP
DEPENDENCY_LOCATION SAME_NODE
OS440 Optional Step:
If the SAP message server or SAP dispatcher should be monitored as
Serviceguard service, the <pkg_name>.config file needs to configure the
monitoring. The recommended naming for the service is <pkg_name>ms
or <pkg_name>disp.
Monitoring Routines periodically check the availability and
responsiveness of the SAP Message Server or SAP dispatcher. If it
recognizes the SAP Message Server or SAP dispatcher to be unavailable,
Serviceguard will switch the package and try to restart on different
hardware since the SAP Message Server or SAP dispatcher are crucial
components of a SAP Central Instance.
First, the monitoring scripts need to be copied to the current package
directory. For a SAP System C11:
cp /opt/cmcluster/sap/SID/sapms.mon /etc/cmcluster/C11
cp /opt/cmcluster/sap/SID/sapdisp.mon /etc/cmcluster/C11
The monitor will be paused within ten seconds if a debug file gets created
for the package:
touch /etc/cmcluster/<SID>/debug
The debug file can be used to allow manual SAP instance shutdowns and
startups.