HP StorageWorks Fabric OS 5.3.0d Release Notes (AA-RWEYH-TE, December 2007)

Closed defec t su mmary
Solution
With large zones
et (over 1200 zones) API library crashes as the zone
library does memcpy that doesn’t have terminating zero in the buffer.
Fixed per Fabric OS 5.3.0
Change made in 5.2.0 to limit the number of FDISCs per unit of time,
caused timeouts of NPIV logins in some BladeServer 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 prev i ousl y 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
full updat
e from the active CP, resulting in standby CP going into
continuou
srestartcycle.
Fixed per Fabric OS 5.3.0
WhenMSrequestissuedwithWWNthatdidn’texistinthefabric,
the MS Daemon panicked.
Fixed per Fabric OS 5.3.0
The2/128wasforwardingPLOGIframesreceivedwithDIDas
broadcast format which was causing issues with other devices in
the fabric.
Fixed in Fabric OS 5.3.0. No longer
forwardsthesetypeofframes.
For platf
orms running 5.2.0 a nd above with domain, port zoning,
thereisasmallwindowduringwhichifadevicesendsitPLOGI
very fas
t, and before the nameserver information has been fully
propag
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 different edge fabrics with same
node W
WN. Applies to 4 /256 with FCR-18i Blad e, and 400 MP
Rout
er. Routers may not forward the Nameserver request to proper
doma
in, resulting in request timeout & retries every 2 seconds.
Fixe
d per Fabric OS 5.3.0
In a FICON environment a Switch panic (in the Management Server
daemon) could be seen if the switch receives one of three FICON
specific frames (FICON GCAP, RLIR, RNID) and the fabric goes
"unstable" (fabric being rebuilt such as when one of the switches in
the fabric is powered off) before a response is sent.
Fixed per Fabric OS 5.3.0
Traffic can’t be routed into backbone fabric from EX_Port on 400 MP
RouterwithdomainID7or12andfromFR4-18iBladein4/256
with various domain ID’s.
Fixed per Fabric OS 5.3.0
Rapidly issuing repeated supportsave commands can cause
s
witch panic due to out of memor y condition.
Fixed per Fabric OS 5.3.0
Wheninteropmodesetto1,“DisableNodeNameZoneChecking”
parameteralsochangesfrom0to1,butreturnsto0afterswitch
reboot .
Fixed per Fabric OS 5.3.0
Due to race condition in RNID command from FICON channels,
FICON CUP daemon crashes and switch panics after switch comes
up then it starts processing the RNID command. P roblem affects
FICON environment for Fabric OS 5.1 and later.
Fixed per Fabric OS 5.3.0
Web Tools error message provided when fmsmode setting fails is
not clear.
Fixed per Fabric OS 5.3.0
HP StorageWorks Fabric OS 5.3.0d release notes
19