Managing Serviceguard 12th Edition, March 2006

Building an HA Cluster Configuration
Creating the Storage Infrastructure and Filesystems with LVM and VxVM
Chapter 5222
where <DiskGroupName> is the name of the disk group that will be
activated by the control script.
When all disk groups have been deported, you must issue the following
command on all cluster nodes to allow them to access the disk groups:
# vxdctl enable
Re-Importing Disk Groups
After deporting disk groups, they are not available for use on the node
until they are imported again either by a package control script or with a
vxdg import command. If you need to import a disk group manually for
maintenance or other purposes, you import it, start up all its logical
volumes, and mount filesystems as in the following example:
# vxdg import dg_01
# vxvol -g dg_01 startall
# mount /dev/vx/dsk/dg_01/myvol /mountpoint
NOTE Unlike LVM volume groups, VxVM disk groups are not entered in the
cluster ASCII configuration file, and they are not entered in the package
ASCII configuration file.
Clearimport at System Reboot Time
At system reboot time, the cmcluster RC script does a vxdisk
clearimport on all disks formerly imported by the system, provided
they have the
noautoimport flag set, and provided they are not
currently imported by another running node. The clearimport clears
the host ID on the disk group, to allow any node that is connected to the
disk group to import it when the package moves from one node to
another.
Using the clearimport at reboot time allows Serviceguard to clean up
following a node failure, for example, a system crash during a power
failure. Disks that were imported at the time of the failure still have the
node’s ID written on them, and this ID must be cleared before the
rebooting node or any other node can import them with a package control
script.