HP-UX iSCSI Software Initiator B.11.31.02 Release Notes (September 2009)

New features in Revision B.11.31.02 of the HP-UX iSCSI Software Initiator include:
• Resolved the issue that affected the discovery and configuration of iSCSI devices by VxVM
(QXCR1000932601).
In the previous release, the init script was not invoked properly.
Limitations
The following information is for revision B.11.31.02 of the HP-UX iSCSI Software Initiator.
• iSCSI usage of IPSec is supported on HP-UX, however, the HP-UX iSCSI Software Initiator
has not been tested with IPSec due to the lack of iSCSI targets that support IPSec.
Support of IPSec with the HP-UX iSCSI Software Initiator is dependent on the availability
of iSCSI targets that support IPSec and target vendor testing of the HP-UX iSCSI Software
Initiator with those targets.
• The HP-UX iSCSI Software Initiator does not support IPv6 addresses.
• The HP-UX iSCSI Software Initiator does not support the definition of the boot, root, primary
swap, dump, or var volumes on iSCSI physical volumes.
Known Problems and Workarounds
• Problem: Event Monitoring Services (EMS) and Support Tool Manager (STM) do not display
events generated by HP-UX iSCSI Software Initiator.
Workaround: None. This issue may be corrected in a subsequent release.
• Problem: iSCSI Physical Volumes (PVs) are network dependent devices, which are not
accessible until the network subsystem is initialized. Attempts during system startup (prior
to network initialization) to activate Volume Groups or mount file systems on an iSCSI
device generate failure error messages.
Workaround: Ignore the error messages. The failure does not affect normal system or iSCSI
device operations.
• Problem: Deleting an operational session using rmsf might cause a hang of up to four
minutes, if rmsf is issued immediately after the physical connection to the target is lost. To
avoid TCP port reuse issues, set the tcp_ip_abort_interval value to at least four
minutes.
Workaround: Wait up to four minutes for rmsf to complete.
• Problem: Deleting an operational session using rmsf might hang when the deletion is
performed within four minutes after physical connection to target is lost.
Workaround: Kill and restart the two iswd daemon processes.
CAUTION: This action tears down the I-T nexi of all of the iSCSI targets. Restarting the
iswd daemon quickly restores the connections promptly and avoid any undesirable side
effects.
• Problem: When the physical connection to target is lost, the health property of iSCSI targets
changes to OFFLINE after the tcp_ip_abort_interval timeout value expires. You can
see this issue only if there is no I/O traffic on the I-T nexus.
Workaround: None. The value of the health property does not affect normal system or iSCSI
device operations.
6 HP-UX iSCSI Software Initiator Release Notes