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
on all cluster nodes. Mount the CFS filesystem on /shared/smb1 using the CFS packages. Use
/shared/smb1 to hold the necessary files and configuration information.
WARNING! CIFS supports CFS with a limitation. A running package fails if another cluster node
tries to start samba using the configuration used by this package. Do not attempt to start another
samba instance on a different cluster node using the shared configuration that is being used by
any samba package.
For information on creating, importing or managing the volume group or disk group and filesystem,
see the Serviceguard user manual available at:http://www.hp.com/go/hpux-serviceguard-docs->
HP Serviceguard
You can configure more shared storage for additional HP CIFS Server instances using the same
method.
In a shared configuration, you can place samba binaries in shared file system. You might have to
create soft links on the local file system, to these binaries residing in shared file system.
The following sections describe the method for creating the Serviceguard package using the legacy
method. For more information on creating the Serviceguard package using the modular method,
see Modular package support in Serviceguard for Linux and ECM Toolkits available at http://
www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard Enterprise Cluster Master Toolkit
Setting up the Package
The following procedures include the steps to configure a package running the HP CIFS Server
instance, which includes customizing the package configuration file and package control script.
You must configure an HP CIFS Server package named "smb1", that consists of one service named
"smb1_monitor". The HP CIFS Server instance is listening to a relocatable IP address "192.168.0.1"
and all of its configuration and document files are in a file system /shared/smb1 directory. Here,
it is assumed that the user has already determined the cluster configuration, including cluster name,
node names, heartbeat IP addresses, and so on. For more information on cluster configuration,
see the latest Managing ServiceGuard manual available at http://www.hp.com/go/
hpux-serviceguard-docs —>HP Serviceguard .
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. After the edit, apply the change to the cluster via
cmapplyconf -C cluster_config_file.
Before you configure the package, create a directory (example, /etc/cmcluster/smb1) for
this package. Each HP CIFS Server package must have its own directory. Copy all SAMBA toolkit
scripts from the directory /opt/cmcluster/toolkit/samba to the package directory.
For example:
$ mkdir /etc/cmcluster/smb1
$ cd /etc/cmcluster/smb1
$ cp /opt/cmcluster/toolkit/samba/* . #copy to $PWD
To create the package configuration (smb_pkg.conf) and the package control
(smb_pkg.cntl) files, cd to the package directory (for example, cd /etc/cmcluster/smb1)
1. Create a package configuration file using the command cmmakepkg -p. Edit the package.
The package name must be unique within the cluster.
For example:
PACKAGE_NAME smb1
NODE_NAME node1
NODE_NAME node2
Setting up the Package 127