HP StorageWorks Fabric OS 5.3.0 Release Notes (AA-RWEYD-TE, July 2007)

Zoning considerations
with FC4–48 blade
B-Series switch es running pre-5.2.0 firmwaredonotacceptzonedatabaseswith
Domain, Port Index, references to ports higher than 255. Zoning in Fabric OS
5.2.0 and later, therefore, do not allow a Domain, Port Index entry for ports
above 255 to be created unless all switches in the fabric are at
Zoning considerations continued...
Fabric OS 5.2 . 0 or later versions. Once such an entry has been put into the zone
database, an attempt to connect a pre-Fabric OS 5.2.0 switch to the fabric results
in that switch being segmented with a Zone Mismatch segmentation reason.
Any zoning that is already in use can continue to be used. However, in Fabrics
containing pre-Fabric OS 5.2.0 switches, if new devices are added on the upper
16 ports (ports 32-47) of the FC4-48 port blade, then WWN zoning has to
be used for those devices. If there is an existing Domain Port Index zone that
connectstoports32–47,HPrecommendsthatyoutransformjustthatzoneto
WWN zoning. This would minimize the likelihood of rebuilding the entire fabric.
Fabrics containing only Fabric OS 5.2.0 and later switches have no zoning
limitation.
Update to B
rocade
4Gb SAN Sw
itch for
HP c-Clas
sBladeSystem
installa
tion instructions,
part num
ber 5697–5678
On page 2, please update the following step:
7. At the command line, type:
c bay x
Where x is the I/O bay where the switch is installed.
to
7. At the command line, type:
connect interconnect x
Where x is the I/O bay where the switch is installed.
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 subn et. You c an work
aroun d 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 fivesecondsormoremaycauseCOPA
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 n etwork for hours at 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.0, a zone with the name “broad cast” (case-sensitive) is a
special zone for setting up recipients of broadcast packets. In Fabric OS
versions earlier than 5.3.0, a zone named “broadcast” does not have special
significance. Therefore, you must ma ke 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 z one configuration.
Refer to the HP Stora geWorks Fabric OS 5.3.0 administrator guide for additional
information about broadcast zones.
Faulty SFPs
External port with a faulty SFP will be disabled, then enabled once good SFP is
inserted. However, port will still show as faulty even though it is hea lthy. To get
the correct "healthy" indication, after enabling the port with the good SFP, remove
and re-insert it and the port will then show as healthy.
16