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 .....................................................................................................4
Definition of terms.........................................................................................................................4
Cluster Easy Deployment ...............................................................................................................4
Introduction ..............................................................................................................................4
Software prerequisite.................................................................................................................5
Cluster Easy Deployment using Serviceguard Manager .................................................................5
Cluster Easy Deployment command-line support ..........................................................................13
Limitations ..............................................................................................................................13
Package Easy Deployment in a Serviceguard cluster using Serviceguard Manager .............................14
Introduction ............................................................................................................................14
Objective ...............................................................................................................................14
Options supported ..................................................................................................................14
Launching package Easy Deployment from Serviceguard Manager ...............................................15
Easy Deployment of SGeRAC toolkit packages ...........................................................................15
Easy Deployment of ECMT Oracle Single Instance DB package ....................................................21
Easy Deployment of SGeEBS applications tier toolkit package ......................................................24
Easy Deployment of a Site Controller package ...........................................................................25
Easy Deployment of the SGeSAP package(s) ..............................................................................29
Easy Deployment of ECMT DB2 package(s)................................................................................32
Prerequisites and restrictions on package Easy Deployment in a Metrocluster environment ................34

For more information...................................................................................................................35

 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. It avoids the need for
demanding deployment wizards and filling of parameters in complex configuration files. With Easy Deployment, most
of the cluster/package attributes are auto-discovered, and storage or application prerequisites are automatically
resolved. Thus, the user can accomplish a deployment procedure with minimal manual input. This also significantly
reduces the learning curve required to deploy complex applications in a Serviceguard environment.
Easy Deployment is made available to users by way of HP Serviceguard Manager B.03.10 and Serviceguard
command-line tools/commands. The Serviceguard Manager Easy Deployment interfaces, coupled with Serviceguard’s
command line tools, present the user with a dramatically simple, yet flexible, deployment process.

Introduction
The demand for higher levels of availability in business IT infrastructures is ever increasing. Minimizing downtime in
environments that involve vital applications is painstakingly time consuming, and involves considerable complexity in
terms of configuration and deployment of robust clustered environments. Following traditional means of deployment
requires a large lead time. It also requires user expertise in areas such as storage and network configuration. The
Easy Deployment feature in Serviceguard makes it faster and significantly simpler to deploy high availability clusters
and packages to offer application availability. The Easy Deployment feature for configuring a cluster is called cluster
Easy Deployment; while the feature for configuring application packages is called package Easy Deployment.
Cluster Easy Deployment enables creation of a basic Serviceguard cluster as well as clusters with additional
capabilities, depending on whether or not the corresponding product is found to be installed on all the selected
nodes. For example, if Metrocluster is detected, Serviceguard Manager will provide the user with options to deploy a
site-aware Metrocluster or a traditional Metrocluster for failover applications. Other examples of this help the user to
deploy a cluster with Cluster File Systems or the Serviceguard Extension for RAC Toolkit. The user may also deploy the
primary or recovery clusters in the context of Continentalclusters. These cluster Easy Deployment options are available
in Serviceguard Manager as an interactive wizard. Designed for optimum flexibility, it allows users to either use
default settings or modify certain parameters. For instance there are provisions in the wizard for selecting nodes,
mapping nodes to sites, setting lock options, enabling the CVM/CFS infrastructure, and tuning network and storage
configurations.
The cmdeploycl and cmpreparestg commands can be used to achieve cluster Easy Deployment from the
command line. These commands:

• Provide a quick and simple way to create and start a cluster

• Automate security, storage, and networking configuration that must always be done before you configure nodes
into a cluster
• Simplify cluster lock configuration
• Simplify creation of shared storage for packages

The package Easy Deployment feature, on the other hand, simplifies the deployment of packages for complex
applications like Oracle Single Instance, Oracle RAC, and the Oracle E-business Suite by auto-discovering
package parameters and creating prerequisite packages to resolve application-related dependencies. It also enables
a single-step deployment of the Site Controller package in a Metrocluster environment. A Site Controller package is
used to configure complex workloads in a Metrocluster/Continentalclusters environment using the Site Aware Disaster
Tolerant Architecture (SADTA).
Serviceguard Manager enables the user to pick a package Easy Deployment task and specify a small number
of required parameters. Once this is done, it generates all the required configuration files, populated with
auto-discovered parameters. Serviceguard Manager combines ease of use with a degree of flexibility as it allows
users to review and edit the configuration files before deploying them.

2
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 curve to deploy such environments and applications.
– Reduces the number of manual steps required to deploy them.
• A command line user is freed from manually generating package configuration files, and editing parameters in
them. Package configuration tasks are also further eased for Serviceguard Manager users as they no longer need
to go through multiple configuration wizards.
However, the Easy Deployment feature offers less flexibility in terms of cluster and package configuration options.
Hence it may not be appropriate for deploying all clusters. It is not a substitute for understanding how Serviceguard
works, and still requires knowledge of basic Serviceguard concepts before users start deploying a cluster.
This white paper shows how the Easy Deployment features can be used for effortless cluster/package deployment.

* Based on comparison of different applications—Traditional vs. Easy Deployment conducted by HP internal R&D team in March/April, 2011.

3
 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 their high availability needs

This document is intended for users who are familiar with Serviceguard configuration and installation. Users must be
aware of installation of toolkits, and the installation/configuration procedures of the supported applications.

Definition of terms
Terms Definition

CFS Cluster File System allows multi-system shared access to common file system.

Complex workload A multi-instance application that uses active resources across multiple nodes in a cluster.
package These workloads are configured using multiple inter-dependent multi-node or failover packages in a cluster.
The workloads need to be managed and moved collectively for disaster tolerance.

