HP Serviceguard manual Cfsmountoptions

Models: Serviceguard

1 407
Download 407 pages 39.81 Kb
Page 318
Image 318

Table 15 Types of Changes to Packages (continued)

Change to the Package

Change

concurrent_vgchange_operations, deactivation_retry_count, enable_threaded_vgchange: modular package

Change cvm_activation_cmd

Add, change, or delete pev_: modular package

Change package auto_run

Add or delete a configured dependency

Add CFS packages

Change modular CFS package parameters:

cvm_activation_mode for Disk group packages

cfs_mount_options,

cfs_primary_policy for Mount Point packages

ckpt_mount_options, ckpt_primary_policy for

Checkpoint packages

Add a generic resource of evaluation type during_package_start

Add a generic resource of evaluation type before_package_start

Required Package State

Package can be running.

These changes in themselves will not cause any volume group to be activated or deactivated.

Package must not be running.

Package can be running.

Package can be running. See “Choosing Switching and Failover Behavior” (page 132).

Both packages can be either running or halted.

Special rules apply to packages in maintenance mode; see “Dependency Rules for a Package in Maintenance Mode or Partial-Startup Maintenance Mode ” (page 289).

For dependency purposes, a package being reconfigured is considered to be UP. This means that if pkgA depends on pkgB, and pkgA is down and pkgB is being reconfigured, pkgA will run if it becomes eligible to do so, even if pkgB's reconfiguration is not yet complete.

HP recommends that you separate package dependency changes from changes that affect resources and services that the newly dependent package will also depend on; reconfigure the resources and services first and apply the changes, then configure the package dependency.

For more information see “About Package Dependencies” (page 137).

The SG-CFS-pkgpackage must be running, before a modular CFS package can be started. For information on modular CFS packages, see “Creating Modular Disk Group and Mount Point Packages” (page 205).

For legacy style packages, before you can add an SG-CFS-DG-id#disk group package, the SG-CFS-pkgCluster File System package must be up and running.

Before you can add an SG-MP-id#mount point package to a node, the SG-DG-id#disk group package must be up and running on that node.

Package can be running. See “Online reconfiguration of modular CFS package parameters” (page 211).

Package can be running provided the status of the generic resource is not 'down'. For information on online changes to generic resources, see “Online Reconfiguration of Generic Resources” (page 136).

Package can be running if the status of generic resource is 'up', else package must be halted.

Remove a generic resource Change the

generic_resource_evaluation_type

Package can be running.

Package can be running if the status of generic resource is 'up'.

Not allowed if changing the generic_resource_evaluation_type causes the package to fail.

318 Cluster and Package Maintenance

Page 318
Image 318
HP Serviceguard manual Cfsmountoptions