HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)
Table Of Contents
- HP Serviceguard Enterprise Cluster Master Toolkit User Guide
- Contents
- 1 Introduction
- 2 Using the Oracle Toolkit in an HP Serviceguard Cluster
- Overview
- Supported Versions
- Support for Oracle Database Without ASM
- Supporting Oracle ASM Instance and Oracle Database with ASM
- What is Automatic Storage Management (ASM)?
- Why ASM over LVM?
- Configuring LVM Volume Groups for ASM Disk Groups
- Sample command sequence for configuring LVM Volume Groups
- Serviceguard support for ASM on HP-UX 11i v3 onwards
- Framework for ASM support with Serviceguard
- Installing, Configuring, and Troubleshooting
- Setting up DB instance and ASM instance
- Setting up the Toolkit
- ASM Package Configuration Example
- Modifying a Legacy Database Package Using an Older Version of Oracle ECMT Scripts to use the Scripts Provided for ASM Support
- Adding the Package to the Cluster
- Node-specific Configuration
- Error Handling
- Network Configuration
- Database Maintenance
- Configuring and packaging Oracle single-instance database to co-exist with SGeRAC packages
- Configuring Oracle single-instance database that uses ASM in a Coexistence Environment
- Attributes newly added to ECMT Oracle toolkit
- Configuring a modular failover package for an Oracle database using ASM in a coexistence environment
- Configuring a legacy failover package for an Oracle database using ASM in a Coexistence Environment
- ECMT Oracle Toolkit Maintenance Mode
- Supporting EBS database Tier
- Oracle ASM Support for EBS DB Tier
- 3 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX
- Overview
- Sybase Information
- Setting up the Application
- Setting up the Toolkit
- Sybase Package Configuration Example
- Creating the Serviceguard package using Modular method
- Adding the Package to the Cluster
- Node-specific Configuration
- Error-Handling
- Network configuration
- Database Maintenance
- Cluster Verification for Sybase ASE Toolkit
- 4 Using the DB2 Database Toolkit in a Serviceguard Cluster in HP-UX
- 5 Using MySQL Toolkit in a HP Serviceguard Cluster
- MySQL Package Configuration Overview
- Setting Up the Database Server Application
- Setting up MySQL with the Toolkit
- Package Configuration File and Control Script
- Creating Serviceguard Package Using Modular Method
- Applying the Configuration and Running the Package
- Database Maintenance
- Guidelines to Start Using MySQL Toolkit
- 6 Using an Apache Toolkit in a HP Serviceguard Cluster
- 7 Using Tomcat Toolkit in a HP Serviceguard Cluster
- Tomcat Package Configuration Overview
- Multiple Tomcat Instances Configuration
- Configuring the Tomcat Server with Serviceguard
- Setting up the Package
- Creating Serviceguard Package Using Modular Method
- Setting up the Toolkit
- Error Handling
- Tomcat Server Maintenance
- Configuring Apache Web Server with Tomcat in a Single Package
- 8 Using SAMBA Toolkit in a Serviceguard Cluster
- 9 Using HP Serviceguard Toolkit for EnterpriseDB PPAS in an HP Serviceguard Cluster
- 10 Support and Other resources
- 11 Acronyms and Abbreviations
- Index

vg /dev/vg00_SYBASE0
vg /dev/vg01_SYBASE0
Define the file systems which are used by the Sybase ASE instance. Note that one of these file
systems must be the shared file system/logical volume containing the Sybase ASE home configuration
information ($SYBASE_HOME). The name of the instance is used to name the volume groups,
logical volumes, and file systems.
fs_name /dev/vg00_SYBASE0/lvol1
fs_directory /SYBASE0
fs_type "ext3"
fs_mount_opt "-o rw"
Define the service related parameters. The service name must include the Sybase ASE instance
name (that is ${ASE_SERVER}). In the following example, there is only one service for this package,
therefore, the ${ASE_SERVER} (that is SYBASE0) is assigned to the 'service_name' parameter.
service_name SYBASE_${ASE_SERVER}
service_cmd
"/opt/cmcluster/conf/scripts/ecmt/sybase/tkit_module.sh
sybase_monitor"
service_restart "-r 3"
Use the Serviceguard command, cmmodpkg, to reset the service restart couter to zero for this
parameter. The service restart counter is incremented each time the service fails. It is used to
determine when a package has exceeded its restart limit as defined by the "service_restart"
parameter in the package control script.
To reset the restart counter run the command cmmodpkg [-v] [-n node_name] -R -s
service_name package_name
After the Serviceguard environment is set up, each clustered Sybase ASE Instance must have the
following files in the toolkit specific directories:
/etc/cmcluster/scripts/ecmt/sybase/tkit_module.sh
/etc/cmcluster/modules/ecmt/sybase/sybase (this is a
symbolic link)
/etc/cmcluster/modules/ecmt/sybase/sybase.1
/opt/cmcluster/toolkit/sybase/README
/opt/cmcluster/toolkit/sybase/SGAlert.sh
Creating the Serviceguard package using Modular method
To create Serviceguard package using Modular method:
1. Create a directory for the package.
#mkdir /etc/cmcluster/pkg/sybase_pkg/
2. Copy the toolkit template and script files from sybase directory.
#cd /etc/cmcluster/pkg/sybase_pkg/
#cp /opt/cmcluster/toolkit/sybase/*./
3. Create a configuration file (pkg.conf)
#cmmakepkg -m ecmt/sybase/sybase pkg.conf
4. Edit the package configuration file.
NOTE: Sybase toolkit configuration parameters in the package configuration file are prefixed
by ecmt/sybase/sybase when used in Serviceguard A.11.19.00.
For Example:
/etc/cmcluster/pkg/sybase_pkg/pkg.conf
70 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX