Managing Serviceguard Eighteenth Edition, September 2010

to agile addressing when you upgrade to 11i v3, though you should seriously consider
its advantages.
For instructions on migrating a system to agile addressing, see the white paper LVM
Migration from Legacy to Agile Naming Model at www.hp.com/go/hpux-core-docs.
NOTE: It is possible, though not a best practice, to use legacy DSFs (that is, DSFs
using the older naming convention) on some nodes after migrating to agile addressing
on others; this allows you to migrate different nodes at different times, if necessary.
For information on migrating cluster lock volumes to agile addressing, see “Updating
the Cluster Lock Configuration” (page 364).
For more information about agile addressing, see following documents in the 11i v3
collection at www.hp.com/go/hpux-core-docs:
• the Logical Volume Management volume of the HP-UX System Administrator’s Guide
• the HP-UX 11i v3 Installation and Update Guide
• the white papers:
— Overview: The Next Generation Mass Storage Stack
— HP-UX 11i v3 Persistent DSF Migration Guide
— LVM Migration from Legacy to Agile Naming Model
— HP-UX 11i v3 Native Multi-Pathing for Mass Storage
See also the HP-UX 11i v3 intro(7) manpage, and“About Multipathing” (page 45).
NOTE: As of A.11.20, Serviceguard supports cluster-wide DSFs, and HP recommends
that you use them. See “About Cluster-wide Device Special Files (cDSFs)” (page 135).
Examples of Mirrored Storage
Figure 3-20 shows an illustration of mirrored storage using HA storage racks. In the
example, node1 and node2 are cabled in a parallel configuration, each with redundant
paths to two shared storage devices. Each of two nodes also has two (non-shared)
internal disks which are used for the root file system, swap etc. Each shared storage
unit has three disks, The device file names of the three disks on one of the two storage
units are c0t0d0, c0t1d0, and c0t2d0. On the other, they are c1t0d0, c1t1d0,
andc1t2d0.
Volume Managers for Data Storage 107