HP StorageWorks 2/16V HP StorageWorks Fabric OS 5.3.0b Release Notes (AA-RWEYF - Page 17

Fabric OS 5.3.0 fixes, Table 3 Fabric OS 5.3.0 closed defects

Page 17 highlights

Fabric OS 5.3.0 fixes Table 3 lists defects closed in the Fabric OS 5.3.0 firmware release. Table 3 Fabric OS 5.3.0 closed defects Closed defect summary Solution 4/256 Director running FICON with fsmode enabled & DLS on and port based route policy panics after upgrade from Fabric OS 5.0.x to Fixed per Fabric OS 5.3.0 5.1.x or 5.2.0. Kernel Ops error when counter is overrun during stress to fail test. Fixed per Fabric OS 5.3.0 Exception error on 4/256 can occur when performing port mirroring causing reboot. Fixed per Fabric OS 5.3.0 Tstimezone command doesn't show correct time and date if configdownload interface is used to update timezone. Fixed per Fabric OS 5.3.0 After executing trunk disable/enable on all edge switches in large scalability fabric, a 2/128 E_port became stuck in Loopback mode. Fixed per Fabric OS 5.3.0 Admin Domains enforcement on SID/DID not performed. Portmirror allowed addition of mirror port in Admin Domain3 when SID and DID were not port members. Fixed per Fabric OS 5.3.0 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 GE0 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 PLOGI 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 with FCR switches, switch may panic causing continuous Fixed per Fabric OS 5.3.0 rebooting. When more than the supported number of intelligent blades (FR4-18i, FC4-16IP, etc) configured in 4/256, powering up the 4th and 5th Fixed per Fabric OS 5.3.0 blades at the same time results in a failover. 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 occasionally 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 FCR 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 Fixed per Fabric OS 5.3.0 ports come online. After an all switches disable on 4/256 with FC4-48 port blades, standby CP asserted and rebooted. Fixed per Fabric OS 5.3.0 HAfailover during FCIP 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 Fixed per Fabric OS 5.3.0 should it). HP StorageWorks Fabric OS 5.3.0b release notes 17

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25

Fabric OS 5.3.0
xes
Table 3
lists defects closed in the Fabric OS 5.3.0
rmware release.
Table 3 Fabric OS 5.3.0 closed defects
Closed defect summary
Solution
4/256 Director running FICON with fsmode enabled & DLS on and
port based route policy panics after upgrade from Fabric OS 5.0.x to
5.1.x or 5.2.0.
Fixed per Fabric OS 5.3.0
Kernel Ops error when counter is overrun during stress to fail test.
Fixed per Fabric OS 5.3.0
Exception error on 4/256 can occur when performing port mirroring
causing reboot.
Fixed per Fabric OS 5.3.0
Tstimezone
command doesn’t show correct time and date if
configdownload
interface is used to update timezone.
Fixed per Fabric OS 5.3.0
After executing trunk disable/enable on all edge switches in large
scalability fabric, a 2/128 E_port became stuck in Loopback mode.
Fixed per Fabric OS 5.3.0
Admin Domains enforcement on SID/DID not performed.
Portmirror
allowed addition of mirror port in Admin Domain3
when SID and DID were not port members.
Fixed per Fabric OS 5.3.0
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 GE0 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 PLOGI 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 with 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) con
gured in 4/256, powering up the 4th and 5th
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
rmware
download and
slotpoweron
followed by
slotpoweroff
.
Fixed per Fabric OS 5.3.0
Tape backup job failures occasionally 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 FCR 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 all switches disable on 4/256 with FC4-48 port blades,
standby CP asserted and rebooted.
Fixed per Fabric OS 5.3.0
HAfailover
during FCIP 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 con
gure 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
HP StorageWorks Fabric OS 5.3.0b release notes
17