Managing Serviceguard Seventeenth Edition, First Reprint December 2009
Quorum Server Worksheet
You may find it useful to use a Quorum Server worksheet, as in the example that
follows, to identify a quorum server for use with one or more clusters. You may also
want to enter quorum server host and timing parameters on the Cluster Configuration
Worksheet. Blank worksheets are in Blank Planning Worksheets (page 429).
You can use the Quorum Server worksheet to record the following:
Quorum Server Host
The host name (and alternate address, if any) for the
quorum server.
IP Address
The IP address(es) by which the quorum server will
be connected to the cluster.
Supported Node Names
The name (39 characters or fewer) of each cluster node
that will be supported by this quorum server. These
entries will be entered into qs_authfile on the
system that is running the quorum server process.
Quorum Server Data:
==============================================================================
QS Hostname: __________IP Address: _______________IP Address:_______________
==============================================================================
Quorum Services are Provided for:
Cluster Name: ___________________________________________________________
Host Names ____________________________________________
Host Names ____________________________________________
Cluster Name: ___________________________________________________________
Host Names ____________________________________________
Host Names ____________________________________________
LVM Planning
You can create storage groups using the HP-UX Logical Volume Manager (LVM), or
using Veritas VxVM and CVM software as described in the next section.
When designing your disk layout using LVM, you should consider the following:
• The root disk should belong to its own volume group.
• The volume groups that contain high availability applications, services, or data
must be on a bus or busses available to the primary node and all adoptive nodes.
• High availability applications, services, and data should be placed in a separate
volume group from non-high availability applications, services, and data.
LVM Planning 131