MNP Multi-node package, a Serviceguard package that runs on multiple nodes at the same time and can be
independently started and halted on individual nodes.

OC Oracle Clusterware can run in conjunction with Serviceguard Extension for RAC and can provide Oracle
cluster membership and resource management services.

OCR Oracle Cluster Registry

RAC Real Application Cluster enables a multi-instance concurrent shared access database.

SADTA SADTA enables deploying complex workloads in a Metrocluster. Complex workloads are applications
configured using multi-node and failover packages with dependencies. These packages, referred to as
complex workload packages, are configured over isolated sub-clusters, such as Oracle Clusterware, or
Serviceguard Storage Management Suite (SG SMS) Cluster File System, which are created within the
Metrocluster. Sub-clusters have access only to the storage arrays within their respective sites.

SG SMS Serviceguard Storage Management Suite Software

SGeRAC Serviceguard Extension for RAC extends Serviceguard to support Oracle RAC.

SGeSAP Serviceguard Extension for SAP extends Serviceguard to support SAP NetWeaver environments.

Site controller A Metrocluster failover package to provide coordinated automatic site failover for the configured complex
package workload. It is created using a Metrocluster modular package module: dts/sc.

Voting disk Shared storage used by Oracle Clusterware as vote tie breaker and for disk-based heartbeat

Cluster Easy Deployment

Introduction
Cluster Easy Deployment is targeted to simplify and speed up the process of bringing up a new cluster, with a
lower level of required expertise.
This cluster Easy Deployment feature is supported by both Serviceguard Manager and the Serviceguard
command-line interface.
In Serviceguard Manager, this feature simplifies cluster configuration with various environments, by providing an
interactive wizard, bolstered with ample auto discovery.
Cluster Easy Deployment is also supported on the command line with the cmdeploycl command. This command eases
cluster-related storage and network configuration aspects.

4
Software prerequisite
• Serviceguard A.11.20 plus PHSS_41628 or superseding patch must be installed on all nodes.

Cluster Easy Deployment using Serviceguard Manager

The cluster Easy Deployment feature helps users by performing the following tasks:

• Setting up cmclnodelist after selection of nodes

• Configuring shared subnets (network configuration)
• Configuring cluster-wide device special files
• Performing cluster lock selection and creating shared storage, if needed
• Updating system files on cluster nodes

Enable CFS or CVM in the cluster

The following prerequisites need to be satisfied to use the cluster Easy Deployment feature to enable CFS or CVM in
the cluster:

• The SG SMS versions A.03.01 or later with Serviceguard A.11.20 plus PHSS_41628 or superseding patch need
to be pre-installed.
• The user must verify that vxinstall has been run on all nodes of the cluster.

When a SG SMS CFS or CVM standalone bundle is installed on all the nodes, the users will be prompted to choose if
they would like to enable CFS or CVM in the cluster. As part of this, the SG-CFS-pkg (SMNP) will be automatically
configured during cluster deployment. This package is the system multi-node package (SMNP) that runs the CVM
infrastructure. It configures and starts the CVM/CFS stack.

SGeRAC cluster Easy Deployment

The following products need to be pre-installed to use the SGeRAC cluster Easy Deployment feature:

• SGeRAC A.11.20 Patch—PHSS_41642 or superseding patch

• Oracle RAC 11gR2

When the SGeRAC product is installed on all the nodes, the cluster Easy Deployment feature checks if the following
conditions are satisfied:

• The cluster configuration has the same LAN interface name on all nodes.
• The cluster is not configured with IPv6 heartbeat.
Specific warning messages are displayed to the user, if the previously listed conditions are not met.

Metrocluster Easy Deployment

One of the following products needs to be pre-installed to use the Metrocluster Easy Deployment feature:

• HP Metrocluster with Continuous Access for P9000 and XP A.11.00 PHSS_41664 or superseding patch
• HP Metrocluster with Continuous Access EVA A.05.01 PHSS_41660 or superseding patch
• HP Metrocluster with EMC SRDF A.09.01 PHSS_41662 or superseding patch

The Metrocluster Easy Deployment feature simplifies the configuration process by:

• Defining sites and associating nodes with these sites

• Enabling that the quorum server is used for arbitration

Continentalclusters Easy Deployment

The cluster configured using Easy Deployment in Serviceguard Manager can be used as a primary cluster or a
recovery cluster of Continentalclusters. However, cluster Easy Deployment doesn’t support Continentalclusters
configuration steps like preparing a Continentalclusters configuration file, setting up Continentalclusters monitoring
daemons, configuring logical or physical data replication, and creating recovery packages.

5
 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 1: Choosing cluster Easy Deployment option

Figure 2: Choosing cluster nodes

6
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.

The functions performed by these Easy Deployment commands are:

• cmpreparestg:
– Creates LVM volume groups
– Creates LVM logical volumes
– Creates file systems on LVM logical volumes
– Configures mount points for LVM logical volumes
– Distributes (imports) LVM configuration across nodes
– Creates and modifies a VxVM/CVM disk group
– Creates file systems on VxVM/CVM disk groups
– Configures mount points for VxVM/CVM disk groups
• cmdeploycl
– Runs cmpreparecl on all prospective cluster nodes
– Applies the network configuration specified by ”net_template” using cmapplyconf –N

– Creates storage for use as a cluster lock using cmpreparestg (if the –b option is specified)
– Creates a cluster with the name specified by ”cluster_name” (or <localhost>_name, default)
– Runs the cluster

