Using Easy Deployment in Serviceguard and Metrocluster environments on HP-UX 11i v3

32
Parameter What it means Value
How is it
generated?
managed_packages Indicates the name of
packages that are managed
by Site Controller
Any package name that is already configured
in the cluster
User input
Appropriate
Metrocluster module
parameters
Indicates the Metrocluster
module that will be included in
the Site Controller package
configuration
This module will be dependent on the type of
replication pair used by the 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.
Auto-discovered.
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.
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.