Managing Serviceguard Nineteenth Edition, Reprinted June 2011
Table 8 Differences between Legacy CFS and Modular CFS
ModularLegacy
Unlike the legacy CFS packages, the modular CVM disk
groups and CFS mount points cannot be created or managed
The CFS legacy disk groups and mount points can be
created or managed only by using the cfsdgadm,
cfsmntadm, cfsmount, or cfsumount.
by using the cfs commands. These are created and managed
using cmmakepkg, cmcheckconf, cmapplyconf,
cmdeleteconf, cmrunpkg, cmhaltpkg, or cmmodpkg
commands.
Multiple disk groups and mount points can be consolidated
into a single package. This significantly reduces the number
Each package can only correspond to one disk group
or one mount point leaving fewer packages for other
of packages used, leaving more packages for otherpurposes, so if you have many packages they may take
a longer time for startup, shutdown, cmviewcl, etc. applications, thus improving the overall system performance
for startup, shutdown, cmviewcl, etc.
You must not edit the package using the cfs commands, but
edit the parameters in the package configuration file if you
You must not manually edit the packages, but use the
cfs commands to edit the package. The disadvantage
want to manage the package. Also, if you have multiple diskis that if you have multiple packages, you must edit each
of them using the commands. groups and mount points in a package, you must halt the
entire package if you want to modify one of them.
The high availability cluster information displayed by the
cmviewcl command output is more compact.
When a large number of packages are configured , the
cluster information displayed by the cmviewcl
command contains too many entries.
Listed below are some of the operational differences in terms of commands used for creating or
managing legacy and modular CFS packages. For usage, syntax, and keyword descriptions, see
the respective Serviceguard man page of each command.
Table 9 Operational commands for Legacy CFS and Modular CFS
Equivalent commands in modular styleCommands used by legacy styleOperation
cfsdgadm addCreate and run a disk
group package
• cmmakepkg –m sg/cfs_all
<package_ascii_file>
Edit the package configuration file for the disk
group parameters
cfsdgadm activate
• cmapplyconf -P <package_ascii_file>
• cmrunpkg <package name>
NOTE: For adding another disk group to an
existing modular CFS package, edit the
configuration file to add the disk group
parameters and run cmapplyconf. This operation
can be performed only in the offline mode, i.e.,
when the package is not running.
If it is the last disk group in the package:cfsdgadm deactivateHalt and delete a disk
group package
cmhaltpkgcfsdgadm delete
cmdeleteconf
If it is not the last disk group in the package:
• cmhaltpkg
• Remove the corresponding cvm_disk_group
entry from the configuration file
• cmapplyconf
• cmrunpkg
cmviewcl —v —p <package_name>cfsdgadm show_packageDisplaying the disk group
package attributes
cfsdgadm show_autorun
cfsdgadm display
Configuring the Cluster 191