Modular Package Support in Serviceguard for Linux and ECM Toolkit

5) cmhaltpkg pkg1

This will halt the package pkg1 but will not halt or cleanup any services or other components that

may have been started manually in the maintenance mode. OR

6) cmhaltpkg –s pkg1

This will halt the package and run the halt scripts up to the module specified with “-m” option in

cmrunpkg.

7) cmrunpkg pkg1

This step is optional, but it is good to make sure that the package can fully come up without any

problems after maintenance has been completed. It is recommended to the users to bring up/and

halt the package modules individually and ensure that the package can fully come up, before

moving it out of maintenance mode.

8) cmhaltpkg pkg1

Need to do this only if step 7 was executed.

9) cmmodpkg –m off pkg1

This operation will switch the package back to its normal mode and Serviceguard.

Note: This feature is available from Serviceguard 11.19 onwards.

Serviceguard Toolkit mandates the use of symmetric halt (cmhaltpkg with –s option) while using the

Serviceguard package maintenance mode.

For more information on Package maintenance mode refer the manual “Managing Serviceguard”

at http://docs.hp.com/en/ha.html. For Linux, refer to the manual “Managing HP Serviceguard for

Linux” at http://docs.hp.com/en/ha.html.

Note: To provide backward compatibility, the toolkit maintenance mode, which also provides

maintenance feature, will be supported in Serviceguard 11.19 also.

Namespace conflict resolution

With Serviceguard 11.19, two applications can be packaged together in a single package. In

Serviceguard 11.18, two application modules having attributes with the same names like

MONITOR_INTERVAL could not be included in the same package configuration files. This

namespace conflict has been resolved in Serviceguard 11.19 by prefixing all toolkit attributes with

the module name in the package configuration file, for e.g., the MONITOR_INTERVAL attribute of

HP Apache and Tomcat applications are represented as

ecmt/apache/apache/MONITOR_INTERVAL and ecmt/tomcat/tomcat/MONITOR_INTERVAL.

For e.g., HP Apache and HP Tomcat can be combined by including both application modules in a

single package configuration file

# cmmakepkg –m ecmt/apache/apache –m ecmt/tomcat/tomcat pkg.conf

‘pkg.conf’ now contains attributes of both the Apache and Tomcat toolkit.