Logon as root on the primary host.
Recommendation
Set AUTO_VG_ACTIVATE=0 in /etc/lvmrc. Edit the custom_vg_activation() function if needed. Distribute the file to all cluster
nodes.
Recommendation
Set AUTOSTART_CMCLD=1 in /etc/rc.config.d/cmcluster. Distribute the file to all cluster nodes.
Create cluster configuration file in /etc/cmcluster:
cmquerycl -v -C /etc/cmcluster/sapr3.conf [-n <nodename> ...]. |
Customize the cluster configuration file. Specify the volume
groups listed in Step Title not available. You might need
to increase the timing parameters.
Obsolete.
Specify package name, node names and subnets in the package configuration
files db.conf and ci.conf or in dbci.conf.
If you implement the one package concept:The standard package
name is dbci<SID>. If you want to use different variables
follow OS530.If you implement the two package concept:
The standard package names are db<SID> and ci<SID>. If you want to use different names here, make
sure that you also specified the appropriate variables in Step Title not available.
Specify the package control script names in the package configuration files:
For one package concept specify in /etc/cmcluster/<SID>/dbci.conf:
RUN_SCRIPT /etc/cmcluster/<SID>/dbci.cntl
HALT_SCRIPT /etc/cmcluster/<SID>/dbci.cntl \
|
For two package concept specify in /etc/cmcluster/<SID>/db.conf:
RUN_SCRIPT /etc/cmcluster/<SID>/db.cntl
HALT_SCRIP /etc/cmcluster/<SID>/db.cntl
|
For two package concept specify in /etc/cmcluster/<SID>/ci.conf:
RUN_SCRIPT /etc/cmcluster/<SID>/ci.cntl
HALT_SCRIPT /etc/cmcluster/<SID>/ci.cntl
|
For each Application Server package specify in /etc/cmcluster/<SID>/ap<SID><ASNR>.conf:
RUN_SCRIPT /etc/cmcluster/PRC/ap<SID><ASNR>.cntl
HALT_SCRIPT /etc/cmcluster/PRC/ap<SID><ASNR>.cntl
|
Follow the directions in Steps Title not available and Title not available to define volume groups, logical volumes,
IP addresses and subnets in the package control scripts dbci.cntl,
db.cntl, ci.cntl and ap<SID><ASNR>.cntl
as appropriate.
Fill the IP[*] and SUBNET[*] array with the IP addresses and subnet addresses
that the package is attached to. For example a 1-pkg control script
dbci.cntl:
IP[0]="15.27.218.238"
SUBNET[0]="15.27.216.0"
|
The filesystems you specify in the LV[*], FS[*] and FS_MOUNT_OPT[*] array are not identical to the filesystems that
are exported. For example:
LV[0]="/dev/vgDBPRD/lvoracle"; FS[0]="/oracle/PRD"; FS_MOUNT_OPT[0]="-o rw"
LV[1]="/dev/vgDBPRD/lvora805"; FS[1]="/oracle/805_64"; FS_MOUNT_OPT[1]="-o rw"
LV[2]="/dev/vgDBPRD/lvsapmnt"; FS[2]="/export/sapmnt/PRD"; FS_MOUNT_OPT[2]="-o rw"
LV[3]="/dev/vgPRC/lvusrsap"; FS[3]="/usr/sap/PRD/DVEBMGS20"; FS_MOUNT_OPT[3]="-o rw"
LV[4]="/dev/vgTRANS/lvtrans"; FS[4]="/export/usr/sap/trans"; FS_MOUNT_OPT[4]="-o rw"
|
The follwing steps will customize the hanfs.<xxx> scripts.
It will customize all required directories for the usage of the
HA-NFS. All directories that are handled by the automounter must
be exported by the scripts if they are part of the packages, for
example:
/export/sapmnt/<SID>
/export/usr/sap/trans
Exported directories can usually be found beneath the special
export directory /export. The directories to be exported are specified
including their export options, using the XFS[*] array the hanfs.<xxx> script
out of the HA-NFS toolkit. This script is called within the runtime
by the standard ServiceGuard contol script dbci.cntl, db.cntl.
The transport
directory is also part of the package in standard installations.
In those cases it also has to be mentioned here. On INFORMIX installations
without local database executables, access must be granted to the
database filesystem too.
Only allow access from machines inside of the cluster that
are configured as backup hosts and additional application servers
of this specific SAP R/3 system. Make sure to allow access for all
addresses that the servers use so they can reach the directories.
Allowing the right addresses is essential if your hosts use more
than one LAN card.
Example of an hanfs.db file:
#!/usr/bin/sh
# A.11.x $Revision: 1.1 $ $Date: 2001/09/11 11:52:30 $
# **********************************************************************
# MC/SERVICEGUARD NFS TOOLKIT CONTROL SCRIPT (template) |
# This script contains NFS specific environment variables and functions that used to be defined/incorporated in the MC/SG package control script before the AR1201 release. |
# Separating this script from the MC/SG package control script provides two key benefits: 1. No need to roll with a MC/SG new release. 2. Provides the solution for integrating MC/SG NFS Toolkit with other MC/SG partner software. |
# NFS: Specifies all exported NFS directories with export options. The directories must be defined in the above mounted file system FS list. |
# These variables are used by the command "exportfs -i" to export the file systems and the command "exportfs -u" to unexport the file systems.# Example: XFS[0]="-o ro /pkg1" |
# Example: XFS[1]="/pkg2" |
# XFS[0]="-o root=hpcc006:hpcc008:hpcc071:trans:db:sap /export/usr/sap/trans" |
# XFS[1]="-o root=hpcc006:hpcc008:hpcc071:trans:db:sap /export/sapmnt/<SID>"# XFS[1]="-o root=hpcc006:hpcc008:hpcc071:trans:db:sap /export/informix/<SID>" |
# The usage of the HA-NFS monitors supplied by the HA-NFS toolkit are optional. Refer to the HA-NFS documentation on how to configure process monitoring of the NFS processes. |
To enable parameter export of variables that are set within
the package control script add the following line "set -a" to the top of each ServiceGuard control script, specifically
at the top line within each package control file:
/etc/cmcluster/<SID>/dbci.cntl
/etc/cmcluster/<SID>/db.cntl
/etc/cmcluster/<SID>/ci.cntl
/etc/cmcluster/<SID>/ap<SID><NR>.cntl
Example:
# "A.11.13 $Date: 02/12/2001 $". |
# HIGH AVAILABILITY PACKAGE CONTROL SCRIPT (template) |
# Note: This file MUST be edited before it can be used. |
# UNCOMMENT the variables as you set them. |
To enable the SAP R/3 specific scripts change the customer_defined_commands sections of the package control script(s):
For the one package concept:
function customer_defined_run_cmds
{
/etc/cmcluster/<SID>/sapdbci.cntl startDBCI <SID>
test_return 51
}
function customer_defined_halt_cmds
{
/etc/cmcluster/<SID>/sapdbci.cntl stopDBCI <SID>
test_return 52
}
|
For a two package concept:
Use the commands stopDB, startDB in file db.cntl or stopCI, startCI in ci.cntl respectively.
For an Application Server
package in ap<SID><ASNR>.cntl:
{
function customer_defined_run_cmds
# ADD customer defined run commands.
/etc/cmcluster/<SID>/sapap.cntl startAP <ASNR> <SID> <SIDADM>
test_return 51
}
function customer_defined_halt_cmds
{
# ADD customer defined halt commands.
/etc/cmcluster/<SID>/sapap.cntl stopAP <ASNR> <SID> <SIDADM>
test_return 52
} |
If you use ORACLE database:
Remove INFORMIX specific files from the cluster directory:
rm /etc/cmcluster/customer.sh /etc/cmcluster/customer.csh |
If you use INFORMIX database:
Move INFORMIX specific files into
the INFORMIX home directory. Read the command example carefully.
Make sure you move the 'dot files'. For example:
mv /etc/cmcluster/customer.sh /home/informix/.customer.sh
mv /etc/cmcluster/customer.csh /home/informix/.customer.csh
chown informix:informix /home/informix/.customer.sh
chown informix:informix /home/informix/.customer.csh
|
Copy all integration files below /etc/cmcluster to the other cluster hosts using rcp(1).
Create the binary cluster configuration file and distribute
it using cmapplyconf(1m).
If you plan to use an additional package for the transport
directory:
Specify
this package in the last position of the cmapplyconf command. Later, if you force a shutdown of the
whole cluster with cmhaltcl -f, the package with the transport directory is the
last one stopped. This prevents the transport directory from disappearing
before all SAP R/3 systems in the cluster have completed their shutdown.
Printable version
