Release Notes HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 (5697-8002, March 2009)

Secure Path device path representation and usage
This section provides information about device path representation, usage, and HP recommendations
for Secure Path devices:
• Device path representation of Secure Path for Active-Active disk arrays
• Differences between Secure Path for Active-Active disk arrays and LVM PVLINKS
• HP recommendations
Device path representation of Secure Path for Active-Active disk arrays
Secure Path for Active-Active disk arrays uses the physical paths to an end device. HP-UX sees the
alternate paths as actual device files. You can view and access these paths.
Example:
# autopath display
==================================================================
HPswsp Version : A.3.0F.04F.00F
==================================================================
Auto Discover : OFF
==================================================================
Array Type : EVA-AA
Array WWN : 5000-1FE1-0015-3530
Read Optimize : ON
Path Verification Period : 00:10
==================================================================
Lun WWN : 6005-08B4-0010-735A-0000-5000-0082-0000
Virtual Device File : /hpap/dsk/hpap0
Load Balancing Policy : No Load Balancing
Lun Timeout : Infinite Retry (-1)
==================================================================
Device Path Status
==================================================================
/dev/dsk/c10t0d1 Active
/dev/dsk/c12t0d1 Active
/dev/dsk/c14t0d1 Active
/dev/dsk/c16t0d1 Active
==================================================================
Differences between Secure Path for Active-Active disk arrays and LVM PVLINKS
This section provides information about Secure Path for Active-Active disk arrays with LVM and LVM
PVLINKS:
• Secure Path for Active-Active disk arrays with LVM
• Secure Path for Active-Active disk arrays with LVM PVLINKS
Secure Path for Active-Active disk arrays with LVM
For a device configured under LVM, if the LVM primary path fails, then Secure Path fails over to an
alternate path and continues processing the I/O until the primary path is restored. When the primary
path is restored, I/O resumes on the LVM primary path.
22