HP-UX iSCSI Software Initiator B.11.11.03e and B.11.23.03e Release Notes (July 2005)

Chapter
HP-UX iSCSI Software Initiator Release Notes
Known Problems and Workarounds
6
Known Problems and Workarounds
Known Problems and Workarounds for the HP-UX iSCSI Software Initiator
Revision B.11.11.03e
• Problem: Kernel Registry Service states that information will be available prior to I/O initialization.
However, kernel modules that use the Kernel Registry Service to store driver information are not
available until after I/O initialization.
Workaround: Patches PHKL_27321 and PHKL_27096 must be installed to provide early access to the
Kernel Registry Services.
• Problem: ioscan displays the device state as “NO_HW” when nodes that have hardware paths
beginning with 255 are scanned.
Workaround: Install patch PHKL_28209.
• Problem: The shutdown command is blocked when the iSCSI Software Initiator is installed. During
shutdown, /sbin/umountall is unable to determine the status of the file system, because the killall
script has killed the iSCSI Software Initiator daemons needed to access devices.
Workaround: Install patch PHCO_28319. This patch will modify the killall script to prevent it from
killing the iSCSI Software Initiator daemons; “iswd”, “iradd”, and “iscsi_resolvd”.
• Problem: Data page fault seen with transfer of data using iSCSI Software Initiator.
Workaround: Install patch PHNE_26939 to resolve data page fault issue.
• Problem: SAM does not support iSCSI.
Workaround: Install patch PHCO_27374 to provide access to iSCSI volumes from SAM.
• Problem: If SLP is being used by iSCSI, and the SLP daemon (slpd) is terminated, the iSCSI islpd
daemon will be killed.
Workaround: No patch available. If a user starts or restarts the SLP daemon (slpd), the islpd deamon
must be restarted using the command line.
• Problem: Operations (such as ioscan, vgcreate, diskinfo, insf, etc.), that require a device open of an
SPC-2 compliant target are delayed, due to extra retries that delay the device open of the SPC-2
compliant target.
Workaround: Install patch PHKL_30510.
• Problem: If Event Monitoring Services (EMS) and Support Tool Manager (STM) are used for diagnostic
logging and monitoring, some new events generated by the HP-UX iSCSI Software Initiator will not be
processed by the iSCSI EMS Monitor. Also, incorrect event messages will be produced, because the
HP-UX iSCSI Software Initiator and the iSCSI EMS Monitor are out of sync.
Workaround: Install patch PHSS_30888 after installing the HP-UX 11i v1 Hardware Enablement
bundle: HWE0406.
• Problem: LVM Volume Group (VG) activation failure error messages are displayed during system
startup.
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 VGs
that include an iSCSI PV, will generate VG activation failure error messages. The iSCSI Software