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
http_pkg.cntl #Package control file
hahttp.conf #Apache toolkit user configuration file
hahttp.mon #Apache toolkit monitor program
hahttp.sh #Apache toolkit main script
toolkit.sh #Interface file between the package
#control file and the toolkit
3. Apply the Serviceguard package configuration using the command cmapplyconf -P
http_pkg.conf.
Use the same procedures to create multiple Apache instances for Serviceguard packages that
will be running on the cluster.
Creating Serviceguard Package Using Modular Method
To create Serviceguard package using Modular method:
1. Create a directory for the package.
#mkdir /etc/cmcluster/pkg/apache_pkg/
2. Copy the toolkit template and script files from apache directory.
#cd /etc/cmcluster/pkg/apache_pkg/
#cp /opt/cmcluster/toolkit/apache/* ./
3. Create a configuration file (pkg.conf).
#cmmakepkg -m ecmt/apache/apache pkg.conf
4. Edit the package configuration file.
NOTE: Apache toolkit configuration parameters in the package configuration file are prefixed
by ecmt/apache/apache when they are used in Serviceguard A.11.19.00 or later.
For Example:
/etc/cmcluster/pkg/apache_pkg/pkg.conf
The configuration file must be edited as indicated by the comments in that file. The package
name must be unique within the cluster.
For Example:
PACKAGE_NAME apache
NODE_NAME node1
NODE_NAME node2
Set the TKIT_DIR variable as the path of <package_directory>. For example, TKIT_DIR
/etc/cmcluster/pkg/apache_pkg.
5. Use cmcheckconf command to check for the validity of the configuration specified.
For Example:
#cmcheckconf -P pkg.conf
6. If the cmcheckconf command does not report any errors, use the cmapplyconf command
to add the package into Serviceguard environment.
For Example:
#cmapplyconf -P pkg.conf
Error Handling
On startup, the Apache server application checks for the existence of the httpd.conf file in the
directory <SERVER ROOT>/conf/httpd.conf. If the configuration file does not exist in this
location or Apache does not start for some other reason the Apache toolkit script halts the package
on that node and attempts to run it on another node. To troubleshoot and start Apache correctly
108 Using an Apache Toolkit in a HP Serviceguard Cluster