Configuring Veritas Multi-node Packages

There are two types of multi-node packages that work with the Veritas Cluster File System (CFS): SG-CFS-DG-id# for disk groups, which you configure with the cfsdgadm command; and SG-CFS-MP-id# for mount points, which you configure with the cfsmntadm command. Each package name will have a unique number, appended by Serviceguard at creation. Serviceguard automatically creates each package’s configuration file, its run and halt scripts, and its control script. See “Creating a Storage Infrastructure with Veritas Cluster File System (CFS)”.

	NOTE: Check the Serviceguard, SGeRAC, and SMS Compatibility and Feature Matrix and the latest Release Notes for your version of Serviceguard for up-to-date information about support for CFS (http://www.docs.hp.com -> High Availability -> Serviceguard).

	CAUTION: Once you create the disk group and mount point packages, it is critical that you administer these packages using the cfs commands, including cfsdgadm, cfsmntadm, cfsmount, and cfsumount. Non-CFS commands could cause conflicts with subsequent command operations on the file system or Serviceguard packages.

The package can be configured to run on a subset of the cluster nodes. It can be halted or started on a specific node or nodes.

	NOTE: The disk group and mount point multi-node packages do not monitor the health of the disk group and mount point. They check that the packages that depend on them have access to the disk groups and mount points. If the dependent application package loses access and cannot read and write to the disk, it will fail; however that will not cause the DG or MP multi-node package to fail.Do not edit configuration files for the Serviceguard-supplied packages VxVM-CVM-pkg, SG-CFS-pkg, SG-CFS-DG-id#, or SG-CFS-MP-id#. Create VxVM-CVM-pkg and SG-CFS-pkg by means of the cmapplyconf command. Create and modify SG-CFS-DG-id# and SG-CFS-MP-id# using the cfs* commands listed in Appendix A “Serviceguard Commands”.

In the case of a multi-node package, if you set “auto_run” to yes, an instance can start on a new node joining the cluster. Otherwise, it will not.