HP Serviceguard Version A.11.18 Release Notes, September 2008

system and application configuration files and scripts to use persistent device files and
in some cases new commands and options; the process is described in the white papers
Migrating from HP-UX 11i v2 to HP-UX 11i v3 and LVM Migration from Legacy to Agile
Naming Model HP-UX 11i v3 at http://www.docs.hp.com.
If you cold-install HP-UX 11i v3, sets of both legacy and persistent device files are
automatically created. In this case, by default the installation process will configure
system devices such as the boot, root, swap, and dump devices to use persistent device
files. This means that system configuration files such as/etc/fstab and /etc/lvmtab
will contain references to persistent device files, but Serviceguard’s functioning will
not be affected by this.
CAUTION: You cannot migrate to the agile addressing scheme during a rolling upgrade
if you are using cluster lock disks as a tie-breaker, because that involves changing the
cluster configuration. But under certain conditions, you can migrate the cluster lock
device file names to the new scheme without bringing the cluster down. For the
requirements and a procedure, see “Updating the Cluster Lock Configuration” in
Chapter 7 of Managing Serviceguard.
NOTE: It is possible, though not a best practice, to use legacy DSFs on some nodes
after migrating to agile addressing on others; this allows you to migrate different nodes
at different times, if necessary.
For more information about agile addressing, see following documents at
http://www.docs.hp.com.:
• the Logical Volume Management volume of the HP-UX System Administrator’s Guide
(in the 11i v3 -> System Administration collection)
• the HP-UX 11i v3 Installation and Update Guide (in the 11i v3 -> Installing
and Updating collection)
• the following white papers:
— The Next Generation Mass Storage Stack (under Network and Systems
Management -> Storage Area Management)
— Migrating from HP-UX 11i v2 to HP-UX 11i v3
— HP-UX 11i v3 Native Multi-Pathing for Mass Storage
— LVM Migration from Legacy to Agile Naming Model HP-UX 11i v3
See also the HP-UX 11i v3 intro(7) manpage.
About LVM 2.0
Logical Volume Manager (LVM) 2.0 volume groups, which remove some of the
limitations imposed by LVM 1.0 volume groups, can be used on systems running
HP-UX 11i v3 0803 Fusion or later with Serviceguard A.11.18 and the Serviceguard
patch listed under “New Features for September 2008 Patch” (page 20).
What’s in this Release 47