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

RUN_SCRIPT /etc/cmcluster/<SID>/<pkg_name>.control.script
HALT_SCRIPT /etc/cmcluster/ <SID>/<pkg_name>.control.script
Specify subnets to be monitored in the SUBNET section.
Installation Step: OS435
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
Optional Step: OS440
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 omponents 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.
NOTE: The manual startup using common startsap/stopsap scripts may not work correctly
with Netweaver 2004s based Application Servers. In this case, the instances need to started by
directly using the sapstart binary passing the start profile as a parameter. Example:
sapstart pf=/sapmnt/<SID>/profile/START_\ <INAME><INR>_<RELOC_IP/hostname>
The service monitor will not be able to detect a stopsap command and will consider a manual
instance shutdown to be a failure. The package will then fail over the instance to another node.
The existence of the debug file can prevent that. If the debug file gets removed, the service monitor
continues to run. Make sure that the packaged SAP instance is already running when removing
the debug file or an immediate failover will occur. As long as the debug file exists locally, a
package shutdown would not try to stop the SAP instance or its database. A local restart of the
package would only take care of the HA NFS portion. The instance would not be started with
the package and the monitor would be started in paused mode.
Example entries in <pkg_name>.config:
Message Server Monitor:
SERVICE_NAME ciC11ms
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300
Dispatcher Monitor:
SERVICE_NAME ciC11disp
SERVICE_FAIL_FAST_ENABLED YES
SERVICE_HALT_TIMEOUT 300
The service name and command referencing the SAP message server monitor and SAP dispatcher
monitor must be specified in <pkg_name>.control.script to use the service defined in the
Legacy Package Configuration 79