e.The volume group attribute. Specify the required logical volume group name to the volume group attribute.

f.If other Serviceguard modules are included, then specify values for the included module attributes accordingly.

g.If any application module is included, then list values for the included module attributes accordingly.

NOTE: If the EMS disk monitor is used as a package resource, then the NO_TIMEOUT value must not be used. If used, the package shutdown hangs if there is no access from the host to the package disks.

4.Copy the environment file template /opt/cmcluster/toolkit/SGCA/xpca.env to the dts/dts/dts_pkg_dir directory specified earlier.

# cp /opt/cmcluster/toolkit/SGCA/xpca.env \ /etc/cmcluster/<package_name>

5.Edit the environment file, xpca.env, as follows:

a.If necessary, add the path where the Raid Manager Software binaries have been installed to the PATH environment variable. If the software is in the usual location, /usr/bin, then uncomment the line in the script.

b.Uncomment the behavioral configuration environment variables that begin with AUTO_. It is recommended that you retain the default values of these variables unless there is a specific business requirement to change them. For more information on these variables, see Appendix A (page 475).

c.Uncomment the PKGDIR variable and set it to the full path name of the directory where this environment file has been placed. This directory must be unique for each package. For example:

PKG_DIR=“/etc/cmcluster/<package_name>”

d.Uncomment the DEVICE_GROUP variable and set it to this package’s Raid Manager device group name, as specified in the Raid Manager configuration file.

e.Uncomment the HORCMPERM variable and use the default value MGRNOINST if the Raid Manager protection facility is not used or disabled. If the Raid Manager protection facility is enabled, set it to the name of the HORCM permission file.

f.Uncomment the HORCMINST variable and set it to the Raid Manager instance name used by Metrocluster/Continuous Access.

g.Uncomment the FENCE variable and set it to either ASYNC, NEVER, or DATA according to your business requirements or special Metrocluster requirements. This variable is used to compare with the actual fence level returned by the array.

h.If you are using asynchronous data replication, set the HORCTIMEOUT variable to a value greater than the side file timeout value configured with the Service Processor (SVP), but lesser than the run_script_timeout set in the package configuration file. The default setting is the side file timeout value + 60 seconds.

i.Uncomment the CLUSTER_TYPE variable and set it to metro.

6.Distribute this Metrocluster environment file to other nodes in the cluster under the same directory by using FTP, RCP or SCP.

rcp -p /etc/cmcluster/<package_name>/* \ other_node:/etc/cmcluster/<package_name>

See the example script Samples/ftpit to determine how to semi-automate the copy operating using FTP. This script assumes that the package directories already exist on all nodes. Using FTP may be preferable at your organization, since it does not require the use of an .rhosts file for root. Root access using the .rhosts may create a security issue.

Configuring Modular Packages 183