Managing Serviceguard A.11.20, March 2013

modular CFS package configuration file created using the sg/cfs_all template. CVM must be
up and running to create, modify, or run modular CFS packages.
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 210).
You can also configure disk groups and mount points in separate packages.
• 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.
(Shared storage required by the snapshot can also be consolidated in the same package.)
IMPORTANT: You must configure the required dependencies (if any) for modular CFS packages:
• For mount point packages - if the disk group used by the mount point is configured in a different
package, then you must configure the dependency of the disk group package explicitly in the
mount point package.
• For checkpoint packages - you must configure the dependency of the mount point package
explicitly in the checkpoint package.
• For snapshot packages - you must configure the dependency of the mount point package
explicitly in the snapshot package. Also, If the disk group used by the snapshot is configured
in a different package, then you must configure the dependency of the disk group package
explicitly in the snapshot 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 groups, CFS mount points, CFS storage checkpoints,
and snapshots required by an application 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 218).
For instructions on creating modular CFS packages, see:
• “Creating Modular Disk Group and Mount Point Packages” (page 210).
• “Creating Modular Checkpoint and Snapshot Packages for CFS” (page 212).
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
node_name node3
node_name node4
210 Building an HA Cluster Configuration