Managing Serviceguard Nineteenth Edition, Reprinted June 2011

NOTE: You can create file systems by means of the cmpreparestg (1m) command. See
“Using Easy Deployment Commands to Configure the Cluster” (page 153) for more information. If
you use cmpreparestg, you can skip the following steps, but it is a good idea to read them so
that you understand what cmpreparestg does for you.
Use the following commands to create a file system for mounting on the logical volume just created:
1. Create the file system on the newly created volume:
newfs -F vxfs /dev/vx/rdsk/logdata/log_files
2. Create a directory to mount the volume:
mkdir /logs
3. Mount the volume:
mount /dev/vx/dsk/logdata/log_files /logs
4. Check to make sure the file system is present, then unmount the file system:
umount /logs
Deporting Disk Groups
After creating the disk groups that are to be used by Serviceguard packages, use the following
command with each disk group to allow the disk group to be deported by the package control
script on other cluster nodes:
vxdg deport <DiskGroupName>
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 file systems 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 configuration
file, nor in the package 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.
176 Building an HA Cluster Configuration