Managing Serviceguard Nineteenth Edition, Reprinted June 2011

SG-CFS-DG-1
Creating Volumes
1. Make log_files volume on the logdata disk group:
vxassist -g logdata make log_files 1024m
2. Use the vxprint command to verify:
vxprint log_files
disk group: logdata
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0 PUTIL0
v log_files fsgen ENABLED 1048576 - ACTIVE - -
pl log_files-01 fsgen ENABLED 1048576 - ACTIVE - -
sd ct4t0d6-01 fsgen ENABLED 1048576 - ACTIVE - -
Managing Disk Groups and Mount Points Using Modular Packages
In a Serviceguard cluster, many disk group and mount point packages are created for applications
using CVM and CFS and the applications are dependent on these packages. These disk group
and mount point packages are configured for activating disk groups and mounting the volumes.
For an application in a cluster, Serviceguard provides the flexibility to combine the CVM disk
groups and CFS mount points into a single modular package. This feature is supported from Veritas
CVM/CFS version 5.0.1 with HP Serviceguard A.11.20 April 2011 patches and later. As a result,
the number of packages used for configuring disk groups and mount points in that cluster reduces
significantly in comparison to the packages used for configuring CVM disk groups and CFS mount
points in the legacy style of packaging. For example, an application requiring 100 disk groups,
100 mount points, 10 check points, and 10 snapshot packages would translate to a total of 220
packages in the legacy style of packaging. However, in the modular style of packaging, the 100
disk groups and 100 mount point packages can be consolidated into one single package, 10
check points into one package, and 10 snap shots into one package, reducing the total number
of packages to three, thereby aiding manageability of packages in that cluster. Also, the number
of packages available for configuring applications in the cluster increases. The high availability
cluster information displayed by the cmviewcl command is more compact. Note that to create
or modify modular CFS packages, CVM should be up and running.
CAUTION: While Serviceguard supports up to 300 configured packages, it is advised to maintain
a manageable level when consolidating the disk groups and mount points in the package. The
more disk groups and mount points in a package, the longer it takes that package to start up and
shutdown, which may have an effect on any other packages that have dependencies on this
package.
NOTE: Serviceguard supports online addition/removal of nodes from modular CFS packages.
Specifying services and resources are not recommended for modular CFS packages. You cannot
create or manage modular CFS packages for disk groups and mount points using VEA GUI; you
can use Serviceguard Manager to do it.
External scripts and External Pre-scripts can be configured as a part of Modular CFS packages. It
is recommended to keep the execution time of these scripts as short as possible. If the script execution
time is huge then it might take a long time to start up the package resulting in bringing down the
performance. See “About External Scripts” (page 142) for more information on external scripts.
Just like the legacy packages, the modular packages are dependent on system multi-node package,
SG-CFS-pkg. For more information, see “Preparing the Cluster and the System Multi-node Package”
(page 193) .
You cannot manage modular CFS packages using the legacy CFS commands cfsdgadm,
cfsmntadm, cfsmount, and cfsumount. You must use the cmmakepkg, cmapplyconf,
cmrunpkg, cmhaltpkg, and cmdeleteconf commands. The cmmakepkg command enables
Configuring the Cluster 195