Serviceguard Extension for RAC Version A.11.20 Release Notes, April 2013

Agile addressing is the default on new 11i v3 installations, but the I/O subsystem still recognizes
pre-11i v3 device files, referred to as legacy device files. Device files using the new nomenclature
are called persistent device files. When you upgrade to HP-UX 11i v3, a set of new, persistent
device files is created. The existing legacy device files are left intact and by default will continue
to be used by HP-UX and Serviceguard.
This means that you are not required to migrate to agile addressing when you upgrade to 11i v3,
though you should seriously consider its advantages (see the white paper The Next Generation
Mass Storage Stack at www.hp.com/go/hpux-core-docs —> HP-UX 11i v3 —> white
papers).
Migration involves modifying 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 HP-UX 11i v2 to 11i v3 Mass Storage Stack Update Guide and LVM Migration from Legacy
to Agile Naming Model HP-UX 11i v3 at www.hp.com/go/hpux-core-docs —> HP-UX 11i
v3 —> white papers.
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.
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 the section “Updating
the Cluster Lock Configuration” in chapter 7 of the latest edition of Managing Serviceguard.
NOTE: It is possible, though not a best practice, to continue to use legacy DSFs on some nodes
after migrating to agile addressing on others. If necessary, this allows you to migrate different
nodes at different times.
For more information about agile addressing, see following documents at www.hp.com/go/
hpux-core-docs —> HP-UX 11i v3:
• HP-UX System Administrator's Guide: Logical Volume Management HP-UX 11i Version 3
(under User guide section)
• HP-UX 11i v3 Installation and Update Guide (under Setup and install - general section)
• white papers:
The Next Generation Mass Storage Stack◦
◦ HP-UX 11i v2 to 11i v3 Mass Storage Stack Update Guide
◦ HP-UX 11i v3 Native Multi-Pathing for Mass Storage
◦ LVM Migration from Legacy to Agile Naming Model HP-UX 11i v3
See also www.hp.com/go/hpux-core-docs —> HP-UX Manpages for HP-UX 11i v3.
Cluster-wide Device Special Files (cDSFs)
Because DSF names may be duplicated between one host and other, it is possible for different
storage devices to have the same name on different nodes in a cluster, and for the same piece of
storage to be addressed by different names. Cluster-wide device files (cDSFs), available as of the
September 2010 Fusion Release, ensure that each storage device used by the cluster (or any group
of nodes within the cluster that you specify) has a unique device file name.
Announcements 9