You can disable package switching to particular nodes by using the -noption of the cmmodpkg command. The following prevents pkg1 from switching to node lptest3:

cmmodpkg -d -n lptest3 pkg1

To permanently disable switching so that the next time the cluster restarts, the change you made in package switching is still in effect, change the auto_run flag in the package configuration file, then re-apply the configuration. (See “Reconfiguring a Package on a Running Cluster ” (page 311).)

Maintaining a Package: Maintenance Mode

Serviceguard A.11.20 provides two ways to perform maintenance on components of a modular, failover package while the package is running. (See Chapter 6 (page 227) for information about package types and modules.) These two methods are called maintenance mode and partial-startup maintenance mode.

NOTE: If you need to do maintenance that requires halting a node, or the entire cluster, you should consider Live Application Detach; see “Halting a Node or the Cluster while Keeping Packages Running” (page 280).

Maintenance mode is chiefly useful for modifying networks, generic resources, and EMS resources used by a package while the package is running.

See “Performing Maintenance Using Maintenance Mode” (page 289).

Partial-startup maintenance mode allows you to work on package services, file systems, and volume groups.

See “Performing Maintenance Using Partial-Startup Maintenance Mode” (page 290).

Neither maintenance mode nor partial-startup maintenance mode can be used for legacy packages, multi-node packages, or system multi-node packages.

Package maintenance does not alter the configuration of the package, as specified in the package configuration file.

For information about reconfiguring a package, see “Reconfiguring a Package” (page 310).

NOTE: In order to run a package in partial-startup maintenance mode, you must first put it in maintenance mode. This means that packages in partial-startup maintenance mode share the characteristics described below for packages in maintenance mode, and the same rules and dependency rules apply. Additional rules apply to partial-startup maintenance mode, and the procedure involves more steps, as explained under Performing Maintenance Using Partial-Startup Maintenance Mode.

Characteristics of a Package Running in Maintenance Mode or Partial-Startup Maintenance Mode

Serviceguard treats a package in maintenance mode differently from other packages in important ways. The following points apply to a package running in maintenance mode:

Serviceguard ignores failures reported by package services, subnets, generic resources, EMS resources, and file systems; these will not cause the package to fail.

NOTE: But a failure in the package control script will cause the package to fail. The package will also fail if an external script (or pre-script) cannot be executed or does not exist.

The package will not be automatically failed over, halted, or started.

A package in maintenance mode still has its configured (or default) weight, meaning that its weight, if any, is counted against the node's capacity; this applies whether the package is up or down. (See “About Package Weights” (page 144) for a discussion of weights and capacities.)

Managing Packages and Services 287

Page 287
Image 287
HP Serviceguard manual Maintaining a Package Maintenance Mode, Cmmodpkg -d -n lptest3 pkg1