HP Serviceguard A.11.20.20 for Linux Release Notes, May 2013

6.6 Installing the Quorum Server
If you choose to use a Quorum Server rather than a lock LUN for tie-breaking, install the Quorum
Server software on a system outside the cluster. The Quorum Server software is on the Serviceguard
for Linux CD. Updated versions may be available from http://www.hp.com/go/softwaredepot.
CAUTION: If you are upgrading both the Quorum Server and Serviceguard for Linux, upgrade
the Quorum Server before you upgrade Serviceguard. This is especially important if you are using
an alternate quorum server subnet. See “Quorum server upgrade required if you are using an
alternate address (page 31).
For more information about Linux installation and configuration process, see Quorum Server Version
A.04.00 Release Notes at http://www.hp.com/go/hpux-serviceguard-docs —> HP Serviceguard
Quorum Server Software.
For more information about the Quorum Server, see Managing HP Serviceguard A.11.20.10 for
Linux manual at http://www.hp.com/go/linux-serviceguard-docs.
6.7 Setting permissions on the /root/.rhosts file
The /root/.rhosts file must not allow write access by group or other. If /root/.rhosts
file write permission is enabled for other or group, HP Serviceguard for Linux commands will
fail, logging a Permission denied for user message. This situation can arise when the
Serviceguard remote security file, $SGCONF/cmclnodelist, is not used and remote node security
is resolved by means of .rhosts.
NOTE: /etc/cmcluster.conf contains the mappings that resolve the symbolic references to
$SGCONF, $SGROOT, and so on, used in these Release Notes. See Understanding the Location of
Serviceguard Files in Chapter 5 of the Managing HP Serviceguard for Linux manual for details.
For more information about configuring security for prospective cluster nodes, and for an existing
cluster, see Chapter 5 of Managing HP Serviceguard for Linux.
6.8 Rolling software upgrades
You can upgrade the Linux operating system and the Serviceguard software one node at a time
without bringing down your clusters. This process can also be used any time when a node in the
cluster needs to be taken offline for hardware maintenance or patch installations. Until the process
of upgrade is complete on all nodes, you cannot change the cluster configuration files, and you
will not be able to use any of the features of the new Serviceguard release.
NOTE: On Red Hat Enterprise Linux or SUSE Linux Enterprise Server, rolling upgrade is allowed
from A.11.19 to A.11.20.20. During rolling upgrade, on the node being upgraded, you must first
install Serviceguard for Linux A.11.20.00 (on Red Hat Enterprise Linux 5 and 6) and A.11.20.10
(on SUSE Linux Enterprise Server 11) and then upgrade it to Serviceguard for Linux A.11.20.20
using the appropriate patch. After the successful installation of A.11.20.20, make the node join
the cluster.
6 Compatibility and installation requirements 19