Managing Serviceguard Extension for SAP, December 2007

Step-by-Step Cluster Conversion
SAP Preparation
Chapter 3 87
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.
In the /etc/cmcluster/<SID>/<pkg_name>.control.script file(s),
there is a section that defines a virtual IP address array. All virtual IP
addresses specified here will become associated to the SAP and database
instances that are going to be installed. Edit the array and create at least
one virtual IP:
IP[0]=xxx.xxx.xxx.xxx
Distribute the edited package templates to all cluster nodes.
Only if the SAP components are meant to be able to run on different
nodes, several packages have to be created using different virtual IPs.
NW04S440 Preparation Step:
Create a debug file on the system on which the installation takes place.
The debug file allows manual SAP instance shutdown and startup
operations during installation.
touch /etc/cmcluster/<SID>/debug
It does not matter, if the system is meant to be run in a multi-tier fashion
that separates the database from the ASCS instance by running them on
different cluster nodes during normal operation. For convenience, all
installation steps should be done on a single machine. Due to the
virtualization, it is easy to separate the instances later on.
NW04S445 Preparation Step:
The package configuration needs to be applied and the package started.
This step assumes that the cluster as such is already configured and
started. Please refer to the Managing Serviceguard user’s guide if more
details are required.
cmapplyconf -P /etc/cmcluster/C11/dbcijciC11.config
cmrunpkg -n <installation_host> dbcijciC11
All virtual IP address(es) should now be configured. A ping command
should reveal that they respond to communication requests.