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)

General problems
This section describes problems that may arise during Secure Path operation and how to avoid them.
• When Secure Path is installed on HP-UX 11i v1.0 and 11i v2.0, the following warning messages
are displayed, which you can ignore:
ld: (Warning) Ignoring .IA_64.unwind_hdr section in file
"/usr/conf/mod/hsx".
ld: (Warning) Ignoring .IA_64.unwind_hdr section in file
"/usr/conf/mod/swsp".
ld: (Warning) Ignoring .IA_64.unwind_hdr section in file
"/usr/conf/mod/swspBus" . 3 warnings.
• After adding new LUNs and executing ioscan, a syslog message indicates that the ioscan
operation aborted. If the newly added LUNs are owned by sdisk instead of hsx (Secure Path),
run rmsf - H h/w_addr for that sdisk entry, and then run ioscan to enable ownership of
the LUNs by Secure Path.
• Concurrent or overlapping ioscans can result in the first ioscan reporting the intermediate path
states of the second ioscan while the second ioscan correctly reports the state of the paths. An
application that performs ioscan comparisons could erroneously detect an error when overlapped
by another ioscan.
• During an ioscan, sdisk drivers attach to swsp interface drivers instead of to the fcparray
(SCSI-3) or fcpdev (SCSI-2). Be careful with applications that use ioscan outputs that
depend on the hardware tree, which existed prior to Secure Path installation.
• When a path to a device managed by LVM becomes unavailable because of a controller, path
link, switch, or HBA failure, I/O requests can be delayed by up to one minute immediately after
the failure. As a result, the responsiveness of mirrored logical volumes may affected briefly.
When a physical volume becomes unavailable, applications normally experience a delay while
an I/O request to that physical volume times out. By default, this delay lasts 30 seconds, (although
you can change the duration of the delay by using the pvchange (1M) command).
• In the case of a read operation, LVM selects another mirror and tries again.
• In the case of a write operation, LVM records the error and continues as long as the data has
been successfully written to at least one mirror.
In either case, with Secure Path installed, this initial timeout can last up to one minute. After the
timeout, LVM keeps track of the physical volume status as Unavailable, and future I/O request do
not suffer the delay.
• Do not make any SAN configuration changes to the system during the upgrade or installation of
Secure Path 3.0F SP4. For example, do not add new arrays or LUNs, or delete arrays or LUNs
during upgrade or installation of Secure Path 3.0F SP4.
• Due to constraints imposed by the software distributor (SD) tools, the server’s network must be
configured before installation of Secure Path.
• Stopping spagent using the spinit stop command, and then starting spagent using the
spinit start command results in stderr messages. To prevent these messages from printing,
start spagent in a new session and then exit that session.
• Do not use the HP System Administration Manager (SAM) to create or extend volume groups.
Creating and extending volume groups must be done using HP-UX commands. When SAM scans
for hardware, any HSV1xx LUNs created after the first LUN are not parsed correctly by SAM and
cannot be selected to create a volume group. Use HP-UX commands to create or extend volume
groups, and then use SAM to create and manage logical volumes.
8