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
test_return 51
}
5. Configure the user configuration file hasmb.conf as explained in the next section“Setting
up the Toolkit” (page 129) and customize it for your environment.
6. Copy this package configuration directory to all other package nodes.
You can use the same procedure to create multiple HP CIFS Server packages (multiple HP
CIFS Server instances) that will be managed by Serviceguard.
Setting up the Toolkit
Toolkit overview
After you install the toolkit, four scripts and one README file will be installed in the location /opt/
cmcluster/toolkit/samba. Two more scripts and one file will be installed which will be used
only for modular packages. The two scripts will be in the /etc/cmcluster/scripts/ecmt/
samba directory. The third file will be in the /etc/cmcluster/modules/ecmt/samba directory.
For legacy packages, one user configuration script ( hasmb.conf) and three functional scripts (
toolkit.sh, hasmb.sh and hasmb.mon) will work together to integrate the HP CIFS server
with the Serviceguard package control script.
The scripts used in legacy packages are:
Table 34 Legacy Package Scripts
DescriptionScript Name
This script contains a list of pre-defined variables that may be customized for
your environment. This script provides you with a simple format for (user)
User Configuration file User
(hasmb.conf)
configuration data. This file will be included (that is, sourced) by the toolkit
main script ( hasmb.sh).
This script contains a list of internal-use variables and functions that support
the start or stop functions of an HP CIFS Server instance. This script is called
by the toolkit interface script (toolkit.sh) to do the following:
Main Script (hasmb.sh)
• On package start, it starts an HP CIFS Server instance and launches a
monitor process by calling hasmb.mon.
• On package stop, it stops the HP CIFS Server server instance and halts
hasmb.mon.
This script contains a list of internal-use variables and functions for monitoring
an HP CIFS Server server instance. This script is called by the toolkit main
Monitor Script (hasmb.mon)
script ( hasmb.sh) and constantly monitors two HP CIFS Server daemons,
smbd and nmbd.
This script is an interface between a package control script and the toolkit
main script (hasmb.sh ).
Interface Script (toolkit.sh)
Creating Serviceguard package using Modular method
To create Serviceguard package using Modular method:
1. Create a directory for the package.
#mkdir /etc/cmcluster/pkg/samba_pkg/
2. Copy the toolkit template and script files from samba directory.
#cd /etc/cmcluster/pkg/samba_pkg/
#cp /opt/cmcluster/toolkit/samba/* ./
3. Create a configuration file (pkg.conf).
#cmmakepkg -m ecmt/samba/samba pkg.conf
Setting up the Toolkit 129