For more information on command-line support for cluster Easy Deployment, refer to the “About Easy Deployment”
and “Using Easy Deployment” sections in Managing Serviceguard Nineteenth Edition, available at
www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard. You can also refer to the command man pages
cmdeploycl (1m) and cmpreparestg (1m) for more details.

Note:
There is no equivalent functionality to the cmpreparestg command in
Serviceguard Manager.

Limitations
• Easy Deployment of extended distance clusters is currently not supported both via the Serviceguard command line
and Serviceguard Manager.
• The network configuration performed as part of cluster Easy Deployment does not support cross-subnet
configurations. However, users can still easy-deploy a cluster from Serviceguard Manager with a cross-subnet
configuration if they skip the network configuration step in the Easy Deploy workflow and perform the network
configuration manually. Users can also use the “Create Cluster” option for performing cross-subnet configurations.

13
 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. From a command-line interface, these manual steps generally are:

• Generating package configuration file(s)

• Editing the required package parameter values
• Applying the package configuration
• Running the package

Users of Serviceguard Manager, too, need a longer lead time to deploy packages because they are required to
traverse multiple forms to provide parameters for configuring various package modules. The traditional procedures
of deployment are tedious, as they lack automation in performing parameter discovery and setting up package
dependencies.

Objective
The objective of the package Easy Deployment feature is to simplify and ease configuration of various modular
packages. This is to be accomplished with minimum or no parameter input by the user. It must also take care of
deploying package dependencies automatically. For example, during the deployment of an Oracle Clusterware
toolkit package, for each CFS used by Oracle Clusterware, there will be a dependency configured from the Oracle
Clusterware MNP to the mount point and disk group MNP corresponding to that CFS. The mount point and disk
group MNP in turn has a dependency on the SG-CFS-pkg (SMNP). All these dependencies are configured by
package Easy Deployment as required, automatically, without any user interference.

Note:
Package Easy Deployment is available only via Serviceguard Manager, and is
not available as any Serviceguard command-line tool/command.

Options supported
Serviceguard Manager provides options for Easy Deployment of:

• SGeRAC toolkit packages:

– The Oracle Clusterware toolkit package, which will also deploy corresponding mount point and disk group
package(s) if they do not exist in the cluster
– The Oracle RAC database toolkit package, which will also deploy Oracle Clusterware/Toolkit and
corresponding mount point and disk group package(s) if they do not exist in the cluster
• The Oracle Single Instance DB package using the ECMT Oracle toolkit, in a basic Serviceguard cluster or
a Metrocluster
• The SGeEBS applications tier toolkit package
• The Site Controller package
• The DB2 package
• The SGeSAP package

14
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.

• Clicking on an enabled package deploy option will open the corresponding deployment form to complete the
deployment process. For further assistance please refer to the appropriate package Easy Deployment section in the
document. Serviceguard Manager also offers context-specific online help on topics related to using Serviceguard
Manager for package Easy Deployment.

Easy Deployment of SGeRAC toolkit packages

Software prerequisites
The following product(s) need to be pre-installed to use the Easy Deployment feature to deploy SGeRAC toolkit
packages:

• Serviceguard A.11.20 plus PHSS_41628 or superseding patch

• SGeRAC A.11.20 Patch—PHSS_41642 or superseding patch
• Oracle RAC 11gR2—must be installed on all nodes
• SG SMS versions A.03.01 or later—must be installed on all nodes
• SG-CFS Patch PHSS_41674 or later—must be installed on all nodes

15
 • 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.

SGeRAC toolkit Oracle Clusterware multi-node package Easy Deployment

To deploy an Oracle Clusterware package, click on [Configuration] -> [Package Easy Deployment] -> [Oracle
Clusterware 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 Clusterware Package] menu option is available only when:

• The HP Serviceguard cluster is running

• Serviceguard A.11.20 plus PHSS_41628 or superseding patch is installed on all cluster nodes
• SGeRAC A.11.20 plus PHSS_41642 or superseding patch is installed on all cluster nodes
• No modular Oracle Clusterware package is already configured

Note:
The Package Easy Deployment operation will not be able to identify a legacy
Oracle Clusterware package.

Once the user chooses to deploy an Oracle Clusterware package from the Serviceguard Manager home page,
auto-generated package configuration files for the Oracle Clusterware package, mount point, and disk group
packages (if required) will be displayed in separate panes for the user’s review. As illustrated in figure 14, the user is
shown a package Easy Deployment operation log and the configuration files so generated. The user can edit these
configuration files. To complete the Oracle Clusterware package deployment the user needs to click on the [Apply]
button in the same screen showing the configuration files.

Note:
The screen template used in figure 14 is followed for package Easy Deployment
features for all other supported packages as well. Subsequent to generation of
required package configuration files, they are displayed along with the package
Easy Deployment operation log in this screen.

16
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 following
illustration in figure 15 provides more details on the dependency structure for Oracle Clusterware, Oracle RAC
database, and mount point and disk group packages:

Figure 15: SGeRAC package's dependency structure

17
 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. The RAC DB package again needs its associated storage to be up, and for this reason it needs to
be dependent on the CFS-DG-MP-MNP2 package.
The SG-CFS-pkg (SMNP) is responsible for configuring and starting the CVM/CFS stack. The CFS-DG-MP-MNP1 and
the CFS-DG-MP-MNP2 packages need CVM to be configured and running, and for this reason these packages need
to be dependent on the SG-CFS-pkg (SMNP).
If a separate storage has been used for Oracle Clusterware 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 Clusterware package Easy Deployment.

Parameter discovery and default parameters

By way of automatic package parameter discovery by the Easy Deployment operation, the following Oracle
Clusterware package attributes are automatically populated in the corresponding configuration file:

• Cluster nodes
• Oracle Clusterware Home path

