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

FICON traps sent with wrong “Enterprise” value resulting in trap
being processed as a swFault.
Fixed per Fabric OS 5.3.0
In Web Tools customized port detail report, the repor t will be
generated for all ports even if the user gives a particular port range
as a filter.
Fixed per Fabric OS 5.3.0
On 2Gb/s platforms, switch panic can occur if unstable or faulty port
generates excessive number of interrupts.
Fixed per Fabric OS 5.3.0
When rebooting the active CP from Root, the warning text that is
displayed when rebooting from Admin to warn that rebooting the
active CP will disrupt traffic, is not displayed.
Fixed per Fabric OS 5.3.0
In edge to bac
kbone fabric configuration with target in backbone
fabric and host in edge fabric, 400 MPR router neither accepted
or aborted a PLOGI. Only happens when there are devices in the
fabric for which the link is taken online/offline quickly within a short
period of time.
Fixed per Fabric OS 5.3.0
4/64 SAN switch with 5.1.0d experienced HW/SW interlock that
became stuck requiring port disable/enable to clear the condition.
This issue was not reproducible.
Change in Fabric OS 5.3.0 made
to generate RASlog CDR-1004
informing the user to reset their por t
should this happen again.
Using API to access default zoning information could cause switch
to panic due to inv alid pointer.
Fixed per Fabric OS 5.3.0
With lar
ge zoneset (over 1200 zones) API library crashes as the zone
library does memcpy that doesn’t have terminating zero in the buffer.
Fixed pe
r Fabric OS 5.3.0
Change made i n 5.2.0 to limit the number of FDISCs per unit of time,
caused timeouts of NPIV logins in some BladeSer ver configurations
with VC-FC.
Fixed per Fabric OS 5.3.0.
When FOS version prior to 5.2.0 is upgraded to a later version and
the fabric.ops.mode.pidFormat value was previously set to zero, the
switch will continually reboot.
Fixed per Fabric OS 5.3.0
In extremely rare conditions when a particular timing window is hit
at the same time an internal end to end monitor wraps its counter,
the standby CP can get stuck in a reboot loop. The condition is
that
due to a race condition, a partial HA update arrives before a
ful
l update from the active CP, resulting in standby CP going into
con
tinuous restart cycle.
Fixed per Fabric OS 5.3.0
When MS request issued with WWN that didn’t exist in the fabric,
the MS Daemon panicked.
Fixed per Fabric OS 5.3.0
The 2/128 was forwarding PLOGI frames received with DID as
broadcast format which was causing issues with other devices in
the fabric.
Fixed in Fabric OS 5.3.0. No longer
forwards these type of frames.
Fo
r platforms running 5.2.0 and above with domain, port zoning,
there is a small window during which if a device sends it PLOGI
v
ery fast, and before the nameserver information has been fully
p
ropa g ated, the PLOGI may be dropped.
Fixed per Fabric OS 5.3.0
CLI systemverification command incorrectly reports false
positive failure on FC4-16IP blade. This diagnostic command is not
typically run by a customer.
Fixed per Fabric OS 5.3.0
“Stats” menu option doesn’t work when executing minicycle
command.
Fixed per Fabric OS 5.3.0
Process login drop due to devices in d ifferent edge fabrics with same
node WWN. Applies to 4/256 with FCR-18i blade, and 400 MP
router. Routers may not forward the Nameserver request to proper
domain, resulting in request timeout & retries every 2 seconds.
Fixed per Fabric OS 5.3.0
18