HP-UX iSCSI Software Initiator (iSCSI-00) B.11.31.03f Release Notes (Edition 1)
4 Known problems and limitations
The following problems are known to exist in version B.11.31.03f:
• Manpage for Address resolution daemon (/opt/iscsi/bin/iscsi_resolvd) is wrongly delivered
as iscsi-resolvd(1M).
Corrective action: To view manpage for Address resolution daemon (/opt/iscsi/bin/
iscsi_resolvd) use following command:
# man iscsi-resolvd
• Consecutive ioscan outputs are different.
Most consecutive ioscan outputs are identical. However, in rare instances, consecutive
ioscan outputs are different.
Corrective action: If a LUN is reported as NO_HW, this is a transient condition which will be
stabilized with another ioscan command. To see the correct status, run ioscan again.
• iSCSI Software Initiator events are not displayed.
Event Monitoring Services (EMS) and Support Tool Manager (STM) do not display events
generated by HP-UX iSCSI Software Initiator.
Corrective action: None. This issue might be corrected in a subsequent release.
• Attempts to activate Volume Groups or mount file systems on an iSCSI device prior to network
initialization cause error messages.
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.
Corrective action: Ignore the error messages. The failure does not affect normal system or
iSCSI device operations.
• Deleting an operational session causes a temporary system hang.
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.
Corrective action: Wait up to four minutes for rmsf to complete.
• Deleting an operational session at certain times might cause a temporary system hang.
Deleting an operational session using rmsf might hang when the deletion is performed within
four minutes after physical connection to target is lost.
Corrective action: Kill and restart the two iswd daemon processes.
CAUTION: This action tears down the I-T nexus of all of the iSCSI targets. Restarting the
iswd daemon quickly restores the connections and avoids any undesirable side effects.
• The health property of an iSCSI target is incorrectly displayed as OFFLINE.
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.
Corrective action: None. The value of the health property does not affect normal system or
iSCSI device operations.
4