After finding the CFS storage location of the VOTE disk/OCR disk path, the Easy Deployment operation checks
whether the required mount point and disk group packages are deployed or not. If these storage packages do not
already exist in the cluster, the Easy Deployment operation automatically deploys these packages. Subsequently, a
dependency on the required mount point packages is configured in the Oracle Clusterware package.
The following Oracle Clusterware parameters are initialized to predetermined values:

• Package name
– In a non-Metrocluster environment, this is set to sgerac_oc_pkg.
– In a site-aware Metrocluster environment, the site_id will be appended to the package name (sgerac_oc_pkg_<site_id>).
• Package type
• Toolkit directory

The Oracle Clusterware package working directory is set to /etc/cmcluster/sgerac_oc_pkg/ in a

non-Metrocluster environment. In a site-aware Metrocluster environment, the Oracle Clusterware package working
directory is set to /etc/cmcluster/sgerac_oc_pkg_<site_id>/. All other package parameters will be set to
default values in accordance to the manual http://www.hp.com/go/hpux-serviceguard-docs -> HP Serviceguard
Extension for RAC. Please refer to the same for more details on default package parameters.

Error and exception handling

An error message will appear in the Serviceguard Manager package Easy Deployment operation log window if the
Oracle Clusterware package deployment fails for one or more of the following reasons:

• The cluster configured with a non-Metrocluster environment already has a non OC package configured for any
other third-party application with the name sgerac_oc_pkg, or in a site-aware Metrocluster a non-OC package
with the name sgerac_oc_pkg_<site_id> already exists, configured for any other third-party application on a
given site.
• An unexpected error occurs during the Oracle Clusterware package deployment operation.

18
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.20 plus PHSS_41628 or superseding patch is installed on all cluster nodes
• SGeRAC A.11.20 plus patch PHSS_41642 or superseding patch is installed on all cluster nodes

Once the user chooses to deploy an Oracle RAC database package from the Serviceguard Manager home page, the
user is presented with a simple form as shown in figure 16.

Figure 16: Serviceguard Manager, Oracle RAC database package prepare screen

The user is expected to input the Oracle Home path and the Oracle RAC database name and click the [Prepare]
button on the screen to trigger the generation of required package configuration files for the Oracle RAC database
package deployment.
The generated package configuration files for the Oracle RAC database package deployment will be displayed in
separate panes for the user’s review. The user can edit these configuration files. To complete the Oracle RAC
database package deployment the user needs to click on the [Apply] button in the same screen showing the
configuration files.
Automatic package dependency configuration for Oracle Clusterware storage
The Easy Deployment operation finds the Database files location and the redo/archive log files location. These are
used to configure the required dependencies on the storage packages managing these locations in the Oracle RAC
database package configuration file. If storage packages do not exist to manage these locations, the Easy
Deployment operation will automatically deploy them before configuring the dependencies.
If the Oracle Clusterware package is not configured already on the cluster, then it will be configured automatically.
Also, if no disk group (DG-MNP) and mount point (MP-MNP) packages are configured for the storage used by the
Oracle Clusterware files and RAC database files, they will be deployed automatically. The dependency between the

19
 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.

Parameter discovery and default parameters

By way of automatic package parameter discovery by the Easy Deployment operation, the following Oracle RAC
database package attributes are automatically populated in the corresponding configuration file:

• Cluster nodes
• Oracle user
• OC-MNP package name
• OC-MNP toolkit directory

The Oracle RAC database package name parameter is initialized in the following manner:

• In a non-Metrocluster environment, this is set to rac_<dbname>_pkg.

• In a site-aware Metrocluster environment, the site_id will be appended to the package name
(rac_<dbname>_pkg).

In a non-Metrocluster environment, the Oracle RAC database package working directory is set to
/etc/cmcluster/rac_<dbname>_pkg/. In a site-aware Metrocluster environment, the Oracle Clusterware
package working directory is set to /etc/cmcluster/rac_<dbname>_pkg_site_<site_id>/. All other
package parameters will be set to default values in accordance to the latest edition of the manual Using Serviceguard
Extension for RAC. Please refer to the same for more details on default package parameters.

Error and exception handling

An error message will appear in the Serviceguard Manager package Easy Deployment operation log window if the
Oracle RAC DB deployment fails for one or more of the following reasons:
• A modular RAC DB package is already configured in the cluster for the Oracle database name specified
by the user.

Note:
The package Easy Deployment operation will not be able to identify a legacy
RAC DB package.

Multiple Oracle Clusterware packages have been configured in the cluster.

Note:
The package Easy Deployment operation will not be able to identify a legacy
Oracle Clusterware package.

• An error occurs during deployment of the Oracle Clusterware package. As mentioned before, Oracle RAC
DB package deployment auto-deploys an Oracle Clusterware package if it is not found to be pre-configured in
the cluster.
• The cluster with a non-Metrocluster environment already has a non-RAC DB package configured for any other
third-party application with the name rac_<dbname>_pkg; or, in a site-aware Metrocluster, a non-RAC DB
package with the name rac_<dbname>_pkg_<site_id> already exists, configured for any other third-party
application on a given site.
• An unexpected error occurs during the Oracle RAC DB package deployment operation.

20
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.

Overview of SGeRAC toolkit package Easy Deployment in a site-aware Metrocluster environment

