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

Closed defect summary
Solution
New active CP got Oops and reboot during initialization after
hafailover command issued.
Fixed per Fabric OS 5.3.0
After CP reboot, VE tunnel doesn’t come up due to G E0 port on
FR4-18i stuck in No_Sync state when using copper SFP’s.
Fixed per Fabric OS 5.3.0
Switch doesn’t generate RSCN following zoning changes using
cfgEnable in interop mode, resulting in no PLOG I from hosts, and
no target discovery.
Fixed per Fabric OS 5.3.0
When more than
the supported number of Ex_Ports attached to same
edge fabric wi
th FCR switches, switch may panic causing continuous
rebooting.
Fixed per Fabric OS 5.3.0
When more than the supported number of intelligent blades (FR4-18i,
FC4-16IP, etc) configuredin4/256,poweringupthe4thand5th
blades at the same time results in a failover.
Fixed per Fabric OS 5.3.0
In rare occurrence, FR4-18i Blade could become faulty after firmware
download and slotpoweron followed by slotpoweroff .
Fixed per Fabric OS 5.3.0
Tape backup
job failures o ccasionally observed in congested IO
conditions
due to tape pipelining not properly handling target
recovery.
Fixed per Fabric OS 5.3.0
After changing FID & enabling F CR switch, all connected/active
ports remain disabled.
Fixed per Fabric OS 5.3.0
If active CP fails over after FC4-16ip port Blade runs slotpower on,
all the FC4-16ip iSCSI ports can get stuck at “No_Sync” while FC
ports come online.
Fixed per Fabric OS 5.3.0
After an a
ll switches disable on 4/256 with FC4-48 port blades,
standby C
P asserted and rebooted.
Fixed per Fabric OS 5.3.0
HAfailover during FC IP IO through IPSec enabled tunnel
sometimes causes VE port to go down, then come back up.
Fixed per Fabric OS 5.3.0
User was able to configure isns client via isnsccfg to communicate
with isns server through a port on FR4-18i, but this will not work (nor
should it).
Fixed per Fabric OS 5.3.0
FICON tr
aps sent with wrong “Enterprise” value resulting in trap
being p
rocessed as a swFault.
Fixed per Fabric OS 5.3.0
In Web Tools customized port detail report, the report 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 r
ebooting the active CP from Root, the warning text that is
displayed when rebooting from Admin to warn that rebooting the
acti
ve CP will disrupt traffic, is not displayed.
Fixed per Fabric OS 5.3.0
In edge to backbone fabric configuration with target in backbone
fabric and host in edge fabric, 400 MP 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.
Fixed per Fabric OS 5.3.0
Us
ing API to access default zoning information could c ause switch
to
panic due to invalid pointer.
Fixed per Fabric OS 5.3.0
18