Veritas Volume Manager 4.1 Administrator's Guide (HP-UX 11i v3, February 2007)

Cluster Initialization and Configuration
358 VERITAS Volume Manager Administrator’s Guide
The detach policy does not change the requirement that a node joining a cluster must have
access to all the disks in all shared disk groups. Similarly, a node that is removed from the
cluster because of an I/O failure cannot rejoin the cluster until this requirement is met.
Limitations of Shared Disk Groups
Note The boot disk group (usually aliased as bootdg) cannot be made cluster-shareable.
It must be private.
Only raw device access may be performed via the cluster functionality of VxVM. It does
not support shared access to file systems in shared volumes unless the appropriate
software is installed and configured.
The cluster functionality of VxVM does not support RAID-5 volumes, or task monitoring
for cluster-shareable disk groups. These features can, however, be used in private disk
groups that are attached to specific nodes of a cluster.
If you have RAID-5 volumes in a private disk group that you wish to make shareable, you
must first relayout the volumes as a supported volume type such as stripe-mirror or
mirror-stripe. Online relayout of shared volumes is supported provided that it does
not involve RAID-5 volumes.
If a shared disk group contains RAID-5 volumes, deport it and then reimport the disk
group as private on one of the cluster nodes. Reorganize the volumes into layouts that are
supported for shared disk groups, and then deport and reimport the disk group as shared.
Cluster Initialization and Configuration
Before any nodes can join a new cluster for the first time, you must supply certain
configuration information during cluster monitor setup. This information is normally
stored in some form of cluster monitor configuration database. The precise content and
format of this information depends on the characteristics of the cluster monitor. The
information required by VxVM is as follows:
◆ cluster ID
◆ node IDs
◆ network addresses of nodes
◆ port addresses
When a node joins the cluster, this information is automatically loaded into VxVM on that
node at node startup time.