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)

Avoiding problem situations
The following problems may arise during Secure Path operations:
• The status of a path is updated only when I/O occurs on that path or when proactive path monit-
oring is enabled.
• Only Fibre Channel connectivity is supported.
• When all paths to an end LUN fail in the case of I/O to non-LVM devices with the HFS file system,
or asynchronous I/O to non-LVM devices, I/O to the LUN waits until connectivity through these
paths are restored. I/O starts only if the original path (the path on which I/O was started) is re-
stored.
• Secure Path does not recognize newly added paths or devices that are in use before running the
autopath discover command.
• Devices are not discovered automatically on installation and after reboot, if autopath discover
is set to off.
• Discovery of new paths or LUNs occurs only if ioscan and insf -e are run before running the
autopath discover command.
• If ioscan and insf -e are not run before running the autopath discover command, and
if changes are made in the SAN, autopath discover may take a long time to complete because
of attempted retries by the lower-level layers on the device paths.
• The Secure Path command line utility (autopath) does not support wildcard characters. For ex-
ample, you cannot use the question mark (?) with a command to invoke the help command.
• If HPswsp is marked for removal using swremove, and if the remove process is aborted, the load
balancing policy setting is reset to NLB (the default).
• In a LUN collision, the new LUN is discovered through paths used by the old LUN, provided the
old LUN is not mounted or open. If the old LUN is mounted or open, the paths to the old LUN are
marked as failed because the LUN is unpresented. To recover the old LUN, assign the same SCSI
LUN ID to the old LUN. To access the new LUN, present it at a different SCSI LUN ID, or unmount
or close the old LUN and run the autopath discover command.
NOTE:
• Supports timeout feature on VxFS file system only.
• If a raw device or a device configured under the HFS file system encounters an All Paths
Fail condition, I/O restarts only if the path on which it was started is active.
• If the file system changes from VxFS to HFS, Secure Path 3.0F SP4 for Active-Active disk arrays
does not automatically set the timeout value for a LUN as Infinite Retry.
• Use autopath delete command before un-presenting the LUN from the host server. This will remove
the existing WWN reference and avoid LUN collisions. This command also needs to be included
in any scripts/applications which add/remove LUNs under Secure Path control.
• The ownership of the virtual device special files created by Secure Path under /hpap/dsk or
/hpap/rdsk may change on reboot. Applications are required to reset the ownership and permis-
sion on reboot.
IMPORTANT:
For information about Secure Path device path representation and usage, see Secure Path device
path representation and usage.
HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 21