This section lists release notes specific to using Serviceguard
in the Integrity VM environment.
Do not attempt to use guests as Serviceguard packages and guests
as Serviceguard nodes at the same time on the same VM Host system.
You can install HP Serviceguard A.11.16 or 11.17 on the VM Host
or on the HP-UX guest. You can install HP Serviceguard 11.18 only
on guests running HP-UX 11i v3.
Packaging VM Guest with CFS/CVM Backing Stores as Serviceguard
Packages |
 |
When creating a Serviceguard cluster with virtual machines acting
as packages, the hpvmsg_package script correctly
identifies CVM logical volumes and CFS files backing stores used by
guests but requires users to verify or provide activation modes and
package dependencies for the backing stores.
The hpvmsg_package script creates the package
configuration in the package directory: /etc/cmcluster/hpvm-name/hpvm-name.conf. Inside the configuration file are instructions, examples, and default
and assigned named-values pairs describing the resources used by the
virtual machines and controlled and monitored by Serviceguard.
For information about selecting the appropriate values for these
items, see the templates files in the Managing Servicguard manual and the Veritas Storage Foundation 5.0 Cluster File System
Administration Guide Extracts for HP Serviceguard Storage Management
Suite.
File Permission Errors When Checking or Applying Integrity
VM Serviceguard Packages to the Cluster Configuration |
|
Depending on the system configuration, you might see an error
similar to the following when running cmcheckconf or cmapplyconf to the virtual machine packages:
# cmapplyconf -P /etc/cmcluster/hpvm-sg1-g4/hpvm-sg1-g4.conf
Incorrect permissions for /etc/cmcluster/hpvm-sg1-g4 (40777). Directory must be executable for owner, and not writable by group and others on node hpvm-sg1-h1.
cmapplyconf: Error found in package file: /etc/cmcluster/hpvm-sg1-g4/hpvm-sg1-g4.conf.
|
To correct this issue, use a chmod command similar to the following
to correct the permission of the package directory on each of the
cluster members:
# chmod go-w /etc/cmcluster/hpvm-name |
Status of Serviceguard Controlled Distributed Guests can Lag |
|
When Integrity VM guests are configured as packages in a Serviceguard
(SG) cluster, hpvmstatus displays which VM Host
is running the distributed guests as an SG package. Because this information
comes from SG, it can be delayed by as much as 10 seconds. This delay
does not cause any risk of starting the same guest on two different
Integrity VM Hosts, because SG is controlling the start of these guests
and allows only a single instance to run at any one time.
The hpvmsg_package Does Not Add Appropriate Entries |
|
The hpvmsg_package does not add appropriate
entries to the package configuration and control script files. After
running the /opt/cmcluster/toolkit/hpvmsg_package script to package a guest that contains CVM or CFS backing stores,
review and modify the package configuration and control scripts for
each cluster member. As part of this process, add CVM and/or CFS backing
store entries to these files.
The package configuration and control scripts can be found at: /etc/cluster/guest-name/
Problem Displaying Truncated IPv6 Address for AVIO LAN with hpvmstatus and hpvmnet Commands |
|
For a guest configured with the AVIO adapter as a network device
(avio_lan) and also configured with an IPv6 address, the IPv6 address
displayed by hpvmstatus -V and hpvmnet -V may be truncated.
Using AVIO LAN Device in a Serviceguard Configured Guest |
|
When using AVIO networking devices for guests that are configured
as Serviceguard Packages, be sure that all Serviceguard standby lans are configured using PPA devices supported by AVIO.
Failure to do so causes network connectivity to be lost even if the
standby link is up.
Required HP Serviceguard Patches |
|
To use Serviceguard to manage HP-UX guests, make sure the required
patches are installed. For more information, see Section .
Reenter Command to Start Packages |
|
The procedure for configuring and starting guest packages includes
the cmrunpkg command. This command does not always
work the first time you enter it. If the command does not start the
package, re-enter the command.
Do not Use Integrity VM Commands to Manage Distributed Guests |
|
Guests configured as Serviceguard packages should only be stopped
and started using Serviceguard package control commands. Do not use
the Integrity VM commands (hpvmstart, hpvmstop, and hpvmconsole) to start
and stop these types of guests. For more information about using Serviceguard
to manage virtual machines, see the Integrity Virtual Machines
Installation, Configuration, and Administration manual.
Different Cluster Nodes Report Virtual Machine Status Differently |
|
Integrity VM commands can receive different warnings and errors
from guests running on different Serviceguard nodes. For example,
the Serviceguard node that is starting a guest as part of a package
knows that the guest is running before any other nodes know. (The
delay is usually less than 10 seconds.) Commands that are run on
different servers report different errors or warnings depending on
whether the guest is running or not.
Syslog Entries for cmcld Can
Be Ignored |
|
With Serviceguard and Integrity VM running, you might see the
following types of message in the syslog file:
Syslog entries - cmcld[XXXX]: Warning: cmcld process was unable to run for the last X.XX seconds |
These messages can be ignored.
Using Virtual Machines Manager (VM Manager) to Manage Distributed
Guests |
|
The following situations might occur when you are using VSE
to manage distributed guests (guests that are configured as Serviceguard
packages):
There is a guest configuration file for each guest
on each VM Host. Therefore, when you modify a distributed guest you
must modify the guest on each VM Host that is a cluster node.
Do not start and stop distributed guests using VM
Manager menu items. Use Serviceguard commands to start and stop distributed
virtual machines. For more information, see the HP Integrity
Virtual Machines Installation, Configuration, and Administration manual.
The VM Hosts field on the VM
Properties page sometimes shows an incorrect list of hosts in the
cluster. If VM Manager is running on the VM Host that is actively
managing the virtual machine that is being viewed, the list is correct.
In all other cases, the list is incorrect.
Printable version
