Managing Serviceguard Extension for SAP on Linux (IA64 Integrity and x86_64), February 2008

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3142
test_return 52
}
# END OF CUSTOMER DEFINED FUNCTIONS
IS500 Installation Step:
Distribute the Serviceguard package ascii files to all cluster nodes.
Copy all Serviceguard configuration files in directory ${SGCONF}/<SID>
from this node into the same directory on all other cluster nodes.
Also copy file ${SGCONF}/sap.functions from this host into the same
directory on all cluster nodes.
IS510 Installation Step:
Use cmapplyconf(1m) to add the newly configured package(s) to the
cluster. cmapplyconf -P verifies the Serviceguard package
configuration, updates the binary cmlconfig file and distributes the
binary file to all cluster node.
cmapplyconf –v –P ${SGCONF}/<SID>/db.config
NOTE If you plan to use the Serviceguard (sapnfs) package specify this
package in the last position of the cmapplyconf command. Later, if you
force a shutdown of the whole cluster with cmhaltcl -f this package is the
last one stopped. This prevents global directories from disappearing
before all SAP components in the cluster have completed their shutdown.
IS515 Installation Step:
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.