Managing Serviceguard Nineteenth Edition, Reprinted June 2011

you to create a package configuration file. The command uses the sg/cfs module that contains
attributes for CVM disk groups, mount points, storage snapshot, and checkpoint parameters. A
modular CFS package template can be generated using the sg/cfs_all template. The modular
CFS packages run as a multi-node package and have a dependency on CVM system multi-node
package, SG-CFS-pkg. The dependency on SG-CFS-pkg is automatically configured in the
modular CFS package configuration file created using the sg/cfs_all template. CVM must be
up and running when you create or modify modular CFS packages.
IMPORTANT: It is strongly recommended not to remove the dependency on SG-CFS-pkg that
is automatically configured in the package configuration file.
The cmrunpkg and cmhaltpkg commands allow you to run and halt the modular CFS packages
respectively. The SG-CFS-pkg package must be running, before the modular CFS packages can
be started.
Refer to the Serviceguard man pages for more information about the commands cmmakepkg
(1m), cmapplyconf (1m), cfsdgadm (1m), cfsmntadm (1m), cmrunpkg (1m),
cmhaltpkg (1m), and cmdeleteconf (1m).
Serviceguard enables you to consolidate resources required for an application as follows:
• You can consolidate all disk groups and mount points for an application into a single modular
package as depicted in “Creating Modular Disk Group and Mount Point Packages” (page 196).
You can also configure disk groups and mount points in separate packages. If you create the
packages separately, you must configure the dependency of the mount point package on the
disk group package explicitly in the package configuration file.
• You can consolidate all storage checkpoint packages and convert them to a single modular
package.
• You can consolidate all snapshot packages and convert them to a single modular package.
• You can consolidate disk groups and snapshots into a single modular package.
Note that the dependency on the mount point package is a must for both checkpoint and snapshot
packages.
It is recommended to configure all CVM disk group and CFS mount points using one style of
packaging, legacy or modular. It is also recommended to use modular style packaging to reduce
the number of multi-node packages consumed by CFS resources. During migration to modular
style, both legacy and modular style CFS packages of different applications might coexist but HP
strongly recommends completing the migration of all legacy CFS packages belonging to an
application to modular style for consistency of administration. For guidelines on migrating from
legacy CFS packages to modular CFS packages, see “Guidelines for Migrating from Legacy CFS
Package to Modular CFS Package” (page 202).
For instructions on creating modular CFS packages, see:
• “Creating Modular Disk Group and Mount Point Packages” (page 196).
• “Creating Modular Checkpoint and Snapshot Packages for CFS” (page 199).
Creating Modular Disk Group and Mount Point Packages
1. Create a package configuration file:
cmmakepkg -m sg/cfs_all /etc/cmcluster/cfspkg1.ascii
Package template is created.
This file must be edited before it can be used.
2. Edit the following package parameters in the cfspkg1.ascii package configuration file:
package_name cfspkg1
node_name node1
node_name node2
196 Building an HA Cluster Configuration