Installation and Reference Guide HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 (5697-8001, March 2009)
• Support for Virtual Device Special File (referred as “vdsf” throughout this guide)
for each LUN under Secure Path’s control that are not configured under HP LVM to provide high-
availability access to raw devices
• Includes a new autopath virtualdsf command to create virtual device files for the LUNs
under Secure Path's control
• Includes a new autopath monitor command to start the monitor deamon to control the failback
and pro-active path monitor features for faster path failover and recovery.
• Supports high-availability dump device on HP-UX 11i v2.0 systems
• Supports interoperability with VxVM 4.1 on 11i v2.0 systems
• Supports rerouting VxVM based I/O's. The I/O is returned to VxVM only on an All Paths
Failed condition
• Supports periodic path polling to check the path state changes
• Supports read optimization with asymmetric EVA Active-Active arrays to increase the I/O perform-
ance
• Supports addition or deletion of EVA arrays using the array WWN and for XP arrays using the
array ID
IMPORTANT:
You must disable the VERITAS DMP multipath feature on a Secure Path owned device, or remove
the device from Secure Path's control by running the autopath delete command to avoid
interoperatebility issues with VxVM 4.1 and Secure Path 3.0F SP4 on HP-UX 11i v2.0.
The HP StorageWorks Secure Path software performs dynamic load balancing of data flow through
multiple paths. It detects multiple paths to each logical device and distributes the data load among
the paths for optimum performance.
The user interface lets a system administrator define load balancing policies and preferred paths and
view device path information. Secure Path manages paths according to the load balancing policy,
ensuring that no single path is a performance bottleneck.
To configure the high-availability dump device on your HP–UX 11i v2.0 systems, you must not use a
device path that has failed even if it has alternate active device paths. If the dump device patch is
not installed and the autopath discover command is run, warning messages are displayed in
the syslog.
You cannot delete an array or array type, if a LUN of the array:
• Is mounted with failed paths, or
• Is open or configured as a dump device.
In such cases, to delete the array or array type, do either of the following:
1. Run the autopath delete – a <array ID> command after restoring the LUNs on the array.
NOTE:
Use caution before running the autopath delete – a <array ID> command. The
persistence of all LUN parameters on the array is lost after you run the autopath delete
-a <array ID> or autopath delete –r <array type> command.
2. Run the autopath discover command to restore the LUNs on the array.
Secure Path for Active-Active disk arrays80