HP StorageWorks Fabric OS 5.3.1 release notes (AA-RWEYI-TE, March 2008)

Closed defect summary
Solution
When upgrading 4/256 to Fabric OS 5.2.0b from 5.2.0a, both ISL
trunk connections to an edge switch connected to FC4-16 IP were lost.
Found in test lab and due to “ lab mode” setting, not accessible to
customers.
Fixed in Fabric OS 5.3.0
Counter Address_err counting inappropriate data. Fixed in Fabric OS 5.3.0
When assigning IP ad dress to a GE port with no cable connection,
the FC4-16IP Blade incorrectly reports back to i SCSI initiator that
port is valid.
Fixed in Fabric OS 5.3.0
The 4/8 and 4/16 SAN Switches would display “Fan x is not faulty”
messages on boot up after upgrade to Fabric OS 5.2.0x, even
though fans
were ok.
Fixed in Fabric OS 5.3.0
Disconnecting Rx end of cable on an L_port and leaving the Tx end
unchanged results in unexpected behavior.
Fixed in Fabric OS 5.3.0
Access Gateway should handle an IPv6 address in a GMAL payload
IP address in “ag – show” truncated to 16 characters (size of IPv4
address) d e pending on size of IP address string for edge switch to
which N_Port attached.
Fixed in Fabric OS 5.3.0
Switchdisable and switchenable on switch that directly
connects to storage will cause the storage to see GLIEN reject error
message.
Fixed in Fabric OS 5.3.0
F_Port count is incorrect in agshow on the 4/32 SAN switch.
Fixed in Fabric OS 5.3.0
In CLI, iscsicfg –show/delete ddset –n xxx complains “requested
objectdoesn’texist”eventhoughitdoesexist,duetoDD/DDSETs
received from Microsoft iSNS server being in uppercase.
Fixed in Fabric OS 5.3.0
During
iSCSI 1024 session stress testing, one p ort lost multiple
sessio
ns. Even though switchshow – iscsi showed less than 64
sessions, iSCSI initiator wasn’t able to log in to the target (out of
resources error).
Fixed in Fabric OS 5.3.0
Incorrect GID_FT response from NameServer. NameServer assumes
device’s FC4 type is FCP when GID_FT request is sent to the switch
asking for PIDs of type FCP. PID of the sending device is incorrectly
included in the reply list.
Fixed in Fabric OS 5.3.0
Unable to merge an upgraded switch with a 4/256 with FC4-48
Blade when using domain/port zoning of the upper 32 ports of the
Blade. When creating D,P zoning definition using these upper 32
ports on FC4-48 connected to another switch running 5.1.0, the two
switches correctly segment due to zoning conflict. After upgrading
to 5.2.0, switches remain segmented, but segmentation should be
removed.
Fixed in Fabric OS 5.3.0
24