HP Serviceguard Extended Distance Cluster for Linux A.01.01 Release Notes, Third Edition, May 2009

NOTE: After installing the Extended Distance Cluster software, you need to configure
Software RAID. The configuration involves creating a package directory and copying
the raid.conf.template file into the relevant package directories. For more
information on creating a package and copying the raid.conf.template file, see
the HP Serviceguard Extended Distance Cluster for Linux Deployment Guide.
Rolling Software Upgrades
If you have already deployed XDC A.01.00 with HP Serviceguard for Linux 11.16, you
can upgrade HP Serviceguard and XDC software one node at a time without bringing
down your clusters. You can complete this process at a time when one system needs
to be taken offline for hardware maintenance or patch installations.
For more information completing a rolling upgrade, see section Upgrading to HP
Serviceguard A.11.18 and XDC A.01.01 in the HP Serviceguard Extended Distance Cluster
for Linux Deployment Guide, Second Edition.
Verifying Installation
After you install XDC, run the following command to ensure that the software is
installed:
# rpm -qa | grep xdc
In the output, the product name, xdc -A.01.01-0 will be listed. The presence of this
file verifies that the installation is successful.
Support for a 4-Node Cluster
XDC now supports a 4-node extended distance cluster for Linux. In this cluster
configuration, 2 nodes are at one site, while the other 2 nodes form the other site. These
sites are geographically dispersed. To ensure that a package is capable of running on
4 nodes and that the data is replicated, you must specify an order of failover for a
package in the package configuration file. The package configuration file contains an
ordered list of nodes on which the package needs to run. This order of nodes is specified
using NODE_NAME parameter.
While specifying the order of nodes in the package configuration file, ensure that every
node in one site is followed by a node of the other site. In other words, you must ensure
that the first node and the second adoptive node for a package are in different sites.
Similarly, the second node and the third adoptive node must be in different sites. The
third and the fourth adoptive nodes must also be in different sites. With this
configuration, if a packages fails on a node in one site, it is targeted to startup on a node
in a different site. Figure 1-1 and Table 1-2 elaborate this configuration order.
Compatibility Information and Installation Requirements 11