In a site-aware Metrocluster environment, Oracle Clusterware and Oracle RAC database package names will be
appended with site IDs.
In a non site-aware environment, before deploying an Oracle Clusterware/RAC DB package, the package Easy
Deployment operation checks if any Oracle Clusterware/RAC DB package(s) already exist in the cluster. The
Serviceguard Manager menu for Easy Deployment of an Oracle Clusterware package is disabled if an Oracle
Clusterware package already exists in the cluster. Also, upon finding Oracle RAC DB package(s) preconfigured, the
package Easy Deployment operation exits with an error.
However, in case of a site-aware environment, the package Easy Deployment operation checks for the existence of
the Oracle Clusterware/RAC DB package(s) only in the site/CRS subcluster associated with the node from where
Serviceguard Manager is launched (henceforth called the current site). The Serviceguard Manager menu for Easy
Deployment of an Oracle Clusterware package is disabled if an Oracle Clusterware package already exists in the
current site. And in order to deploy an Oracle Clusterware package for the other site, users must launch Serviceguard
Manager from one of the nodes belonging to that site.
Similarly, if Oracle RAC DB package(s) are found to be preconfigured in the current site, the package Easy
Deployment operation exits with an error. To deploy an Oracle RAC DB package for the other site, users must launch
Serviceguard Manager from one of the nodes belonging to that site.
The rest of the deployment process in a site-aware Metrocluster environment is the same as in a basic
Serviceguard cluster.

Easy Deployment of ECMT Oracle Single Instance DB package

Software prerequisites
The following product(s) need to be pre-installed to use the Easy Deployment feature to deploy the ECMT Oracle
Single Instance DB package:

• Serviceguard A.11.20 plus PHSS_41628 or superseding patch

• ECMT Oracle Toolkit B.06.00 version plus PHSS_41636 or superseding patch
• Oracle Database—only versions supported by the above mentioned ECMT Oracle toolkit version
• SG SMS version A.03.01 or later bundle, if CFS storage has been used
• In a Metrocluster environment, the following module versions will be supported:
– Metrocluster XPCA A.11.00 PHSS_41664 or superseding patch
– Metrocluster SRDF A.09.01 PHSS_41662 or superseding patch
– Metrocluster CAEVA A.05.01 PHSS_41660 or superseding patch

The Oracle database must be created and running on one of the cluster node for invoking the Package Easy
Deployment Operation.

21
 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.
The [Oracle Single Instance DB Package] menu option is available only when

• HP Serviceguard cluster is up and running

• ECMT Oracle Toolkit patch PHSS_41636 or superseding patch is installed on all cluster nodes

Once the user chooses to deploy an Oracle Single Instance DB package from the Serviceguard Manager home page,
the user is presented with a simple form as shown in figure 17.

Figure 17: Serviceguard Manager, Oracle Single Instance DB package prepare screen

The user is expected to input the Oracle session ID and the absolute path of the Oracle Home location and click the
[Prepare] button on the screen to trigger the generation of required package configuration files for the Oracle Single
Instance DB package deployment.
The generated package configuration file for the Oracle Single Instance DB package deployment will be displayed in
a separate pane for the user’s review, where the user can edit the file. To complete the Single Instance DB package
deployment the user needs to click on the [Apply] button in the same screen showing the configuration file.

Parameter discovery and default parameters

Using the Oracle Home location and Oracle session ID values provided by the user, the following Oracle Single
Instance DB package attributes are automatically discovered and populated by the Easy Deployment operation:

• Package name
• Toolkit directory name
• Cluster nodes names
• Oracle admin user
• Service names for Oracle, listener, and hang monitor
• Storage type and its attributes for:
– Oracle Home
– Data file location
– Flash recovery area
– Control file location

22
 – Log file location
– Temp file location
– Log archive destination

All other attributes will either remain commented or will be initialized to default values.
Storage configuration considerations
The following types of storage are supported for the ECMT Oracle Single Instance DB toolkit package:

• CFS storage
• LVM/VxVM storage
There are a few considerations that need to be taken care of while using any of the above storage types for Oracle
Single Instance DB package Easy Deployment:

• If CFS storage has been used, the ECMT Oracle Easy Deployment operation will require CFS mount point and disk
group packages to be up and running for mount points used by Oracle. The Easy Deployment operation will
discover whether mount point and disk group packages for the Oracle mount points are created or not. If these
packages are configured, it will update the ECMT Oracle toolkit package configuration file with the dependency
parameters.

Note:
If there are no mount point and disk group packages configured for the CFS
storage used by the Oracle files, they will not be configured automatically.

• If LVM/VxVM storage has been used for any of the data files or Oracle binaries, the ECMT Oracle Easy
Deployment operation will discover the file system, mount points, and volume groups used for the same and will
update the package configuration file with the storage values required for setting up the package.
• If the user prefers to use a local disk for Oracle binaries, no storage parameters will be updated in the package
configuration file for Oracle binaries.

Error and exception handling

An error message will appear in the Serviceguard Manager package Easy Deployment operation log window if the
Oracle Single Instance DB package deployment fails for one or more of the following reasons:

• The package directory that the operation is trying to create for the package already exists.
• An unexpected error occurs during the Oracle Single Instance DB package deployment operation.

Limitations
The Easy Deployment feature for the ECMT Oracle Single Instance DB toolkit:

• Supports only modular style of packaging

• Does not support Oracle database using ASM storage
• Supports CFS storage type only if the SG-CFS-pkg (SMNP), mount point, and disk group packages are configured
for the mount points used by the Oracle files

ECMT Oracle package Easy Deployment in Metrocluster Environment

In a Metrocluster environment, the ECMT Oracle Single Instance DB Easy Deployment operation will discover the
values as in a basic Serviceguard cluster. Additionally, if a volume group/disk group is configured on a replication
pair, the appropriate Metrocluster module will be configured. Please refer to the Prerequisites and Restrictions in the
Metrocluster environment for each supported module.

