HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

HPVM_VOLUME_GROUP /dev/vgmobileG
HPVM_VOLUME_GROUP /dev/vgsharedA
#
NOTE: Each SLVM volume group being used by Integrity VM must have an entry.
f. Check the cluster:
# cmcheckconf -k -v -C /etc/cmcluster/creekQuorumRiver.cfg
Begin cluster verification...
Checking cluster file: /etc/cmcluster/creekQuorumRiver.cfg
Defaulting MAX_CONFIGURED_PACKAGES to 300.
Checking nodes ...
Creating the cluster configuration for cluster River
Adding node creek1 to cluster River
Adding node creek2 to cluster River
cmcheckconf: Verification completed with no errors found.
Use the cmapplyconf command to apply the configuration.
#
Note the next to last message, “Verification completed with no errors found.”
g. Apply the configuration:
# cmapplyconf -v -C /etc/cmcluster/creekQuorumRiver.cfg
Begin cluster verification...
Checking cluster file: /etc/cmcluster/creekQuorumRiver.cfg
Defaulting MAX_CONFIGURED_PACKAGES to 300.
Checking nodes ...
Creating the cluster configuration for cluster River
Adding node creek1 to cluster River
Adding node creek2 to cluster River
Marking/unmarking volume groups for use in the cluster
Completed the cluster creation
#
h. Start the cluster:
# cmruncl
cmruncl: Validating network configuration...
cmruncl: Network validation complete
Waiting for cluster to form .... done
Cluster successfully formed.
Check the syslog files on all nodes in the cluster to verify that no warnings occurred during startup.
#
4. Activate the volume groups correctly:
a. On all the VM Hosts where this cluster is defined, activate the VG:
# vgchange -a s -p /dev/vgsharedA
Activated volume group in Shared Mode.
This node is the Server.
Volume group "/dev/vgsharedA" has been successfully changed.
#
b. Check the VG Status line of the vgdisplay —v /dev/vgname output to make sure
that it is shared:
# vgdisplay -v /dev/vgsharedA | grep "VG Status"
VG Status available, shared, client
If the VG is not listed as shared, deactivate it and reactivate it with vgdisplay —v
/dev/vgname.
11.5 Migrating VMs That are Using Logical Volume Backing Stores 203