Using Easy Deployment in Serviceguard and Metrocluster environments on HP-UX 11i v3 Serviceguard Manager B.03.10 or later Technical white paper Table of contents Executive summary .......................................................................................................................2 Introduction ..................................................................................................................................2 Purpose and intended audience ...................................
Executive summary This document describes the Easy Deployment feature that is available with the HP Serviceguard A.11.20 with PHSS_41628 or later. Easy Deployment provides an intuitive and straightforward configuration solution to users in a clustered environment. It not only enables users to configure a cluster and cluster-wide storage with a single command, but also greatly simplifies configuration of packages for popular applications.
Easy Deployment of clusters and packages is advantageous over traditional configuration methods in the following ways: • Reduces manual effort by over 80 percent* • Reduces the lead time/overhead for deployment • Reduces total cost of ownership (TCO) by not requiring network and storage expertise during cluster deployment • Reduces human error • Automates configuration steps related to complex applications and environments like Metrocluster, Oracle RAC, and Oracle E-Business Suite – Reduces the learning c
Purpose and intended audience The purpose of this white paper is to: • • • • Introduce the reader to the Easy Deployment feature in HP Serviceguard and Serviceguard Manager Describe Easy Deployment in the context of cluster configuration—cluster Easy Deployment Describe Easy Deployment in the context of package configuration—package Easy Deployment Help customers understand prerequisites and usage details for Easy Deployment of a cluster/package using Serviceguard Manager, in order to effortlessly meet th
Software prerequisite • Serviceguard A.11.20 plus PHSS_41628 or superseding patch must be installed on all nodes.
For detailed information on using Serviceguard Manager for cluster Easy Deployment, Serviceguard Manager offers context-specific online help accessible from all its screens. The following screenshots demonstrate the Serviceguard Manager workflow for cluster Easy Deployment.
Figure 3(a): Choosing to configure a simple Serviceguard cluster Figure 3(b): Choosing to configure Continentalclusters (primary or recovery cluster) with site awareness 7
Figure 3(c): Choosing to configure Continentalclusters (primary or recovery cluster) Figure 3(d): Choosing to configure a site-aware Metrocluster 8
Figure 3(e): Choosing to configure a Metrocluster Figure 4: Configuring the network 9
Figure 5: Choosing a cluster lock option Figure 6: Choosing the cluster lock option for a Metrocluster Figure 7: Creating a cluster-wide device special file group 10
Figure 8: Configuring system files Figure 9: Enabling CFS/CVM for the cluster Figure 10: Specifying cluster name 11
Figure 11: Cluster configuration summary Figure 12: Operation log showing completion of cluster deployment 12
Cluster Easy Deployment command-line support Easy Deployment of a Serviceguard cluster and easy creation of clustered LVM, VxVM/CVM storage is supported using the cmdeploycl and cmpreparestg commands, respectively.
Package Easy Deployment in a Serviceguard cluster using Serviceguard Manager Introduction Modular package configuration procedures for important applications need intensive manual effort and involve several steps.
Launching package Easy Deployment from Serviceguard Manager Figure 13: Serviceguard Manager home page • In the Serviceguard Manager home page, as shown in figure 13, click on the [Configuration] drop-down menu. • Click on [Package Easy Deployment] to open a second-level menu for the available deployment options. Note: These options are enabled only if the prerequisites for the corresponding applications, modules and/or toolkits are satisfied.
• Storage required for Oracle CRS and RAC DB should be configured and up on all nodes. The user can choose to use local or shared storage for Oracle CRS and RAC DB binaries. The user must use shared storage for OCR (Oracle Cluster Registry), voting disk, and RAC database. • The Oracle CRS and RAC DB must be up and running on all the nodes in the cluster.
Figure 14: Generated package configuration file(s) with operation log window Automatic configuration of Package Dependencies for Oracle Clusterware storage. If there are no disk group (DG-MNP) and mount point (MP-MNP) packages already configured for the storage being used by the Oracle Clusterware files, the packages will be configured automatically. The dependency between the Oracle Clusterware package and the mount point and disk group packages will also be established.
The CFS-DG-MP-MNP1 package manages the mount points and disk groups associated with the Oracle Clusterware package. The Oracle Clusterware package needs its associated storage to be up, and for this reason it needs to be dependent on the CFS-DG-MP-MNP1 package. Similarly, the CFS-DG-MP-MNP2 package manages the mount points and disk groups associated with the Oracle RAC DB package.
SGeRAC toolkit Oracle RAC database multi-node package Easy Deployment To deploy an Oracle RAC database package, click on [Configuration] -> [Package Easy Deployment] -> [Oracle RAC DB Package] menu toolbar of the Serviceguard Manager home page. For more details, refer to the “Launching package Easy Deployment from Serviceguard Manager” section. The [Oracle RAC DB Package] menu option is available only when: • HP Serviceguard cluster is running • Serviceguard A.11.
Oracle Clusterware package, the Oracle RAC database package, and the mount point and disk group packages will also be thereby established. If a separate storage has been used for Oracle Database software, then the storage information will be populated in the package configuration so that the user is freed from having to activate the volumes, mount the file system, etc. This will be taken care of as part of the Oracle RAC database package Easy Deployment.
Limitations • Supports only Oracle 11gR2 RAC • Supports only shared storages configured using CFS (SG SMS A.03.01 or later) • Supports only modular package style • If a legacy package for a CFS disk group already exists in the cluster and no mount point package exists, users must not use the Serviceguard Manager package Easy Deployment feature to deploy modular packages for the same Oracle Clusterware/RAC DB.
ECMT Oracle Single Instance DB toolkit package deployment To deploy an Oracle Single Instance DB package, click on [Configuration] -> [Package Easy Deployment] -> [Oracle Single Instance DB Package] menu toolbar of the Serviceguard Manager home page. For more details, refer to the “Launching package Easy Deployment from Serviceguard Manager” section.
– Log file location – Temp file location – Log archive destination All other attributes will either remain commented or will be initialized to default values.
Easy Deployment of SGeEBS applications tier toolkit package Software prerequisites The following product(s) need to be pre-installed to use the Easy Deployment feature to deploy the SGeEBS applications tier toolkit package: • Serviceguard A.11.20 plus PHSS_41628 or superseding patch • SGeEBS B.02.
The user is expected to input the applications tier base directory path (directory where instance specific installations are done) and the Oracle Database SID, and click the [Prepare] button on the screen to trigger the generation of required package configuration files for the SGeEBS applications tier toolkit package deployment. The generated package configuration file for the SGeEBS applications tier toolkit package deployment will be displayed for the user’s review.
Objective The objective of package Easy Deployment is to make the deployment of a Site Controller package a single step process. The user needs to select the complex workload packages in each site and click a button to generate all the configuration files required for the proper deployment of a Site Controller package.
The user is expected to input the Site Controller package name and select the packages that will make up the complex workload on both sites. Subsequently, clicking the [Prepare] button on the screen triggers the generation of required package configuration files for the Site Controller package deployment. The generated package configuration files for the Site Controller package deployment will be displayed for the user’s review. The user can edit the configuration files.
Parameter discovery and default parameters By way of automatic package parameter discovery by the Site Controller Easy Deployment script, most of the package attributes are automatically populated in the Site Controller and managed packages’ configuration files. The rest are set to recommended default values.
Easy Deployment of the SGeSAP package(s) Easy Deployment of SGeSAP packages is supported from Serviceguard Manager B.03.20 (available with Serviceguard A.11.20 patch PHSS_42137) Objective The objective of Package Easy Deployment in SGeSAP is to simplify initial deployment of SGeSAP packages(s) for a given SAP System in a SGeSAP cluster.
Figure 21: Serviceguard Manager, SGeSAP package(s) prepare screen The user must select the desired type of packaging option and the SAP System Id, and click the [Prepare] button on the “Deploy SGeSAP packages” screen (figure 21) to trigger the generation of required package(s) configuration files for the SGeSAP package(s) deployment. Note: If no SAP Central Service Instance is found on cluster nodes, a message will be displayed mentioning: ”No SAP Central Service Instance found on cluster nodes.
Adding Additional SAP Systems to SGeSAP cluster Both packaging options will prefer to add a SAP instance to an already existing package instead of creating a new package under certain conditions. This will happen in case an already existing package has resources configured on which the SAP instance depends. Example for such a situation is if a SAP Instance is installed on a virtual hostname that resolves to a relocatable IP address of an existing package.
Easy Deployment of ECMT DB2 package(s) Easy deployment of ECMT DB2 packages is supported from Serviceguard Manager B.03.30 (available with Serviceguard A.11.20 patch PHSS_42558 or later) Software prerequisites The following product(s) need to be pre-installed to use the Easy deployment feature to deploy the ECMT DB2 package(s): Serviceguard A.11.20 with patch PHSS_42558 or later for HP-UX 11i v3 ECMT B.07.00.
The generated package configuration file for the DB2 package deployment will be displayed for the user’s review. If required the user can edit the configuration file. To complete the DB2 package deployment, click [Apply] button in the same screen showing the configuration file.
Prerequisites and restrictions on package Easy Deployment in a Metrocluster environment Prerequisites and restrictions in a Metrocluster CAEVA environment • Prerequisites: – The replication pair must have been created already. – The supported version of evainfo tool is installed. – The Metrocluster version in all nodes of the cluster is Metrocluster CAEVA A.05.01 PHSS_41660 or superseding patch. – The /etc/dtsconf/caeva.map file should have been created and distributed.
For more information To download additional white papers or Serviceguard technical documentation, go to http://www.hp.com/go/hpux-serviceguard-docs and click on “HP Serviceguard” under the “Select your product” section. You can directly access Managing Serviceguard, Nineteenth Edition at www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard.
