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

Table 35 User Configuration Variables (continued)
DescriptionConfiguration Variables
This variable holds the log directory path of the CIFS
Server instance of the particular package. By default,
LOG_DIRECTORY
(for example, LOG_DIRECTORY=/var/opt/samba/
${NETBIOS_NAME}/logs)
the path is /var/opt/samba/${NETBIOS_NAME}/
logs. If the path is different, modify the variable.
This variable holds the PID file of the smbd process of
the particular package. The default PID file name is
SMBD_PID_FILE
(for example, for CIFS Server version older than 02.04,
SMBD_PID_FILE=/var/opt/samba/${NETBIOS_NAME}/
changed in CIFS Server version 02.04. The toolkit
detects the version and uses the default value
appropriately.
locks/smbd.pid and for CIFS Server version 02.04 or later,
SMBD_PID_FILE=/var/opt/samba/${NETBIOS_NAME}/
locks/smbd-smb.conf.${NETBIOS_NAME}.pid)
This variable holds the PID file of the nmbd process of
the particular package. The default PID file name is
NMBD_PID_FILE
(for example, for CIFS Server version older than 02.04,
NMBD_PID_FILE=/var/opt/samba/${NETBIOS_NAME}/
changed in CIFS Server version 02.04. The toolkit
detects the version and uses the default value
appropriately.
locks/nmbd.pid and for CIFS Server version 02.04 or later,
NMBD_PID_FILE=/var/opt/samba/${NETBIOS_NAME}/
locks/nmbd-smb.conf.${NETBIOS_NAME}.pid)
This variable enables or disables maintenance mode
for the Samba package. By default, this is set to "yes".
MAINTENANCE_FLAG
(for example, MAINTENANCE_FLAG=yes)
To disable this feature, set theMAINTENANCE_FLAG
to "no". If Samba needs maintenance, then you must
create a file <package directory>/
samba.debug. During this maintenance period
Samba process monitoring is paused. Even if Samba
is brought down, its package is not failed over to the
standby node. To continue monitoring and return from
the maintenance mode, remove the samba.debug
file. Ensure that Samba is properly running after the
maintenance phase.
NOTE: Setting MAINTENANCE_FLAG to "yes" and
touching the samba.debug file in the package
directory will put the package in toolkit maintenance
mode. Serviceguard A.11.19 release has a new
feature which allows individual components of the
package to be maintained while the package is still
up. This feature is called Package Maintenance mode
and is available only for modular packages. For more
information using Package Maintenance mode, see
white paper 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.
This variable holds a time interval (in seconds) for
monitoring the CIFS Server instance. The monitor
MONITOR_INTERVAL
(for example, MONITOR_INTERVAL=5)
process checks to ensure the smbd and nmbd daemons
are running every MONITOR_INTERVAL seconds. The
default value is 5 seconds.
This variable holds the number of attempts to check
the CIFS Server daemons before it exits to fail state.
RETRY_TIMES
(for example, RETRY_TIMES=0)
The default value is 0. SERVICE_RESTART *
RETRY_TIMES = total restart count.
The following information provides the steps for configuring the toolkit and running the package.
This includes configuring the SAMBA toolkit user configuration file.
NOTE: Before you configure the toolkit, create, the package directory (example, /etc/
cmcluster/smb1), and then copy the toolkit scripts to the package directory.
Setting up the Toolkit 131