HP Serviceguard Metrocluster with EMC SRDF for Linux B.01.00.00

Serviceguard variables are not defined on your system, then include the file /etc/
cmcluster.conf in your login profile for the root user. For more information on these parameters,
see Understanding the Location of Serviceguard Files and Enabling Serviceguard Command Access
sections in Managing Serviceguard for Linux A.11.20 available at http://www.hp.com/go/
linux-serviceguard-docs.
Create the cluster or clusters according to the process described in the Managing Serviceguard
for Linux A.11.20 manual available at http://www.hp.com/go/linux-serviceguard-docs. In the
case of a Metrocluster, create a single Serviceguard cluster with components on multiple sites.
NOTE: Do not configure an SRDF device belonging to a device group as a cluster lock disk. A
cluster lock disk must always be writable. Since it cannot be guaranteed that either half of a paired
volume is always writable, neither half may be used as a cluster lock disk. A configuration with a
cluster lock disk that is part of a paired volume is not a supported configuration.
Site aware failover configuration
To use either of these policies: site_preferred_manual or site_preferred, the underlying
cluster must be configured with sites and each cluster node must be associated to a site. The
Serviceguard cluster configuration file includes the attributes described in Table 2 (page 23) to
define sites.
Table 2 Site aware failover configuration
DescriptionAttributes
To define a unique name for a site in the cluster.SITE_NAME
SITE keyword under the node's NODE_NAME definition.SITE
Following is a sample of the site definition in a Serviceguard cluster configuration file:
SITE_NAME san_francisco
SITE_NAME san_jose
SITE san_francisco
NODE_NAME SFO_2
SITE san_francisco
NODE_NAME SJC_1
SITE san_jose
NODE_NAME SJC_2
SITE san_jose
Use the cmviewcl command to view the list of sites that are configured in the cluster and their
associated nodes. Following is a sample of the command, and the output:
# cmviewcl -l node
SITE_NAME san_francisco
NODE STATUS STATE
SFO_1 up running
SFO_2 up running
.........
SITE_NAME san_jose
NODE STATUS STATE
SJC_1 up running
SJC_2 up running
You can configure either of these failover policies for regular Metrocluster failover packages. To
use these policies, you must specify site_preferred or site_preferred_manual for the
failover_policy attribute in the Metrocluster package configuration file.
NOTE: For a Metrocluster package, set the failover_policy parameter to site_preferred.
Creating the cluster 23