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
4. Edit the package configuration file.
NOTE: Samba toolkit configuration parameters in the package configuration file are prefixed
by ecmt/samba/samba when used in Serviceguard A.11.19.00 or later.
For Example:
/etc/cmcluster/pkg/samba_pkg/pkg.conf
Edit the configuration file according to the instructions provided in that file. The package name
must be unique within the cluster.
For Example:
PACKAGE_NAME samba
NODE_NAME node1
NODE_NAME node2
Set the TKIT_DIR variable as the path of <package_directory>. For example, TKIT_DIR
/etc/cmcluster/pkg/samba_pkg.
SERVICE_NAME smb1_monitor
To use CFS mounted file system you must configure dependency of this Samba package on
SG CFS package. If the Samba package is configured to depend on a SG CFS package, the
Samba package runs only if the dependee package is running. If the package fails, the
dependent Samba package also fails.
To configure dependency of the Samba package, you must set the following configurable
parameters in the package configuration file:
DEPENDENCY_NAME smb1_dependency
DEPENDENCY_CONDITION SG-CFS-MP-1 = up
DEPENDENCY_LOCATION SAME_NODE
5. Use cmcheckconf command to check 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
Toolkit user configuration
All the user configuration variables are kept in a single file in shell script format. The variable
names and their sample values are in Table 35 (page 130):
Table 35 User Configuration Variables
DescriptionConfiguration Variables
This variable holds the NetBIOS Name of the server.
If you configure the HP CIFS Server using
NETBIOS_NAME
(for example, NETBIOS_NAME=smb1)
/opt/samba/bin/samba_setup command, the
NetBIOS name is found in /etc/opt/samba/
smb.conf. If you configure multiple HP CIFS Server
packages, ensure the NetBIOS name is unique for
each package.
This variable specifies the path of the
"smb.conf.<netbios_name>". By default, the path is
CONF_FILE
(for example, CONF_FILE=/etc/opt/samba/
smb.conf.${NETBIOS_NAME})
/etc/opt/samba/smb.conf.${NETBIOS_NAME}.
If the path is different, modify the variable.
130 Using SAMBA Toolkit in a Serviceguard Cluster