23
 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.00 for HP-UX 11i v3
• Oracle EBS—only versions supported by the above mentioned SGeEBS toolkit version

The EBS applications tier must be configured and running on the node from which the user is invoking the package
Easy Deployment Operation.

SGeEBS applications tier toolkit package deployment

To deploy a SGeEBS applications tier toolkit package, click on [Configuration] -> [Package Easy Deployment] ->
[SGeEBS Applications Package] menu toolbar of the Serviceguard Manager homepage. For more details, refer to the
“Launching package Easy Deployment from Serviceguard Manager” section.
The [SGeEBS Applications Package] menu option is available only when

• HP Serviceguard cluster is up and running

• SGeEBS B.02.00 for HP-UX 11i v3 is installed on all cluster nodes

Note:
If the user wants to configure the EBS database tier as a Serviceguard package,
he must use the ECMT Oracle Single Instance DB toolkit to package the EBS
database tier.

Once the user chooses to deploy a SGeEBS applications tier toolkit package from the Serviceguard Manager home
page, the user is presented with a simple form, as shown in figure 18.

Figure 18: Serviceguard Manager, SGeEBS application package prepare screen

24
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. The user can edit the configuration file. To complete the SGeEBS applications tier
toolkit package deployment, the user needs to click on the [Apply] button in the same screen showing the
configuration file.
Parameter discovery and default parameters
By way of automatic package parameter discovery by the SGeEBS Easy Deployment operation, the following
package attributes are automatically populated in the SGeEBS Applications Tier Toolkit package configuration file:

• Package name
• Toolkit directory name
• Service names
• Web entry IP
• Volume group, LVM, mount point, and file system

If a separate storage has been used for EBS instance-specific and application tier stack file system, then the storage
information will be populated appropriately in the package configuration.
All other package parameters will be set to default values.
Error and exception handling
An error message will appear in the Serviceguard Manager package Easy Deployment operation log window, if the
SGeEBS package Easy Deployment operation fails for one or more of the following reasons:

• The package directory that the operation is trying to create for the package already exists.
• An unexpected error occurs during the SGeEBS applications package deployment operation.

Limitations
The Easy Deployment feature for the SGeEBS applications tier toolkit package supports only modular style of
packaging.

Easy Deployment of a Site Controller package

Introduction
The configuration of a Site Controller package is a multi-step process that requires editing multiple package
configurations. The following are the steps required to configure a Site Controller package manually.
1. Selecting the appropriate Metrocluster module while creating the Site Controller package configuration.
Ex. cmmakepkg –m dts/sc –m dts/mcxpca <pkg_name>.conf
2. Applying the empty Site Controller package configuration file with the site and node information.
3. Editing the root-most complex workload packages’ configuration and inserting the resource dependency for site
safety latch
4. Re-applying the edited complex workload packages’ configuration
5. Editing the Site Controller package configuration and entering the complex workload package information and
the Metrocluster module parameters values
6. Re-applying the edited Site Controller configuration

Please refer to the chapter on “Designing a disaster recovery solution using site-aware disaster-tolerant architecture”
in the latest version of the Designing Disaster Recovery Clusters using Metroclusters and Continentalclusters, available
at www.hp.com/go/hpux-serviceguard-docs.

25
 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.
Software prerequisites
The following product(s) need to be pre-installed and the listed conditions must be met to use the Easy Deployment
feature to deploy a Site Controller package:

• Products to be pre-installed:
– Serviceguard A.11.20 plus PHSS_41628 or superseding patch
– Metrocluster XPCA A.11.00 PHSS_41664 or superseding patch
– Metrocluster SRDF A.09.01 PHSS_41662 or superseding patch
– Metrocluster CAEVA A.05.01 PHSS_41660 or superseding patch
• Exactly two sites must have been configured in the Serviceguard cluster.
• All nodes in the cluster must be up and running.
• The complex workload package set in the primary site must have been deployed.
• The complex workload package set in the recovery site must have been deployed.

Site Controller package Easy Deployment

To deploy a Site Controller package, click on [Configuration] -> [Package Easy Deployment] -> [Site Controller
Package] menu toolbar of the Serviceguard Manager home page. For more details, refer to the “Launching package
Easy Deployment from Serviceguard Manager” section.
The [Site Controller Package] menu option is available only when the HP Serviceguard cluster is configured with sites.
Once the user chooses to deploy a Site controller package from the Serviceguard Manager home page, the user is
presented with a simple form, as shown in figure 19.

Figure 19: Serviceguard Manager, Site Controller package prepare screen

26
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. To complete the deployment of the Site Controller package, the user
needs to click on the [Apply] button in the same screen showing the configuration file.
The following workflow diagram in figure 20 illustrates the details of the Site Controller Easy Deployment process:

Figure 20: Workflow diagram for Site Controller Easy Deployment

27
 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. The following table explains more about how each Site Controller
package parameter is generated:

How is it
Parameter What it means Value generated?

failover_policy Indicates the preference for site_preferred (default) auto-created

package failover Other possible value: (recommended)
site_preferred_manual (The user needs
to manually edit the generated
configuration file in this case)

package_name Name of the Site Controller Auto-created but

package editable by user

critical_package Indicates the name of a package, Any package name that is already User input
upon whose failure the entire configured in the cluster
complex workload set is halted by
Site Controller

managed_packages Indicates the name of packages Any package name that is already User input
that are managed by Site configured in the cluster
Controller

