Managing Serviceguard Nineteenth Edition, Reprinted June 2011

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 ____________________________________________

Cluster Name: ___________________________________________________________

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.

• You must group high availability applications, services, and data, whose control needs to be

transferred together, onto a single volume group or series of volume groups.

• You must not group two different high-availability applications, services, or data, whose control

needs to be transferred independently, onto the same volume group.

• Your root disk must not belong to a volume group that can be activated on another node.

• HP recommends that you use volume group names other than the default volume group names

(vg01, vg02, etc.). Choosing volume group names that represent the high availability

applications that they are associated with (for example, /dev/vgdatabase will simplify

cluster administration).

• Logical Volume Manager (LVM) 2.0 volume groups, which remove some of the limitations

imposed by LVM 1.0 volume groups, can be used on systems running some recent versions

of HP-UX 11i v3 and Serviceguard. Check the Release Notes for your version of Servicegaurd

for details. For more information, see the white paper LVM 2.0 Volume Groups in HP-UX 11i

v3 at http://www.hp.com/go/hpux-core-docs -> HP–UX 11i v3.

Using EMS to Monitor Volume Groups

You can use EMS (Event Monitoring Service) resource monitors to monitor the status of LVM volume

groups used by packages. You do this by defining a resource for the package, as in the example

that follows.

96 Planning and Documenting an HA Cluster