Technical data

Table 4 lists the configuration limits for Secure Path 3.0F SP3 for Active-Passive disk arrays.
Table 4 Configuration limits for Secure Path 3.0F SP3 for Ac tive-Passive disk a rrays
Parameter
Minimum
Maximum
qualified
Maximum
supported
Adapter support
1
8
Platform limit
Storage arrays per host
1
8128
LUNs per storage array per host
1
256
Array limit
Avoiding problem situations
The section describes problems that may arise during Secure Path operation and how to avoid them:
• General problems
• Problem with setboot command
•Reconfiguring dump devices in the event of path failover
• Installing Secure Path in a Virtual Partitions environment
• LUN collision
IMPORTANT:
ForinformationaboutSecurePathdevicepathrepresentationandusage,see“Secure Path device path
representation and usage”.
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 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 a dding 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 canresultinthefirst 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 tha t 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
whileanI/Orequesttothatphysicalvolumetimesout. Bydefault,thisdelaylasts30seconds,
(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.
HPStorageWorksSecurePath3.0FServicePack3forHP-UX11iv1.0and11iv2.0
7