Overview: The Next Generation Mass Storage Stack (September 2009)

Table Of Contents
DSFs. For example:
# lvlnboot -v
Boot Definitions for Volume Group vg00:
Physical Volumes in Root Volume Group:
/dev/disk/disk48_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk48_p2
Root: lvol3 on: /dev/disk/disk48_p2
Swap: lvol2 on: /dev/disk/disk48_p2
Dump: lvol2 on: /dev/disk/disk48_p2, 0
legacy DSFs. For example:
# lvlnboot -v
Boot Definitions for Volume Group vg00:
Physical Volumes in Root Volume Group:
/dev/dsk/c0t0d0s2 -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t0d0s2
Root: lvol3 on: /dev/dsk/c0t0d0s2
Swap: lvol2 on: /dev/dsk/c0t0d0s2
Dump: lvol2 on: /dev/dsk/c0t0d0s2, 0
Sets default view to legacy Sets default view to legacy
Enables multi-pathing on legacy and persistent DSFs Enables multi-pathing on legacy and persistent DSFs
Sets I/O retry policy to infinite retries Sets I/O retry policy to infinite retries
Table 1: Differences Between Installing and Updating to HP-UX 11i v3
Migrating an Existing System
The migration process from the legacy view to the agile view has a dedicated white paper entitled HP-UX 11i v3
Persistent DSF Migration Guide. It is described in the For More
Information section.
Note: Some systems can only be partially migrated away from the use of legacy DSFs. Some applications, such
as ISVs, do not yet support the agile view. Check the list of restrictions in the HP-UX 11i v3 Persistent DSF
Migration Guide.
Migrating Kernel Software
If you are an independent software or hardware vendor (ISV/IHV) who delivers kernel components, your
migration to the next generation mass storage environment might require changes to your software. For example,
interface drivers must now register their controller and target devices with the SCSI stack. Class drivers must
register with the SCSI stack and may claim LUNs based on their peripheral data type, vendor identifier, and
product identifier. Lock management, I/O prioritization, error recovery, and asynchronous event notification have
also been modified.
For more information on migrating to HP-UX 11i v3, see the following documents on the HP websites:
Driver Development Kit
http://www.hp.com/go/hpux_ddk
Software Transition Kit
http://devresource.hp.com/STK/
Conclusion
The next generation mass storage stack represents a paradigm shift in the management of disks and tapes. Agile
addressing and native multi-pathing coupled with increased adaptability, scalability, and performance make the
I/O subsystem in HP-UX 11i v3 easier to manage. New and expanded commands, as well as integration of other
software components with the mass storage stack, present a simplified and consistent interface to mass storage.
Finally, the ability to select either the legacy or the agile view retains backward compatibility with previous HP-UX
releases.
37