Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
Cluster Configuration
Chapter 3 145
IS500 Installation Step:
Distribute the package setup to all failover nodes, i.e. 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.
IS510 Installation Step:
Use cmapplyconf(1m) to add the newly configured package(s) to the
cluster.
NOTE If you plan to use a sapnfs package as central NFS service, 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.
Verify that the setup works correctly to this point. All operating system
resources should be able to switch between the hosts. To do this, you can
temporarily create debug files /etc/cmcluster/<SID>/debug. This
prevents SAP specific package operations to be executed for each node on
which this file gets created. SAP specific package operations would not
succeed at this point of the integration. Do not forget to remove all debug
files after the tests.