HP Serviceguard Version A.11.18 Release Notes, September 2008

NOTE: You are not required to move to LVM 2.0 volume groups and everything will
work as before if you do nothing.
If you do use LVM 2.0 volume groups, you can still manage them with the same
commands as before, although you may have to make minor changes to any scripts
you use that parse the output of lvdisplay, vgdisplay, pvdisplay or vgscan, as
the output of these commands has changed slightly. In addition, new options are
available for some commands.
For more information, see the white paper LVM 2.0 Volume Groups in HP-UX 11i v3 at
docs.hp.com -> 11i v3 -> LVM Volume Manager. For information about all
other aspects of LVM on HP-UX 11i v3, see the Logical Volume Management volume
(volume 3) of the HP-UX System Administrator’s Guide, at the same address.
About olrad
You must remove a LAN or VLAN interface from the cluster configuration before
removing it from the system. You can do this without bringing down the cluster.
HP-UX 11i v3 provides a new option for the olrad command, olrad -C, to help you
determine whether or not an interface is part of the cluster configuration: run olrad
-C with the affected I/O slot ID as argument.
If the NIC is part of the cluster configuration, you’ll see a warning message telling you
to remove it from the configuration before you proceed. See the olrad(1M) manpage
for more information about olrad.
After removing the NIC from the cluster configuration, you can remove it from an
HP-UX 11i v3 cluster node without shutting down the system by running olrad -d.
See “Removing a LAN or VLAN Interface from a Node” in Chapter 7 of Managing
Serviceguard for more information.
About HPVM and Cluster Re-formation Time
When a node fails and the cluster re-forms, Serviceguard must wait a certain amount
of time to allow I/O from the failed node to be written out to the target storage device.
Only after that time has elapsed can Serviceguard allow an adoptive node access to
that device; otherwise data corruption could occur. The amount of time Serviceguard
waits is calculated by Serviceguard and is not user-configurable.
The above is true whether or not the cluster includes virtual machines (VMs), but using
VMs as Serviceguard nodes increases the amount of time Serviceguard needs to wait
before it is safe to allow another node access to the same storage. This additional wait
can increase cluster re-formation time by as much as 70 seconds.
The additional time Serviceguard needs to wait depends in part on whether or not a
VM guest depot is installed on the VM node. (See HP Integrity Virtual Machines
Installation, Configuration, and Administration, at the address given below, for information
48 Serviceguard Version A.11.18 Release Notes