HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

Checking for inconsistencies .. Done
Cluster cluster1 is an existing cluster
Maximum configured packages parameter is 10.
Configuring 3 package(s).
7 package(s) can be added to this cluster.
200 access policies can be added to this cluster.
Modifying configuration on node host1
Modifying configuration on node host2
Modify the cluster configuration ([y]/n)? y
Marking/unmarking volume groups for use in the cluster
0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%
Modifying the cluster configuration for cluster cluster1.
Modifying node host1 in cluster cluster1.
Modifying node host2 in cluster cluster1.
Modifying the package configuration for package compass1.
Completed the cluster creation.
If the package configuration file contains the appropriate settings, start the Serviceguard service
as described in Section 11.3.4 (page 161).
11.3.3 Modifying the Package Configuration Files
The Serviceguard for Integrity VM toolkit creates templates that supply basic arguments to
Serviceguard parameters. Review and modify the Serviceguard parameters based on the
information for your Serviceguard cluster and the information supplied in the Managing
Serviceguard manual. Make the appropriate changes to the guest-name.config and the
guest-name files.
Edit the package configuration file to add any LVM volume groups that are used by the distributed
guest. Include a separate VOLUME_GROUP parameter for each cluster-aware volume group.
These volume groups will be initialized with the cluster ID when the cmapplyconf command
is used.
11.3.4 Starting the Distributed Guest
To start the distributed guest:, enter the following command:
# cmrunpkg -v guest-name
For example, to start the guest named compass1, enter the following command:
# cmrunpkg -v compass1
Running package compass1 on node host1.
cmrunpkg : Successfully started package compass1.
cmrunpkg : Completed successfully on all packages specified.
Verify that the guest is on and running. Use both the Integrity VM hpvmstatus command and
the Serviceguard cmviewcl command to verify the status. For example:
# hpvmstatus -P compass1
[Virtual Machines]
Virtual Machine Name VM # OS Type State #VCPUs #Devs #Nets Memory Runsysid
==================== ===== ======= ========= ====== ===== ===== ======= ========
compass1 1 HPUX On 1 5 1 512 MB 0
# cmviewcl -v compass1
CLUSTER STATUS
cluster1 up
NODE STATUS STATE
host1 up running
Network_Parameters:
INTERFACE STATUS PATH NAME
PRIMARY up 0/2/1/0/4/1 lan7
PRIMARY up 0/2/1/0/6/1 lan9
PRIMARY up 0/5/1/0/7/0 lan6
STANDBY up 0/1/2/0 lan1
11.3 Serviceguard in VM Host Configuration 161