Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX README: Release B.06.00

ManualsBrandsHP ManualsSoftwareHP Serviceguard Enterprise Cluster Master Toolkit

Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX

================================================================

Release B.06.00

CONTENTS:

A. Overview

B. Sybase Information

C. Setting up the Application

D. Setting up the Toolkit

E. Sybase Package Configuration Example

F. Adding the Package to the Cluster

G. Configuring Access Roles

H. Node-specific Configuration

I. Error-Handling

J. Network Configuration

K. Database Maintenance

PREFACE

This README file describes the High Availability Sybase Adaptive

Server

Enterprise (ASE) Toolkit designed for use in a Serviceguard

environment.

This document covers the basic steps to configure a Sybase ASE

instance

in Serviceguard Cluster, and is intended for users who want to

integrate

a Sybase ASE Server with Serviceguard in HP-UX environments.

This document assumes that its readers are already familiar with

the

Serviceguard configuration, as well as with Sybase ASE

concepts,

including installation and configuration procedures.

NOTE: This toolkit supports:

- HP Serviceguard versions

* A.11.19

* A.11.20

- Sybase ASE version 15.0.2 or later

- HP-UX 11i v2 and HP-UX 11i v3

NOTE: Unless otherwise stated, this toolkit runs on all distributions

and

all hardware supported by Serviceguard.

NOTE: It is recommended to set appropriate roles for users managing

the

Summary of content (20 pages)

