Table 8 Differences between Legacy CFS and Modular CFS (continued)

Legacy

Modular

Legacy CFS packages can be created using the Veritas Enterprise Administrator (VEA).

Each package can only correspond to one disk group or one mount point leaving fewer packages for other purposes, so if you have many packages they may take a longer time for startup, shutdown, cmviewcl, etc.

You must not manually edit the packages, but use the cfs commands to edit the package. The disadvantage is that if you have multiple packages, you must edit each of them using the commands.

When a large number of packages are configured , the cluster information displayed by the cmviewcl command contains too many entries.

using cmmakepkg, cmcheckconf, cmapplyconf, cmdeleteconf, cmrunpkg, cmhaltpkg, or cmmodpkg commands.

Modular CFS packages can be created using Serviceguard Manager.

Multiple disk groups and mount points can be consolidated into a single package. This significantly reduces the number of packages used, leaving more packages for other applications, thus improving the overall system performance for startup, shutdown, cmviewcl, etc.

Multiple checkpoints and snapshots can also be merged into individual modular checkpoint and snapshot packages. See “Guidelines for Migrating from Legacy CFS Package to Modular CFS Package” (page 213) for recommendation.

Provides improved manageability of the package by allowing you to edit the parameters in the package configuration file. Also, allows online addition, deletion, and/or modification of CFS parameters. See “Online reconfiguration of modular CFS package parameters” (page 211).

The high availability cluster information displayed by the cmviewcl command output is more compact.

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

Operation

Configure and activate a disk group in a package

Delete a disk group in a package

Commands used by legacy style

cfsdgadm add

cfsdgadm activate

cfsdgadm deactivate

cfsdgadm delete

Equivalent commands in modular style

cmmakepkg –m sg/cfs_all <package_ascii_file>

Edit the package configuration file for the disk group parameters

cmcheckconf -P <package_ascii_file>

cmapplyconf -P <package_ascii_file>

cmrunpkg <package name>

Remove the corresponding cvm_disk_group entry from the configuration file

cmapplyconf

For information on the parameters that can be added, removed, or modified online, see “Online reconfiguration of modular CFS package parameters” (page 211).

Displaying the disk group cfsdgadm show_packagecmviewcl –v –p <package_name>

package attributes

cfsdgadm show_autorun

 

 

cfsdgadm display

200 Building an HA Cluster Configuration

Page 200
Image 200
HP Serviceguard manual Operational commands for Legacy CFS and Modular CFS