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
NOTE: To increase the number of packages that can be added to this cluster, modify the cluster
configuration file and set the variable MAX_CONFIGURED_PACKAGES to reflect the number of
packages to be added to the cluster. Once the cluster is edited, change it through thecmapplyconf
-C cluster_config_file
Before working on the package configuration, create a directory (for example, /etc/cmcluster/
pkg/http_pkg1) for this package to run. This directory must belong to a single Apache package.
Copy all Apache toolkit scripts from the directory /opt/cmcluster/toolkit/apache to the
package directory.
For example:
$ mkdir /etc/cmcluster/pkg/http_pkg1
$ cd/etc/cmcluster/pkg/http_pkg1
$ cp/opt/cmcluster/toolkit/apache/*.
To create both the package configuration (http_pkg.conf) and package control
(http_pkg.cntl) files, cd to the package directory (example, cd /etc/cmcluster/pkg/http_pkg1).
1. Create a Serviceguard package control file using the command cmmakepkg -s
http_pkg.cntl. The package control file must be edited as indicated by the comments in
that file. The package control file must be customized to your environment.
For Example:
PACKAGE_NAME http_pkg1
NODE_NAME node1
NODE_NAME node2
NOTE: When you configure an Active - Active configuration, the package configuration file
must hold the name of only the single node on which the instance will run. For example, on
node1, NODE_NAME parameter in the package configuration file must be edited as
NODE_NAME node1 and in node2 as, NODE_NAME node2
RUN_SCRIPT /etc/cmcluster/pkg/http_pkg1/http_pkg.cntl
RUN_SCRIPT /etc/cmcluster/pkg/http_pkg1/http_pkg.cntl
HALT_SCRIPT /etc/cmcluster/pkg/http_pkg1/http_pkg.cntl
SERVICE_NAME http1_monitor
If you see the CFS mounted file system is used, configure dependency of this Apache package
on SG CFS package. If the Apache package is configured to depend on a SG CFS package,
the Apache package runs as long as the SG CFS package is running. If the SG CFS package
fails, the dependent Apache package will also fail.
To configure the dependency of the Apache package, set the following configurable parameters
in the package configuration file:
DEPENDENCY_NAME
http1_dependency
DEPENDENCY_CONDITION SG-CFS-MP-1 = up
DEPENDENCY_LOCATION SAME_NODE
2. Create a Serviceguard package control file with command cmmakepkg -s http_pkg.cntl.
The package control file must be edited as indicated by the comments in that file. The package
control file must be customized to your environment.
#The service name and the name defined in the package #configuration file must be same.
For example:
LVM | VxVM
----- | ------
104 Using an Apache Toolkit in a HP Serviceguard Cluster