Modular Package Support in Serviceguard for Linux and ECM Toolkit

For e.g. In the Apache package configuration file

PRIORITY 40

In the Tomcat package configuration file

PRIORITY 20

This is to ensure that if the Apache package fails, it will bring down the Tomcat package along with

it since it has higher priority than the Tomcat package, and both packages will be started in the

appropriate order on the adoptive node.

Apply the configuration of both the packages using cmapplyconf command.

Start the Tomcat package and then the Apache package.

Features available in Serviceguard 11.19

This section contains the features available for toolkit modular packages with Serviceguard 11.19

Package Maintenance mode

Serviceguard package maintenance provides the capability of doing maintenance on a package

while the package is still up in the cluster. This allows the user to perform maintenance on

individual components in a package. For example, modifying a service without bringing down the

rest of the components in the package, like other services and resources in the package.

In package maintenance mode, Serviceguard will turn off all the monitoring of package

components namely subnets, services, ems resources, package dependency failures etc. The

package will not automatically fail over or halt, for any failure condition that may occur when the

package is in this maintenance mode. When the package is in this mode, Serviceguard will turn

off monitoring of all package components which means that package manager will not react to any

failures that may occur.

The following steps need to be executed to perform maintenance of a service on a package.

1) cmhaltpkg pkg1

Halt the package if the package is already running.

2) cmmodpkg –m on pkg1

This operation would place the package pkg1 in the maintenance mode.

3) cmrunpkg –m sg/package_ip [-e module_name][-n node_name] package_name

Run the package up to and including the module sg/package_ip. To pick the right module name

here, the user needs to be aware of the operation sequence of the package and also the relation

between the module name and module script name, which can be obtained by looking at the

current package configuration using cmgetconf. The “-e” option in the command provides the

module name that needs to be excluded from the package run sequence, the “-e” module needs to

come before the “-m” module in the package run sequence.

4) Do manual maintenance on the package.