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)

• After a LUN has been deleted using the spmgr delete command, and is unpresented at the
array, any re-presenting of that device and an ioscan results in the device being displayed in
the spmgr display –u unattached list. The Secure Path driver keeps track of the deleted status
of the device WWLUNID.
• Do not make any SAN configuration changes to the system when upgrading or installing Secure
Path. For example, do not add new LUNs or delete arrays or LUNs.
• When the system is booting, do not execute Secure Path commands until the Secure Path startup
services have started.
• If you configure Secure Path devices under volume groups and reboot the system, the volume
groups are not activated as part of the system's volume group configuration during boot time. This
occurs because the Secure Path persistence module is loaded (at init level 1) only when the
LVM configuration is complete (before init level 1). The volume groups are activated by
Secure Path's init script at init level 2.
• Concurrent or overlapping ioscans can result in the first ioscan reporting intermediate path
states of the second ioscan. The second ioscan correctly reports the state of the paths. An ap-
plication doing ioscan compares could erroneously detect an error when another ioscan begins.
• During an ioscan, sdisk drivers attach to swsp interface drivers instead of fcparray (SCSI-
3) or fcpdev (SCSI-2). Be careful with applications that use ioscan output that depends on
the hardware tree that existed before installation of Secure Path.
• When a path to a device managed by LVM becomes unavailable because of a controller, path
link, switch, or HBA failure, you can delay the I/O requests by up to one minute immediately after
the failure. As a result, the responsiveness of mirrored logical volumes may be affected briefly.
When a physical volume becomes unavailable, applications generally experience a delay while
an I/O request to that physical volume times out. By default, this delay is 30 seconds, but you can
change the delay time using the pvchange(1M) command.
• If you issue a read command, LVM selects another mirror and tries again.
• If you issue a write command, LVM records the error and continues, as long as the data has
been written successfully to at least one mirror.
In either case, with Secure Path installed, this initial time out can take up to one minute. LVM keeps
track of the physical volume status as Unavailable and future I/O requests do not experience this
delay.
NOTE:
Before deactivating the volume group, ensure that all logical volumes of the volume group are
unmounted. See Secure Path device path representation and usage for details.
HP StorageWorks Secure Path 3.0F Service Pack 4 for HP-UX 11i v1.0 and 11i v2.0 17