HP StorageWorks 4/16 HP StorageWorks Fabric OS 6.0.1a release notes (AA-RWFMA- - Page 15

Only World Wide Name WWN zone including normal zone and FC Fast

Page 15 highlights

Topic FC fast Write iSCSI Broadcast zones Description • Only World Wide Name (WWN) zone (including normal zone and FC Fast Write zone) is supported on FC Fast Write enabled port. • Only single device loop port is supported. • N_Port ID Virtualization (NPIV) (example Access Gateway) port is not supported. • FCR backbone devices are not supported. That is FC Fast Write should not be enabled on backbone devices. • FCR edge to edge support is limited by all the target devices on given edge fabric that host talks to should be connected to a 400 Multi-protocol Router or FR4-18i in FC Fast Write mode. FC Fast Write should not be enabled on ports when testing the remote mirror application. • When a very high volume of traffic is being sent by host, FC Fast Write IOs may time out and frame may be dropped. • Within the context of FC Fast Write, L_Port is not supported. • Enterprise storage array targets may not show up consistently in the disk management window of an iSCSI initiator when the same LUNs are mapped to two different virtual targets (VTs). When the initiator logs in to the VTs, the targets keep disappearing from the disk management window. If the session to one of the VTs is disconnected, the remaining VT appears and stabilizes in the disk management window. • Under certain conditions, hosts on an IP network may not be able to issue a ping command to iSCSI gateway ports in another subnet. You can work around this problem by issuing a ping command from the iSCSI gateway port. The hosts will then be able to successfully issue ping commands to the iSCSI gateway port. • An IP network disconnection lasting five seconds or more may cause COPA failure on the disconnected PC, which in turn may cause a loss of connection to an enterprise storage array. • If traffic is run from hosts to certain targets with severe impairment conditions in the IP network for hours at a time, throughput to the targets will drop, and may take up to 10 minutes to recover after the impairment condition is removed. Note that this problem is highly intermittent, and is unlikely to be seen in a customer environment. We believe that this issue is the result of host/target interaction, and is not the result of action on the iSCSI gateway. • A Microsoft windows PC host was unable to discover enterprise storage array LUNs. The Microsoft iSCSI initiator is able to discover targets if the software is uninstalled and reinstalled without the MPIO option. In Fabric OS 5.3.x, a zone with the name "broadcast" (case sensitive) is a special zone for setting up recipients of broadcast packets. In Fabric OS versions earlier than 5.3.x, a zone named "broadcast" does not have special significance. Therefore, you must make sure that if a broadcast zone is configured, then the active and standby CPs should be running the same Fabric OS version. Otherwise an HA failover might change the zone configuration. Refer to the HP StorageWorks Fabric OS 6.x administrator guide for additional information about broadcast zones. HP StorageWorks Fabric OS 6.0.1a release notes 15

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23

Topic
Description
FC fast Write
Only World Wide Name (WWN) zone (including normal zone and FC Fast
Write zone) is supported on FC Fast Write enabled port.
Only single device loop port is supported.
N_Port ID Virtualization (NPIV) (example Access Gateway) port is not
supported.
FCR backbone devices are not supported. That is FC Fast Write should not
be enabled on backbone devices.
FCR edge to edge support is limited by all the target devices on given edge
fabric that host talks to should be connected to a 400 Multi-protocol Router
or FR4-18i in FC Fast Write mode. FC Fast Write should not be enabled on
ports when testing the remote mirror application.
When a very high volume of traf
c is being sent by host, FC Fast Write IOs
may time out and frame may be dropped.
Within the context of FC Fast Write, L_Port is not supported.
iSCSI
Enterprise storage array targets may not show up consistently in the disk
management window of an iSCSI initiator when the same LUNs are mapped
to two different virtual targets (VTs). When the initiator logs in to the VTs, the
targets keep disappearing from the disk management window. If the session
to one of the VTs is disconnected, the remaining VT appears and stabilizes in
the disk management window.
Under certain conditions, hosts on an IP network may not be able to issue a
ping
command to iSCSI gateway ports in another subnet. You can work
around this problem by issuing a
ping
command from the iSCSI gateway
port. The hosts will then be able to successfully issue
ping
commands to the
iSCSI gateway port.
An IP network disconnection lasting
ve seconds or more may cause COPA
failure on the disconnected PC, which in turn may cause a loss of connection
to an enterprise storage array.
If traf
c is run from hosts to certain targets with severe impairment conditions
in the IP network for hours at a time, throughput to the targets will drop,
and may take up to 10 minutes to recover after the impairment condition is
removed. Note that this problem is highly intermittent, and is unlikely to be
seen in a customer environment. We believe that this issue is the result of
host/target interaction, and is not the result of action on the iSCSI gateway.
A Microsoft windows PC host was unable to discover enterprise storage array
LUNs. The Microsoft iSCSI initiator is able to discover targets if the software is
uninstalled and reinstalled without the MPIO option.
Broadcast zones
In Fabric OS 5.3.x, a zone with the name “broadcast” (case sensitive) is a special
zone for setting up recipients of broadcast packets. In Fabric OS versions earlier
than 5.3.x, a zone named “broadcast” does not have special signi
cance.
Therefore, you must make sure that if a broadcast zone is con
gured, then the
active and standby CPs should be running the same Fabric OS version. Otherwise
an HA failover might change the zone con
guration.
Refer to the
HP StorageWorks Fabric OS 6.x administrator guide
for additional
information about broadcast zones.
HP StorageWorks Fabric OS 6.0.1a release notes
15