HP StorageWorks Fabric OS 5.2.0b Release Notes (AA-RWEYB-TE, February 2007)

Closed defect summary
Solution
ISCSI: unable to disable iSNS after peering
with iSNS server .
If not upgrading to Fabric OS 5.2.0b,
the workaround is t
o issue the following
commands.
1. Display the outs
tanding transaction:
iscsicfg --show
transaction
2. Abort transact
ion that is displayed in
Step 1 above: is
csicfg --abort
transaction -
x
ISCSI: host loses target with any IO when
port is set to Error Recovery Level 2 (ERL2),
digests enabled.
If not upgrading to Fabric OS 5.2.0b, the
workaround is to reconnect to targets from
initiators.
Using the tape pipelining feature, a ccessing
data spanning on a 1Gb tape library
causes the backup application to remain
stuck in running state.
Fixed per Fabric OS 5.2.0b
CUP Port fails to come online on a SilkWorm
7500 due to F-Rej to PLOGI to the CUP Port
Fixed per F
abric OS 5.2 .0b
When using the SMIAgent to connect to a
switch in a larger fabric containing more
than 383 FDMI devices, the LoginAsUser
fails and switch panics.
Fixed per Fabric OS 5.2.0b
Linux 2.6 iSCSI initiator is not able to
discover a third-party storage array.
Fixed per Fabric OS 5.2.0b
iSCSI: Cannot fail back after performing
a Path Failover with certain third-party
multi-pathing software. It works with iSCSI
GE ports, but not on FC.
If not upgrading to Fabric OS 5.2.0b, the
workaround is to log in again to the target
when it comes back online.
Registration to a storage array by a specific
third party storage management agent fails
with CRC error on the FC side.
Fixed per Fabric OS 5.2.0b
Third-party storage array adapter
disengages when running I/O between
iSCSI host and certain third-part y storage
array via FC4-16IP (iSCSI to FC bridge) with
iSCSI Header and Data Digest enabled.
If not upgrading to Fabric OS 5.2.0b, the
workaround is to disable header/data
digest.
i
SCSI traffic through an FC4-16IP blade has
l
ow throughput between iSCSI initiator and
c
ertain third-party storage array.
I
f not upgrading to Fabric OS 5.2.0b, the
w
orkaround is to disable immediate data.
If the domain ID of a switch changes,
iSCSI initiators may not be able to access
targets due to the Name Server database
containing stale iSCSI host information.
If not upgrading to Fabric OS 5.2.0b, the
workaround is to avoid domain ID changes.
20