PAGE 1
Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX ================================================================ Release B.06.00 CONTENTS: A. B. C. D. E. F. G. H. I. J. K.
PAGE 2
cluster and packages so that unauthorized users are restricted from viewing sensitive package attribute values like the Sybase administrator password. See section G in this README file for more details on configuring Role Based Access (RBA). A. Overview The Sybase ASE Toolkit for Serviceguard consists of a shell script that is used to start, stop, and monitor a single instance of Sybase ASE. Please note that this toolkit supports only modular packages.
PAGE 3
to run the package. Here the Sybase ASE binaries reside on the local storage. If any change is made to the configuration files, the file must be copied to all nodes. The user is responsible to ensure the systems remain synchronized. Shared Configuration This is the recommended configuration. Here, the configuration and database files are kept on shared disks (but the Sybase ASE binaries can be on the local storage).
PAGE 4
maintained across the nodes. A disadvantage of storing the configuration on local disks is that this can increase the chance of the configuration for a database instance becoming inconsistent if changes are made to the configuration in one node, and this configuration data is not distributed to all nodes that can run that database instance. It is therefore recommended that the master database and other ASE system database files - like master.dat, sysprocs.dat and sybsysdb.
PAGE 5
package configuration file). This can be done at the time of configuring the ASE server processes, with entries made in the file while configuring with the default configuration tool, or in the $SYBASE/$SYBASE_ASE/init/sample_resource_files/srvbuild.adaptive_server.r s and similarly for the other servers. NOTE: The dataserver and the monitor server, both need to be installed on the same disk as monitor server is dependent on the presence of the dataserver for its working. b.
PAGE 6
For more information on creating, importing, or managing the VG and file system, please refer to the chapter entitled "Building an HA Cluster" in the "Managing Serviceguard" manual for explicit instructions. d. The ASE system files, data table-spaces and files must be located in the file system /SYBASE0 during the initial creation of database. Refer to your Sybase ASE documentation for information on setting up these files.
PAGE 7
Again, using a naming convention for the VG(s) that includes the instance name (${ASE_SERVER}) could be used to associate a VG with a unique instance.
PAGE 8
Toolkit Module Script (tkit_module.sh) - Attribute Definition File (sybase) The ADF is used to generate a package ASCII template file. This file contains a list of pre-defined variables that will be added to the package configuration file during cmmakepkg, which the user must customize for use with a particular Sybase ASE instance. It has an attribute TKIT_DIR which will have the path of the package directory.
PAGE 9
SYBASE_ASE_ADMIN: administrator. System login name of the Sybase User will be logged in using ASE this account for starting and stopping of the database. ASE_SERVER: during Name of the installation Sybase or ASE instance configuration of set the ASE. This uniquely identifies an ASE instance. ALERT_MAIL ID: address Sends an email message to the specified email when packages fail.This email is generated only when packages fail,and not when a package is halted by the operator.
PAGE 10
If "wait" is specified, the instance is shutdown using the wait option, which will be a clean shutdown. If "nowait" is specified, the instance is shutdown using the nowait option. The default value is "wait". MONITOR_INTERVAL: script The interval of time, in seconds, which this should wait between checks to ensure of value is the Sybase database running. Default 30 seconds.
PAGE 11
MONITOR_PROCESSES: The names of all processes that must be executing to ensure this instance is up and running. MAINTENANCE_FLAG: the Maintenance flag will enable or disable maintenance mode for the Sybase package. By default this is set to "yes". In order to disable this feature, MAINTENANCE_FLAG should be set to "no". If the Sybase ASE instance needs to be maintained, a file "$TKIT_DIR/sybase.debug" needs to be touched.
PAGE 12
instance. By default, only the "€˜dataserver€" process of ASE is monitored. This process is contained in the variable MONITOR_PROCESSES. E. Sybase Package Configuration Example - Package Setup and Configuration 1. Assuming Sybase ASE is already installed in its default home directory (e.g., /home/sybase), perform the following steps to make necessary directories shareable by all clustered nodes.
PAGE 13
package to ensure Sybase ASE can be brought up and down successfully. 4. Create the Serviceguard package using modular package method Create a package configuration file (SYBASE0.conf) as follows: cmmakepkg -m ecmt/sybase/sybase -p SYBASE0.conf The configuration file should be edited as indicated by the comments in that file. The package name needs to be unique within the For clarity, use the $ASE_SERVER to name the package "package_name " cluster.
PAGE 14
in the Cluster Database. If users are not restricted access based on their roles, this password can be viewed by unauthorized users using the cmviewcl command. It is highly recommended to grant access to users based only on their roles in managing the cluster and packages. See section G in this README file for more details on configuring Role Based Access (RBA).
PAGE 15
SYBASE0) is assigned to the 'service_name' parameter. service_name SYBASE_${ASE_SERVER} service_cmd "/opt/cmcluster/conf/scripts/ecmt/sybase/tkit_module.sh sybase_monitor" service_restart "-r 3" The service restart counter can be reset to zero for this service by using Serviceguard command "cmmodpkg".The service restart counter is incremented each time the service fails.
PAGE 16
also stored in the Cluster Database. If you do not restrict access of users for the SAPASSWD package attribute, then unauthorized users can use the cmviewcl command to view the Sybase administrator password. HP recommends that you grant access to users based only on their roles in managing the cluster and packages.
PAGE 17
are updated and present on each node in the cluster or accessible through shared storage. It is the userâ€™s responsibility to replicate all files across all nodes, when using local configuration. I. Error-Handling During start up, the ASE server would require the IP/hostname that is mentioned in the interfaces file to be associated with a node name that it is configured to run on. If the IP is not configured, or pingable, the ASE instance may fail to come up.
PAGE 18
This needs to be edited to have the re-locatable IP-address, as follows: MIG29 master tcp ether 192.168.10.1 5000 query tcp ether 192.168.10.1 5000 If user requires a re-locatable hostname to be associated with this relocatable IP-address, there are two important things to be taken care of: 1. Use the re-locatable hostname in the srvbuild.adaptive_server.rs and similar files for all the other 'server' processes and use srvbuildres utility to configure the servers. 2.
PAGE 19
the ASE instance, the /etc/hosts file on each node should contain the re-locatable IP-address associated with the physical hostname of that node. For example, if node1_hostname and node2_hostname are the physical hostnames of two nodes in the cluster, and if 192.168.10.1 is the re-locatable IP-address the ASE instance, /etc/hosts of node1 should have for then the an entry like: 192.168.10.1 node1_hostname And the /etc/hosts file of node2 should have an entry like: 192.168.10.
PAGE 20
- Perform maintenance actions (Example: changing the configuration parameters in the parameter file of the Sybase ASE instance. If this file is changed, please remember to distribute the new file to all cluster nodes). - Start the Sybase ASE database instance again if it has been stopped: $ export SG_PACKAGE=SYBASE0 $ SGCONF/scripts/ecmt/sybase/tkit_module.sh start - Allow monitoring scripts to continue normally as shown below: $ rm -f /opt/cmcluster/pkg/SYBASE0/sybase.