Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), April 2009

package is the last one stopped. This prevents global directories from disappearing before all SAP components
in the cluster have completed their shutdown.
Installation Step: IS515
Verify that the setup works correctly to this point.
Use the following commands to run or halt a SGeSAP/LX package:
cmrunpkg dbC11
cmhaltpkg dbC11
NOTE: Normally the (sapnfs) Serviceguard package is required to be configured and running before
any of the other SGeSAP/LX packages can be started.
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.
Installation and Configuration Considerations
This section details the installation and configuration of the SGeSAP scripts for the Standalone Enqueue
Server and Enqueue Replication Server components.
Prerequisites
A Serviceguard cluster with at least two nodes attached to the network. For documentation purposes,
clunode1 and clunode2 represent Serviceguard clusters nodes. Node clunode1 will run the Serviceguard
package for the Standalone Enqueue Server. Node clunode2 runs the package for the Enqueue Replication
Server.
In the event of a failure the Standalone Enqueue the Serviceguard package for the Standalone Enqueue it
will go through the following steps:
1. “follow and restart the Serviceguard package for the Standalone Enqueue Service on the node running
the Enqueue Replication Service.
2. Reclaim the replicated SAP locks that the Enqueue Replication Service had collected.
3. Halt the Enqueue Replication Service.
Installation Step: IS516
Create Serviceguard templates and edit the files for both packages.
In this example the Serviceguard package name for the Standalone Enqueue instance is ascsSX1 and for
the Enqueue Replication the name is ers12SX1
cmmakepkg -p ascsSX1.config
cmmakepkg -s ascsSX1.control.script
cmmakepkg -p ers12SX1.config
cmmakepkg -s ers12SX1.control.script
vi ascsSX1.config
PACKAGE_NAME ascsSX1
NODE_NAME clunode1
NODE_NAME clunode2
RUN_SCRIPT /opt/cmcluster/conf/SX1/ascsSX1.control.script
HALT_SCRIPT /opt/cmcluster/conf/SX1/ascsSX1.control.script
SERVICE_NAME ascsSX1_enqmon
SERVICE_FAIL_FAST_ENABLED NO
SERVICE_HALT_TIMEOUT 60
vi ascsSX1.control.script
VG[0]="vgusrsapSX1_02"
LV[0]="/dev/vgusrsapSX1_02/lvusrsapSX1_02"; \
80 Step-by-Step Cluster Conversion