Appropriate Indicates the Metrocluster module This module will be dependent on the Auto-discovered
Metrocluster module that will be included in the Site type of replication pair used by the
parameters Controller package configuration complex workload packages:
If it is XP DEVICE GROUP, then
dts/mcxpca will be included along with
its parameters.
If it is SRDF DEVICE GROUP, then
dts/mcsrdf will be included along with
its parameters.
If it is CAEVA DR GROUP then
dts/mccaeva will be included along
with its parameters.

Limitations
• The Site Controller package Easy Deployment feature is not currently supported for a Continentalclusters
environment.
• During deployment, the complex workload packages must be in a halted state.
• The complex workload packages that use raw disks over a replication pair will not be supported.
• All the complex workload packages must be modular style packages.
• All the complex workload packages for single Site Controller must use exactly one replication pair.
• The prerequisites and restrictions for Metrocluster XPCA, Metrocluster EMC SRDF, and Metrocluster CAEVA are
applicable here as well. Please refer to the section “Prerequisites and restrictions on package Easy Deployment in a
Metrocluster environment” for more information.

28
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.

• To automatically generate cluster package configuration(s) for the following SAP software solution components with
necessary modules and appropriate values for all attributes:
– System Central Services (SCS/ASCS)
– Enqueue Replication Services (ERS)
– Database Services (Oracle, MaxDB, DB2)
– NFS
• To provide an easy way to extend existing package(s) if new SAP instances or resources need to be added.

Packaging options
There are two type of packaging options in which SGeSAP can be configured as packages: Multiple Packages and
Combined Packages.
Multiple Packages: This option allows to distribute the non-redundant SAP components across multiple, separate
packages to avoid dependencies between SAP components. Use this packaging option, if each non-redundant SAP
component has exclusive resources available (e.g., volume groups, virtual hostnames, and IP addresses).
Combined Packages: This option allows to combines the non-redundant SAP components of a SAP system in as few
packages as possible, to keep the setup simple and save resources. In this option a package could failover in case
any of the SAP components fails when multiple components are configured in the same package.
Easy Deployment allows you to deploy SGeSAP packages in either way.
Software prerequisites
The following product(s) need to be pre-installed to use the Easy Deployment feature to deploy the SGeSAP
package(s):

• Serviceguard A.11.20 plus PHSS_42137 or later for HP-UX 11i v3

• SGeSAP B.05.10 plus patch PHSS_42151 or later for HP-UX 11i v3

SGeSAP package(s) deployment

To deploy the SGeSAP package(s), click on [Configuration] -> [Package Easy Deployment] -> [SGeSAP Package(s)]
menu toolbar of the Serviceguard Manager home page. For more details, refer to the “Launching package Easy
Deployment from Serviceguard Manager” section.
The [SGeSAP Package(s)] menu option is available only when

• HP Serviceguard cluster is up and running

• SGeSAP B.05.10 or later for HP-UX 11i v3 is installed on all cluster nodes
• PHSS_42151 and PHSS_42137 or superseding patches are installed on all cluster nodes

Once the user chooses to deploy the SGeSAP package(s) from the Serviceguard Manager home page, the user is
presented with a simple form, as shown in figure 21.

29
 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.
Please setup the SAP Central Instance prior to using SGeSAP Package Easy
Deployment.”

The generated package configuration file(s) for the SGeSAP package(s) will be displayed for the user’s review in the
“Easy Deployment Operation Log” screen (figure 14). The configuration needs to be manually checked for
completeness and plausibility. The user can edit the configuration file(s) to reflect customer-specific requirements. To
complete the SGeSAP package(s) deployment, the user needs to click on the [Apply] button in the Operation Log
screen showing the configuration file(s).
SGeSAP Easy Deployment populates package configuration files with information from the existing storage layout
and the network settings for the SAP instances on the nodes. The resulting package configuration files include
Serviceguard services and resources that will monitor the SAP instance operation.
New package configuration files will be created for those SCS/ASCS, ERS, database and NFS services that

• are installed and discoverable on any cluster node

• belong to the selected SAP System ID
• are not already clustered.

Based on the way the SAP environment is installed, it might become mandatory to either combine instances in the
same cluster package or separate them into different ones. Both packaging options detect these conditions and
override their default behavior to fulfill such requirements.
For example, an SCS instance and the assigned ERS instance will never be configured in the same package, because
that would violate an architectural requirement of SAP.
A different example would be, if SCS and ASCS instance are installed on the same virtual hostname. In this case
they’ll be configured in the same package by both packaging options.

30
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. An addition of the Instance to the existing package will be suggested with both
packaging options.
This behavior is useful to simplify SAP installations with HA option: Serviceguard packages should be manually
created and started with relocatable IP address settings first. As a second step, the SAP installer will be invoked for all
required Instances specifying these addresses. Afterwards, Easy Deployment can be used to quickly add the
previously installed SAP instances to the packages.

Synchronize SGeSAP packages to changes in Network Settings and Storage Layout

When you change the network or storage layout of a SAP System, it is mandatory to synchronize the corresponding
SGeSAP packages with the changes. Using Easy Deployment for SGeSAP you can synchronize the corresponding
SGeSAP packages easily. From Serviceguard Manager home page, click on [Configuration] -> [Package Easy
Deployment] -> [SGeSAP Package(s)] menu toolbar. On the “Deploy SGeSAP Packages” screen (figure 21) select the
SAP System ID whose network and/or Storage layout has changed. This will generate a new configuration file with
the latest network and/or storage layout. When you click [APPLY] on the “Easy Deployment Operations Log” screen
(figure 14), the existing SGeSAP package will be reconfigured with the latest network and/or storage layout.
For example, if IPv6 became enabled and the virtual hostnames that SAP uses now also have an IPv6 address,
Easy Deployment will modify the existing package configurations to include the IPv6 address.
The configuration file(s) in the Easy Deployment Operations Log screen will not be available for editing if the
package(s) of the generated ASCII file(s) exists in the cluster and the configuration is up-to-date. An information note is
displayed mentioning: “For the selected SAP System ID <ID>, the package configuration is up-to-date. Hence no
update/change is required.”

