Modular Package Support in Serviceguard for Linux and ECM Toolkit

ManualsBrandsHP ManualsSoftwareHP Serviceguard Enterprise Cluster Master Toolkit

- 1 -

Introduction .......................................................................................................................2

Overview of modular packages............................................................................................2

Install and Configuration directory operations ...................................................................3

Setting up a modular package .............................................................................................3

Creating the package ....................................................................................................4

Modifying the package ..................................................................................................4

After halting the package ............................................................................................4

After putting the package in Toolkit Maintenance mode...................................................5

Migration from legacy to modular packages ..........................................................................5

Combinational Packages with Serviceguard 11.18 .................................................................7

Features available in Serviceguard 11.19..............................................................................8

Package Maintenance mode...........................................................................................8

Namespace conflict resolution.........................................................................................9

Cross Subnet configuration ...........................................................................................10

IPv6 Support...............................................................................................................10

Guest Application Monitoring ............................................................................................10

For more information.........................................................................................................11

Modular Package support in Serviceguard for

Linux and ECM Toolkits

Summary of content (11 pages)

PAGE 1
Modular Package support in Serviceguard for Linux and ECM Toolkits Introduction .......................................................................................................................2 Overview of modular packages ............................................................................................2 Install and Configuration directory operations ...................................................................3 Setting up a modular package ..........................................
PAGE 2
Introduction This whitepaper describes the support for modular packages in toolkits used in Serviceguard for HPUX (SG) and Serviceguard for Linux (SG/LX) 11.18 and 11.19 environments. This document is intended for users who want to install and configure supported HP-UX applications (e.g., Oracle, HP Apache, HP Tomcat, HP CIFS, Sybase ASE, IBM DB2 and MySQL) and Linux applications (e.g., Oracle, NFS, MySQL, PostgreSQL, Sendmail, Samba, Apache, or Tomcat) using modular packages.
PAGE 3
Note: In the case of NFS lock_migration.sh External Script for Lock Migration These files are installed in the locations below: On HP-UX: $SGCONF/modules/ecmt// $SGCONF/modules/ecmt//.1 $SGCONF/scripts/ecmt//tkit_module.sh $SGCONF/scripts/ecmt//tkit_gen.sh where $SGCONF is /etc/cmcluster On Linux: $SGCONF/modules/tkit// $SGCONF/modules/tkit//.1 $SGCONF/scripts/tkit//tkit_module.sh $SGCONF/scripts/tkit//tkit_gen.
PAGE 4
For example, the service parameters in the package configuration file created on Linux with the apache module included will be preset with the below values: service_name service_cmd service_apache “$SGCONF/scripts/tkit/apache/tkit_module.sh apache_monitor" Please refer to Chapter 6 of the document Managing Serviceguard Fifteenth Edition for details on how to modify the package configuration file at http://docs.hp.com/en/ha.html.
PAGE 5
modules to the package configuration file. The modified package configuration then needs to be reapplied. The sequence of operations for modifying the package is: 1) #cmmakepkg –i pkg_old.conf –m pkg_new.conf This command adds a module, if required, to the already existing package configuration file pkg_old.conf and creates a new package configuration file pkg_new.conf. The module added can be any supported module such as a Serviceguard module or another toolkit module.
PAGE 6
1) #cmmigratepkg –p legacy_pkgname [-s] -o modular1.ascii Create a modular ASCII file as shown above, from the already existing legacy package. The ‘–s’ is optional and has been given to comment out the service part from the configuration file, so that the pre-configured service parameters from the toolkit module can be included into the package configuration file. 2) #cmmakepkg –i modular1.ascii -m tkit// -t modular2.
PAGE 7
comment out the service part from the legacy package configuration file before using the cmmigratepkg command. b) Add the toolkit module to the new modular configuration file using "cmmakepkg -i -m [-t] " option. c) Modify TKIT_DIR and other toolkit specific parameters in the modular package conf file. d) Apply the modular package configuration file. 4) Migration of modular packages that do not use toolkit modules.
PAGE 8
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.
PAGE 9
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.
PAGE 10
Cross Subnet configuration All the ECM toolkits and SG/LX toolkits support cross subnet environment. For more information on cross subnet configuration, 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. IPv6 Support All the Linux and HP-UX toolkits are IPv6 complaint. However, IPv6 support is only possible if the application provides it internally.
PAGE 11
SERVICE_NAME[1]=v-smp1_guest_ORACLE_TEST0_service SERVICE_CMD[1]=/usr/lbin/cmappmgr –node v-smp1 –service "/etc/cmcluster/pkg/ORACLE_TEST0/toolkit.sh monitor" – cmappserver_timeout 152 SERVICE_RESTART[1]="-r 2" Note that the guest application service in this example defines a timeout of 152 seconds for the cmappserver-cmappmgr connection. This is optional. But kindly note that this timeout duration entirely depends on the user configuration of the virtual machine.