HP Serviceguard Toolkit for Integrity Virtual Servers Release Notes Version B.02.00

To receive the latest information on recommended patches, product support matrices, and recently
supported hardware, subscribe to the High Availability program tips and issues digest available
at http://www.hp.com/go/hpux-serviceguard-docs.
Patches can be superseded or withdrawn at any time. Check the status of any patch before
downloading it. An updated list of patches is available on the Hewlett-Packard Support Center
website at:
http://www.hp.com/go/hpsc
Fixes
The following defects are fixed in patch PHSS_43634 release:
QXCR1001294741 Executing cmhaltnode -f might start up multiple vswitchmgr processes
on alternate nodes.
QXCR1001296407 Enabling graceful shutdown of VM or vPar guest through the SG IVS Toolkit.
QXCR1001324239 When a Serviceguard package configuration is created using
cmdeployvpkg for HPVM or HP-UX vPars with CVM disk backing stores,
package startup fails with the following errors in the package log:
Activating disk group cfsdg1 with non-exclusive option.
VxVM vxdg ERROR V-5-1-3424 Disk group cfsdg1:
activation failed: Disk group already activated
ERROR: Function sg_activate_disk_group
ERROR: Failed to activate cfsdg1
QXCR1001291588 This is an enhancement to cmdeployvpkg to support creating Serviceguard
package configurations for HPVM or HP-UX vPars with NFS file backing
store.
The following defects are fixed in patch PHSS_43573 release:
QXCR1001266212 Problem: When you create a Serviceguard package for an HPVM or vPar
guest that has the DIO interface, the cmdeployvpkg and cmapplyconf
commands display the following error without suggesting an action to the
reported problem.
Failed to set application control for vpar2 :
hpvmmodify: Cannot set '-j 1' because the guest has at least one DIO
device.
QXCR1001266214 Problem: After a DIO interface error occurs while creating a Seviceguard
package for VM or vPar guest, you might not be able to modify VM or vPar
by using the hpvmmodify command. The DIO interface error is reported in
QXCR1001266212.
QXCR1001200150 Problem: If Serviceguard messages are not logged in syslog.log file, or if
there is a problem logging to syslog.log file, the vswitch manager does not
detect a local failover. Because of this, the vswitch cannot be re configured
and VM or vPar guest are not reachable.
The following defect is fixed in the patch PHSS_43277:
QXCR1001248759 Problem: A Serviceguard IVS package fails to start on an adaptive node
after a node failure is reported in the package log. The log file displays
that the VM is running on another node when it is not. The package log
has the following error messages:
nl
ERROR: VM is already running on node
nl
ERROR: Function start_vpar_or_vm: Failed to start VM
process
The following defects are fixed in the patch PHSS_43126:
Patches and fixes in this version 7