Limitations
The Easy Deployment feature for the SGeSAP package supports only modular-style packaging.
Easy Deployment feature for SGeSAP cannot be used:

• To create clusters for SAP software that could also be installed in a redundant way, including Dialog Instances,
Java instances and Web dispatcher instances
• in multi-instance database environments, for example, Oracle RAC configurations
• To create cross subnet package configurations
• To create Metrocluster or cluster filesystem-based configurations

31
 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.01 or later for HP-UX 11i v3
The DB2 instance must be created and running on one of the cluster node for invoking the Package
Easy Deployment Operation.

DB2 package(s) deployment

To deploy the DB2 package(s), click on [Configuration] -> [Package Easy Deployment] ->
[DB2 Package] menu toolbar of the Serviceguard Manager home page. For more details, refer to
the “Launching package Easy Deployment from Serviceguard Manager” section.

The [DB2 Package] menu option is available only when:

 Serviceguard cluster is up and running

 Serviceguard A.11.20 with patch PHSS_42558 or later for HP-UX 11i v3
 ECMT B.07.00.01 or later for HP-UX 11i v3

Once the user chooses to deploy the DB2 package(s) from the Serviceguard Manager home page,
the user is presented with a simple form, as shown in Figure 20.

Figure 20: Serviceguard Manager, DB2 package prepare screen

The user is expected to input the DB2 instance name, and click [Prepare] button on the screen to
trigger the generation of required package configuration files for the DB2 package deployment.

32
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.

Parameter discovery and default parameters

By way of automatic package parameter discovery by the DB2 Easy Deployment operation, the
following package attributes are automatically populated in the DB2 package configuration file:

 Package name
 Toolkit directory name
 Service names
 Volume group, LVM, mount point, and file system
If a separate storage has been used for DB2 instance and database, then the storage information will
be populated appropriately in the package configuration.

All the mandatory parameters will be set to default values.

Error and exception handling

If any error, then message will appear in the Serviceguard Manager package Easy Deployment
operation log window. The DB2 package Easy Deployment operation may fails for one or more of the
following reasons:

 The package directory that the operation is trying to create for the package already exists.
 The DB2 application is not running on any of the cluster nodes.

 The instance name provided is invalid.

Limitations

 The Easy Deployment feature for the DB2 package supports only modular style of packaging.

 Easy Deployment feature for DB2 cannot be used for packaging DB2 instance with multi-
partitioned database.

 The Easy Deployment feature for the DB2 package is not supported in a Metrocluster
environment.

33
 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. This file is created using
smispasswd and evadiscovery tools that are a part of MC CAEVA.
– The SMIS servers are up and reachable.
• Restrictions:
– The node name in Command View (EVA array management tool) should be same as the node name in the
cluster configuration.
– The active management server should be listed in CAEVA.map file.
– If the physical disks are configured with enclosure-based naming, then Easy Deployment of Metrocluster
CAEVA will not be supported.
– The source vdisks in a DR group should be presented to all primary site nodes.
– The destination vdisks in a DR group should be presented to all recovery site nodes.

Prerequisites and restrictions in a Metrocluster SRDF environment

• Prerequisites:
– The replication pair must have been created already.
– The supported version of SYMCLI should have been installed.
• Restriction:
– If the physical disks are configured with enclosure-based naming, then Easy Deployment of
Metrocluster SRDF will not be supported.

Prerequisites and restrictions in a Metrocluster XPCA environment

• Prerequisite:
– The device group pair must have been already created.
• Restrictions:
– A device group configuration with a HORCMPERM file is not currently supported.
– All physical devices must belong to exactly one replication pair (DEVICE GROUP).
– The device group monitor will not be configured as a part of Easy Deployment.
– If the physical disks are configured with enclosure-based naming, then Easy Deployment of
Metrocluster XPCA will not be supported.

34
 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.

For case studies to understand how Serviceguard provides availability to mission-critical applications in various
industries and to see what is new in Serviceguard, visit: http://www.hp.com/go/serviceguard

HP recommends modular style packages for new application deployment in Serviceguard clusters.
HP also urges you to convert all existing legacy packages to modular style packages in your Serviceguard clusters.
Only with modular style packages can you take advantage of the new Serviceguard features explained in this white
paper and many other advanced Serviceguard features. For more details on migrating to modular style packages,
please refer to this white paper:
“Migrating packages from legacy to modular style” (October 2007) at:
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02056215/c02056215.pdf
HP strongly recommends using Dynamic Root Disk software to enable safe and less disruptive upgrades to your
HP-UX 11i v3 servers. You can obtain the DRD software for free from: www.hp.com/go/drd
Please contact your HP representative to learn more about any of the following products:
Serviceguard, Serviceguard Manager, Serviceguard Extension for Oracle RAC (SGeRAC), Serviceguard Extension
for SAP (SGeSAP), Enterprise Cluster Master Toolkit (ECMT), Metrocluster, and Continentalclusters.

To know more about how you can meet the demand for higher levels of availability in business IT infrastructure,
minimize downtime, and reduce complexity of configuration and deployment of robust clustered environments,
visit http://www.hp.com/go/ha.

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services.
Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or
omissions contained herein.
Oracle is a registered trademark of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group.
SAP AG in Germany and several other countries. IBM® and DB2® are registered trademarks of IBM in the United States and other countries.

5900-1593, Created March 2012