HP StorageWorks Fabric OS 5.2.1b Release Notes (AA-RWEYC-TE, June 2007)

SNMP configuration set via agtcfgset command can sometimes be
initialized back to default when upgrading from one firmware version
to another.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
E-port offline t
ransition caused fabric reconfiguration after firmware
download on 2/32 switch in 2560 port fabric. Encountered under
specifictestconditions.
Unlikely user scenario
Fixed per Fabric OS 5.2.1
Running continuous portshow command loop hangs telnet session. Fixed per Fabric OS 5.2.1.
Switch panic or CP failover when a kernel process is spawned by
non-root user.
Fixed per Fabric OS 5.2.1.
Switch doesn
’t generate RSCN to hosts after cfgEnable when in
interop mode
, so hosts do not PLOGI or discov er targets.
Fixed per Fabric OS 5.2.1.
After manual change of switch domain ID in AD, then changing it
back, CAM entries for D,P zoned device may not be properly installed.
Fixed per Fabric OS 5.2.1.
In large fabric (30+ embedded switches), Web Tools GUI hangs on
launch so no Web Tools access possible.
Fixed per Fabric OS 5.2.1.
ASIC failure can cause performance degradation on 4/256, or switch
fault on oth
er 4Gb switches, undetected by porterrshow,even
though ISL
s on remote switch show large number of frame errors.
Fixed per Fabric OS 5.2.1.
Error message displayed a fter upgrading firmware on 4/256, and
FR4-18i router blade in 4/256 on remote side of FCIP tunnel is faulted.
Fixed per Fabric OS 5.2.1.
When running script to repeatedly add/remove LSAN zones in
backbone with multiple routers (MPR 400 or 4/256 with FR4-18i)
zoning config does not propagate to b oth routers.
Fixed per Fabric OS 5.2.1.
After run
ning stress-to-fail routing test for 2 hrs, FR4-18i router blade
ina4/256directorfaultedwitherrorFaulty 21 and FC4-32 port
blade in different 4/256 director faulted with error Faulty 3.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
One of two FR4-18i router blades in 4/25 6 went faulty after
using firmwaredownload -sf and reboot -f on both CPs
simultaneously.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
If all router event messages turned on, may see FCR-1031 event
Device Off message continuously on FR4-18i router blad e, even
though devices are intact.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
Portdisabled and portenabled 2Gb JBOD port on MPR 400 router,
which was connected to FR4-18i router blade & FR4-18i, went faulty.
Unlikely user scenario
Fixed per Fabric OS 5.2.1.
When using tap e pipelining feature, backing up data whose size is
larger than available space on tape, backup application could get
stuck in running state. Seen with 1Gb tape library, but not 2Gb.
Fixed per Fabric OS 5.2.1.
Blade fault on 2/128, 2/64, 2/32, 2/16, 2/16v, with data dumped
in /core file/fdet directory.
Fixed per Fabric OS 5.2.1.
Switch panic can occur if invalid ipaddress makes it into
syslog.conf file. Not likely to happen in production as all
user/admin interface commands validate ipaddress before adding
it to
syslog.conf file.
Fixe
dperFabricOS5.2.1.
CUP port fails to come online on MPR 400 in FICON environment
due to F-Rej to PLOGI to CUP port.
Fixed per Fabric OS 5.2.1.
Switch panics with FICON daemon in FICON environment with zero
byte payload for Chain Commands with Command Response Request
enabled.
Fixed per Fabric OS 5.2.1.
16