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

 

package failover

site_preferred (default)

Other possible value:

site_preferred_manual (The user needs to manually edit the generated configuration file in this case)

auto-created (recommended)

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

 

that are managed by Site

 

Controller

Any package name that is already

User input

configured in the cluster

 

Appropriate

Indicates the Metrocluster module

Metrocluster module

that will be included in the Site

parameters

Controller package configuration

This module will be dependent on the

Auto-discovered

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.

 

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

Page 28
Image 28
HP Serviceguard Extension for SAP (SGeSAP) manual How is it